/design-partners
Build this with me.
AI staff for the team you already have. RepoStaff doesn't exist yet in a form you can buy, and I'm looking for at most five teams to shape it before it does.
For teams whose senior engineers are the bottleneck.
Audience hypothesis, not validated demand
Likely a fit
- A product team of five to thirty engineers
- Code on GitHub
- Already using AI coding tools
- Senior engineers are the bottleneck for planning and review
- You care where your code runs, and can run compute on your own machines or AWS
- A budget holder is in the conversation
Not yet
- Regulated enterprise
- GitLab or Azure DevOps
- Teams on Jira
- Management on your own infrastructure
- Teams outside the US, at launch
- Anyone who needs a data residency guarantee
Proposed terms.
These terms are planned, untested hypotheses and may change before anyone signs. Exact participation terms still need review and aren't finalized.
| Term | Planned value |
|---|---|
| Teams | At most five |
| Self-run | $149 per org, per month for 12 months, half the planned self-run list price |
| RepoStaff-hosted compute, once available | $349 per org, per month for 12 months, with 100 VM-hours included, then $0.60 per VM-hour up to an overage cap |
| Billing begins | After the first completed agent run on your repo. Before that, a signed non-binding commitment and interviews only, and no money changes hands |
| After 12 months | List price at that time, with 60 days' notice |
| If you cancel | Cancel any time. A refund for a month when no pull request merged is planned, but its exact conditions aren't settled. It isn't a free idle month or a refund of unused allowance |
| Program length | Six active months, inside the 12-month price lock |
| Still yours to pay | Your own model usage, on your API keys, and your own compute, including any AWS costs that accrue without task activity |
| Your name | No name, logo, quote, or metric published without your written permission |
What goes each way.
You get
- A direct line to the person building it, with no response-time guarantee
- Real influence over what gets built first
- Help setting up gates and importing skills
- A brain repo you keep regardless
I'll ask for
- A named budget holder and a technical contact
- An honest account of how your team works today
- A 45-minute kickoff, then a 30-minute check-in every two weeks for the first 12 weeks
- At least five real, non-production-critical tickets a month through the flow
- Access to your cost and outcome figures in those meetings
- Blunt feedback, including "we wouldn't pay for this"
- Your patience. Things will break
Nothing touches your code first
Nothing touches your code before a signed agreement. Reading this page commits neither of us to anything.