Platform delivery
Your product live on your own domain in weeks, and still running next year.
You bring what the product has to do. You get a platform your customers sign in to, a public site, the capabilities you need switched on, and a team that keeps all of it running.
What you get
What lands, not what is promised.
Every line below is something you can open on the day it goes live.
A platform of your own
Your customers sign in, join organisations, get roles, and see only what they should. Your brand, your domain.
A public site
A site anyone can read, on a domain you own, editable without waiting for a developer or a deploy.
The capabilities you need
Members, courses, events, catalogue, tasks, media, chat, payments — switched on and configured, instead of the six months it takes to build them.
AI where it earns its place
Assistants and automations inside the product, with a person approving anything that acts on someone else's behalf.
Infrastructure somebody runs
Deploys, certificates, DNS, backups, monitoring and alerts. You do not get a repository and a good-luck email.
A person who answers
When something is wrong at two in the morning it reaches somebody who can fix it, not a form.
How it goes
Four moves, and you decide the third.
The third one is a person rather than a machine, and that is the feature rather than the bottleneck.
Brief
A conversation and a written brief: what the product has to do, for whom, and what would make it a failure.
you and us
Blueprint
Your brief becomes a proposed platform — what it is called, what it does, who can do what, how it looks — and we read it before you do.
days, not weeks
Your approval
Nothing is provisioned until a person has reviewed the blueprint and you have approved it. This gate has never been optional and will not become optional.
the gate
Live and operated
On your domain, branded, monitored and backed up — and then changed as your product changes.
ongoing
Which one is you
Three ways in.
Every one of them carries a monthly operations fee. The factory makes the build cheap for us too, so that is a structure rather than a discount.
Launch
One product, one audience, one public site.
Priced from your brief until the ranges are published.
- Your brief turned into a platform, reviewed before it is built
- One set of capabilities configured for your product
- Your brand on the app and on the site
- One public site on a domain you own
- Three months of operations included
+ monthly operations
Scale
A product that needs its own features, or the systems you already run.
Priced from your brief until the ranges are published.
- Everything in Launch
- Features built for the part only your product does
- Connections to the systems you already run
- Assistants and automations inside the platform
- Twelve months of operations included
+ monthly operations
Custom
Something nobody has built before — a lab platform, a simulator, a marketplace.
Talk to us.
- A scoped engagement rather than a tier
- A fractional CTO on your side of the table
- Research-grade work where your product needs it
- Operations for the life of the engagement
+ monthly operations
Takeover
Built it yourself? Hand it over and stop firefighting.
A first version built with an AI tool is often the right first version. The wall is rarely the features — it is the second customer, the first payment, the first security question, the first time two people edit the same row.
You get a verdict
We read what you have and tell you what is load-bearing, what is a liability, and what would survive a move. In writing, and yours whether or not you continue with us.
week one
You keep what is worth keeping
The parts that earn their place move onto the platform's own accounts, permissions and contracts. Your data comes with you; the accumulated shortcuts do not.
the engagement
You stop operating it
After that it is a platform like any other we run: deployed, monitored, backed up, and changed by people who can explain the change.
monthly, ongoing
Ownership
What is yours, and what we operate.
Worth reading before the contract rather than after it. The exit path is stated as it is, not as it would sound best.
Yours
- Your data, and an export of it on request at any time
- Your brand, your content and your domain names
- The commercial relationship with everyone who uses your platform
- The decision to leave, without asking us first
Ours to operate
- The runtime: deploys, certificates, DNS, backups, monitoring and alerts
- The shared services your platform runs on, and their upgrades
- Your platform's configuration, changed with you rather than at you
- The on-call answer when something is wrong at two in the morning
The honest half: your data is portable and we will hand it over, but the software is a system we operate for many customers rather than a codebase that ships to you. If running your own copy is a requirement, say so on the first call — it changes the shape of the engagement, and it is a fair thing to want.
Questions
What technical buyers ask first.
- How fast can we be live?
- Weeks rather than quarters — you get a date after the brief, because your content, your integrations and your approvals decide it as much as we do.
- What does it cost?
- A fixed fee to build it and a monthly fee to run it, both quoted from your brief.
- Where does it run, and where does the data live?
- On our own servers in Europe, with the databases on a different machine from the one serving your traffic, and backups off site. If your project needs a specific jurisdiction, that is a conversation before the contract rather than after it.
- Can we use our own domain?
- Yes, for both the app your customers sign in to and the public site, and it is the normal case rather than an upgrade. Certificates are issued and renewed for you.
- How is one customer's data kept out of another's?
- Every request that touches your data checks who is asking and which platform they are asking about, in the code path itself rather than in a gateway that trusts a header — and any change to those paths ships with a test proving the other customer is refused.
- Can we get our data out?
- Yes, on request, in a documented format. The software itself stays ours to operate; the ownership section above says so in more detail than most vendors will.
- Who does support, and for whom?
- We support you, the operator. Supporting your own users is your relationship with them, running on tools inside your platform — and if you want us in front of them, that is a scoped addition rather than an assumption.
- What happens when we need something the platform does not do?
- It becomes a configuration change, a shared capability, or something built only for you — in roughly that order, because the first two are cheaper for you and the third is the one nobody else gets.
- Are payments included?
- The commerce side is built — catalogue, orders, money to the cent, fees — and the payment provider is not switched on in production yet. If taking money is part of your first release, tell us early and you will get the current state rather than a roadmap.
Platform delivery · next step
Send the brief.
A paragraph is enough to start. A person reads every message.