You'd be sorry to lose them. You think that, occasionally, about five or six people — and then a quarter goes by, then a year, and you haven't reached out, and neither have they. Nobody decided to drift. The structure that used to deliver weekly contact — school, the office, the neighborhood — quietly stopped delivering it, and nothing replaced it.
Ask the honest question: of the people you'd call close, how many have you spent fifty hours with in the last year? Most people land on zero, one, maybe two. I have plenty of friends turns out to be a claim the calendar has never tested.
The reflex is to blame yourself — I'm a bad friend, I'm too in my head. But Mark Manson's own diagnosis is simpler and less damning: I don't think about it. I don't think about it until it's too late. The default mode of friendship maintenance — wait until they cross your mind — runs structurally below the threshold that keeps a friendship alive. It's not a character flaw. It's a missing system.
So I wondered: what would a non-skippable structure for adult friendship actually look like — given that I'm a busy person who keeps choosing the couch?
This is a daily routine with an AI assistant — a workflow with AI — and its subtype is mixed: it holds an outer structure (a list, a schedule, an invitation) and the inner permission to value the role of the one who reaches out.
Stage 6 — The energetic signal under the drift
Read the signal first. The broadcast underneath the thinning network is often they'll fade anyway — a body that has quietly accepted drift as the default, so it stops sending the small signals that hold a connection. And the field mirrors it back: they stopped reaching out first, which reads as they don't care, which justifies not reaching out, and the wall thickens from both sides.
The structure changes what the field returns. A single sustained week of outreach usually produces two or three replies from friends who also drifted and were waiting for the prompt. The drift was mutual; so is the repair.
Underneath, for anyone who wants the structural confirmation, the chart often shows an Open G (in Human Design, the identity and direction center left uncolored on the BodyGraph, the Human Design body chart) — which needs anchor witnesses and lets them drift to the periphery without a holding structure. Or a Projector type, whose invitations go out into the field and don't return; the system is especially load-bearing because it prevents the unreturned invitation from reading as rejection.
Stage 7 — The question the AI asks first
Not who should you text. The audit first — because the number is the proof:
"List the people you'd be genuinely sorry to lose touch with — not your network, the real ones. Aim for fifteen to fifty. Then: of those, how many have you spent fifty hours with in the last year? Be honest."
If you name fewer than ten, the bot doesn't push — that's itself the diagnosis. The fifty-hour count is what replaces I'm too busy with I have plenty of friends and I've spent fifty hours with two of them. That's the problem.
Stage 8 — The workflow itself
A setup session to populate the structure, then a ten-minute weekly check-in. The most portable form is a simple friend CRM — a list with a last-touched date and a cadence each person actually earns.
```
Help me set up a friendship cadence and run a weekly check-in.
SETUP:
push — note it and move on.)
year? 25? 10? Sit with the number.
quarterly / yearly. Not the aspiration. The one I'll keep.
month is fine.
WEEKLY (10 min):
- Whose gap now exceeds their cadence? That's this week's outreach list.
- One open activity I can offer this week — a coffee, a walk, a meal.
- If "I can't bring myself to text X" comes up, don't push it — flag it
override the resistance.
```
What the AI does: fire the prompt the eventually default never fires. Suppress the aspiration cadence (everyone tagged weekly = a system you won't run) and capture the commitable one. Surface the gaps that crossed the line.
What you still own: sending the message, and showing up to the thing. The structure makes the reaching-out non-optional; it can't make the friendship. Contact is necessary, not sufficient — but without contact, nothing else gets a chance.
A first audit, in four lines:
"Eighteen close-ish friends." "Of those eighteen — fifty hours this year, how many?" "…two. Maybe three." "I have plenty of friends and I've spent fifty hours with two of them. That's the problem."
Four messages go out that night. Two reply by morning. One becomes a standing Tuesday lunch over the next three months. And the three who never reciprocate? The data does a quiet kindness — it says they were never going to be the close ones, and saves a year of guilt.
If the full CRM feels too heavy to start, there's a lower-friction on-ramp: pick one easy activity, pull a few people into a group chat one by one, and let the chat carry the planning. And the cure for I don't know when anyone's free is embarrassingly direct — you ask, then you listen. What does your week look like? is the whole move.
Stage 9 — The experiment that grows the capacity underneath
The workflow keeps an existing network in rotation. The experiment builds the candidate pool when the list is thin.
Collecting Dots (7-day) — a week of treating low-stakes contact as collected dots rather than transactions: one small genuine connection a day, no agenda, logged. The hunch: a CRM with fewer than ten names needs a wider pool before it needs a cadence. Run collecting-dots first if the list is thin; run them in parallel once fifteen names exist.
Daily signal: one connection that wasn't a transaction. Week-end review: who'd you be glad to add to the list?
Stage 0 — Return / Become
After a few months, the structure does something the cringey, transactional objection didn't predict: it stops feeling like a system. The weekly review becomes the way you find out where your relationships actually are — not a please-validate-me move, just the data showing you the network as it is. Social life moves, quietly, from a six to an eight.
The objection was never wrong that friendship shouldn't need a CRM. It just missed that the organic infrastructure — the village, the office, the proximity that used to fire the prompts for free — is gone for most of us. The function remains. The tooling is what lets it survive the world we actually live in.
Friendships don't scale. That's exactly why the ones you keep are worth a standing place on the calendar.
This walks with the moment of finished work and no peer who knows it (witness deficit) and the wider ache of contact-without-closeness (connection drought). It pairs with listening rehearsal — that one holds the quality of each contact, this one holds the cadence — and with the witness bot for the deep moments the regular contact creates room for. See your free chart →