Skip to main content
Build n Bloom

The next goal is built the way the first was.

The first piece is accepted and your people run it. What you want from the business has not stopped there.

You want the same work sharper. Or you have a new goal: after enquiry to booked job comes finished job to full invoice. Or several teams want the change at once.

None is open‑ended. A sprint is one week, a Build is three to five, and a Programme is bought a quarter at a time.

Book a Fit Call

A 25‑minute call. No files, no homework. A written note either way.

Example job. The business shown is not a client.

A new goal takes the same steps as the first
Build n BloomFor Wexcombe Joinery

A new goal takes the same steps as the first

We find the work that carries the new goal, and a Build makes one piece real. Two or three pieces working together are a Connected Build.

Sharpening what already runs takes one week

Sharpening what already runs takes one week

An Optimisation Sprint is one week on an existing Build, to lift one measured number: accuracy, throughput or exceptions handled.

We promise the week of work, not where the number lands.

Build n BloomFor Wexcombe Joinery

Monthly note

December

1714212831
JobAgreed by
Quote from enquirySam
Final invoicePat
Questions about a jobPat
CareNamed responsibility
Monthly note
Example job. The business shown is not a client.
A migration moves a Build and tests it again

A migration moves a Build and tests it again

A Model or provider migration moves a Build to a different model or provider, then runs acceptance again. It is done one Build at a time, and priced per Build.

Care already handles a new version of the model you use.

A Programme is Builds

A Programme is Builds, bought a quarter at a time

A Programme is a sequence of Builds and Connected Builds, plus the things no single Build pays for. Each one keeps its own acceptance tests and written acceptance. What you buy is delivery capacity and a roadmap for a quarter, paid monthly in advance.

It is a Programme when two or more of these are true:

  • More than one outcome across more than one team, needing shared foundations built once.
  • The scope is discovered as you go: a roadmap and backlog re-planned each quarter, not an output fixed before signing.
  • It needs a standing team, not a project crew that leaves after acceptance.
  • There is organisational work beyond any one job: procurement and security review, change management, training at scale, governance reporting to an executive sponsor.
  • The effort exceeds what a Connected Build holds, within a quarter.
If one Build would do

If one Build would do, that is what we quote

One of those five alone is usually a Connected Build, or two Builds. We do not sell a Programme to someone who needs one Build.

Larger organisations start the same way: one build, accepted in writing. If you want that proof first, the Programme starts the quarter after you accept it.

Wexcombe Joinery

Price list, 4 November

LineItem
12Ash door blank
13Maple door blank
14
White oak door blank$112.00
15Walnut door blank
Price list, 4 November

Sam signs

Sam, office manager

Example job. The business shown is not a client.
A Programme holds six things

A Programme holds six things

ItemIncluded
Set-up, in the first two weeks. Discovery across teams, roadmap, governance and policy pack, backlog, first Build scoped.
Shared foundations. Knowledge layer, permissions, provider setup under your agreement, evaluation harness.
A delivery stream. Builds and Connected Builds from the backlog.
Enablement. Workshops, builder coaching, internal champions.
Operations. Programme Care across the installed base.
Steering and reporting each quarter. Hours released, accepted outputs, error rates, adoption, provider cost.

Those five figures are reported, not promised.

The installed base is every system we have installed for you.

A Programme runs under your own agreement with the AI provider: we specify, you contract. The AI Operating Policy and Controls Pack is included.

It is steered weekly

It is steered weekly, and ends at a quarter

There is a weekly delivery check, a monthly report and a quarterly plan made with your sponsor. Each quarter is reviewed against the Programme’s measures.

You bring an executive sponsor and budget holder, with IT and security in the room. We bring the founders plus hired or contracted engineers, named to you.

A Programme ends on 30 days’ notice at the end of a quarter. You receive a handover pack of everything built.

Build n Bloom

Programme

In place of one job for a fixed fee, you buy delivery capacity and a roadmap for a quarter. The work inside is still delivered as Builds and Connected Builds, each with its own acceptance tests and written acceptance.

Build n Bloom

Schedule

Weeks12345678910111213

Weekly

Delivery check

Monthly

Report

Quarterly

Plan made with the sponsor

Executive sponsor

In the room

Executive sponsorBudget holderITSecurity
Each Build in a Programme is covered by the guarantee

Each Build in a Programme is covered by the guarantee

Each Build or Connected Build inside a Programme is covered by the written guarantee, which also has a section for Programmes.

Any of it can be delivered in person

Any of it can be delivered in person

Any item can be delivered in person, as on-site days. They are charged at the day rate plus travel at cost.

Bring the next goal, or only the question

Twenty‑five minutes with a founder, free, and a written note either way.

Fit Call

Fit Note

Build n BloomFit Call

Fit Note

  1. What we saw
  2. What you told us
  3. What we think might be true
  4. What we do not know
  5. One useful next step
Written byBuild n Bloom

To keep whether or not you proceed.