Your brand, not ours

Look at the software on this site and you'll notice something odd for a studio portfolio: almost none of it looks like us. Hartley OS is violet. BookIt is cobalt. Fern & Bean's dashboard is cream and forest green. The mint code-rain stops at the edge of every build, because the build isn't ours — it's theirs.

That's a design decision with teeth. When software carries your name and your colours, your team treats it as yours: adoption stops being a training problem, because nobody needs persuading to use 'our system'. And when a customer sees your booking portal, they see a business that has its act together — not the logo of whatever platform you're renting this year.

It's also an honest signal about ownership. Off-the-shelf tools rent you a seat inside their brand, and 'making it yours' means a settings page and an uploaded logo. A custom build inverts that: the system is an asset on your side of the ledger. It looks like you because it is you — your workflows, your language, your rules encoded.

So when we show off our work, the brief includes disappearing. The only place Zion's fingerprints should show is in how it runs: fast, boring to maintain, and quietly cheaper every month than the stack it replaced. Software that pays for itself — wearing your badge, not ours.