Changing a logo stopped needing a deployment
Every report in the system, configurable from one settings screen — per report, per page, or per company and language.
The problem a client brought us
“Every company PDF has its letterhead baked into the template. Changing a logo means opening a code editor and redeploying.”
Before and after
A letterhead baked into each template
- Invoice
- Quotation
- Purchase order
- Every other report
Changed by an admin
One settings screen
What we found and built
A settings screen listing every report in the system, letting an admin set its letterhead per report, per page, or per company-and-language — with a live browser-side preview, because the server has no PDF rasteriser available.
Result
Zero template edits, zero deployments, to change a logo.
The pattern behind it
Make the next change a setting, not a deployment
A new logo is a setting. A new tax treatment is a category on the tax. A new operating company gets its document sequences automatically. The next change shouldn't need a developer.
How we think about problemsRecognise any of this?
Most of our work starts with a message that sounds a lot like this one did.