Case Study · Our own operation
The client in this one is us.
Over 10,000 hours of client work and more than 230 software projects since 2020 have run through software we wrote for ourselves, because we are the same shape as the companies we build for: small, busy, and with nobody whose job is IT.
At a glance
- Client
- Albright Labs (yes, really)
- Industry
- Software and consulting
- Engagement
- Our own operations stack
- Running since
- 2020
10,000+
hours of client work since 2020
What runs on it
10,000+
hours of client work since 2020
230+
software projects shipped since 2020
14
free audit tools built and running
2020
first invoice through it, in January
Counted from production on 3 October 2026. Hours worked out from billed client work since 20 January 2020.
The problem
Nobody here has IT as their job.
That is the condition we build for, and it is our own. There is no IT department, no ops hire, and no afternoon set aside for maintaining the tools. Everything that keeps every client relationship moving has to run without supervision, or it does not get run.
The default answer is to buy a subscription for each problem: one tool for invoices, another for time, a CRM, a project tracker, something for email, something for calls. Each is reasonable on its own. Together they become a stack nobody owns, where the same client exists five times with five slightly different names, and where the answer to any question about the business depends on which tab you ask it in.
What we built
One system, extended a piece at a time.
Not a platform built in one go. A single October CMS application that started with clients and invoices in 2020, and has had a piece added whenever something became annoying enough to be worth an afternoon. Clients, contacts, agreements, invoices, recurring billing, time tracking, tickets, tasks, expenses and profit-and-loss reporting all read from the same records, so there is one answer to any question rather than one per tool.
The parts added most recently are the ones that show what changes when you own the stack rather than rent it.
Calls become work
Recorded calls sync in, and each one is read into six lists: our to-dos, follow-ups, what we are waiting on the client for, risks, opportunities and decisions. One click turns an item into a task carrying the call as context.
Billing that argues back
Recurring invoices, service renewals and time entries reconcile against each other. When a draft slips its issue date it still goes out rather than sitting stranded, which is a bug we found in our own books before a client found it in theirs.
Fourteen free audit tools
Site, AI visibility, SEO, accessibility, performance, security, schema, local and more. A Python analyzer set behind the site, returning a report anyone can run without talking to us first.
Software that reports its own problems
Our site and products send their errors to us automatically. Each one becomes a support ticket with the details, worked through Brightwork, with a person approving every fix before it ships.
We find our own bugs in our own books first. That is the argument for running on what you sell, and it is also the uncomfortable part.
What it cost
This is not free, and we would not pretend otherwise.
Owning the stack means owning the bugs. An invoice that should have sent and did not is our fault, not a vendor's, and we are the ones who find it. Six years of additions also means six years of decisions to live with, some of which we have since had to undo in public.
What buys it back is that nothing is waiting on someone else's roadmap. When a call needs to become a task list, that is an afternoon rather than a feature request. When billing needs to behave differently for one client, it does. And the answer to any question about the business is one query, because there is one place the answer lives.
That trade is the whole decision, and it is the same one we walk clients through. It is worth making when the tools are load-bearing and the business is unusual enough that the off-the-shelf version needs bending. It is not worth making to save a subscription.
Operations Audit
Running more tools than anyone owns?
Two weeks to map what you have, what it costs you, and which piece is worth replacing first. The fee comes off the work that follows.
A senior engineer reads it and replies within one business day.