How we price

Pricing you can actually understand

No mystery day-rates, no "it depends." Depending on the work, you'll see one of three clear commercial models — and for ongoing delivery, a transparent system of delivery points you control month to month.

The promise

No mystery day-rates, no invoices you can't explain to your board. You see the model, the number, and exactly what it buys — before anything is load-bearing.

Three ways we price

The right model for the work

01 Best for clear scope

Fixed-fee sprints

Where scope is clear, the price is fixed — no hourly billing, no surprises. One-time, defined deliverables; great for assessments, audits, PoCs. Fee credits toward the build if you proceed. e.g. AI Opportunity Assessment.

02 Best for ongoing build

Delivery points

For ongoing build and product work, you buy a monthly budget of points and spend it however you like. Monthly, flexible, re-prioritised as you go; work sized in points, not opaque hours; scale the budget up or down by month. e.g. a dedicated squad delivering a set points budget/month.

03 Best for AI products

Build → licence + usage

For AI products, a monthly build transitions to a platform fee plus usage once it's live in production. Predictable build phase; platform fee once deployed; usage priced to the value you process. e.g. Agentic Workflow — build, then platform + per-action usage.

The system behind Model 02

How delivery points work

One honest planning unit. Every piece of work has a fixed points cost by size — you buy a monthly budget and spend it however you like.

Delivery point level
40pts / month
Time5 medium deliverables shipped monthly
Cost×1 of the base monthly budget

Add points to accelerate delivery — scale down when you need to. You pay for the outcome of the work, not the hours behind it.

XS2 pointsA small, self-contained change — a config, a minor tweak, a short task.
S3 pointsOne straightforward deliverable with a narrow scope.
M8 pointsA multi-part deliverable with one integration or dependency.
L20 pointsA complex deliverable across several systems, with QA and monitoring.
XL40 pointsA large, interconnected body of work delivered together.
In practice

Simple to run, month to month

Fine print — Delivery points are a planning unit based on the agreed delivery level; the monthly mix can be re-prioritised and is not a fixed or guaranteed deliverable count. Where a piece of work grows beyond its agreed size, we agree a change order before the extra work proceeds.

Choose a delivery level

Pick the monthly capacity that fits your pace and budget. It sets your points budget for the month.

Spend it your way

Prioritise the work that matters most. Mix sizes freely — a couple of big items, or many small ones.

Re-prioritise anytime

Priorities shift? Re-plan next month. Scale the level up or down as your needs change.

They received feedback and took action quickly.
Collin DanielsOwner and CEO, Daniels Dynamic Ltd.
Common questions

The pricing questions we get most

Something we didn't cover? Ask us directly — you'll get a straight answer, not a sales sequence.

It depends on scope — but you'll never get a black box. Most engagements start with a fixed-fee assessment, and ongoing build work runs on delivery points so you always know what your monthly budget buys.

Yes. If you engage us for the build phase within 30 days of a sprint's delivery, 100% of the one-off fee is credited toward your first build invoice.

That's the point of the model. Scale your delivery level up or down each month, and re-prioritise what the points are spent on as your needs shift.

For build→licence products, usage is priced transparently to the value you process (e.g. per action or per model call), with the platform fee shown upfront.

Get a clear number, not a maybe

Tell us the problem and we'll map it to the right model — and prove it with a 48-hour prototype. Book a scoping call.