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 goals decide what gets built.
A Build does not begin with a task to automate. It begins with what you want the business to do. In our example joinery, two of the three goals were from enquiry to booked job, and from the job to a full invoice.
From there we find the work inside your business that carries the goal. A Build makes one piece of it real. It runs in the tools you already have. It is tested on your own cases and accepted by you in writing, and your people are trained to run it.
Book a Fit Call
A 25‑minute call. No files, no homework. A written note either way.
Quote from enquiry
Lena RuizWebsite enquiry
QuoteLena Ruiz
Follow-upQuote
Website enquiry
Could you quote for 12 white oak cupboard doors, 720 x 450 mm, fitted before 18 December?
Wexcombe Joinery10 November
Quote for 12 white oak doors
Lena Ruiz
| Item | Amount |
|---|---|
| 12 x $112.00 | $1,344.00 |
| Fitting, 6 hours | $510.00 |
Total$1,854.00 + GST
Signed by Sam, 6:31 pm
Sam, office manager
Quote for 12 white oak doors
Build n BloomFor Wexcombe Joinery
A runbook
Build
What your people need to run it
Operator and reviewer trained
An access and ownership record
A connection inventory
Quote from enquiry
JobProofPeopleCosts
Build n BloomFor Wexcombe Joinery
Handover
Quote from enquiry
Lena Ruiz
12 white oak cupboard doors
The job itself
- One trigger: an email arrives, a form is submitted, a file lands, Monday 8am, an operator clicks
- Inputs from up to two connected systems, plus uploads
- The work: retrieval, preparation, drafting, checking, classification, routing, as many AI or rule steps as the job needs
- One accepted output a named person uses or signs: a drafted reply, a prepared pack, a filled record, a flagged list
- One operator role and one reviewer role, exceptions routed to a named person
- One simple form or review screen included; no new system of record, no multi-screen application
Proof that it works
- Installed in your existing tools, tested on your real cases (normal, adverse, incomplete)
- Written acceptance
- 30 days of stabilisation
What your people need to run it
- Operator and reviewer trained
- Runbook handed over
- An access and ownership record
- One Team Enablement Workshop
What it costs to run
- Your AI provider account set up, or yours used, with a budget cap and alerts
- A run-cost estimate
One accepted output
Build n BloomFor Wexcombe Joinery
Acceptance tests
| Case | Expected | Actual | Pass |
|---|---|---|---|
| Ordinary day | |||
| Normal | $1,854.00 + GST | $1,854.00 + GST | |
| Bad day | |||
| Incomplete | “no source found” | “no source found” | |
| Adverse | Nothing leaves without your person. | Stopped for Sam | |
Written acceptance
Sam, office managerAcceptedAcceptance tests
Sam signs
Sam, office manager
Example job. The business shown is not a client.
Build n BloomFor Wexcombe Joinery
A goal is built in pieces. Each passes one sentence.
“When ___ happens,
the system ___
so that ___ can ___.”
One trigger, one accepted output, one person who uses or signs it. That is one Build.
For example: a quote reply drafted from the price list. A weekly client report assembled from source systems. Meeting notes turned into CRM updates. Enquiry triage and routing. A billing-readiness pack per engagement.
Wexcombe Joinery
Price list, 4 November
| Line | Item |
|---|---|
| 12 | Ash door blank |
| 13 | Maple door blank |
| 14 | White oak door blank$112.00 |
| 15 | Walnut door blank |
Price list, 4 November
Sam signs
Sam, office manager
Some goals need two or three pieces working together
A Connected Build is two or three Builds that must work together for one accepted result, sharing a foundation. Intake to delivery to billing, across teams, is one. It has up to four integrations and one outcome, and takes six to ten weeks.
Build n BloomWeeks
Evidence CheckOne week
BlueprintTwo weeks
BuildThree to five weeks
Connected BuildSix to ten weeks
- 0
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
Technical ReviewTwo to three daysDays
You hold all of this when a piece is done
The job itself
- One trigger: an email arrives, a form is submitted, a file lands, Monday 8am, an operator clicks
- Inputs from up to two connected systems, plus uploads
- The work: retrieval, preparation, drafting, checking, classification, routing, as many AI or rule steps as the job needs
- One accepted output a named person uses or signs: a drafted reply, a prepared pack, a filled record, a flagged list
- One operator role and one reviewer role, exceptions routed to a named person
- One simple form or review screen included; no new system of record, no multi-screen application
Proof that it works
- Installed in your existing tools, tested on your real cases (normal, adverse, incomplete)
- 30 days of stabilisation
What your people need to run it
- Operator and reviewer trained
- One Team Enablement Workshop
What it costs to run
- Your AI provider account set up, or yours used, with a budget cap and alerts
- A run-cost estimate
Acceptance takes your written word. Payment, use or silence alone is not acceptance. The workshop is half a day, remote, for up to 12 people. Usage is per token, paid to the provider in your own account.
It takes three to five weeks
A Build takes three to five weeks, in one environment, one language and one jurisdiction. The delivery date is agreed before you pay a deposit.
It is made of parts that each do one thing
One part finds the permitted source material for a case and cites it. One drafts. One compares the draft with the source and your rules, and flags what does not match or is missing. It never approves. Where a rule beats a model, we use the rule.
None of these is sold alone.
Wexcombe Joinery
Website enquiry form
- From
- Lena Ruiz
- Item
- 12 white oak cupboard doors
- Size
- 720 x 450 mm
- Fitted before
- 18 December
Tuesday 10 November6:12 pm
Build n BloomFor Wexcombe Joinery
Reads
- Input
- Website enquiry
- Item
- 12 white oak cupboard doors
- Size
- 720 x 450 mm
Build n BloomFor Wexcombe Joinery
Reads to Finds
- Item · text
- White oak cupboard doors
- Quantity · number
- 12
- Size · dimensions
- 720 x 450 mm
- Fitted before · date
- 18 December
Structured output
Build n BloomFor Wexcombe Joinery
Finds
- Source
- Price list, 4 November, line 14
- Past quotes
- 3 similar past quotes
Build n BloomFor Wexcombe Joinery
Finds to Drafts
- Source · document
- Price list, 4 November
- Line · number
- 14
- Item · text
- White oak door blank
- Unit price · amount
- $112.00
- Precedent · documents
- 3 similar past quotes
August to October
Structured output
Build n BloomFor Wexcombe Joinery
Drafts
| Item | Amount |
|---|---|
| 12 x $112.00 | $1,344.00 |
| Fitting, 6 hours | $510.00 |
Total$1,854.00 + GST
Build n BloomFor Wexcombe Joinery
Drafts to Checks
- Draft · document
- Quote for 12 white oak doors
- Total · amount
- $1,854.00 + GST
- Terms · clause
- 3: Quotes hold for 30 days.
Structured output
Build n BloomFor Wexcombe Joinery
Checks
Checked terms of trade, clause 3
Checked: prices and totals match
Stopped for Sam
Sam signs
Sam, office manager
Example job. The business shown is not a client.
You can add seven things
| Item | Included |
|---|---|
| Additional integration. Connecting a system beyond the two a Build holds. | |
| Business Knowledge Layer. Prior work ingested (up to 5,000 documents), permissions mapped, retrieval tested for accuracy, every output cited to source. | |
| Review Screen or internal tool. A purpose-built screen beyond the included one: queue, side-by-side check, approvals. | |
| Extended Acceptance Testing. Larger case sets, adversarial cases, evidence pack for regulated work. | |
| Second site or team rollout. The same Build for another team or location, with its own cases and training. | |
| Data migration or cleanup. Getting historical data fit to use. | |
| Rush delivery. An agreed date inside half the standard timeline. |
Sometimes a Build is the wrong answer
When it is, we say so. The same job at two sites that work differently is a Build for each site, or a Connected Build. Work that needs a new database or application is a Programme. A backlog of fixes with no single output is Engineering Days. Sometimes the proportionate answer is a process fix, standard software, or nothing.
If one question stands between you and a decision, an Evidence Check answers it first. It takes one week, on a sample of your real cases.
For small workflows, Builder Coaching teaches a named member of your staff to build and maintain them. It is four sessions, with our review.
- Build
- Already have it
- Fix first
- Leave it
A Build is covered by our written guarantee
Every Build has agreed acceptance tests and an authorised reviewer on your side. Our written guarantee covers a Build and a Connected Build.
Build n Bloom
Service guarantee
Our guarantee, quoted. Not summarised.
Build n Bloom
Service guarantee
- The Blueprint
- The Blueprint fee credit
- Installation
- Stabilisation and continuing support
- Programmes
- Engineering Days and Technical Reviews
- Claims
- The limits, gathered
Build n BloomService guarantee
Installation
Each workflow or agent installation has a separately agreed scope, fixed quoted fee, deposit amount, delivery date, representative examples, core acceptance tests and authorised reviewer. The deposit is paid upfront. The remaining installation balance becomes payable on written acceptance; payment, use or silence alone is not acceptance.
Build n Bloom
Service guarantee
calendar days
14 calendar daysThirty calendar days
The Blueprint14 calendar daysAfter delivery of the complete Blueprint and its decision review
The agreed Blueprint fee is paid upfront. After delivery of the complete Blueprint and its decision review, the buyer has 14 calendar days to request a full refund if they do not believe it was worth the fee. No proof of a defect, correction round or installation purchase is required. Refund within five business days of the request. The buyer keeps the delivered Blueprint and its agreed use rights. A supported recommendation to simplify, defer or stop is legitimate; the buyer can still use the satisfaction promise.
Stabilisation and continuing supportThirty calendar daysafter written acceptance
Thirty calendar days of in-scope installation stabilisation are included after written acceptance. A core failure against the agreed tests reported during that period uses the same ten-business-day correction and linked-fee refund process, even when resolution falls after the stabilisation end date. Minor defects are corrected without charge; new features or expanded responsibility require separate agreement.
business days
five business daysten business days
The Blueprintfive business daysof the request
The agreed Blueprint fee is paid upfront. After delivery of the complete Blueprint and its decision review, the buyer has 14 calendar days to request a full refund if they do not believe it was worth the fee. No proof of a defect, correction round or installation purchase is required. Refund within five business days of the request. The buyer keeps the delivered Blueprint and its agreed use rights. A supported recommendation to simplify, defer or stop is legitimate; the buyer can still use the satisfaction promise.
Installationten business daysafter receiving the failure report and agreed lawful evidence/access
If the core workflow or an essential agent fails the agreed tests, correct and retest at no extra charge within ten business days after receiving the failure report and agreed lawful evidence/access. A pause for a genuine dependency requires documentation and an agreed revised date; provider-controlled delays are not client dependencies. A workaround or scope reduction requires the buyer’s explicit agreement.
Installationfive business daysat the end of that correction period
If the core workflow still fails at the end of that correction period, the buyer may stop. Refund all installation fees actually paid for that scope and the associated Blueprint fee actually paid, within five business days. Waive the remaining installation balance. Complete the agreed restoration and handover at no extra charge.
Installationfive business daysIf a provider-controlled delay misses the delivery date
Agree the delivery date and restoration scope before taking the deposit. If a provider-controlled delay misses the delivery date, the buyer can agree a revised written delivery plan at no extra charge or end the installation and receive the installation fees actually paid within five business days. The Blueprint remains subject to its own satisfaction promise unless the core-workflow failure remedy applies. Client dependencies and approved scope changes are documented before a revised date applies.
Stabilisation and continuing supportten-business-day correctionreported during that period
Thirty calendar days of in-scope installation stabilisation are included after written acceptance. A core failure against the agreed tests reported during that period uses the same ten-business-day correction and linked-fee refund process, even when resolution falls after the stabilisation end date. Minor defects are corrected without charge; new features or expanded responsibility require separate agreement.
Stabilisation and continuing supportten business daysafter receiving the scope-listed evidence/access
The promise follows the commissioned job across workflow, agent, integration and governance installation services; it is not a guarantee of every illustrative design or a promise to install the entire firm-wide path. Free fit calls and demonstrations carry no paid-fee refund. Optional managed operation and other paid continuing support use their agreed written service checks. If those checks fail, correct without extra charge within ten business days after receiving the scope-listed evidence/access; genuine dependency pauses require a documented, agreed revised date. If the agreed service still fails, the buyer may end that support service and receive the fee actually paid for the affected billing period within five business days; no remaining future support balance is due. This refunds the affected support period, not the original installation or Blueprint again. Support does not start automatically or renew the installation refund promise.
Stabilisation and continuing supportfive business daysIf the agreed service still fails
The promise follows the commissioned job across workflow, agent, integration and governance installation services; it is not a guarantee of every illustrative design or a promise to install the entire firm-wide path. Free fit calls and demonstrations carry no paid-fee refund. Optional managed operation and other paid continuing support use their agreed written service checks. If those checks fail, correct without extra charge within ten business days after receiving the scope-listed evidence/access; genuine dependency pauses require a documented, agreed revised date. If the agreed service still fails, the buyer may end that support service and receive the fee actually paid for the affected billing period within five business days; no remaining future support balance is due. This refunds the affected support period, not the original installation or Blueprint again. Support does not start automatically or renew the installation refund promise.
Programmesten-business-day correction periodif its core workflow still fails the agreed tests
A Programme buys delivery days per quarter, paid monthly in advance. Every Build or Connected Build delivered inside it keeps its own agreed scope, representative tests, authorised reviewer and written acceptance, and the installation promise above applies to each one: if its core workflow still fails the agreed tests at the end of the ten-business-day correction period, the buyer may stop that Build and receive the fees actually paid for that Build’s scope within five business days. Across the Programme as a whole, refunds are capped at the fees actually paid for the current quarter; days already delivered against accepted work are not refunded. Either party may end a Programme with 30 days’ notice at the end of a quarter, and the buyer receives a handover pack of everything built.
Programmesfive business daysthe buyer may stop that Build
A Programme buys delivery days per quarter, paid monthly in advance. Every Build or Connected Build delivered inside it keeps its own agreed scope, representative tests, authorised reviewer and written acceptance, and the installation promise above applies to each one: if its core workflow still fails the agreed tests at the end of the ten-business-day correction period, the buyer may stop that Build and receive the fees actually paid for that Build’s scope within five business days. Across the Programme as a whole, refunds are capped at the fees actually paid for the current quarter; days already delivered against accepted work are not refunded. Either party may end a Programme with 30 days’ notice at the end of a quarter, and the buyer receives a handover pack of everything built.
Engineering Days and Technical Reviewsfive business daysIf Build n Bloom ends a prepaid block early
Day-rate work is delivered against a written backlog with a definition of done for each item, so there is no single accepted job for the installation promise to test. Instead, any item that is defective against its definition of done is redone at no charge within 30 days of delivery. If Build n Bloom ends a prepaid block early, unused days are refunded within five business days.
days
30 days
Engineering Days and Technical Reviews30 daysof delivery
Day-rate work is delivered against a written backlog with a definition of done for each item, so there is no single accepted job for the installation promise to test. Instead, any item that is defective against its definition of done is redone at no charge within 30 days of delivery. If Build n Bloom ends a prepaid block early, unused days are refunded within five business days.
Programmes30 days’ noticeat the end of a quarter
A Programme buys delivery days per quarter, paid monthly in advance. Every Build or Connected Build delivered inside it keeps its own agreed scope, representative tests, authorised reviewer and written acceptance, and the installation promise above applies to each one: if its core workflow still fails the agreed tests at the end of the ten-business-day correction period, the buyer may stop that Build and receive the fees actually paid for that Build’s scope within five business days. Across the Programme as a whole, refunds are capped at the fees actually paid for the current quarter; days already delivered against accepted work are not refunded. Either party may end a Programme with 30 days’ notice at the end of a quarter, and the buyer receives a handover pack of everything built.
quarter
current quarter
Programmescurrent quarterpaid monthly in advance
A Programme buys delivery days per quarter, paid monthly in advance. Every Build or Connected Build delivered inside it keeps its own agreed scope, representative tests, authorised reviewer and written acceptance, and the installation promise above applies to each one: if its core workflow still fails the agreed tests at the end of the ten-business-day correction period, the buyer may stop that Build and receive the fees actually paid for that Build’s scope within five business days. Across the Programme as a whole, refunds are capped at the fees actually paid for the current quarter; days already delivered against accepted work are not refunded. Either party may end a Programme with 30 days’ notice at the end of a quarter, and the buyer receives a handover pack of everything built.
You know the fee before you commit
A Build is quoted as a fixed fee before you commit. You pay a deposit up front, and the balance when you accept the work in writing.
What shapes the fee: how many systems the job connects, how much testing the work needs, how many sites or teams it covers, and how fast you need it.
Build n Bloom
The scope in writing
- Scope
- One accepted output a named person uses or signs
- Tests
- Acceptance tests on normal, adverse and incomplete cases
- Review
- Written acceptance
Build n Bloom
The fixed fee
You get a fixed fee in writing before you commit. It is the same for every client.
Build n Bloom
Build n Bloom
You commit
Build
- Time
- three to five weeks
- Date
- The delivery date is agreed before you pay a deposit.
- Acceptance
- Acceptance takes your written word.
You
Bring the goal, or only the question
If you know what you want the business to do, bring that to a Fit Call. If you do not, bring the question. The call is free, 25 minutes, and with a founder.
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.