Follow-Up Has No Owner

It is Labor Day, which makes it a decent day for a time-spent audit. I was born on Labor Day, a long time ago, so the holiday has always been a reflective one for me. This year more than most. I have spent it at Civic working on giving my peers their time and effort back, and it seemed fair to check whether I had ever managed that for myself.

So, an audit. Not of the funnel. Of the week.

Where the week went

The last time I was the only market-facing person in the building, here is where the hours actually went.

Checking the visitor feed. Twice, because the first check was before coffee and did not count. Cross-referencing trial signups against the CRM by hand, one tab to the other, because the two systems had never been introduced. Guessing which signup deserved a note today. Writing that note. Forgetting the other four. Or was it five. I do not know, and that is the tell.

None of that was strategy. It was chores. Janitorial work. Manual labor, on the holiday named for it.

Here is what took me too long to admit. I did not lack signals. The feed was full of them. I lacked the hours to act on what the feed showed me, and I spent the hours I did have re-checking the feed. The instrument was fine. The operator was busy babysitting the instrument.

Paint your own week. Every half-hour block that went to housekeeping, mark it. The panel adds it up.

The pattern, named by parts

I have a habit of writing GTM patterns the way Bryn logs them: surface, behavior, window. Applied to my own week, the pattern is:

follow-up → maybe → forgot (3d)

A signup arrives. It goes on a mental list titled "maybe today." Three days later it is not on any list. That is not a kitschy way to pseudocode a workflow. It is a condemnation. It is the most common Play running on small GTM teams, and nobody wrote it, nobody approved it, and nobody logs it.

Here it is with five signups and two lanes. One lane is what happens when nobody owns the follow-up. The other is what happens when something does.

The no-owner lane is not a strawman. It is a Tuesday.

It is not a lead problem

The founders and superhero ICs I talk to are usually convinced they have one of three problems. A lead problem: not enough people showing up. A funnel problem: people showing up and leaking out somewhere. An interest problem: people showing up and not caring.

Most of them have none of those. They have a follow-up-has-no-owner problem. The signup happened. The intent was real. The note that should have gone out inside the hour went out inside the week, or did not go out at all, because the person who would have sent it was cross-referencing a spreadsheet.

I wrote about the shape of this in The Four Handoffs: every step between detection and action is a human handoff with no owner and no deadline. And last week, in The Class You Own, I made the case that product signals are the highest-fidelity class in the field and the class almost nobody runs. Put those two together and you get the audit above. The best signals you have, sitting in a feed, while the only person who could act on them checks the feed again.

What an owner looks like

An owner is one of two things. A person, or a Play.

A person works. A human checking one pattern every morning and sending one note is a perfectly good v0, and if you have the headcount, do that first. Write the pattern down. Write the note down. Give it a name and a time of day.

A Play is what it looks like when that stops being manual. You write the pattern once: when a signup clears your profile and matches this pattern, send this note from this owner, and log it. You approve it once. Then Bryn watches, scores each account against the profile you set, runs the Play you approved, and writes a record line for every instance. Not "initiating outbound sequence." A record: I scored acct_2210 at 0.71 and ran welcome-nudge-v2 at 09:14 UTC. Plain, checkable, yours.

Bryn is not another dashboard to watch. It is the governed execution layer that runs Plays through your stack. We ran it on ourselves first, and we still do. The first thing it gave back was not pipeline. It was Tuesday morning.

Which brings me to the question I asked on LinkedIn last week. If the babysitting hours came back to you, what would you build with them? (Assuming you did not want to spend them in The Club. If you were an 80s kid you know which club, and you know Saturday detention was not the productive kind.) I am serious about the question. Hours are the one budget a growth owner cannot raise more of.

Do the audit

Here is the gift, and it takes ten minutes. Monday or Tuesday, it is a holiday.

Tick the chores you actually did last week. Set the minutes a day each one took. Read the number in hours per week and hours per quarter. Then name the one follow-up on that list that has no owner, and give it one. A person or a Play.

Whatever number you land on, it is illustrative, not a benchmark. Your week is the benchmark. But I have not yet met a growth owner who ran this honestly and came back with a small number.

The offer, plainly

We priced a month of that labor at zero. Save Your Labor (Day) runs from Sep 3 to Sep 17. The first month of Bryn is free on any tier. Pick your tier and enter the code at checkout: LABOR-E26 for Explore, LABOR-B26 for Bootstrap, LABOR-G26 for Growth, LABOR-S26 for Scale. Plans start at $49 a month, billed monthly. The details are on the campaign page.

Why a month. Because the first month is where Bryn shows you the work. Not in a deck, in the log: every signup scored, every Play run, every note that went out at 09:14 instead of never. If the log does not give you your hours back, you will know by the end of it, and you will have paid nothing to find out.

Stop watching signals. Start running them.