Projects come and go; the relationship stays

Anna's redesign wrapped in May. Her Q4 follow-on starts in October. Same Anna, two engagements, full history intact.

The problem

Most CRMs collapse "the work" and "the person" into one thing called a "deal." A deal moves through a linear pipeline — prospecting, discovery, proposal, negotiation, closed. When the deal closes, the system treats it as terminal. The contact and everything you knew about them gets filed under deals/closed-won and quietly disappears from your daily view.

But a closed project isn't the end of a relationship. The person you delivered for is still a past client. They might be a referrer for the next two years. They might be a repeat customer in six months. Their context — what their team is like, what their constraints were, what they said about Q4 — shouldn't vanish the moment the invoice clears.

And real indie work doesn't move in a straight line anyway. A project pauses for two weeks because the client's travelling. A dormant client comes back ten months later. A "prospect" never converts but introduces you to two who do.

What changes

People are permanent. Engagements are episodes attached to them.

Anna's landing page redesign is one engagement. It has a start date, a few transitions ("proposal signed," "client paused for travel," "delivered"), an end date, and an outcome you wrote in your own words. When it closes, the engagement gets an end date — Anna doesn't. She stays a current client. Her cadence, her roles, her history of stated positions and answered questions all persist.

When her Q4 follow-on lands in October, you start a new engagement. Same Anna, second engagement. The first one is still there as history — "what did we deliver in May? what did she say about her team's analytics needs?" — but it doesn't bleed into the new project's state.

Engagements move in any direction. Dormant → active is a normal transition, not a regression. Active → paused → active is normal too. The phase is just where this piece of work is right now, not a stage on a treadmill you can't reverse.

Why we built it this way

Sales-pipeline CRMs were built for teams who hand off work — an SDR books a meeting, an AE runs the demo, a CSM handles the renewal. Each stage is a baton-pass. For an indie operator there's no baton; it's all you. The thing that matters is the long-running relationship, not the linear deal.

Separating engagements from people means you can close a project cleanly without losing the relationship's history. And it means repeat work — which is most indie work — isn't a special case. Anna doesn't reset to "prospect" when she comes back. She's still Anna.

What to read next

→ When the system isn't sure, it asks — how the CRM handles facts it isn't quite confident about, without silently guessing.