Field Notes · The Stack Series

Every lead becomes a record

By Will Hess · Founder, Inside Intelligence

Fifth in our series on the stack we run Inside Intelligence on. We've covered the books, the tickets, the wiki, and the vault. Now: the front door — where every sales lead and customer actually lives.

We run a self-hosted CRM application on our private infrastructure. Same posture as everything else in the stack.

Why a CRM, and why it's the front door

An operations team doesn't keep its customers in a spreadsheet or in someone's head. It keeps them in one place — every lead, every contact, every account — so nothing falls through the cracks. That's what a CRM is for. It's the record of who's talking to us, what they need, and where they are in the process.

For us, the discipline is simple: every lead becomes a record. Someone reaches out, they get a record. They become a customer, they get a record. It's all in one place, queryable, and never lost.

The part that matters: an agent captures the leads

Here's where it becomes Operator. We didn't just install a CRM and have a human type in every lead. We wired an agent to do the capture — the same way Operator would run a client's sales pipeline.

When someone fills out the contact form on our site, the agent doesn't just get an email. It creates a lead record automatically — with the person's name, their email, what they told us, and where it came from. No manual entry, no lost inquiry, no "did anyone follow up on that?"

The point

An operations team doesn't lose a lead. The CRM is the record. The agent is the one who makes sure every inquiry lands in it — automatically, the moment it comes in.

Why this matters for a duty-of-care office

If you run a law, medical, financial, or licensed-trade office, you don't care about our CRM software. You care about this: your leads and clients are tracked. Not in a spreadsheet that goes stale, not in someone's inbox — in a living record that an agent keeps current, so nothing slips through.

That's what running a business looks like in practice. It's not a promise. It's a record of every person who reached out and what happened next.

Next in the series

We'll tie the whole stack together — how Operator uses all of it as one operations team in a box.


← Back to Field Notes