Skip to content
BuiltForProd Assessment

Know where you stand. Know what to fix. Know what comes next.

An independent, evidence-based assessment of your infrastructure against the BuiltForProd Standard. We review the systems in scope, talk with your engineers, and write down what works, what needs attention, and what could not be verified. Then we design the future state and the plan to reach it.

Fee
Fixed, quoted before it starts
Credit
Up to 50% toward a Baseline within 90 days
Delivery
About two weeks after kickoff
Framework
The BuiltForProd Standard, eight properties

When you need more than another opinion

An Assessment is built around the decision in front of you, not a standard checklist. These are the decisions it is usually bought for.

A migration is on the table

Off a single account, off a platform, off a hand-built estate, or onto a second region. Before choosing a tool or committing to a rebuild, establish what is there and which changes are worth making.

Due diligence flagged infrastructure

An investor or an acquirer put infrastructure on the risk list. The Assessment turns that into a specific, ordered list of work with the evidence behind each item.

An audit date exists

SOC 2, HIPAA, PCI DSS 4.0, NIST CSF, CMMC 2.0 or CIS. We map the controls and evidence you have against what is missing. Certification stays your auditor’s decision.

Leadership wants a second opinion

Before a platform budget is approved, somebody independent should say whether the plan is the right one. Sometimes that means telling you to keep what you have.

You inherited it

Nobody fully documented the environment, the person who built it has moved on, and every change feels risky. The Assessment writes down what exists and what it would take for a second engineer to run it.

Security questions are getting harder

A customer questionnaire, a pen-test finding, a near miss. You need to know where access, logging and recovery actually stand, in writing, before the next question arrives.

What we review

Evidence, not intentions. We look at the systems in scope, the code, the configuration and the documentation, and we talk to the people who run it. You choose the areas that matter to your next decision.

Cloud architecture and dependencies
Accounts, networks, regions, shared services, and what depends on what.
Security and access controls
Identity, standing access, credentials, encryption, guardrails and detection.
Terraform and infrastructure as code
What is in code, what is not, state, modules, drift, and how safe a change is.
CI/CD and deployment readiness
How a change reaches production, who approves it, and what can be rolled back.
Reliability and operational ownership
Failure modes, backups and restores, monitoring, on-call, and who can run it.
Compliance readiness gaps
Controls and evidence against the framework you are working toward.

Measured against eight properties

Secure
Is it secure by default?
Reliable
What happens when something fails?
Observable
Can operators see what is happening?
Scalable
What happens when demand grows 10x?
Automated
How much depends on manual intervention?
Recoverable
Can the system actually be restored?
Compliant
Can controls and evidence be demonstrated?
Operable
Can another engineer operate it safely?

The same eight properties every BuiltForProd deployment is built to. You do not need to adopt any BuiltForProd product to be assessed against them. Read the Standard.

What you receive

One written assessment in four parts, that your engineers can trace and your leadership can act on.

  1. The assessment against the Standard

    • Evidence-based findings for each BuiltForProd Standard property in scope.
    • Technical discussions with your engineering and platform teams, and a review of architecture documentation, configuration evidence, infrastructure code and operating practice.
    • A written statement of the assessment boundaries, the evidence available, the assumptions made, and anything that could not be verified.
  2. Findings and prioritized recommendations

    • An executive summary: business impact, the most important risks and gaps, recommended first actions, and the decisions for leadership.
    • Detailed findings mapped back to the relevant property, with the evidence behind each one and the risk it represents.
    • Recommendations in three groups: immediate concerns, foundational improvements, longer-term improvements. What to change, what to keep, and why.
  3. Future-state architecture and migration plan

    • A future-state architecture designed around your goals, constraints and required production characteristics, with diagrams of the environment, its components, dependencies and major design decisions.
    • Design decisions mapped to the Standard, with assumptions, trade-offs and dependencies written down.
    • A phased migration and implementation plan: sequencing, dependencies between workstreams, major activities and estimated effort. Executable by your team, by BuiltForProd, or by another partner.
  4. Delivery and follow-up

    • The complete written assessment about two weeks after kickoff, subject to timely access and your team’s availability.
    • Documentation your engineers and your leadership can share, question and plan from.
    • Follow-up after delivery for questions, clarifications and reasonable refinements within the agreed scope. Implementation is not included and can be contracted separately.

How it runs

