Why We Built Our Own Client Dashboard Before AI Was a Thing

When a client hires a software agency, the code is rarely the part that goes wrong. What goes wrong is everything around it. A request gets mentioned in a call and then forgotten. Nobody can say where the budget has actually gone. The client wants to know how their project is doing and has to email someone to find out. We couldn’t find an honest way to promise that none of that would happen, so a few years ago we built our own client dashboard to make sure of it. This was well before AI became the thing every agency opens with.

Accountability, not software

We used to run the way most small agencies do: email, phone calls, the state of each project carried around in someone’s head. That holds up at two or three clients. After that it starts to come apart.

You could see it in one question that came up most days: “what’s happening on my project?” Each time, we had to rebuild the answer from Slack, the repo, the time log, and memory. The information existed. It just wasn’t anywhere a client, or a colleague covering for someone, could actually reach it.

Two things were wrong, and both were about organisation rather than engineering:

• We were charging for visibility we didn’t really provide. Proposals promised reporting and progress tracking. In practice the reporting was one of us typing an update into Slack when a client asked.
• Nothing survived a person being away. If whoever held a project in their head was off for a week, the project went quiet, because its real status lived in that person and nowhere else.

That second point is what separates an agency from a good freelancer. An agency is meant to run on something that outlasts any one individual. We didn’t; we just had better invoices.

What it does

The client dashboard handles the dull but important things on its own:

• Requests get logged and tracked through to done, rather than sitting in an inbox.
• Time is recorded against the work and shown to the client, so the budget question has an answer ready before it’s asked.
• Email gets turned into tickets, so a message can’t quietly get buried.
• The signed scope sits in the system as a checklist, with every item marked not-started, in-progress, or done, so progress stays accurate without anyone keeping a spreadsheet up to date.

None of that is impressive, and we didn’t want it to be. We wanted a client to be able to answer their own “how’s it going” without us, and we wanted it to be very hard for work to stall without somebody noticing. Three years on, most of the ways an engagement can fall apart have been turned into a part of the system, fixed one at a time as we hit them.

Guardrails

The way we describe it to people is bowling with the guardrails up. You still won’t bowl a perfect game, and some weeks go better than others, but the ball can’t end up in the gutter. A freelancer, however talented, has no guardrails. If they get ill, overloaded, or simply lose interest, the work stops, and you tend to hear about it late. The dashboard is our version of those guardrails. It doesn’t make every project brilliant. It makes the kind of silent, total failure that wrecks trust very difficult to have.

Why AI raised the stakes here

AI has made it cheap to produce something that looks finished. It has done nothing to make sure that thing is still looked after six months later, and in plenty of cases it has made ownership murkier, because no one quite remembers how the output was built or why.

That changes what’s worth asking a software partner. Whether they can build it matters less now that so much can be built quickly by anyone. What matters more is whether someone will still be accountable for it when it breaks on a Friday night, and whether there’s a record of how it works that doesn’t depend on one person’s memory. Those are questions about process, which happens to be the part we’d spent years getting right before the tools arrived. It’s the same reason most “we need AI” requests turn out to be process problems once you look underneath.

Who it’s not for

If your main concern is the lowest possible day rate, and how the work gets tracked genuinely doesn’t matter to you, we’re probably the wrong agency. Running this properly costs money and we charge for it. It lands best with people who have already had a project go dark on them once and would rather not repeat the experience.

Where this leads

The dashboard is the most visible example of how we work, but the same instinct runs through everything we build: make the result dependable, keep ownership in-house, and avoid handing accountability to a tool that was never designed to carry it. If that’s what you want from a partner, tell us about your project, or read more about how we work.