We build niche products for specific industries. Agencies, interior designers, small employers, real estate associations. Different customers, different problems... but they all share the same foundations underneath, and they share these rules.
None of these came from a whiteboard. Every one of them came out of a real decision in a real week, and each links back to the studio log where it happened.
Trust first
1. Anything that emails your client is opt-in.
Your client relationship is yours. The first time software sends something in your name that you didn't expect, you stop trusting it... and you switch the whole thing off. So automations that talk to clients start switched off, and you can see exactly what's queued before you turn them on. (Week 27)
2. New things your client can see start switched off.
Every business shares differently. If we switch a new view on for everyone, some people find out from their client. Nothing new becomes visible until you decide it should. (Week 28)
3. New money settings ship switched off.
If your margin changes overnight, even for a good reason, the first thing you feel is "what just happened?". You choose the moment your numbers change. And anything that touches money gets a second, separate review before it ships. (Week 30)
4. Every automation needs an undo window.
People drag cards around to think. So automations wait (24 hours by default in Arbeo), and undoing the action cancels them. A little slower... and trustworthy enough that you'll actually turn it on. (Week 34)
5. Approval is a label, not a gate.
A greyed-out pay button because someone's on leave helps nobody. Approvals and questions are visible and trackable, but they never block the person who's ready to pay. (Week 37)
When we do switch something on by default, we say why. Pay-by-bank is on because it costs your client nothing and costs you less than card. Files that release on payment are on because nothing reaches your client until you send the invoice. If we can't explain the exception in a sentence, it isn't one.
Where AI stops
6. Give AI read access before write access.
Our AI connectors start read-only. You can try them on real data without worrying about what they'll do, and we add actions one at a time once we see which ones people actually want. Decisions about people stay with people. (Week 35)
7. AI drafts, people decide.
AI pre-fills a bill, but it never invents an amount. It drafts a mood board, but you choose what the client sees. It suggests milestones for you to review. (Weeks 28 and 29)
Honest numbers
8. When a data change could lose something, pick the version where nobody loses anything.
Copy rather than move. Build the bigger model later, when real requests show it's needed. (Week 36)
9. Don't draw a guess like a fact.
Forecasts and actuals don't share a style. Converted figures say they're converted. Missing data shows as "—", not a guess. (Weeks 33 and 39)
10. If it matters and changes slowly, send it to people.
A number on a dashboard is a number nobody looks at. The important, slow-moving figures come to your inbox on a schedule. (Week 38)
How we ship
11. Put the page up before you build the thing.
An honest early-access page tells us who wants it, and what they need, before we write any code. (Week 29)
12. Shipping and launching are different days.
Merging is a promise to ourselves. Launching is a promise to you that it's ready. We launch when the product, the docs and the page all agree. (Week 31)
13. Fast deploys make small changes.
Our deploys take about nine minutes, so small changes ship the moment they're ready instead of waiting in a big batch. Smaller batches are easier to check and quicker to reach you. (Week 32)
14. Do quality in sweeps, then lock it in.
"We'll make it accessible as we go" never quite happens. So we did accessibility across three codebases in one week, with automated checks that stop it slipping back. (Week 33)
15. Fewer choices for the buyer.
Pricing tiers are a tax on attention. One plan, everything included. (Week 39)
If you want something built this way for your industry, that's what we do.
— Daz
Consulting Inquiries
