Fixed scope, fixed price engineering. The studio takes ownership of a defined deliverable end to end. From the SOW through production handoff and a 30 day stabilization window. Two engagement shapes inside one umbrella, both priced before work starts.
Drop a working AI feature into an existing product. Common patterns: RAG over a documentation corpus, agentic workflows for an ops team, evaluation harness on a shipped feature, model migration off a vendor lock.
Greenfield product, platform modernization, or a feature your team has been blocked on for two quarters. Architecture, implementation, deployment, observability. Production ready handoff with documentation and runbooks.
One week paid scoping. Output is a written spec, milestones, acceptance criteria, and a fixed price. If we cannot agree, the engagement ends here cleanly.
Milestones are anchored to working software, not to time spent. Weekly written status. Working demo at each milestone gate.
Acceptance criteria checked in production. Repo, configuration, runbooks, and documentation handed over. 20% holdback released.
Bug fixes within the original scope at no extra cost for 30 days after handoff. After that, support is a separate, optional retainer.
Fixed price puts the studio on the hook for delivery, not hours. Both sides agree the price before work starts, and the holdback at the final milestone keeps the studio honest on the production handoff. Time and materials creates incentive to drag; fixed price creates incentive to ship.
Written change order. Spec gets updated, the price delta and timeline impact are agreed in writing, and work continues. Small adjustments inside the original spec are absorbed; meaningful new scope is priced.
If the studio misses a milestone, a remediation plan is shared inside the milestone week and the timeline shifts at no cost to the client. If the client is the blocker (delayed approvals, missing access, blocking dependencies), the timeline shifts for that side.
Yes. Common path is build engagement followed by a 90 day support retainer or a Fractional CTO retainer for the technical leadership seat. Both are priced separately.
Standard NDA: signed before scoping week. DPA where personal data of EU residents is in scope: signed before the SOW. Both are templates the studio operates from; light redlines are routine, heavy redlines move to the lawyer's track.
The SOW pins the implementation to a model and provider that meet the acceptance criteria. If the model space shifts mid-build and the client wants to migrate, that is a written change order. If the chosen model fails to meet acceptance criteria, the migration is on the studio at no cost.
Send a paragraph about the system, the deadline, and the constraints. The first call is 30 minutes. Within a week of that call we can have a scoping engagement booked.
Start a project →