Our pricing

Two principles run our proposals. Clear in writing. Named team.

The AI System Plan

The plan is the no-question filter for whether a Sprint makes sense. We read the workflow and write back honestly before anyone talks about a build.

The AI System Build

The AI System Build is defined before kickoff. The workflow, owner, review loop, and handoff path are named in the proposal. New requests go into a follow-up build, not a retainer.

That is why this chapter does not publish a menu of package prices. The useful question is not which tier sounds affordable. The useful question is whether the repeated work, source material, tool access, review owner, and business result are clear enough to price as one fixed build.

The proposal includes:

• The named workflow and why it matters.
• The named outcome and how we will review it.
• The named team (CS roles + client owner).
• The named ship date.
• The defined build terms.

When the metric does not move

If the review week shows the system is not improving the named business result, we run a short recovery pass. If recovery does not converge, we say so plainly and document what we learned instead of dragging the engagement out.

Why not hourly

Hourly billing penalizes speed. Our engagements run six weeks because that is the right length for the work, not because filling six weeks of timesheets pays the rent. Fixed pricing aligns us with the client on the outcome.

Why not retainer

A retainer is a contract to keep showing up. The Sprint is a contract to ship a thing. If the client wants ongoing work after the Sprint ends, we propose a second Sprint with its own named workflow, outcome, and price. We have never sold an open-ended retainer.

What we will not price

• Discovery calls. The plan is the discovery.
• Strategy decks divorced from a Sprint.
• Ongoing AI consulting beyond a named deliverable.
• Anything that does not name a metric we are moving.