Skip to main content
Build n Bloom

Care keeps it working, for as long as you choose.

Your Build is accepted and its thirty days of stabilisation are over. Then a model version changes, someone new needs access, or a run fails. Somebody has to notice and put it right.

Care makes that a named responsibility. After the first thirty days, Care is a monthly choice you can cancel with 30 days’ notice. If you would sooner run the system yourself, you take the handover.

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.

Care is the named responsibility for keeping it working
Build n BloomFor Wexcombe Joinery

Care is the named responsibility for keeping it working

You receive

ItemIncluded
Monitoring and failure alerts
Fixes to prompts, rules and integrations
Model-version changes handled
Provider cost oversight against the cap
Access and permission changes
A response within one business day
A monthly note

The cap is the budget limit set on your AI provider account when the Build was installed. Usage is per token, paid to the provider in your own account.

Care Plus adds a monthly optimisation sprint

Care Plus adds a monthly optimisation sprint

You receive

  • Everything in Care
  • A monthly optimisation sprint: the evaluation set re-run on the latest real cases, exception handling extended, accuracy and speed improved, model upgrades adopted proactively
  • A quarterly review with the owner on measured use and value
  • Office Hours

The evaluation set is your real past cases with known correct outputs. Re-running it on the latest cases shows whether anything improved. We do not promise a number.

Office Hours is a monthly open hour for your team.

Three additions cover scale, hosting and speed

Programme Care. Care Plus across a Programme’s installed base, with named engineer hours, an SLA and reporting. It is quoted.

Hosted environment. For when we run the system on our infrastructure and not yours. Usage and hosting are capped at the figure in your scope. An overrun needs your written approval before it is incurred.

SLA upgrade. Same-business-day response and a named escalation, added to Care or Care Plus.

An SLA is a written standard for how quickly we respond. A named escalation is the named person a problem is passed up to.

You can run it yourself instead

You can run it yourself instead

Every Build ends with your operator and reviewer trained, a runbook handed over, and an access and ownership record. After stabilisation the choice is Care or handover.

If your people can keep it working, take the handover and do not buy Care.

Some work sits outside Care

Some work sits outside Care

Care keeps an installed system working. Moving a Build to a different model or provider is a migration, under Grow. A system we did not build comes under Care for inherited systems, in Fix.

Care does not start by itself when stabilisation ends. You choose it.

Build n BloomFor Wexcombe Joinery

Monthly note

Care

December1714212831
  • Monitoring and failure alerts
  • Provider cost oversight against the cap
  • Access and permission changes
Build n Bloom

Fixes

Fixes to prompts, rules and integrations

Under Care
Build n Bloom

Migration

Moving a Build to a different model or provider

Grow
Build n Bloom

Care for inherited systems

A system we did not build

Fix
Outside Care
The written guarantee covers paid continuing support

The written guarantee covers paid continuing support

Its terms for support are on one page.

Read the guarantee

Start with the call, and decide about Care later

Care is chosen after a Build is accepted. The first step is still a Fit Call: twenty‑five minutes with a founder, free, and a written note either way.

Book a Fit Call
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.