Agency billed separately for a 'service blueprint' during the UX phase — what is this, and do we have to pay extra?

In business, you never pay for any extra line item that didn't have written approval. A service blueprint is a great deliverable for operationally heavy businesses like healthcare—it'll even save you thousands of pounds in logic errors during development. But the agency doesn't get to just say 'we did this, now pay up'.

Do you have a change management clause in your contract? Standard agency contracts in the UK require a signed approval document in advance for any work that exceeds the budget. If that clause is in there, you can reject the invoice outright.

Send the agency a clear email: 'Our contract is fixed-fee. Any additional work carried out without my written approval does not constitute a financial obligation. I recognize the value of the work, but I do not accept the charge.' Start the discussion from there.

We paid a separate consultant 3,000 GBP for a service blueprint for our logistics platform. 2,800 GBP is standard market rate, but we ordered it intentionally and knowingly. Hitting you with a surprise invoice is just unprofessional on the agency's part.

they usually keep service design and ui design separate on purpose but they should've told u upfront. tacking it onto the invoice after the fact is super shady definitely don't back down.

If the scope of work in the contract is defined as 'Comprehensive UX' without specified exclusions, analysis tools inherently part of that process fall under the agreed fee. You are legally entitled to dispute any unauthorized invoice items.

They probably ran into an operation that was far more complex than they anticipated at the start, and now they're trying to recoup their overtime this way. Don't let them bill you for their own miscalculations.

The document is genuinely useful and necessary for your operations, no question about that. But billing it without your sign-off is unfair. Keep the blueprint, but insist that they absorb the cost into the originally agreed 14,000 GBP.

My questions are cleared up, thanks.

Thanks for writing this, that's the right way. Weekly written progress reports are much more useful than asking for dates.

Implementing a change request process doesn't slow things down, it speeds them up. Correct me if I'm wrong.

You're right.

I've been down this road, let me tell you. Weekly written progress reports are much more useful than asking for dates.

Trying to do this alone is the most expensive way. Of course, it varies if your situation is different.

We experienced almost the exact same thing last year. tbh hasty decisions become decisions you have to fix six months later.

Proven by experience.

Let's separate the concepts, they're getting mixed up. Code without setup documentation isn't yours, even if you have it.

Of course, it varies if your situation is different.

Just a heads-up. If you don't write this down from the start, it leads to arguments later.

Ask who prepared the quote and who will actually do the work. Of course, it varies if your situation is different.

Same here. The real issue isn't the number, but what it's based on.

I went through the same thing two years ago. The biggest time-waster for us was not knowing who had the final say.

Mistakes made on the ux service blueprint side are usually reversible but expensive. This is my opinion, I'm not claiming it's absolute truth.

Exactly like that. Solutions that work at a small scale collapse when you grow; I learned this late.

If acceptance criteria aren't written when the work is done is open to debate. If I were you, I'd go this route.