Studio Cashflow Case Study: When Good Work Is Not Enough to Make Payment Ready

A studio cashflow case study rarely begins with a finance problem. It usually begins with a site conversation: “Can you just move that?” A revised drawing arrives after fabrication has started. Photos are sent on WhatsApp. The work is completed, but the client says they need to inspect it before approving the invoice. By then, the studio has paid for labour, materials and specialist suppliers, while the basis for payment readiness rests on a conversation nobody can reconstruct properly.

This is an illustrative composite case study, not a report of an actual Bespea customer or measured product outcome. The project value and events are illustrative. They describe a familiar pattern in high-value bespoke fit-out and joinery work, and how a more disciplined governance process could address it.

The project: profitable on paper, tight in reality

A specialist joinery and fit-out studio secured a £280,000 package for a private members’ club refurbishment. Its scope included a reception desk, wall panelling, banquette seating, display joinery and specialist metal details. The work was technically demanding, visually important and subject to a compressed programme.

The agreed payment schedule looked sensible at the outset: a deposit, a manufacturing-stage payment, a delivery payment and a final balance following installation and sign-off. The studio had costed the project carefully. Its cashflow plan depended on those stages progressing in line with the agreed terms.

But the payment schedule depended on something more fragile than the spreadsheet suggested: clear agreement on what each stage meant, what evidence would support review, and who had authority to accept it.

During manufacture, the designer asked for a change to the reception desk’s feature trim. The instruction came during a site walkaround and was followed by photographs and a short WhatsApp exchange. The workshop had already machined part of the original detail. To protect the programme, the studio remade the affected components immediately.

No one was trying to create a problem. The client wanted a better result. The designer wanted the instruction actioned quickly. The studio wanted to be helpful. Yet the change had a cost, a programme effect and a consequence for the next milestone. Neither those consequences nor the authority to approve them were clearly recorded before work proceeded.

Where the cashflow problem appeared

The studio delivered the reception desk and substantial joinery to site. Its project manager believed the manufacturing and delivery milestones had been achieved. The client team believed final approval would happen only after complete installation, visual review and resolution of a separate issue concerning the panelling alignment.

The invoice went in. The response was not a refusal to pay. It was uncertainty: “We need to confirm where we are against the changes.”

The accounts team was waiting for a clear decision from the project team. The project team was discussing the changed desk detail, delivery condition, incomplete installation and a snag as though they formed one question. Meanwhile, the studio had supplier invoices falling due.

The studio was left assembling evidence from email threads, phone notes, drawing folders, delivery notes and messages. It could show that work had been done. What it could not show quickly was the decision history: what had originally been agreed, what changed, whether the change had been authorised, which milestone was ready for review, and what remained unresolved.

A defined challenge should remain connected to the work it concerns rather than silently rewriting unrelated acceptance decisions. That does not determine whether a payment may be withheld under the contract. Equally, a contractor should not expect acceptance or payment simply because it says work is complete. Both sides need a record connecting scope, evidence, authorised decisions and the resulting project state.

Studio cashflow case study: the control points to establish

The studio did not need another project management tool. It needed a governed record of the decisions that changed the commercial state of the project.

For a subsequent project, the approach would be to define milestones with acceptance criteria and authorised human decision-makers before work reached the point of sign-off. Evidence would be submitted against those criteria. Changes affecting cost, programme, quality, responsibility or acceptance would be recorded when they occurred rather than reconstructed later.

The sequence would be:

Define the milestone → Capture evidence → Submit → Accept or Challenge → Preserve the Decision → Establish Payment Readiness.

Payment readiness would not mean that Bespea released money or decided that an invoice must legally be paid. It would mean that the project had a governed, evidence-backed record showing the state reached by the relevant work, including outstanding decisions. Payment itself would remain between the parties, subject to their contract and applicable requirements.

Set milestones around real decisions

Broad labels such as “manufacture payment” can carry different meanings for different people. A clearer milestone identifies the deliverable, acceptance criteria, required evidence and the person authorised to make the relevant decision for the relevant party.

A role or membership can establish participation. It does not automatically establish authority to make a consequential project decision. Being the designer, project manager or platform administrator is not, by itself, permission to approve a change or accept a milestone.

