Pricing
How we price projects
A range before you sign, then a fixed price that rests on assumptions written into the contract. One agreement covers the Blueprint and the build, so you make one decision, not two.
The principle
Fixed scope, not hours
You know the cost up front
Every stage has a defined scope and a price agreed before work starts. No surprise invoices at the end of the month.
The estimate risk is on us
Hourly billing pushes the risk of a bad estimate onto you. A fixed price keeps it where it belongs, with us.
The price rests on written assumptions
Catalog size, integrations, migration scope, what you supply. Every assumption behind the number is listed in an annex to the contract, so you can see exactly what we priced.
One decision, not two
A single agreement covers the Blueprint and the build. You are not asked to buy a discovery phase first and a platform later, with a second negotiation in between.
No open-ended development
The scope is defined, the backlog stays controlled, and bigger new features are quoted separately, never billed as a running meter.
Worked example
How we’d bill a project like our D2C jewelry build
Same scope we show in the example build, a fine jewelry D2C platform on a modern stack. Here’s how the billing splits across the BEAM stages.
See the full example build →Where the one-time budget goes
Blueprint
What it covers
Platform, product data and integration map, plus a buildable plan and confirmation of the assumptions the quote was built on.
How it’s billed
Part of the total quote, not a separate purchase and not a separate decision. Its share is small because its job is to make the next number reliable, not to fill a budget line.
Engineering
What it covers
Storefront, checkout, payments, import of ~1,500 SKU and the core integrations.
How it’s billed
A fixed price for the defined scope, paid in milestones across the build (e.g. kickoff, mid-build, go-live). You pay for the outcome, never by the hour.
AI Automation
What it covers
Product descriptions, PL→DE/EN translations, feed localization and listing error analysis.
How it’s billed
Scoped and priced per workflow. You add, and pay for, only the ones you switch on, when they pay back.
Maintenance & Growth
What it covers
Keeping the platform healthy and the roadmap moving after launch.
How it’s billed
A flat monthly retainer with no long lock-in, plus an optional success fee on channels we actually influence. Bigger features run as separate fixed-price Feature Sprints.
Figures depend on scope, this shows how billing and proportions split across stages, not a price list. You get a range before you sign; the Blueprint confirms the assumptions behind it and the number becomes final.
Estimate your scope
Map your project, see your Blueprint
The choices below, catalog, channels, integrations, starting point and AI, are exactly what shape a quote. Pick what fits and you’ll see the complexity, which BEAM stages come into play and what your Blueprint would focus on. No price here, because a real range needs a look at your actual setup, and we do that before you sign anything.
Your scope
Complexity
–
BEAM stages in play
Your Blueprint would focus on
This is an indicative scope read, not a quote. A real range comes from a short conversation, and the final number from the Blueprint that confirms it.
Pricing questions
Do you charge by the hour?
No. We work in fixed scopes with fixed prices. Hourly billing pushes the risk of a bad estimate onto you; a fixed scope keeps it on us.
How do I get an actual price?
A short conversation plus a look at your current setup gives you a range within a few days, at no cost. If the range works, we sign one agreement covering the Blueprint and the build, with the assumptions behind the number listed in an annex. The Blueprint then confirms them and the price becomes final.
What if the Blueprint finds something different?
Small differences we absorb; the price does not move. If something moves the effort materially, we show you what changed, what it costs and why, and you choose: accept the corrected price, or trim scope to fit the original one. What we never do is discover the problem halfway through the build and send an invoice for it.
When is the price final?
You get a range before you sign anything. It becomes a fixed number once the Blueprint has confirmed the assumptions it was built on, which is the point where we know your systems rather than assume them.
Can we start small?
Yes. The first phase can be deliberately narrow, and the plan itself is a buildable specification you own. You can build it with us, phase it, or take it elsewhere.
What if the scope changes later?
New, larger features are quoted as separate Feature Sprints with their own fixed scope. Small improvements fit inside the Maintenance & Growth retainer, so the backlog and the price both stay predictable.
Do you offer ongoing work?
Yes, Maintenance & Growth is a monthly retainer that keeps the platform healthy and the roadmap moving, optionally with a success fee on channels where we have real influence.
Why don’t you publish prices?
Because a platform build is bespoke: the number depends on your catalog, integrations, channels and migration. Publishing a random figure would be misleading. You get a real range for your project instead, before you commit to anything.
The fastest way to a real number
Tell us what you sell and what you run it on. Within a few days you get a range and the assumptions behind it, at no cost and with nothing to sign.
Book a Blueprint →