How Authentic CRM Started as a Spreadsheet and Ended Up as a Product Other Firms Pay For
Every CRM assumed Apparatus had thousands of leads and wanted automated follow-up. It had about 100 relationships that actually mattered. What it built instead.
Professional services business development has a particular shape. It is not a funnel. There is no pipeline of warm leads moving through stages toward conversion. There are relationships - a few dozen, maybe a hundred - and those relationships generate almost everything: referrals, return engagements, introductions, reputation. The quality of attention you give those relationships determines whether they stay active or quietly go cold.
Every major CRM platform was built for a different problem. They were built for high-volume sales: hundreds of prospects, automated email sequences, lead scoring, conversion tracking. The feature set assumes you need to manage a lot of low-quality relationships at scale. Apparatus had the opposite problem - a small number of high-value relationships that required careful, personal attention.
Why the spreadsheet worked and didn't
The honest answer is that for a long time, a spreadsheet was the right tool. A list of names, last contact dates, notes from the last conversation, a column for "next step" updated manually. It captured what mattered. It did not try to be a pipeline.
The problem with the spreadsheet was the same problem all passive tracking systems have: it did not tell you anything. It recorded what had happened. It did not surface when you should reach out to someone, or why, or remind you of the context that would make that outreach feel personal rather than transactional. You had to remember to look at it. When things got busy - when client work was intense - the spreadsheet went unreviewed for weeks. Relationships that should have gotten attention didn't.
The other thing a spreadsheet cannot do is hold the right information. The data fields that actually inform a good outreach message are not "last contact date" and "company." They are things like: this person just moved to a new firm, this person mentioned they were starting a search for a particular kind of partner, you talked about their daughter's college decision last time and you've been meaning to follow up. That information lives in memory and in email threads. A spreadsheet holds none of it unless you are disciplined enough to copy it in immediately, which almost nobody is.
What Authentic does
Authentic is a relationship management system built around the data that actually informs personal outreach. It tracks context - promotions, role changes, life events, things discussed in past conversations - and surfaces when and why to reach out based on that context, not based on an arbitrary follow-up interval.
The suggestion engine is the core of it. When enough signals accumulate around a relationship - a LinkedIn update, a note from a recent conversation, a configurable time trigger - Authentic surfaces a suggestion. Not a draft email. A prompt: this person just got promoted, here is the context from your last conversation, here is why this might be a good moment to reach out. What you do with that is up to you.
The constraint that shaped everything else: Authentic suggests, it never sends. The system surfaces the right moment and the relevant context. A human makes the call on whether to reach out, and writes the message. This was a deliberate design decision from the start - and it is now the thing the system's users cite most often as the reason it feels different from what they tried before.
The distinction matters more than it sounds. Automated follow-up sequences can be turned on without thinking. They feel efficient until a contact responds and makes clear the email was clearly not written for them specifically, or until you send a sequence to someone during a difficult moment they mentioned to you personally. The damage to a relationship from impersonal automated outreach is real and often irreversible. Authentic is built around the assumption that the human always needs to be in the loop - not as a rubber stamp, but as the actual author of the relationship.
What the build involved
The first work was identifying which data fields actually informed good outreach. This sounds simple. It required careful conversation with people who were good at relationship management - what do you actually need to know about someone to reach out in a way that feels personal? The answer was not the fields a CRM has by default. It was a different list: context from the last conversation, what was happening in their professional life, anything you committed to following up on, any shared connections worth mentioning.
Building the relationship context layer meant designing a system that made it easy to capture that information in real time - after a call, after a coffee, after seeing something about someone on LinkedIn. The data model had to be flexible enough to hold unstructured context without requiring a rigid taxonomy that nobody would maintain.
The trigger logic for suggestions required the most iteration. Too sensitive and the system surfaces suggestions constantly, which trains users to ignore it. Too conservative and it goes quiet for weeks, which means people stop looking. Finding the calibration that felt like useful background awareness rather than noise took several rounds of testing against real relationship histories.
The pattern that made it a product
Authentic was built for Apparatus. It solved a specific problem in a specific context. When it came up in conversations with other professional services firms - when partners at consulting firms or boutique law firms described the same frustration with off-the-shelf CRMs - it became clear the problem was common.
The firms that find Authentic useful share a characteristic: their business is driven by a small number of high-value relationships rather than a large pipeline. They are not trying to manage hundreds of contacts at a cadence. They are trying to stay genuinely in touch with the people who matter, without that becoming a manual administrative burden or devolving into impersonal sequences.
The tool does not work for everyone. If your firm genuinely needs pipeline management and high-volume outreach, Authentic is the wrong fit and there are better options. But for firms whose business development looks more like tending a garden than running a sales funnel, the mismatch with conventional CRMs is real - and building something purpose-fit for that context turns out to be worth the effort.
Both Codex and Authentic followed the same path: an internal problem, a focused build scoped to the actual constraints of the situation, and enough refinement against real use that the tool became something others found useful. If you have a similar problem at your firm - something that a well-scoped custom tool might address better than anything off the shelf - figuring out whether it is the right first build is worth doing before anything else. The Apparatus custom development practice starts with that conversation.