Reviews · Builds · Advisory

One-week reviews, then engineering when the findings justify it — described by shape, not a rate card.

One-week reviews, a two-week prompt engagement, then engineering, advisory, and retained leadership. Fees are quoted per engagement. If your MSP introduced us, they stay in the work.

MSP partner? Send the individual offer pages, not this catalog, when a client is in the thread. This page is for you: what exists, how long it takes, what comes back in writing. Partner kit →

Review first, unless you already know the build.

Most work starts with a one-week review so you have a document, not a workshop. Skip it when the workflow is already named.

start here

Productized AI Review

One week. Opportunity or Compliance & Privacy. Written plan.

when a prompt is the bottleneck

Prompt Optimizer

Two-week fixed scope. Eval layer around a production LLM, then a measurably better prompt.

when you need it shipped

Engineering, Advisory & Retained

Scoped builds, decision support, and ongoing ownership — quoted per engagement.

see the three lanes →

Two one-week reviews. Same shape, different lens.

Same shape: 30-minute discovery, one-week analysis, 30-minute readout, written deliverable.

productivity 1 week

AI Opportunity Review

Where the team is losing hours to work AI can absorb — ranked, written, no vendor pitch.

  • Workflow drag, tool stack, current AI usage
  • Prioritized actions with hour-savings targets
  • Full sample report — the actual document shape

Pick the lane that matches the problem.

For work past a review — or when you already know what needs to be built. Every lane is fixed-scope and quoted per engagement. Not billed hourly.

◆ /engineering

Engineering

Fixed scope
builds & sprint embeds

Design, build, and ship a specific AI product, internal tool, or agentic workflow — or embed a senior engineer into the team for a focused sprint. Best when the workflow is already named.

  • Scoped Production Build — end-to-end design and implementation in their environment, deployed, with code the operating team can own.
  • Sprint Embed — a senior engineer joins for a focused 2–4 week sprint to unblock delivery, accelerate a roadmap, or rescue a workstream already in motion.
Scope a build
◆ /advisory

Advisory

Working session
architecture, diligence & operating model

Before the wrong bet: a focused technical session, diligence ahead of a vendor or deal, or help defining how AI should operate across the organization. Best when a shallow recommendation would be expensive.

  • Technical Advisory — stack, constraints, vendor choices, and delivery path. A technical recommendation, not an abstract brainstorm.
  • AI Due Diligence — system quality, data governance, infrastructure maturity, and delivery risk for acquisitions, investments, or high-stakes vendor selection.
  • AI Operating Model — how teams, workflows, governance, and rollout sequencing should work when AI becomes an operating capability.
Scope advisory
◆ /retained

Retained

Ongoing
fractional leadership & post-deployment ops

When the work needs ongoing senior ownership — part-time leadership over AI priorities and architecture, or operational oversight once systems are live. Best for teams already deploying who don't want a full-time hire.

  • Fractional AI Leadership — priorities, architecture direction, vendor decisions, and executive-level technical judgment.
  • Post-Deployment AI Ops — monitoring, drift, incident response, and performance oversight after the system has shipped.
Talk retained work

FAQ

What people usually ask before starting an engagement.

How do engagements start?

A 30-minute call. From there we either run a one-week review or scope Engineering, Advisory, or Retained before anything is signed. If your MSP introduced us, they can stay on the thread.

Why isn't there a price on this page?

Fees are quoted per engagement so they match the work, not a published menu — fixed fee, not hourly. If your MSP introduced us, they'll have the number. If you found us directly, we quote after the 30-minute call.

What's the difference between a review and advisory?

A review is a one-week, fixed-scope engagement that ends in a written plan whether or not anyone hires us further. Advisory is a deeper working relationship: we sit with the team on live decisions like architecture, vendor selection, or governance, rather than handing over a single document.

Do you work with existing teams?

Yes. Sprint Embed and Fractional AI Leadership are built to slot in alongside existing engineers. Scoped Production Build always ends in handoff — code the operating team can run, not a black box that depends on us.

Not sure which lane fits?

Book the 30-minute call. We'll tell you quickly which shape fits — or whether to start with a review so there's a written map before anything larger.

Know which lane you're in? Let's talk.

Bring the situation. We'll tell you the engagement shape. If your MSP introduced us, they stay in the work.