Pricing.
Three build lanes, priced monthly in credits — plus the fine print, stated plainly: overages, third-party costs, minimums, and workstream limits.
Choose your build lane
Start with one focused workflow lane. Scale credits as the backlog proves itself.
All pods start with a 90-day commitment so we can map the backlog, ship the first workflows, and prove the delivery lane works.
Best for one focused AI workflow lane.
- ▸Request intake
- ▸Credit-based scoping
- ▸Build + QA
- ▸Basic documentation
- ▸Two working sessions/month
- ▸Monthly impact summary
Best first pod for companies with recurring AI/build backlog.
- ▸Weekly delivery call
- ▸1–2 shipped workflows/month depending on scope
- ▸Training handoff
- ▸Priority backlog review
Best for teams ready to ship multiple workflows.
- ▸Biweekly demos
- ▸Expanded delivery capacity
- ▸Monthly executive report
- ▸Roadmap for next build cycle
Note — Credits are not hours. Credits represent delivery complexity, integrations, testing, documentation, and acceptance criteria.
Third-party tools, model usage, enrichment, hosting, and client-specific software costs may be billed separately when required.
Not sure which lane fits? We'll scope your first workflow on the call.
View full pricing details›The fine print, stated plainly
no surprises by design- ▸Credits are not hours. They represent delivery complexity: scope, integrations, testing, documentation, and acceptance criteria.
- ▸Credits are reserved when you approve a written scope and deducted when the work ships and is accepted.
- ▸Fixes inside the approved acceptance criteria do not consume extra credits. New requirements are scoped separately.
- ▸If a request doesn't fit the month's remaining credits, you choose: move it to next month, approve overage credits, reduce the scope, or upgrade the pod.
- ▸Nothing gets built without approved credits behind it — overages are always an explicit yes, never a surprise invoice.
- ▸Third-party tools, model usage, enrichment, hosting, and client-specific software costs may be billed separately when required.
- ▸Any separate cost is named in the written scope before you approve it.
- ▸Every pod starts with a 90-day commitment: enough time to map the backlog, ship the first workflows, and prove the delivery lane with real usage.
- ▸After the first 90 days, pods continue month to month.
- ▸Starter and Core pods run one active workstream: one build in flight at a time, done properly.
- ▸Scale pods run two parallel workstreams for teams shipping multiple workflows at once.
- ▸Queued requests wait in a ranked backlog you control — reordered monthly, never lost.
- ▸Full custom SaaS builds, major data warehouse rebuilds, regulated workflows without security review, and unrelated consulting are scoped separately from pod credits.
- ▸The client owns the deliverables after payment, subject to third-party platform and tool terms.
Not sure which lane fits? We'll scope your first workflow on the call.