Backlog sizing
Start with the smallest team that ships
We read the backlog before proposing headcount. Most engagements start with exactly one senior engineer, not a pod handed to you by default.
Senior engineers who already build inside the harness method, dropped straight into a backlog we didn't write, sized to what you need this month, not a fixed team from day one.
Resized every month, not fixed at kickoff.
Most staff-augmentation engagements hand you a résumé and a board invite. The engineer learns your stack from zero, ships the way any contractor would, and the context leaves when they do.
A generic contractor
An AI Engineering Sprint
We staff your backlog directly, not a fixed team. Start with one senior engineer fluent in the harness method; add a specialist (front-end, on-chain, data) only when the backlog actually calls for it; wind down to on-demand maintenance once it stabilizes.
Dynamic team · sized month to month
Four moments in a typical engagement, not a sample backlog.
Backlog sizing
We read the backlog before proposing headcount. Most engagements start with exactly one senior engineer, not a pod handed to you by default.
Spec, then code
Spec-driven, then test-driven: the test fails on the bug before the fix exists, and passes after. A recurring procedure, like investigating a data spike or closing the month, gets saved as a skill instead of living in one engineer's head.
Specialist add-on
A front-end, design, or on-chain specialist joins when the backlog actually has that kind of work, not on day one because the org chart says so.
Domain fluency
Engineers already fluent in the domain (blockchain, fintech, regulated data) spend the ramp-up on your codebase, not on the subject matter underneath it.
Wind-down
When the backlog stops growing, the engagement doesn't end abruptly. It steps down to a documented maintenance floor, hours as needed.
Week 1
What's real versus nice-to-have, where the risk actually sits, and the smallest team that can ship it, not the team that's easiest to sell.
Week 2
One AI-native engineer, spec-driven and test-driven from commit one, in a weekly Scrum cadence you can see.
Ongoing
A specialist joins only when the backlog calls for it. Recurring procedures get saved as skills along the way. Cadence stays weekly either way.
When it stabilizes
Steps down to an on-demand maintenance floor, documented and handed off, not a cliff.
Tell us the backlog and what's blocking it. We reply within two business days with how we'd size the team.
AI Systems is for a system we build from scratch, and optionally keep shipping backlog for afterward. Engineering Sprints is for a backlog and a codebase that already exist, that we didn't build, staffed as standing capacity from day one, not after a build.
The headcount looks similar. What's different is what the engineer brings on day one: AI-native engineering (Claude Code as the default way of building, not an occasional tool), spec-driven + test-driven delivery, and domain fluency instead of a learning curve you pay for.
Every backlog item starts as a short written spec (what changes and why) before any code. Then a test is written that fails on the current bug and passes once it's fixed. A data-quality fix doesn't come back silently because nobody remembered to check for it by hand.
Scrum, weekly: a groomed and prioritized backlog, a sprint goal, and a review you can see. Recurring procedures, like closing the month or investigating a data spike, get written up as reusable skills instead of staying in one engineer's head.
We don't publish pricing: every engagement starts with a short paid assessment of the backlog, then a retainer sized to the team that backlog needs that month, stepping down to a maintenance floor once it stabilizes. Tell us the backlog and you get a real number, not a rate card.
That's the default starting point, not the exception. Most engagements begin with one senior engineer against the highest-priority backlog item and grow only when the work in front of us justifies it.
It steps down to an on-demand maintenance floor instead of ending the relationship outright: documented, handed off, and billed only for hours actually used.