First we agree the questions, the systems in scope and the access. Then we combine conversations with your team, documentation, configuration evidence and technical review.

  1. Discovery

    Start with your goals. Agree the questions to answer, the focus areas, the systems in scope, the constraints, the access we need, and what a useful outcome looks like.

  2. Assessment

    Talk with your team and review the systems in scope. Establish what works, what needs attention, and what we can and cannot verify.

  3. Recommendations

    Explain what to change, what to keep, and why. Prioritize the work and make the trade-offs explicit.

  4. Future-state architecture

    Design the target environment around your goals, with diagrams, dependencies and the reasoning behind each choice.

  5. Migration plan

    Lay out a phased path from where you are to where you want to be, with sequencing, dependencies and effort estimates.

  6. Follow-up

    Ask questions after delivery and work through clarifications and reasonable refinements within the agreed scope.

Timing and fee

Delivery is targeted at about two weeks after kickoff, subject to timely access and your team’s availability. The fee is fixed, scaled to the agreed scope, and quoted before anything starts. It is credited up to 50% toward a BuiltForProd Baseline purchased within 90 days.

What it is not

It is not a certification, not a formal compliance attestation, and not a penetration test. There is no proprietary score. Not every Assessment covers every property or system: the agreed scope, the review boundaries, the evidence available and anything that could not be verified are documented in the deliverable.

Start with a free consultation.

30 minutes with an engineer who scopes engagements, not a salesperson. We ask what you run and what decision is in front of you, then say whether an Assessment would answer it, what it would cover, and what it would cost. No preparation needed.

The calendar invite and the video link go to this address. Prefer to write? Send a message instead.

Before you book: ten questions about your own production

Two minutes, free, and private. Check every question you can answer yes to, without a caveat and without a heroic effort. Nothing here is sent anywhere: the count is worked out in your browser, nothing is stored, and no analytics event is sent.

Production readiness self-check: check each question you can answer yes to
Ten questions, no score.

Count the questions you could not check. Three or more “no” or “don’t know” answers means production is carrying risk you can name, and that is usually worth a conversation. Fewer than three and you are in better shape than most: keep the list for your next planning cycle.

Assessment questions

What is the BuiltForProd Assessment?

The BuiltForProd Assessment is a fixed-fee, evidence-based engineering assessment of your cloud infrastructure against the eight properties of the BuiltForProd Standard: secure, reliable, observable, scalable, automated, recoverable, compliant and operable. You receive findings, prioritized recommendations, a future-state architecture and a phased migration plan, about two weeks after kickoff.

Read the Standard

What does it cost?

It is a fixed fee, scaled to the scope we agree, and quoted before it starts. It is credited up to 50% toward a BuiltForProd Baseline purchased within 90 days: if the Assessment leads to a deployment, up to half of its fee comes off the Baseline. The consultation that scopes it is free.

How pricing works

How long does it take?

The complete written assessment is delivered approximately two weeks after kickoff, subject to timely access and your team’s availability. Follow-up for questions and refinements continues after delivery.

Do we have to use BuiltForProd products to be assessed?

No. The BuiltForProd Standard is the framework, and it applies to systems we built, systems we have never touched, and environments run by another provider. The migration plan is written so your own team or another partner can execute it.

Is it a certification, an audit or a penetration test?

No. It is a practical engineering assessment. It is not a certification, not a formal compliance attestation, and not a penetration test, and there is no proprietary score. It answers three questions: where are we today, what needs attention, and what should we do next.

How compliance readiness works

Does every Assessment cover every property and every system?

No. Every Assessment is scoped around your goals and your next decision rather than a fixed checklist. You choose the areas you need help with; the Standard provides the framework. The agreed scope, review boundaries, available evidence and anything that could not be verified are documented in the deliverable.

How is it different from the ten-question self-check on this page?

The self-check is free, takes two minutes and runs entirely in your browser: it is your own read on your estate. The Assessment is engineers reading your accounts, your pipelines and your runbooks, talking to your team, and writing down what they find with the evidence attached. The self-check tells you whether the conversation is worth having.

Do our answers to the self-check go anywhere?

No. The ten questions are counted in your browser. Nothing is submitted, nothing is stored, and no analytics event is sent. Close the tab and the answers are gone.

What if the Assessment says we do not need you?

Then it says so, and you keep the findings, the architecture and the plan. Disqualifying quickly is part of how we work: if BuiltForProd is not the right implementation partner, the report will still be the one you execute with someone else.

Find out what an Assessment would tell you.

A free 30 minutes consultation with an engineer who scopes engagements, not a salesperson. Bring the decision in front of you; leave knowing whether an Assessment answers it, what it covers, and the fixed fee.

The invite goes to this address. Prefer to write? Send a message.