Build n BloomFit Call
Fit Note
- What we saw
- What you told us
- What we think might be true
- What we do not know
- One useful next step
Written byBuild n Bloom
To keep whether or not you proceed.
Your roadmap is built one accepted piece at a time.
You have outcomes to reach across more than one team. You have a sponsor who answers for them, and reviewers in IT, security and procurement who must be satisfied first. We start from those outcomes and find the work that carries them.
Larger organisations start the same way: one build, accepted in writing.
That first piece has a fixed scope, agreed acceptance tests and an authorised reviewer on your side. If you want proof before a Programme, this is it. The Programme starts the quarter after you accept.
Book a Fit Call
A 25‑minute call. No files, no homework. A written note either way.
Shared foundations
Knowledge layer
Permissions
Provider setup under your agreement
Evaluation harness
Build n BloomWritten acceptance
First Build
Fixed scope
| Acceptance | Signed |
|---|---|
| Agreed acceptance tests | |
| Written acceptance |
| Scope and acceptance | ||
|---|---|---|
| Operators | IT | Finance |
A Build takes three to five weeks. It is a fixed fee quoted before you commit, with the balance due on your written acceptance.
Authorised reviewer
On your side
AcceptedProcurement
Build n Bloom
Programme
Delivery capacity and a roadmap for a quarter.
Set-upFirst two weeksDelivery streamQuarter end
Discovery across teams
Builds
Connected Builds
Enablement
Programme Care
Weekly delivery checkMonthly reportQuarterly plan
| Set-up in the first two weeks |
|---|
| Discovery across teams |
| Roadmap |
| Governance and policy pack |
| Backlog |
| First Build scoped |
| Steering and reporting each quarter |
|---|
| Hours released |
| Accepted outputs |
| Error rates |
| Adoption |
| Provider cost |
Those figures are reported as measured. None is promised.
| Enablement |
|---|
| Workshops |
| Builder coaching |
| Internal champions |
Executive sponsor
Budget holder
Build n BloomProgramme
AI Operating Policy
and Controls Pack
Included in every Programme
| It covers | |
|---|---|
| What AI may read | |
| Who approves what | |
| The audit trail | |
| A staff usage policy | |
| Provider settings |
You hold
A written policy
A permission map
A provider configuration checklist
A Programme runs under your enterprise agreement with the AI provider. We specify, you contract.
Security
The first piece gives your reviewers something exact to read
What the system may read, and who approves, is written down before it reads anything. Your operators, reviewers, IT, security and finance people shape the scope and the acceptance.
A Build takes three to five weeks. It is a fixed fee quoted before you commit, with the balance due on your written acceptance.
How we build for security is on the security page.
It becomes a Programme when two of these are true
One alone is usually a Connected Build, or two Builds. We will not sell a Programme where a Build will do.
A Programme is still Builds, each accepted in writing
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. It includes:
| Item | Included |
|---|---|
| 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 figures are reported as measured. None is promised.
The installed base is every system we have installed for you.
Delivery is checked weekly, reported monthly, planned quarterly
A Programme is bought by an executive sponsor and budget holder, with IT and security in the room. There is a weekly delivery check, a monthly report and a quarterly plan made with the sponsor.
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 holderITSecurityYour security reviewer gets the controls in writing
Every Programme includes the AI Operating Policy and Controls Pack. It covers what AI may read, who approves what, the audit trail, a staff usage policy and provider settings. You hold a written policy, a permission map and a provider configuration checklist.
A Programme runs under your enterprise agreement with the AI provider. We specify, you contract.
The team is named to you
We are two founders. A Programme is delivered by the founders plus hired or contracted engineers, named to you.
Entity, insurance and contracting arrangements for a client of your size are set up as the work is won.
It ends with 30 days’ notice at quarter end
Either side can end a Programme with 30 days’ notice at the end of a quarter. You receive a handover pack of everything built. The written guarantee has its own section for Programmes.
Bring the outcome your sponsor answers for
Twenty‑five minutes with a founder, free, and a written note either way.
Fit Call
Fit Note
Build n BloomFit Call
Fit Note
- What we saw
- What you told us
- What we think might be true
- What we do not know
- One useful next step
Written byBuild n Bloom
To keep whether or not you proceed.