Agency CRM — Built Because We Were the Ones Losing Track
An agency CRM organised around client health rather than sales stages, where an update is one plain sentence instead of a form.
Client
FameWeb (internal product)
Industry
Digital Agency / Professional Services
Timeline
[CONFIRM: build duration]
Services
Product Design, Custom CRM Development, Task & Pipeline Management, Natural-Language Capture
The Challenge
Agencies do not lose clients to bad work. They lose them to silence.
A client rarely leaves the week something goes wrong. They leave after a stretch where nothing went wrong and nothing was heard either — no update, no next step, no evidence that anybody was thinking about them.
The uncomfortable part is that this is invisible from inside the agency. Everyone is busy. Everyone is working on something. Nobody is working on the client who has gone quiet, precisely because quiet clients generate no messages.
Why the available tools do not answer it
A sales CRM is built around a pipeline that ends at “won”. Agency work starts at won — the relationship that matters is the one after the deal, and a tool built for closing has no opinion about it.
A project tool is built around tasks, which answers “what is being done” but not “who have we neglected”. A client with no open tasks looks healthy in a project tool and is, in reality, the one most at risk.
So agencies run both, plus a spreadsheet, and none of the three can answer the only question that predicts churn: which client has not heard from us, and for how long?
The logging problem underneath all of it
Every CRM depends on people entering updates, and entering an update means opening a form. A form is friction. Friction means the entry gets postponed to the end of the day, then to the end of the week, then not at all.
An out-of-date CRM is worse than no CRM, because people still trust it. A client that was handled last Tuesday looks abandoned; a client genuinely abandoned looks fine. Decisions get made on both.
What needed to be solved
A view where the first thing visible is which clients need attention, not which deals are open.
A last-contact figure that is honest, including when the honest answer is “never”.
Capturing an update in one sentence, in the words someone would actually use.
Leads and clients in one tool, because a lead becoming a client should not mean re-entering them.
A home screen that answers “what needs me today” rather than showing charts.
Fields that each agency can turn on and off, because no two track the same things.
Why we built it for ourselves first
We had this problem. Three tools, none of which could tell us who had gone quiet. Building it for our own desk meant the design was tested against real neglect rather than an imagined workflow — and it meant we had to live with every bad decision we made.
What We Did
We organised the system around client health, and made logging cost one sentence.
Our approach
Two decisions shaped everything else: health is the primary object rather than pipeline stage, and the cost of recording an update has to be close to zero or the system will be wrong within a month.
01 — Client health as the organising idea
Every client carries a health state — Healthy, Attention, or At risk — derived from open work, overdue work and how long it has been since the last update. The client list can be filtered to each state directly.
This inverts the usual CRM. Instead of asking the user to look at a list and work out who is in trouble, the system makes the judgement and the user reviews it. Software is better at noticing eleven days of silence than a person with a full week is.
02 — “Last update”, including “Never”
Last update sits as a column on the client overview, next to open tasks, overdue tasks, progress, next due date and pipeline value.
Showing “Never” was a deliberate choice. It is the single most useful cell in the table and the one a politer design would have hidden behind a dash. A client with no recorded update is not a formatting problem — it is the finding.
03 — Log anything, in one line
A single text box takes a plain sentence — “Met Rishabh, he needs a website”, “Move Shubham from leads to clients” — with a client selector and a date beside it.
No form, no required fields, no stage dropdown. The sentence is the record, and the structure is derived from it rather than demanded up front.
This is the feature the whole system stands or falls on. Everything else in a CRM is downstream of whether people actually put things into it, and people put things into a text box in a way they have never put things into a form.
04 — Today as the home screen
The landing view is Today: clients, open tasks, how many are overdue, average progress, what was completed in the last seven days, and the value sitting in leads and opportunities.
It is a working screen, not a reporting screen. The difference is whether a number is there to be admired or acted on — every figure on Today is a link into the thing that needs doing.
05 — Leads and clients in the same tool
Opportunities and lead pipeline live alongside the client list, with value attached, so a lead turning into a client is a change of state rather than a re-entry into a different system.
06 — The small things that decide whether it gets used
Task-due notifications that surface in the interface rather than only by mail.
A Planner for the week ahead.
Show / hide fields on the client table, because every agency tracks something slightly different.
Autosave throughout — the interface confirms changes are saved rather than asking anyone to save them.
Per-client task entry from the overview row itself, so adding a task does not require navigating away.
None of these are impressive on a feature list. All of them are the difference between a tool that is open all day and one that is opened on the first of the month.
The Outcome
A CRM that tells you who you are neglecting, before the client does.
FameWeb runs its own client work on this system. Clients, open and overdue tasks, progress, next due dates, leads and opportunity value sit on one screen, and the client list sorts itself by who needs attention.
The question that could not be answered now has a column
“Which client has not heard from us, and for how long” is visible on the overview rather than reconstructed from memory, three tools and a spreadsheet.
Updates get logged because logging costs a sentence
Replacing the update form with a plain text box removed the friction that makes most CRMs inaccurate. The system is current because entering into it is faster than not.
Leads and clients stopped being two systems
Pipeline value and client health sit in one tool, so the handover from sales to delivery does not involve retyping anybody.
Built on our own desk first
We did not design this against an imagined agency workflow. We built it for the problem we had, used it on our own clients, and kept only the parts that survived contact with a real week.
What this unlocked
The ability to catch a quiet client while it is still a quiet client — which is the only point at which it is cheap to fix.
Client health states — Healthy, Attention and At risk — derived automatically from open work, overdue work and time since last contact.
One plain-text box replaces the update form, so an update costs a sentence instead of a dialogue.
[CONFIRM: a real figure — e.g. clients managed on the system, updates logged per week, or tools replaced. Do not publish an invented number.]
