Skip to content

I'm building a CRM for one person

My pipeline has lived in a to-do app and my inbox for years. That works, and I want to be fair to it, because for a long stretch it was completely fine.

It stops working at one specific point. Something goes quiet, and nothing tells you.

A to-do list only knows about the tasks you remembered to write down. An inbox is a list of things other people wanted, in the order they wanted them. Neither of them has an opinion about the quote you sent six weeks ago that nobody has replied to. The work doesn’t fail loudly. It just sits there being nothing.

So I’m building Drey, a small CRM for the Mac. The whole shape of it comes from one admission: I am one person, and almost nothing in a normal CRM is built for one person.

What a CRM is mostly made of

Open any of the big ones and look at what’s actually in there. Owner fields. Assignment rules. Permissions and roles. Seats. An activity feed. Stages designed to pass a lead from whoever found it to whoever closes it. Forecasting, so somebody further up can put a number in a spreadsheet.

Every one of those exists because there is more than one of you.

I run a small studio. New work comes from search, referrals and people I already know. There is nobody to assign anything to, nobody whose permissions need restricting, and nobody to forecast at. When I took out everything that only exists for the second person, there was surprisingly little left.

What’s left is who it’s with, where it stands, what it’s worth, and what I do next.

That’s the app. It’s just me, so that’s all it needs to be.

One next action, always

The rule I keep coming back to is this: every live opportunity has exactly one thing you do next, with a date on it. You can’t tick that off without saying what happens after, or deliberately parking it.

I know how that sounds. A constraint dressed up as a feature.

But it is the feature. The reason work goes quiet is never that you decided to let it go. It’s that you finished a thing and didn’t decide anything after it, and the gap filled up with everything else. Forcing the next decision at the only moment you’re actually thinking about that client is the entire idea. Nothing goes cold unless you choose to let it.

If you’ve used Things 3, this will feel familiar, because it’s the same thought applied to clients instead of tasks. I’ve held my other app up against Things for years. I’m doing it again here.

Today is the whole job

The main screen is what’s overdue and what’s due. You do it, set the next thing, and the row moves on. Everything else is there when you want it, and not before.

I don’t want a dashboard. I have never once opened a pipeline chart and changed my mind about anything.

Drey's Today view: two overdue follow-ups and two due today, each with the client, the work, its stage and its value. The focused row offers Done, set next, Reschedule and Open thread.
The Today view, from the design mock-up. The clients and the figures are made up.

The bit I argued with myself about

I wrote a few weeks ago that there is no AI in My House, My Things and that I have no plans to put any in. I meant it. That app’s job is to hold facts you typed and give them back unchanged, and nothing about that job is improved by a guess.

Drey is a different job. A chunk of the work is reading what came in this morning and deciding what it means for the people you’re already talking to. So Claude can read the mail and propose changes: a reply logged, a follow-up moved. It proposes, and nothing happens until you approve it.

I’m aware that’s a line I’ll have to keep defending. It’s the right one for an app whose job is partly reading, and the wrong one for an app whose job is remembering.

What it costs and what it won’t do

One payment. No subscription, no seats, no renewal date. I’ve written before about why, and I’m not going to do the whole argument again.

It’s local only. No server and no account, because I don’t have one and don’t want one. Your clients and your figures sit on your devices and sync between them through your own iCloud. Mac first, iPhone after.

Nothing gets thrown away either. Work that’s lost or has gone cold is closed, not deleted, and every change is dated, so you can go back and see where your work came from and why it went. The numbers are plain: what’s in play, weighted by how close it is, and what’s due in each month. No lead scores. No win-rate predictions. I don’t believe mine and I wouldn’t believe yours.

Where it is

The brief is written, the design pass is done, and the rules underneath are next, tested before any screen exists. There’s no release date, and I’m not going to invent one.

A drey is a squirrel’s nest. Squirrels store plenty and lose none, which is roughly the job description.

I’m writing the build up as I go, at dreycrm.com. It’s mostly for me, which I suspect is the only honest reason to start one of these.