How a project runs

Three steps, each ending in documents you keep, whether or not the next step happens. You talk to the engineer writing the code, every week.

Who you talk toThe senior engineer on it
How oftenA demo and an update, weekly
Where the code livesYour repository

Book a technical consult See the three steps

Weekly update, week 6 of 12

On track: search is live in staging

Shipped: search by meaning on your Postgres, behind a feature switch.

Eval run 31 scored 93.4% accuracy against a 90% target. Cost per answer is over target and is next week's first fix.

Decision needed from you: which team gets staging access on Monday.

Next week: ticket summaries, then the cost fix.

Three steps

You can stop after any of them and keep everything it produced.

Prove it in a 2-week sprint

A working prototype on your data, measured against an eval set you agree. The sprint answers one question: should this go to production?

Length2 weeks
You receivePrototype, eval set, go/no-go report
ThenPlan the build, or stop

The PoC Sprint in detail

sprint/contracts-qazshweek-2

~/sprint/contracts-qa$make eval

4 of 4 files

evals/accuracy.py240 q92.1%

evals/citations.py240 q96.7%

evals/cost.py240 q$0.012

evals/latency.pyp953.1s

Targets met4(of 6)

Reportgo-no-go.mdwritten

Donein 6m 12s

~/sprint/contracts-qa$

Plan the product build

Discovery & Architecture: we write down what gets built, how it fits the systems you run, and what it costs to build and to run.

Length1 to 2 weeks
You receiveSpec, architecture, estimate
ThenA fixed-scope build, or you take the plan elsewhere

Discovery documents

2 of 3

Spec, agreed with you
Architecture document
Estimate for the build

Ship the product, hand it over

A Product Build of 8 to 16 weeks, or Embedded Engineering by the month. The code lives in your repository from the first commit.

Length8 to 16 weeks, or monthly
You receiveThe product, its docs, the eval set
ThenYour team runs it, or we stay on

Handover notes mergednowdocs/handover.md, in your repository
v1.0 deployed to production2hOn your own cloud account
Admin rights moved1dYour team owns the repository

Every week

The same rhythm in every step, so you always know what shipped and what is open.

Monday
Plan the week
A short call to agree what ships this week and what we need from you.
Every day
Notes in your channel
Progress and blockers in your Slack or Teams, written, so nobody waits for a meeting.
Thursday
Demo
Working software on your data, not slides. You try it before Friday.
Friday
Written update
What shipped, the latest eval numbers, what is open, and the decisions we need from you.

Two ways to work together

Fixed scope when the work is clear, monthly when you need an engineer in your team.

Fixed scopeSprint, Discovery, Build
MonthlyEmbedded Engineering
PricesPublished, agreed up front

See the prices

The handover

Built to be run by your team, not by us.

CodeIn your repository from the first commit
DocsArchitecture, runbook, handover notes
EvalsThe eval set and the harness that runs it
AccessMoved to your team, ours removed

Questions about the process

Anything else, ask on the consult.

Who will we actually talk to?

The senior engineer who leads the project and writes its code. When a collaborator joins, you meet them before they start.

Do you work in our tools?

Yes: your repository, your issue tracker, and your Slack or Teams.

Which time zones do you cover?

We keep working hours that overlap with the US, Europe or Australia, agreed per project.

What if the scope changes during a build?

We write the change down with its cost and time before any work on it starts. Nothing changes silently.

Can we stop between steps?

Yes. Every step ends in documents you keep, and none of them commits you to the next.