Field Notes
Anatomy of a Revenue Machine
Most case studies are adjectives. This one is a parts list.
Revenue Rx spent the past year building the revenue systems for Custom Crafted Homes, a custom building company on Cape Cod. Second-generation builders, third generation on the Cape. Seven-figure projects, long sales cycles, a reputation earned one house at a time. They had the craft. What they didn't have was infrastructure: no way for clients to see their own projects, a CRM full of half-right records, and no outbound motion beyond word of mouth.
This post walks through what we built, piece by piece, and why each piece is there. If you run an owner-led, high-ticket company, the parts will look familiar. You probably have gaps in the same three places.
Start with the clients who already signed
The first thing we shipped was not a lead machine. It was a portal.
A custom home takes the better part of a year to build, sometimes longer. The client writes a very large check and then, in most builders' worlds, enters a fog. They call for updates. The builder returns calls at night. Nobody enjoys any of it, and the builder is losing hours he could spend on the actual house.
So we built owner portals: a private page per project where the client sees where their build actually stands. Two are live right now, with real clients checking real projects. Not demos, not staged screenshots for a sales deck. Actual homeowners logging in on a Sunday morning instead of calling on Monday.
Why start here instead of at the top of the funnel? Because in high-ticket work, the referral is the growth engine, and referrals come from clients who felt taken care of the whole way through. An informed client refers. An anxious one doesn't. Every update call the portal absorbs is an hour that goes back into building.
One system for email and data
Next problem: the data was a mess, the way it is at most owner-led companies. Leads arrived with names misspelled and stayed misspelled forever. Sending a project update meant someone manually dumping data out of one tool and into another, every time. Each list was a little wrong, so nobody fully trusted any of them.
We replaced the pile of disconnected tools with one cohesive email and data system. It scrapes metadata at the point of entry, so a lead lands in the CRM spelled correctly with the details already attached. It geo-fences communications per project, so messages about a build in one town go to the people connected to that build and nowhere else. The misspelled leads stopped. The manual data dumps stopped. The lists became trustworthy, which means they actually get used.
None of this is glamorous. That's rather the point. A revenue machine is mostly plumbing, and plumbing earns its keep by staying boring for years at a stretch.
Letters on paper to people who just bought land
Then the outbound piece, and it's not what you'd guess. No ad budget. No cold email sequence. Physical letters.
Here's the logic. Someone who just bought a vacant lot on Cape Cod, or a teardown-grade property, has told the public record exactly what they're about to do: hire a builder. The window is short and the moment is knowable. So we built an engine that watches recent sales of vacant land and teardown candidates, qualifies the properties, and mails a letter from the builder himself to each new owner.
Think about what that letter is. A note signed by the man who would actually build your house, arriving the same season you closed on the land. It out-competes any ad because it isn't one. It's a neighbor introducing himself at the right moment, backed by a system that makes sure the moment is never missed.
That engine sources pipeline on paper, season after season. Sourced is the honest word. The letters open doors. What happens after a door opens is a different craft entirely, and we'll get to whose craft it is.
What the numbers say
Right now there is $3 million in qualified pipeline actively working in the CRM — deals the rebuilt site and the data system produced together, visible stage by stage instead of living in someone's head.
Hold the distinction, because most agencies won't. Pipeline is not revenue. What has closed through that CRM is roughly $1.4 million — and that's the number that makes the pipeline believable, because the same system that holds the deals is the system that walked them to signatures.
The flagship close inside that work was a $1.1 million home — won on the rendered 3D proposal. Inside the closed figure, not on top of it. It's worth naming a single deal because it shows the unit economics plainly: at this ticket size, one conversation that happens on time can pay for years of systems work.
Who closed what
Be careful with credit here, because agencies rarely are.
Revenue Rx built the systems. Custom Crafted closed the sales. The craft is theirs. The estimating is theirs. The trust that gets a seven-figure contract signed is theirs, and it took two generations of building on the same peninsula to earn it. No portal frames a house, and no letter shakes a hand.
Our work was narrower, and easy to state plainly: make the right conversations happen, reliably. The right land buyer gets a letter while the decision is still open. The right lead lands in the CRM spelled correctly. The right client checks a portal instead of stewing by the phone. Everything after that was them.
The pattern underneath
Strip out the Cape Cod specifics and the anatomy is simple.
One system that takes care of the clients you already have. One system that keeps your data honest without anyone tending it. One system that starts conversations with the exact people who are about to need you. Wire them together so that nothing depends on somebody remembering.
That's what "Systems. Scale. Exit." means in practice. Not a dashboard. A company that runs on rails — rails the owner can eventually hand to someone else, which is the only version of a company that's ever worth selling.
If the machine described above sounds like the thing you keep meaning to build, that's a conversation worth having.