Fixed fee, quoted per engagement

BuiltForProd pricing is a fixed fee for a scope we agree before anyone starts work. Deployments are one-time. Managed is a recurring service, sold separately. This page tells you what is in each package, what moves the number, and how to buy.

How pricing works

One fee, one scope

You get a fixed fee for the work named in the offer, not an hourly meter. The fee is scoped to what you run: your accounts, your environments, your regions, your frameworks. If the scope changes, the offer changes first.

Deployments are one-time

Baseline and Blueprints are deployed by our engineers into your own cloud accounts and handed over. One fee, paid once, and the repositories and accounts are yours from then on.

Managed is separate

BuiltForProd Managed is a recurring service with its own agreement. You can buy a deployment without it, add it later, or stop it when your own team is ready.

No list prices, on purpose A price list that fits a two-account startup and a forty-account enterprise is a price list that is wrong for both. We would rather quote you than have you guess.

Deployment packaging

Three ways to buy a deployment. All three are executed end to end by BuiltForProd engineers and end with a hands-on handover.

Tier 1

Standard Deployment

The BuiltForProd Baseline, deployed into your own cloud accounts.

  • The Baseline edition for your cloud, customized to your organization profile.
  • Deployment into your accounts by our engineers, phase by phase.
  • The repositories, in your own version control organization.
  • Verification checks and a master checklist signed off before handover.
  • A hands-on handover session where your engineers run the platform themselves.
  • The documentation set, written with your namespace, domains and accounts in it.

The AWS Enterprise Baseline deploys 14 accounts across 2 OUs, with 3 service control policies and 11 permission sets.

BuiltForProd Baseline

Tier 2

Full Deployment with Blueprints

Everything in Tier 1, plus any two Blueprints on top of it.

  • Everything in the Standard Deployment.
  • Any two Blueprints, deployed into the workload accounts of your Baseline.
  • Blueprint repositories handed over with the rest of the estate.
  • The promotion path wired up: pull request, plan, review, gated apply.
  • Blueprint documentation and runbooks in the same documentation set.

Pick the Blueprints that match the workloads you actually run: a web application, a data and ETL pipeline, secrets management.

BuiltForProd Blueprints

Tier 3

Blueprint Deployment

More Blueprints for an estate that already has a Baseline.

  • As many Blueprints as you want, each one priced individually.
  • Deployed into your existing Baseline workload accounts.
  • Each Blueprint reads the network and account facts your Baseline already owns.
  • Its own least-privilege deployer role and its own state.
  • Repositories and documentation handed over per Blueprint.

Tier 3 is for existing Baseline customers. There is no bundle limit: add one Blueprint now and three next year.

See the Blueprints

BuiltForProd Managed tiers

Managed is how production keeps running after handover. Our engineers work through your own single sign-on groups, pull requests and pipelines. Rates and service levels live in your agreement, not on a web page.

BuiltForProd Managed: the four ways to buy engineering time.
Tier Shape Who it suits
On-Demand Pay as you go, with a minimum of 10 hours. Teams that own production day to day and want experienced engineers on call for the hard changes: an upgrade, a new region, a review before an audit.
Support SLA A pre-paid annual block of 100 hours, governed by service levels agreed in your contract. Teams that need a commitment in writing rather than best effort, and a predictable line in next year’s budget.
Team Augmentation, part-time Four hours a day, on a 6- or 12-month commitment, billed monthly. Teams hiring their first platform engineers who need the platform moving forward in the meantime.
Team Augmentation, full-time Eight hours a day, on a 6- or 12-month commitment, billed monthly. Teams with no platform function at all, where production needs an owner every working day.

Channels are email, Slack and video. Response commitments are set per agreement, so we publish none here. The tiers, channels and scope are described in full on the service levels page, and the service itself on the Managed page.

Start with the BuiltForProd Assessment

The low-commitment first step. A fixed fee, a short engagement, and an honest answer about what production would take.

The BuiltForProd Assessment measures what you run today against the eight properties of the BuiltForProd Standard: secure, reliable, observable, scalable, automated, recoverable, compliant, operable. You get a prioritized gap list and a straight answer on fit.

It is a fixed fee, scaled to the size of the estate, and it is credited in full toward a Baseline purchase. If we are not the right fit, we will tell you, and you still keep the gap list.

Take the 10-question self-check

Good reasons to start here

  • Due diligence flagged infrastructure and you need to know how bad it is.
  • An audit date exists and nobody has mapped the controls yet.
  • Leadership wants a second opinion before approving a platform budget.
  • You suspect the answer is a foundation, but you want it written down first.

What shapes your quote

Five variables move the number. Bring answers to these and a scoping call takes one meeting.