For example, a manufacturing milestone for a bespoke bar unit might require approved shop drawings, photographs of completed carcasses and finished visible faces, confirmation of specified hardware, and a record of agreed exclusions pending site access. An installation milestone might identify what must be fitted, the relevant tolerances and how outstanding remedial work will be recorded separately from the acceptance decision.

This does not make the project rigid. Bespoke work requires judgement. It makes the point at which authorised human judgement is needed visible, rather than leaving it buried in a message thread.

Submit evidence while the work is fresh

Photographs, quality checks, delivery notes and timestamps become more useful when connected to a defined milestone and its acceptance criteria. Where a material substitution is proposed, the record should identify the alternative, the reason, supporting samples and the decision required.

That is more useful than a late bundle of photographs labelled “site pics”. The reviewer can see which requirement each submission supports, rather than merely that somebody took a photograph on a particular day.

Evidence does not remove the need for inspection or constitute acceptance by itself. It gives review a clearer basis. A challenge can identify the relevant criterion, evidence and concern rather than relying on “that’s not what we agreed”.

Record changes before they become rework

Change control should preserve the relationship between the agreed baseline and the proposed revision. A site instruction can be raised quickly, but material consequences should be recorded: revised scope, estimated cost and programme impact, supporting drawings or images, and the authorised decision being requested.

The earlier baseline should remain traceable. A revised drawing should not silently replace the information relied upon when manufacture started.

Not every small clarification requires a heavy formal workflow. The practical test is whether it alters cost, time, quality, responsibility or the basis on which a milestone will be accepted.

Where immediate action is genuinely necessary, the record should preserve uncertainty. It might show that work is proceeding at risk pending confirmation, or that a limited enabling action has been agreed without approval of the full cost. Recording that position does not create authority, turn a proposal into approval or replace the contract or professional advice.

Accept or challenge defined work

If a concern arises about one run of panelling, the record should identify the item, relevant criterion, evidence, challenge and response. Any agreed corrective action should remain separately traceable.

An existing acceptance decision concerning other defined work should not disappear because a new concern is raised. Equally, a recorded acceptance does not automatically determine the value payable, create a partial-payment entitlement or transfer funds.

The purpose is to make the state of the work reviewable: what has been submitted, what has been accepted by an authorised human, what remains challenged and what still requires action. The parties must assess the commercial consequences under their agreed terms.

The commercial result to seek

The commercial result is not “faster payment by software”. It is less ambiguity at the moment payment decisions have to be made.

A shared decision history would give the studio and client a clearer view of what had been agreed, what had changed, what evidence had been submitted and which decisions remained outstanding. It would provide a more dependable basis for reviewing payment readiness than an invoice accompanied by a retrospective bundle of screenshots. These are intended benefits, not measured outcomes from this illustrative case.

Bespea’s governance model connects important authorised decisions with their evidence and attributable history. A Decision Passport records the governed decision: what was proposed, what evidence supported it, who acted, for which party, under what authority, what was decided and what happened next. A challenge remains part of that history rather than silently rewriting it.

Proof Packs provide a portable, tamper-evident record of governed project evidence and decision history. They are not public by default. Their integrity does not, by itself, establish workmanship quality or contractual entitlement.

Bespea sits alongside the tools already used to design, communicate, manage and account for the project. It does not replace them. It provides the governance and evidence layer connecting important project decisions; it does not make those consequential decisions on behalf of the parties.

It does not hold money, release funds, provide escrow, guarantee payment or decide contractual entitlement. It does not decide who is legally right in a dispute.

Bespea preserves the decision you may need to prove later.

What studio owners should take from this

Cashflow protection is often discussed as deposits, credit control and tighter payment terms. Those matter, but they are only part of the picture. A disputed or unclear project state can leave teams struggling to assess an invoice even when substantial work has been delivered.

The useful question is not simply, “Have we sent the invoice?” Ask: “Can both parties see the agreed milestone, material changes, supporting evidence, authorised acceptance or challenge, and remaining actions without reconstructing the story across six systems?”

If the answer is no, the project is relying on goodwill and memory at precisely the point where pressure is highest.

Build the record before the site instruction, before the remake, and before “Sent you the photos on WhatsApp mate” becomes the only context for work worth thousands of pounds.