Embedded AI Product Build
One accountable path from wedge to shipped software.
For a validated product wedge with a named owner: architecture, engineering, evaluation, deployment, and handoff — run as a monthly mandate or a fixed sprint, scoped after a wedge review.
A v1 runs as a fixed-scope sprint or a monthly mandate with a senior product team on it; the review tells you which, and the number, before you decide.
§ 01 — What's included
Everything a shipped v1 needs, nothing billed by the hour.
- One named product wedge with an explicit product owner on your side
- Sequenced milestones with acceptance tests, not a promised headcount
- Production-quality code, integrations, evaluation, and observability sized to the scope
- Human approval boundaries wherever the workflow needs judgment, not just automation
- Documentation and a real handoff — software you can run without us if you choose to
§ 02 — Fit
Where this build fits, and where it doesn’t.
Ready when you have
- A wedge already scored or reviewed — see the Product Wedge Review
- A named product owner with a weekly acceptance window
- Access to the data, systems, and people the build depends on
- A decision-maker who can approve scope changes without a committee
Not the fit
- An open-ended staff-augmentation request billed by the hour
- "Add AI" with no wedge, owner, or acceptance criteria named
- Guaranteed throughput, 24/7 delivery, or parallel-team promises
- A build you want cheap rather than right
Wedge not scoped yet? Email the workflow that hurts or start with the Product Wedge Review.
FAQ
Questions before a build.
Is this a monthly mandate or a fixed sprint?
Either, depending on what the wedge needs. A recurring monthly mandate suits ongoing product work with a moving milestone list; a fixed-scope sprint suits a bounded deployment with a clear finish line. The Product Wedge Review is where that shape gets decided.
Who owns the code and the data?
Ownership, data access, reuse rights, and any pre-existing components are named explicitly in the signed scope before work begins. The applicable agreement — not this page — controls those rights.
How much of the team is agentic vs. human?
Senior engineering judgment owns architecture, review, and every ship decision — nothing goes out unreviewed. Agentic build loops handle the around-the-clock drafting: code, tests, docs, and variants, inside logged guardrails.
What does 'evaluated' actually mean here?
Acceptance tests defined before the build starts, a value ledger that shows whether v1 is earning its keep, and human approval gates wherever a wrong output would be expensive. Built is not the same claim as deployed, and deployed is not the same claim as adopted — we track the difference.
Next step
Bring the validated wedge.
Architecture, engineering, evaluation, deployment, and handoff, scoped around the wedge and the owner you already have.