Your data model, not a plugin configuration.
A platform business usually breaks the assumptions a generic tool makes: what a customer is, how money moves, or who is allowed to see what. Those are model-level changes, and they're the ones this architecture is built to absorb.
Your own models
The records your business has, in the places the core understands, without forking the platform underneath.
Your own apps
Your applications sit on top of the core rather than inside it, so the core can keep moving without stepping on them.
Everything else, inherited
Identity, record-level permissions, payments, billing, content and deployment, maintained centrally and upgraded over time.
Scope first, then a number.
Platform work varies more than anything else we do. The same brief can differ by an order of magnitude depending on your data model and what you are migrating, so we don't publish a range. A number without scope behind it is a guess.
Your project brief
Tell us roughly what you're building. We send back a written brief, free, and talk it through with you on a 30-minute call.
A scoping conversation
Free, and longer than the discovery call, because a platform takes more than thirty minutes to understand. You pick the time; the calendar invite comes with a link to move or cancel it.
Discovery, quoted
Inception, reverse brief, data modelling and a guided pass through the generation pipeline. Quoted from what we learn in the scoping conversation, and credited against the build if you go ahead.
The build, quoted from the brief
Priced against a brief you have read and corrected, not an estimate made before anyone understood your records.
Ask us for pricing and you'll get it, after a conversation, in writing, against a defined scope. That's slower than a number on a page, and it's the reason our quotes hold.
Why this beats a from-scratch build
You skip the foundation
The expensive, unglamorous half of a platform already exists and runs in production. You aren't the first client to need accounts and permissions to work properly.
It doesn't become a fork
Custom work in your own app keeps receiving improvements to the core. A copied-and-edited platform stops improving the day it's copied.
Handover is available, on a licence
Your data, your infrastructure and the code written for you are yours, and your project is documented the way every Pure Stack deployment is. Another team can take it on with a Pure Stack licence of its own, or you can buy the platform out first.
Tell us what you're building.
Send us the shape of it. We write it up and talk it through with you, then take the longer scoping conversation a platform needs.