Partners

Work with us

We build one narrow thing well: the production foundation, the architectures on it, and the engineers who operate them. Everything around that is better done by someone else.

What the partner program is

The BuiltForProd partner program has four tracks: referral, delivery, technology and cloud marketplaces. They exist because the work around a production foundation — the application build, the migration, the audit, the tooling that watches it — is work we deliberately do not do.

Partnering with us should be simple: we deliver a defined outcome at a fixed fee, we keep no standing access to the customer’s environment afterward, and we hand over everything. There is no lock-in for us to protect and therefore nothing awkward to negotiate around.

Referral partners

Who this is for

Consultancies, agencies, fractional CTOs, auditors, investors and anyone who repeatedly meets teams with a production problem they do not want to own.

How it works

You make an introduction. We qualify honestly, including telling the customer when we are not the right fit, and we keep you informed at every stage. A referral fee is agreed in the partner agreement.

It fits when

You have the relationship and the trust, and no interest in building a landing zone yourself.

Delivery partners

Who this is for

Cloud and DevOps consultancies with their own engineers who want a finished foundation underneath their work rather than a blank repository.

How it works

We deliver the Baseline and the Blueprints; you deliver the application work, the migration or the ongoing engagement around it. Your team is trained on the platform and works from the same documentation ours does.

It fits when

You want to spend your engineering hours on the part your customer is actually paying you for.

Technology partners

Who this is for

Compliance automation, observability, security and developer tooling vendors whose products sit next to a production foundation.

How it works

The platform exposes documented attachment points — a notification topic, an event bus, an observability sink, the audit archive and pipeline apps — with integration guides. We document how your product connects, and we say plainly that it is an integration point rather than a native integration.

It fits when

Your customers keep asking who builds the foundation your product observes, secures or evidences.

Cloud marketplaces

Who this is for

Customers and resellers who would rather transact through their existing cloud agreement than onboard a new vendor.

How it works

Offerings are available through an AWS Marketplace private offer: you pay with your AWS account, on your consolidated bill, with your existing discounts, and the spend counts toward your commitment.

It fits when

Procurement is the slowest step in the deal, and there is cloud commitment to draw down.

Who we work with

Compliance and audit

Compliance automation vendors and audit firms. Their customers need real technical controls and evidence sources underneath the program. What the foundation produces.

Observability and security vendors

Products that watch, scan or protect a production environment connect through the platform’s documented attachment points, with an integration guide for each.

Agencies and software houses

Teams that build a client’s product and then face the question of who runs it. The client gets a foundation they own; you keep your focus on application code.

Investors and accelerators

Platform teams inside funds and programs, where the same infrastructure question arrives with every portfolio company after a round closes.

Fractional CTOs and advisors

People who are asked to make the build-or-buy call on infrastructure and would rather make it with a comparison than a vendor pitch. The honest comparison.

Resellers and integrators

Organizations that transact through cloud marketplaces or existing procurement relationships, where a private offer removes the slowest step in the deal.

How to get in touch

Email [email protected] with what you do, the kind of customers you work with, and which track sounds closest. You will get a reply from a person.

The first conversation is about whether the overlap is real. If it is, the second is about the agreement and how customers get introduced. If it is not, we will say so — the same way we do with customers.

Useful before you write

Press enquiries and general questions go through the contact page instead.

Questions about partnering

What does the partner program cover?

Four tracks: referral partners who introduce customers, delivery partners who work alongside our engineers, technology partners whose products attach to the platform, and transacting through cloud marketplaces. Each has its own agreement.

How are referral fees structured?

As a percentage of the engagement, agreed in the partner agreement before any introduction is made. Terms are set per partner rather than published, because the right structure depends on how much of the sale the partner carries.

Can we resell BuiltForProd?

Not under the standard license. The source we deliver is licensed to the customer for internal use, and it cannot be resold, sublicensed, hosted publicly or used to provide managed services to third parties. Reselling arrangements are handled separately, so talk to us first.

The license

Do you take our customer relationship?

No. A referral partner stays the customer’s trusted advisor and a delivery partner keeps the engagement it owns. We are deliberately narrow — the foundation, the workload architectures and operating them — and we do not compete for application work.

Do you integrate natively with our product?

We will document how it connects, and we will not overclaim. The platform exposes five documented attachment points and ships integration guides for them. Tools such as observability, paging, chat and ticketing platforms connect through those points; they are integration points, not built-in integrations.

How do we get started?

Email [email protected] with what you do and the kind of customers you work with. The first conversation is about whether there is real overlap; if there is not, we would rather say so than sign a partner agreement nobody uses.

Start a partner conversation.

Tell us what you do and the kind of customers you work with. If there is no real overlap we will say so, which is cheaper for both of us than a partner agreement nobody uses.