Qutira CRM
The system the studio runs on: every client account, asset, domain, subscription and renewal in one place, with reminders that escalate before anything lapses.
The problem
The studio ran on a spreadsheet. Every client site, domain, subscription, renewal date and invoice lived in one workbook whose totals agreed only because somebody kept making them agree, and a renewal nobody notices is a client’s site going dark. An agency that sells systems has exactly one honest way to prove it builds them: run its own business on one.
The system
- 01
One place for everything with a date on it
Client accounts, assets, domains, subscriptions, contracts and invoices sit in one system, each carrying the date it comes due. Reminders escalate at 120, 45, 7 and 1 days across email, Slack and Telegram, and every message carries signed links that snooze the item or mark it done straight from the inbox, with no login and no dashboard visit. Overdue invoices keep chasing daily until they are settled or cleared.
- 02
A system that refuses to guess
Every money and date row carries a verification level, from a document on file down to nobody has established this yet. A figure nobody can support is named and left out of the totals rather than estimated into them, and the interface says which rows were excluded and why. The arithmetic is asserted inside the build itself: a deploy that breaks the numbers fails before it ships.
- 03
The app decides, the automation sends
The application owns the rules: what is due, to whom, on which channel, and whether it has already been sent this cycle. A separate automation layer does the delivery, so the app holds no messaging credentials of its own. Every write is logged: what changed, from what, to what, and when.
The result
It replaced the workbook and runs the studio’s operations today: nine sections, 22 data models, roughly 18,600 lines of TypeScript, and 68 tests that run inside every build. The screenshots on this page come from an isolated copy seeded with invented accounts; the live system holds client data and is never shown.
Have a problem shaped like this? We reply within two business days.