Project Retrospectives · Published August 2, 2026
Retrospective: Where to Save Money on a Tight Budget
At half the usual budget, the way to protect quality is to cut scope rather than foundations.
This internal management system had a budget of one hundred and fifty thousand yuan against a typical three hundred thousand. The client understood the constraint and wanted the core live first. We delivered in three months, with several good calls and one mistake.
Three things we got right
Cutting to a single business line, leaving the others on spreadsheets with interfaces reserved but not built.
Reusing our component library so the admin looked consistent without custom design, saving about three weeks.
Focusing testing on money calculations and permissions, leaving visual detail to departmental acceptance.
One mistake
To save cost we skipped a data import tool, and twenty thousand historical records were entered by hand, costing the client ten extra days.
A simple Excel importer would have taken two days and paid for itself immediately.
Cut scope, customisation and edge features on a tight budget, never data accuracy or permissions. Saving in the wrong place costs more later.
← Previous post
Form Design: One Field Fewer, One Step More Completion
Next post →
How to Run a Retrospective That Works: A Real Session from Our Team
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →