Terms of Service
Updated 2026-06-12These terms cover every fixed-price build and dev lane sold on this site. They are written to be read, not skimmed past. If anything here is unclear, ask before you pay.
What Lab Twelve is
Lab Twelve is a one-person product studio. You describe your app in the scope chat, the AI extracts a structured scope, a deterministic pricing engine turns that scope into a fixed price, and you pay through Stripe. I build and ship the scoped work. The AI never sets prices, and neither of us negotiates them mid-build.
Two ways to buy: fixed-price builds (a defined scope, a defined price, a defined delivery window) and dev lanes (a monthly subscription: unlimited queued requests, one active request at a time). Current packages and prices live on the pricing page, which is canonical.
Payment terms
- Fixed-price builds are paid in full, up front, through Stripe Checkout. The build starts once payment clears and I have the materials the scope needs from you (content, access, decisions).
- Quotes from the scope chat are valid for 7 days. After that, the scope gets re-priced before you can pay.
- Dev lanes bill monthly in advance through Stripe. Pause or cancel anytime. Pausing preserves your unused days; canceling stops future billing.
- Rush delivery carries a surcharge, listed with the add-ons on the pricing page. Rush fee refund rules are in the refund policy.
Delivery: what done means
A build is done when all five of these are true:
- Every feature listed in your locked scope is implemented.
- The app is deployed to production hosting.
- The happy paths are tested: every core flow in the scope works end to end.
- Handoff is delivered: source code, repository access, and handoff docs.
- Your included revision rounds are completed or expired.
Each package lists a delivery window in business days. The window starts when payment clears and required materials are in, not at the moment of purchase. Included revision rounds expire 14 days after delivery if unused.
The delivery guarantee: if I can't deliver the agreed scope, I keep working until the scoped deliverables are complete or refund the undelivered portion.
Revisions and scope changes
Your package includes the revision rounds listed on your quote. What counts as a revision, what counts as a change request, and how change requests are priced is defined in the scope policy. The short version: small adjustments are included, new functionality is quoted separately, and nothing is ever billed as surprise hours.
Who owns the work
You own the code and the repository once the build is paid in full. Before full payment, the work product is mine. Fixed-price builds are paid up front, so in practice ownership transfers at delivery.
I keep ownership of generic tooling, internal libraries, and build infrastructure that predate your project or aren't specific to it. Anything of that kind shipped inside your app comes with the rights you need to use, modify, and run it.
Your app is built on open-source software (Next.js, Postgres, and similar). Those components keep their own licenses. I may show non-confidential parts of your project in the examples gallery; tell me if you'd rather I didn't.
Liability limits
My total liability for any build or lane is capped at the amount you paid for it. I'm not liable for indirect or consequential damages: lost profits, lost data, or downtime of third-party platforms your app depends on. The deliverable is the scoped software. There is no warranty beyond the scope, the delivery guarantee above, and the refund policy.
Refunds
Full refund before work starts; partial after scoping before development; none after development starts except failure to deliver the agreed scope. The full rules are in the refund policy.
Governing law
Governing law and venue: to be specified after formal legal review, which is pending (see the note at the bottom of this page). Until then, disputes start with an email, which is where almost everything gets resolved anyway.
Contact
Questions about these terms: email hello@labtwelve.dev. Ready to scope a build instead: start an AI scope.
I can update these terms; the dateline at the top changes when I do. A build in progress is governed by the terms in effect when you paid.