Kesey · a note from the road

I was the highway guy.

Christopher O'Donnell at Day wrote a half hour on life after CRM and closed it by telling you to send it to whoever runs yours. For twenty nine years, that has been me. This is what the same argument looks like from the road.

Six miles · two pictures · one guy with a flag
Mile 1

The read

I read the whole thing in one sitting. My girlfriend checked on me every ten minutes to see what exactly I was doing, because I do not sit still for half an hour, and I definitely do not do it for an essay about CRM. By the end I had concluded that my life's work was for naught. By the next afternoon I had rebuilt my entire website. That is the short version of how it landed.

The long version is this page. Christopher wrote his from the highway, where the product gets built. I have spent my whole career on the shoulder, waving people up onto the highway, and I want to say what the same argument looks like from down here. Down here is where the CRM actually dies.

Mile 2

The road and the highway

When my business partner and I ran EzHire Cannabis, we had two words for the company: the road and the highway. I built the tech that optimized the business. That was the highway: the systems, the automations, the reports that made the whole thing move faster. He handled the customers and the daily grind of running a small company. That was the road: the phone ringing, the placement that fell through on a Friday, the client who wanted to talk to a person.

It took both of us, because the two never really connected. It was also what we fought about most of the time. I would build something beautiful on the highway and he would not drive on it, and from where I sat that looked like stubbornness. From where he sat, the highway was a place where you had to stop what you were doing and type.

He was right. It took me twenty nine years and a half hour essay to admit it.

FORECAST · PIPELINE · DASHBOARD THE HIGHWAY NEVER CONNECTED THE ROAD
The highway: forecasts, pipeline, dashboards, moving fast. The road: the customer, the call, the Friday. A median between them, and for twenty nine years nothing crossed it except a person who stopped driving to type.
Mile 3

Twenty nine years on the highway

I started in 1997, at thirteen, typing other people's phone calls into a database. Summers through high school and college, data entry. Everything since has been the same job at a different scale.

1997Data entry at thirteen.The seat where the typing happened.
2006Built one.Helped architect a CRM from nothing and ran over a hundred and fifty people on it.
2012Sold one.Built the onboarding program at Pipeline CRM, then closed the largest deal in the company's history on wireframes I drew myself.
2018Sold the big one.Six years at HubSpot, channel then enterprise. President's Club twice.
2024The janitor.Going back for what the record threw away.

Every version needed a person to be its keyboard, and every version threw the conversation away. Here is one real call, and what the record kept of it.

What the customer said

We lost two people in support in June, the renewal is in March, my boss wants a single vendor, and if onboarding had gone the way the demo did we would have signed for three years.

typed in as
What the record kept
StageQualified
Next stepFollow up
Notesgood call, follow up
F1 HELP · F3 EXIT · F7 PREV · F8 NEXT · F10 SAVE

That is not a bad rep. That is a person on the road doing exactly what the highway asked of them, which was to stop driving and type. Half of the job was being the keyboard, and the half that mattered, remembering what the customer actually said, was the half the software was worst at.

Every CRM project I ever ran was a highway project that asked the road to do the driving. I was good at it. I have the President's Club plaques. It was still the wrong job.

Mile 4

What changes

Christopher's argument, from the highway, is that the record could never be smarter than what a person had already boiled down into a dropdown. From the road it is simpler than that. The road never wanted to type. The road was right. And for twenty nine years the only fix on offer was a nicer form.

The road never wanted to type, and the road was right.

What changed is that the record can read the inbox, the calendar and the calls, and write itself. Nobody has to be the keyboard. The best conversation of the quarter is in the record the next morning, whole. One person leaving does not take the pipeline with them, because the pipeline was never in their head in the first place. A number on the report can say which conversation it came from.

I did not take that on faith. Over the last few months I built my whole operation on Claude: a status board for every client, scheduled runs that read my calls and my email, a session per client that does the delivery work. Then I pushed all of it into Day in an afternoon. Every client is an organization with the board's fields on it. My agent is named Doug. He creates the deal when a proposal goes out and closes it when the agreement is signed or the payment lands. I wrote that down once, in plain words, and he does it.

Here is the part that matters for anyone who is not a one man band. What I built only works because I am one person. The moment there is a second person, the memory has to live somewhere shared, with an agent on top of it that both of you can talk to. That is what Day is.

Mile 5

The on-ramp

So here is the analogy that made somebody at Day laugh out loud on a Wednesday morning.

What Day is building is the on-ramp. It gets the people on the road onto the highway without needing a highway guy to take them there. The record fills itself from the driving they are already doing. The dashboards come from what actually happened, not from what somebody remembered to type at 4:45 on a Friday. The road keeps being the road, which is the whole point.

FORECAST · PIPELINE · DASHBOARD THE HIGHWAY THE ROAD THE ON-RAMP
Same highway, same road, one ramp. The van is doing what it was already doing on the road, and it ends up on the highway anyway. The guy at the bottom of the ramp is me.

I signed the partner agreement the day they sent it, for two reasons, and neither of them is the analogy.

Day builds the software and hands the build, the agents and the watching afterward to partners. That is the half I am good at and the half I have done for twenty nine years, so the partnership is a split and not an overlap. And you pay for the work an agent does, not for a seat a person sits in, which is the first pricing shape I have seen that matches how a small team actually works.

Who it is for: five to fifty people on Google Workspace, selling by conversation rather than by form fill, with a CRM nobody updates. Technical services firms, MSPs and agencies are where most of it lands. Who I am not the right call for: a business that sells by the transaction and never by the conversation, or a one person shop that can do what I did with a weekend and a chatbot. I will tell you which one you are on the first call, because finding out in week three is expensive for both of us.

Mile 6

The guy with the flag

That leaves me. I am the one out front with the goofy hat and the flag, waving the road up the ramp while I smoke a Marlboro Red and complain about Drake Maye. Three ways to get waved on.

Start here

A thirty day pilot

Fixed scope, one team, one month. Credits in full against a build if you keep going.

Keep the CRM

An agent fleet beside what you run

Nothing you run gets moved. Mail, calendar and calls read in on top of it, and the agents are built beside the record you already have.

Replace the CRM

A full workspace build

Day becomes the system of record, with the history brought across so day one is not a blank screen.

Your tools stay. I add the layer that remembers, build the agents, and stay on after go-live, because the janitor's job did not go away when the typing did. It used to be scrubbing the fields. Now it is going back for what the fields threw away, and building it so nothing gets thrown away again.

Christopher ended his piece by telling you to send it to whoever runs your CRM. If somebody just sent you this one, they think that person is you. I have been you. Let's talk.

Tell me what the record forgot.

Thirty minutes, on the phone or on a video call, whichever you hate less. You describe how work comes in and where it stalls, and I tell you whether the on-ramp is for you. If it is not, I will say so on that call, and you will have spent half an hour and gained a straight answer.

No sequence, nothing automated. One personal follow-up from me after the call, and the word "no" ends it.