Most of the conversation about account health monitoring assumes a certain organizational scale. A dedicated customer success team. A CS platform. Someone whose job it is to watch the numbers. For boutique consultancies running 10 to 25 client relationships with a team of 5 to 12, that infrastructure does not exist and it does not make sense to build it from scratch.
But the renewal risk problem is real regardless of size. A five-person strategy consultancy where two accounts decide not to renew in the same quarter is dealing with a meaningful revenue event. The stakes are just as high as at a larger firm. The tools and processes need to be scaled down, not skipped.
This is a practical guide for building a renewal radar at boutique scale, using the resources most consultancies already have.
Start with what you already track
Before buying any tooling or redesigning any process, inventory what data you are already producing. Most consultancies have at least some of the following: post-meeting notes in some form (Notion, Google Docs, Word documents), periodic client check-in surveys (even if informal), email threads with key contacts, and an internal knowledge of which accounts have upcoming renewals.
The goal is not to create new data sources. Boutique consultancies are already data-constrained, and asking consultants to log more things into more systems will not work. The renewal radar needs to operate on data that is being produced as a natural byproduct of running the engagement, not data that requires additional work to collect.
Define your signal set before you start monitoring
A renewal radar without a defined signal set is just a to-do list. Before you start reviewing any data, define the three to five signals you are specifically trying to detect.
For most boutique consultancies, a practical signal set looks something like this:
Engagement quality in meetings. Is the client bringing substantive topics to the conversation, or are they attending mostly to receive status updates? A shift from substantive engagement to passive consumption is a meaningful signal.
Survey verbatim length and specificity. If you run any kind of periodic feedback survey, watch what happens to the open-text responses over time. Shorter, more generic responses over three or four cycles often indicate disengagement even when scores remain flat.
Proactive communication from the client side. Does the client initiate conversations that are not strictly necessary? Do they share internal context, forward relevant articles, or bring up problems that are adjacent to the contracted scope? When this stops, the relationship has shifted from partnership to service consumption.
Renewal conversation timing. How early does the client bring up renewal terms? Clients who are planning to continue tend to surface the renewal conversation naturally, often before the account manager does. Clients who are evaluating alternatives tend to wait until approached.
Stakeholder access. In healthy engagements, clients tend to bring the consultancy into conversations with more senior stakeholders over time. When access narrows, when you are only talking to the same operational contact who cannot commit to renewal anyway, that is a signal worth flagging.
Build the radar in a spreadsheet first
No software required at this stage. A simple spreadsheet with one row per account and columns for each signal, updated monthly, gives you the pattern over time. Color code each cell based on signal state (healthy, watch, concern). Review it as a team once a month.
This approach is crude but functional for a portfolio of 10 to 25 accounts. The discipline of updating it consistently is more important than the sophistication of the system. An imperfect system that gets reviewed every month is substantially better than a sophisticated one that no one has time to maintain.
The goal of this phase is to develop a shared team vocabulary around account health signals. What does "engagement quality dropping" actually look like for a specific account? What are the concrete behaviors that justify a "watch" flag? Getting your team aligned on these definitions before you layer in any tooling prevents the system from becoming a source of internal disagreement rather than insight.
The 30-day intervention window
A renewal radar is only useful if it triggers action within the right timeframe. For boutique consultancies, the minimum useful lead time for a genuine account recovery conversation is typically 30 days before the renewal discussion. Within 30 days, you are essentially in salvage mode, where the conversation has to acknowledge a problem that both sides already know about.
The signal set described above should ideally surface warning signs 8 to 12 weeks before renewal, giving you a genuine window to investigate the root cause and have a substantive conversation before the stakes become explicit. That window is what converts the radar from a diagnostic tool into an intervention tool.
When to add tooling
The spreadsheet approach has a ceiling. It works well for 10 to 25 accounts with a small team that reviews it consistently. It starts to break down when the portfolio grows, when note-taking quality is inconsistent across team members, or when the analysis becomes dependent on one person who happens to be attentive.
That is the natural transition point for a tool like Avara: not as a replacement for the judgment your team has developed, but as a way to apply that judgment's framework consistently across every account every week. The structured extraction happens automatically against the notes you are already writing. The signal tracking happens without anyone having to manually update a spreadsheet.
We would not argue that tooling is necessary at 15 accounts. We would argue that it becomes worth evaluating as soon as maintaining the manual process starts competing with client work for your team's attention. That threshold varies by firm, but for most boutique consultancies, it arrives somewhere between 20 and 35 active accounts.
What the radar cannot do
A renewal radar, whether manual or tool-assisted, can surface signals and flag accounts worth investigating. It cannot diagnose why a relationship is cooling or prescribe what to do about it. That requires a conversation, and that conversation requires human judgment and relationship knowledge that no system will ever replace.
The value of the radar is precision: getting your team's attention to the accounts where it is most needed, at the time when intervention is still likely to work. That is a significant improvement over the alternative, which is discovering account cooling at the renewal call when there is nothing left to do about it.