Accounts, environments and regions
How many accounts and workload stages the foundation carries, and whether you start in one region or more than one.
Which Blueprints
Each Blueprint is a working system with its own repositories, pipelines and documentation, so each one is priced on its own.
Compliance frameworks in scope
Which control sets and evidence sources you need switched on, and how much of the audit conversation the engagement has to support.
Migration from an existing estate
A greenfield organization is cheaper than moving live workloads off a single account, a hand-built estate or an earlier landing zone.
Managed tier
Whether you take the platform over at handover, or keep our engineers on it, and at which tier and commitment.

What is not included

Said plainly, so nothing arrives as a surprise on an invoice.

Cloud spend

Your cloud provider bills you directly for what the platform runs. We do not resell cloud capacity. Expensive features ship switched off, with the provider’s price documented next to the switch.

Domain registration

You own your domains and register them yourself. We configure delegation, zones and records for the domains you already hold.

Application code

Beyond the sample applications that come with a Blueprint, your product code stays yours to write. Your competitive advantage is your application, not your VPC design.

Ongoing operation

A deployment ends at handover. Running production with you afterwards is BuiltForProd Managed, priced separately as a recurring service.

How to buy

Direct

We scope the engagement, send a written offer with the fee and the deliverables, and invoice on acceptance. Onboarding starts as soon as the organization profile is agreed.

  1. Scoping call.
  2. Written offer: scope, deliverables, fixed fee.
  3. Acceptance and invoice.
  4. Organization profile, then deployment.

Cloud marketplace private offer

Every offering can also be delivered as a private offer through your cloud provider’s marketplace. Tell us which marketplace your agreement sits in and we will prepare the offer there.

  • Pay with the cloud account you already have.
  • Consolidated billing, on an invoice your finance team already receives.
  • Can count toward a committed spend agreement you have already signed.
  • Often a shorter path through procurement than onboarding a new vendor.

What the alternative costs

No invented numbers here. These are the costs that do not appear on an invoice, which is exactly why they are easy to underestimate.

Cost of the alternative, compared with a scoped fixed fee.
Instead of a deployment What it costs you What a fixed fee changes
Build it in-house Senior platform engineers, hired and retained, spending months on account structure, identity, networking, guardrails, pipelines and documentation before the first workload moves. A fixed fee converts an open-ended internal project into a scoped one, and keeps your engineers on the product.
Learn production through outages The audit scramble, the incident nobody can explain, the backup that has never been restored, the one engineer who knows how it works. The controls, runbooks and evidence exist before the event that would have taught you to build them.
A one-off consultancy build A bespoke estate whose decisions live in someone else’s head, and which starts aging the day it is delivered. Every decision is documented, every optional choice is labeled in the code, and improvements arrive as pull requests you approve.
Rent a platform Lower effort today, and an estate you cannot take with you when the requirements change. Not a black box you rent. The repositories and the accounts are yours after handover.

Don’t make your company learn infrastructure through outages.

The full comparison, including reference architectures, landing zone accelerators and managed DevOps firms, is on alternatives compared.

Pricing questions

Why are there no prices on this page?

Every BuiltForProd engagement is quoted as a fixed fee for a defined scope, so a list price would be wrong for most readers. Scope is set by how many accounts, environments and regions you run, which Blueprints you take, which compliance frameworks are in scope, and whether you are migrating an existing estate. Tell us those five things and you get a real number.

Ask for a quote

How long does a quote take?

A quote follows one scoping call in most cases. We ask what you run today, what is driving the date, and who will own the platform after handover. If we need a second conversation with your security or compliance lead, we say so on the first one.

What does a fixed fee cover?

A fixed fee covers the deployment named in the offer: customization, the deployment work itself, verification, the documentation set, and the hands-on handover session. Cloud spend, domain registration and application code sit outside it, and so does ongoing operation, which is BuiltForProd Managed.

What happens if the scope changes?

A change in scope is a change to the offer, agreed in writing before anyone starts work on it. Adding a region, a Blueprint or a compliance framework mid-engagement is normal; discovering the fee has moved after the fact is not.

Can we buy through a cloud marketplace?

Yes. Any offering can be delivered as a private offer through your cloud provider’s marketplace, so you pay with the cloud account you already have, on consolidated billing, and the purchase can count toward a spend commitment you have already made.

Is the BuiltForProd Assessment credited if we buy?

Yes. The Assessment is a fixed fee, and it is credited in full toward a Baseline purchase. It exists so you can find out what production would take before committing to a deployment.

About the Assessment

Find out what production would take.

Tell us what you are running and what is coming: a funding round, an audit, a first enterprise customer, a migration. We will tell you what we would build, what it costs, and whether we are the right fit.