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 for companies with a recurring AI workflow backlog.
- ▸Weekly delivery call
- ▸1–2 shipped workflows/month depending on scope
- ▸Training handoff
- ▸Priority backlog review
Best for multiple priorities, locations, or stakeholders.
- ▸Biweekly demos
- ▸Expanded delivery capacity
- ▸Monthly executive report
- ▸Roadmap for next build cycle
Note — A credit is a unit of scoped delivery complexity, not an engineering hour. Every request gets a fixed credit value you approve before work begins.
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- ▸A credit is a unit of scoped delivery complexity, not an engineering hour.
- ▸Each request is assigned a fixed credit value before work begins based on the scope, integrations, data readiness, testing, documentation, security requirements, and acceptance criteria.
- ▸Credits are reserved when a scope is approved and consumed when the work is accepted.
- ▸1–3 credits: minor enhancement or adjustment
- ▸3–5 credits: focused automation or workflow improvement
- ▸5–8 credits: focused workflow · 8–13: standard build
- ▸13–20 credits: deeper or multi-system build · 20+: phased or separately scoped implementation
- ▸Up to 25% of unused credits may roll over for one additional month, then expire.
- ▸Larger builds may span multiple monthly cycles — credits reserve continuous delivery capacity, not a guaranteed number of completed workflows.
- ▸Work beyond monthly credits can be deferred to the next month, covered by approved overage credits, or scoped separately.
- ▸Fixes required to meet the approved acceptance criteria do not consume additional credits. New features or expanded requirements are re-scoped.
- ▸Third-party tools, model usage, hosting, enrichment, and client-specific software costs may be billed separately with approval.
- ▸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 lane. Month to month after.
- ▸Nexus Build and Nexus Flow run one active workstream; Nexus Scale runs up to two. Queued requests wait in a ranked backlog you control.
- ▸The client owns paid deliverables, subject to third-party platform and software terms.
Not sure which lane fits? We'll scope your first workflow on the call.