C3 · DEL.6 → FIN.2 · Example design

See why accepted work is still unpaid

Delivery acceptance, an invoice and a payment answer different questions. Match all three in a fictional engagement to expose an unsupported charge and show exactly what remains outstanding.

Run this workflow example ↗Discuss this kind of work ↗How a Blueprint is scoped

FROM THE FIRST RECORD TO THE NEXT REVIEWAccepted milestone → collected cash

For finance owner and managing partner. Example design, with the source, receiving owner and human review shown at each step. Your Blueprint’s three opportunities are selected after measurement.

01 / HANDOFF DESIGN

What goes in. What comes out. Who decides.

Select a stage to inspect the records it needs, the work it prepares and the person who accepts or returns it. Follow a role link to try its own fictional example.

C3 · DEL.6 → FIN.2EXAMPLE DESIGN · HUMAN REVIEW AT EACH STEP

Choose a step to see the input, prepared output and person who decides. The complete sequence remains available below.

Selected handoff / 01

Accepted work

Engagement lead owns this step.

What goes in: Issued deliverable and contract condition
What comes out: Acceptance or exception record
Try a supporting role: Case coordinator
Allowed sources and actions: Current signed milestone boundary
Who decides: Client / lead confirms acceptance

Other stop and return routes

A client dispute at collection returns to the account partner (REL.2), engagement lead (DEL.6) and finance owner to reconcile acceptance, scope and signed payment terms before any action.
A partial payment remains an open receivable until finance records the remaining balance or an authorised resolution; invoice issue alone is not cash.

Read the full handoff and exception sequence

Accepted work (DEL.6) — Engagement lead receives issued deliverable and contract condition and produces acceptance or exception record. The handoff is acceptance receipt. Client / lead confirms acceptance.
Invoice basis (FIN.2) — Finance owner receives acceptance, terms and time/fee and produces reconciled invoice evidence. The handoff is matched invoice packet. Finance resolves mismatch.
Invoice decision (FIN.2) — Finance owner receives matched packet and produces approved invoice or hold. The handoff is invoice id and receivable. Finance approves issue.
Collect / resolve (FIN.2 / REL.2) — Finance + account partner receives receivable and client response and produces cash, dispute or write-off route. The handoff is collection or dispute receipt. Finance approves collection action.
Cash record (FIN.2) — Finance owner receives bank/ledger event or approved resolution and produces collected contribution or explicit open balance. This is the recorded outcome. Finance signs reconciliation.

Return path: Amount mismatch / invoice hold sends work from Invoice decision to Invoice basis.

A client dispute at collection returns to the account partner (REL.2), engagement lead (DEL.6) and finance owner to reconcile acceptance, scope and signed payment terms before any action.

A partial payment remains an open receivable until finance records the remaining balance or an authorised resolution; invoice issue alone is not cash.

02 / WHY ASSESS IT

What would make this worth changing?

Fewer missing invoice prerequisites and avoidable delays may improve collected contribution; an invoice is not cash.

MEASUREMENT BASIS

Records to inspect

Signed payment term, authorised milestone, acceptance evidence, invoice and bank/ledger receipt.

STOP / RETURN

Where it can fail

Missing acceptance, amount mismatch, duplicate attempt or dispute blocks issue and returns to delivery, relationship or finance.

DESIGN ACCEPTANCE

Cases to test

Test accepted/unaccepted milestones, changed terms, duplicate retry, dispute and partial payment; reconcile IDs and cash.

03 / SPECIALIST ROLES

Give each supporting role a clear job.

These candidate roles prepare specific parts of the work. Inspect the output and the reviewer before deciding whether a person, existing software, a rule or AI role is appropriate.

COORD

Case coordinator

Show who needs to act, what is overdue and which earlier decision is holding up the case.

Human review: The operations or account owner approves commitments and resolves missing cover. This example sends no reminders or reassignments.

Try this role’s example ↗

COMMERCIAL

Commercial analyst

Check scope and cost for sales, or reconcile milestone, invoice and payment for finance.

Human review: The partner and finance owner approve fees, terms, invoices and collection decisions. Sales and finance keep separate source access.

Try this role’s example ↗

CHECK

Quality checker

Compare the proposed output with the original evidence and explain each discrepancy.

Human review: The named reviewer decides whether to correct or issue the work. A clean check is not professional sign-off.

Try this role’s example ↗

All ten roles ↗

Find out whether this could improve your firm’s capacity

Start with a no-fee Firm Capacity Fit Call about a constraint on client work. If the paid Blueprint is the right next step, it measures one important revenue path, fully designs three connected improvements and ranks the first installation. A simpler process or no installation may be the right answer. Installation is separately scoped; pricing is quote-specific.

Book a free Fit Call ↗

Two promises.
In writing.

A clear Blueprint decision—or your money back.

14 calendar days after complete delivery and the decision review to request your Blueprint fee back.

No defect proof or installation purchase is required. We refund the fee actually paid within five business days. You keep the delivered Blueprint and its agreed use rights.

The agreed workflow works—or both fees back.

If the core workflow or an essential agent fails the agreed tests, we correct and retest within ten business days after the failure report and agreed lawful evidence/access. If it still fails, you may stop. We refund the installation fees actually paid and the associated Blueprint fee actually paid within five business days, with no duplicate refund.

How the guarantee works

Deposit upfront. The remaining installation balance is due only on written acceptance.

If the core workflow or an essential agent fails its agreed tests, we correct and retest within ten business days after the failure report and agreed lawful evidence/access. If it still fails, you may stop: installation fees actually paid and the associated Blueprint fee actually paid are refunded within five business days, with no duplicate refund. The remaining balance is waived; agreed restoration and handover are included.

30 calendar days of in-scope stabilisation follow written acceptance. Later support is a separate choice; no automatic retainer.

A clear Blueprint decision — or your Blueprint fee back. An agreed workflow and its essential agents working against their written tests — or the installation fees paid and the associated Blueprint fee back. Agreed ongoing service checks — or the affected support-period fee back.

This voluntary guarantee applies to new engagements agreed from 27 September 2026. It covers the defined Blueprint decision, separately scoped workflow-and-agent installation and separately scoped support service, not revenue, savings, professional judgement or client action. A third-party outage is outside the promise, but does not excuse a failure of Build n Bloom's agreed configuration or integration work.

The promise covers the agreed deliverable and written tests, not revenue, savings, adoption or professional judgement. Free calls and demos carry no paid-fee refund. Statutory rights remain unaffected; full terms apply.

Read the full terms and claim process