The cost of a customer, in hours

You know what a customer costs you in money. If you run ads, you know it to two decimal places. If you don't, you know it is roughly zero, and you say so with some pride.

It is not zero. It is a number of mornings, and nothing you own records it.

The input nobody logs

Every other tool in a go-to-market stack measures the channel. None of them measure what the channel costs, because the cost is your attention and your attention lives in your head.

The consequence is not that you make bad decisions. It is that you cannot make the comparison at all. A community that returned nothing over nine hours and a community that returned nothing over forty minutes are different problems with different answers, and every dashboard you have shows them as the same row: zero customers.

So the mornings keep going to whichever room feels loudest, and the one that quietly produces customers at half the cost gets whatever is left over. Not through carelessness, but through an absence of the number that would have settled it.

The block, and why it goes first

Effort only becomes a number if the work happens on a schedule. Two-hour floor, three-hour ceiling, in the morning.

The morning is not a preference. Building has a forcing function. Something is broken, someone is waiting, the deploy failed. Marketing has none. Whichever of the two goes second gets eaten by the first, every week, and you will have a good reason each time.

The block has a shape, and the shape is what makes the minutes comparable across days:

Time	Block	Scope
0:00	Sweep · 20 min	All apps. Replies, DMs, support, mentions.
0:20	Post round · 25 min	One post each, written in one sitting.
0:45	Community dive · 40 min	Today's room. Three contributions, zero links.
1:30	Build block · 20 min	Alternating: acquisition asset, then userbase.
1:50	Outreach and log · 10 min	One person helped. Then the numbers.

It ends on the output, not on the clock. Every app swept with no open loops, one post per app, three contributions with no links, one thing that could produce a customer today, one thing shipped, numbers logged. Done at 1h20? Go build. Not done at 2h? Not done.

And a short list of things that are not marketing, all of which will expand to fill the block if you let them: refreshing analytics, re-reading your own landing page, lurking, and tweaking copy nobody has seen yet.

Batch the writing, and post early

Two details of the block do more for the minutes-per-customer figure than anything else in it, and both are about the cost of context rather than the cost of the work.

Three posts written in one sitting cost far less than three posts written on three mornings. The expensive part is not the writing, it is loading the context: remembering what you were arguing, what you already said last week, which room takes which register. Pay that once. The distribution can happen on separate days; the writing should not.

And post early, harvest late. Replies land thirty to ninety minutes after posting, which means a post at the end of the block gets its conversation after you have closed the laptop, and you will either miss it or pay a second context load to answer it. Post at the start, and the sweep at the top of tomorrow's block collects the replies for free.

Neither of these makes the marketing better. They make the same marketing cheaper, which shows up in exactly the number this post is about.

Log it honestly, including the bad days

This is the part that decides whether any of the rest is worth anything.

The temptation is to round up. You were at the desk for forty minutes but you were also reading something else, so call it forty. You skipped Thursday but you thought about it, so call it twenty. Each individual rounding is defensible and the total is a lie.

It matters because effort is a denominator. Inflated effort makes cost-per-customer look worse than it is for the rooms you actually work, and better than it is for the ones you avoid. That figure is what drives rotation, which room gets tomorrow morning. Corrupt it and you will systematically rotate away from your best channel while feeling data-driven about it.

A skipped Tuesday logged as a skipped Tuesday is worth more than a plausible number.

The effort gate is a floor, not a target

Before this product will say anything about a community, it wants twelve contributions or 120 minutes recorded there. It is worth being clear about what that threshold is and is not.

It is not a productivity target. Nothing rewards you for exceeding it, and there is no streak. It is a data-quality floor: below it, the room has not been tested, and a conclusion drawn from two visits would be a conclusion about your availability rather than about the room.

Note also that effort is measured over the last seven days while the funnel accumulates from the day you entered the room. Those windows are deliberately different. Effort describes what you have been doing lately and should move when your behaviour moves. The funnel is evidence, and evidence should not evaporate on a rolling basis. A 30-day window would subtract clicks as fast as they arrive and hold a slow room permanently just under the threshold.

What it costs to not have it

It is worth naming the failure, because it does not feel like a failure while it is happening.

You work four rooms. One of them is genuinely good. The people there have your problem, the posts land, the signups convert. It is also quiet, and it is the one where you feel least clever, because the useful contributions there are short factual answers rather than anything you would screenshot.

Another room is loud. Every post gets replies. The replies are from other builders, none of whom will ever pay you, and the threads are enjoyable. You spend nine hours a month there because it feels like the room where things are happening.

With no effort log, both rooms show the same thing at the end of the quarter: some clicks, a few signups. The loud one has more clicks, because more people saw it. You conclude that the loud room is your best channel and give it more mornings.

With the effort log, the loud room is nine hours for two signups and the quiet one is ninety minutes for six. The decision reverses, and it reverses on a number rather than on a mood. That is the entire value of writing the cost down, and it is only available in retrospect, which is why it has to be recorded before you know you will need it.

What the number is for

Once effort is recorded, the comparison you could never make becomes routine. Thirteen customers for six hours and twenty minutes is twenty-nine minutes each. Four signups and no revenue for eight hours and forty minutes is a different kind of nothing from four signups over forty minutes.

What it does not tell you is how hard to try. Community work gets a project its first ten to fifty customers and tells you quickly whether anyone cares, and it stops the day you stop. that is its honest ceiling. Passive revenue comes from retention and from the always-on layer, not from more mornings in rooms.

So the number is a rotation instrument. It answers "where does tomorrow morning go", which is the only question you actually get to decide each day.