Three partners. One working system.
Kesey partners with the platforms it builds and runs for clients. Day.ai and Attio keep the record, two different ways. BrandJet does the reaching. All three are working relationships with the people who make the product, and that is what you get the day something needs them.
Reach, record, and someone running it
Twenty years on one road. I helped build a homegrown CRM in 2006, because that is what you did then, and the tools are cheap now where the trust is not, which is why one partner is the record and Kesey builds everything else on top of it.
Built our own CRM
Early cloud. That was what you did.
Migrated to HubSpot
The day someone outside the team had to trust it.
Finds the people and starts the conversation, across the channels that fit, from one sequence. The row that decides whether anything else happens.
Day.ai goes on top of the CRM you keep and writes the record itself from the email, the calendar and the calls. Nothing moves on the first call; the layer goes on and what matters comes out.
Builds it, migrates what you already have, and watches it every month. A person, on the record, reading what the software did.
Day.ai
The layer that reads email, calendar and meetings and writes the record itself, on top of the CRM you keep or as the record outright. An agent per person, not a seat per person.
It answers the question every CRM project dies on
Who is going to keep this updated? I have spent years getting sales teams to type into a CRM. Day.ai is the first product that stops asking them to. The record reads the inbox and the calendar and writes itself.
A clean split
Day.ai builds the software and leaves the build, the agents and the watching afterwards to partners. That is the half I am good at, so the partnership is a split, not an overlap.
Who it fits
Teams that sell in meetings, on Google Workspace, five to fifty people, with a CRM nobody updates or a spreadsheet standing in for one.
Having it built for you, everything about running it, and why I chose it, from the road.
Attio
The CRM you shape around what the business actually runs on: your own objects, relationships and pipelines, with the record built from email and calendar on top. For when contacts, companies and deals are not the whole story.

It answers why teams build their own
Most homegrown CRMs exist because the business had a noun the template did not. Attio lets a team model that noun without owning the record, and the record is the half of a homegrown system that eventually fails.
The model is the work
Attio will model almost anything, which is why the model needs designing before a record moves. Attio sends teams that want it designed and built to its Expert Partners, and that design is the work I do.
Who it fits
Businesses with nouns the template does not have, a fund, a property, a project, a placement, up to about sixty people, or a system built in house that has started to creak.
Having it built for you, and where Attio sits among the four.
BrandJet
Outbound across six channels from one sequence, with every reply landing in one inbox.
It replaced four tools on my own stack page
Outbound used to be four bills and four places for a prospect to fall through: a contact database, a tool to fill in the details, a sequencer and a warmup service. BrandJet is one platform doing all of it.
Set up once, properly
Sending domains architected before a single email goes out, one sequence across the channels that fit, and the replies routed into your record at the reply, never at the import.
Who it fits
Teams for whom outbound is how you grow, not an experiment, who need sourcing, sending and replies in one place, and who have a record to land replies in.
Not sure which record you need? That is the first call.
I say no when it does not fit. Day.ai for the team that sells in meetings on Google Workspace, a hard qualifier, not a preference. Attio for the business the standard template does not fit. BrandJet beside either the moment outbound becomes a channel, not a hope. If none of them is the answer, you will hear that on the call.