Pricing
Priced per Team, shaped to your org.
Pricing here is a model, not a menu. The price follows the Teams you staff and the work you hand them, and it flexes as your org grows: more capacity when you need it, less when you don't.
You staff an org, not licenses
A Team owns a slice of your product plus its Numbers: the proposals, the code, the review, the production watch. The price follows the Teams you staff and the intensity they run at.
No per-seat charges, ever
Your whole team is inside the workspace at no charge: reading the record, reviewing PRs, answering the org's asks. We never bill you for a reader.
Flexes as you scale
Start with one Team and add the org around it as trust extends. Intensity dials up for a launch and back down after; the price follows, in both directions. The estimate on the call is built for the org you have, and the one you're becoming.
The point was never fewer engineers. It's what each of yours becomes: a product engineer running fleets of agents, while the org carries the review, the watch, and the routine.
For finance, security, IT
The boring part, handled.
Monthly by default
Month-to-month, cancel any time. Annual contracts with invoicing are available; we set those up on the call.
SOC 2 and DPA
Our SOC 2 Type II certification work is in progress. A DPA is available on request.
Encrypted and scoped
Connector credentials are customer-scoped, AES-256-GCM encrypted, and resolved only at execution time, never placed in model prompts.
Sanitized action trail
Tool calls record the triggering user, tool, sanitized parameters, status, duration, and timestamp. Result payloads and message bodies are not copied into the audit row. A sample export is available on request.
Custom security review
We support custom security questionnaires, share current control evidence, and will join your security review call.
The standard ones
MSAs, NDAs, MNDAs. We sign yours or you sign ours. Procurement mailbox at procurement@yagni.app. AP at ap@yagni.app.
We've been through procurement at companies of thirty, fifty, two hundred, five hundred. We can move at your pace.
Questions on pricing
The small print, large.
Why isn't there a rate card?
Because the price is scoped to your org, not picked off a shelf. It depends on how many Teams you staff and how much of the engineering day you hand them. Thirty minutes with the founder ends with an estimate: which Teams, at what intensity, at what price. You get the number on the call, not in a follow-up.
What does the price scale with?
The capacity you staff: how many Teams run for you, and the intensity they run at. It never meters your outcomes or your revenue. Results are what the track record proves, not what the invoice counts.
Do you charge per seat?
No. Humans are free, always. Your whole team works inside the workspace: reading the record, reviewing PRs, answering the org's asks. Per-seat math punishes exactly the behavior we want more of.
Can we start small?
You start with probation, not with a starter plan. For the first thirty days you review everything the org does, the way you would with any new hire. If it isn't pulling its weight, we work with you free until it is.
What's the contract shape?
Month-to-month by default, cancel any time. Annual contracts with invoicing are available, and we support procurement end to end: MSAs, NDAs, security review, the standard ones. We set the shape up on the call.
Is the engineering work billed separately?
No. Everything the org does is inside the price: the proposals, the code, the PR review, the production watch, the triage, and pairing with your engineers in the terminal. One line item, per workspace.
The number comes from the call.
Thirty minutes with the founder ends with an estimate: which Teams, at what intensity, at what price. And every org starts on probation, so the first month is yours to judge.
or read the editor's note