Six ways I get hired,
one philosophy underneath.

Where to go next, in what order, and why. Market prioritization, content tiering, ROI framing, and the org changes required to make any of it stick.

• —Market & language roadmap
• —Content tier model
• —Cost & ROI projections

TMS selection or escape, repo-level integrations, string lifecycle design, and CI hooks. Pragmatic, version-controlled, and reviewable.

• —Workflow blueprint
• —Tooling evaluation
• —Integration spec

Designing pipelines that use LLMs and agents for translation, review, terminology, and QA — with the evaluation loops that make the output trustworthy.

• —Pipeline architecture
• —Eval & guardrail design
• —Cost & quality benchmarks

Style guides, glossaries, LQA scorecards, and review processes your team will actually use. Boring on purpose.

• —Style guide & glossary
• —LQA framework
• —Review playbook

Hiring, sourcing, RFP support, and SOW design — whether you're building an internal team, working with LSPs, or both.

• —RFP package
• —SOW templates
• —Onboarding plan

Embedded for a quarter or two to stand up the program, hire a successor, and hand it over cleanly.

• —Hands-on program ownership
• —Hire & handover
• —Documentation