Building something that has not launched

The accurate sentence about QuoteHive is that it has not launched and the website is in early beta. I say it that way deliberately, and it is a strange sentence to keep saying, because it is a status rather than a result. Nobody asks a follow-up question to a status.

It is a marketplace for contractor bidding in Canada. Clients post work for free, verified contractors spend credits to bid on it. That is the shape of the thing, and the shape has been the same for months, and none of it has met a stranger yet.

What every previous job gave me that I did not notice

I spent about ten years in work that returned a signal on a fixed cycle.

A month closes. Either it closed on time or it did not. Either the two records agreed or somebody had to sit with them until they did. A filing goes out and is accepted or it is not. A client either pays or you find out why. None of those signals is pleasant, particularly, and several of them are just an absence of complaint, but they are external. They come from outside your own head, on a schedule you did not set, whether or not you feel ready for them.

I never thought of that as a feature of the job. It was just what a month was.

Pre-launch work has none of it. Effort goes in continuously and nothing comes back out. There is no cut-off, no acceptance, no external party with a view. You can work a very good week and a very bad week and the feedback from the world is identical in both cases, which is silence, because the world has not been told.

That is the actual psychology of it, and I do not think it gets described honestly very often. The difficulty is not doubt about the idea. Doubt would be a signal. The difficulty is that there is no mechanism by which the idea could currently be shown to be wrong, so you are running on your own assessment of your own work, indefinitely, and that is a measurement instrument with a known calibration problem.

Why I think most things end here

Not from a decision. I have never once heard of a project that held a meeting and resolved to stop.

They end because the internal signal is the only signal, and an internal signal decays. There is a week where less gets done and nothing at all happens as a result, which is the discovery that nothing happening as a result is the default state. After that the cost of a slow week is zero, and zero is a price that does not go up.

The people who get through it seem to have something that keeps producing an external event when the world is not producing one. Somebody else waiting. A date somebody outside would notice. I am not sure how much of that is temperament and how much is arrangement.

The part I am probably getting wrong

The obvious response is to manufacture signals. Set milestones, set dates, review against them, treat the internal calendar as if it were external.

I have done a lot of that in delivery work, professionally, for other people, and it works there. It does not obviously work here, and I have become suspicious of it, because a milestone you set, judge and pass is not evidence about the product. It is evidence about your own diligence, which was never the thing in question. There is a version of the pre-launch period where you get extremely good at hitting your own targets and learn nothing whatsoever about whether anyone wants the thing.

So I hold both. The internal cadence is necessary to keep the work moving and it is not information. Confusing those two is how a team arrives at a launch with eighteen months of green status and no customers.

I do not have the resolution. What I have is a habit of writing down, at the time, what I currently believe and why, so that when there is finally an external signal I can check my own assessment against it rather than reconstructing what I must have thought.

Which is, I notice, the only part of this that is genuinely borrowed from accounting. Not the discipline. The dating.