skicoachapp

Link for context: skicoach.app

Fair point.

I meant “finished enough to be used,” not “done forever.” The question is whether even that threshold still matters.

That makes sense.

It feels less like paying for coverage and more like paying for the machinery around it.

Once that’s the case, it barely matters whether something is finished or not. What matters is whether there’s a budget and a push behind it.

That’s the part I’m trying to wrap my head around.

Good reference.

“The Submarine” assumes visibility can come later. What I’m unsure about today is whether later still exists — or if coordinated amplification is now the price of entry.

That’s a great framing “the intensity of indifference” really resonates.

What I’m struggling with is less the idea that hustle is required and more the scale of it.

When even a finished product requires a ream of paper, 10 variants, repeated exposure, coordination, timing — it starts to feel like the signal isn’t “this exists” but “this has already broken through elsewhere.”

At that point, shipping feels necessary but almost irrelevant without an external amplifier.

Do you think that indifference has increased, or that the cost of breaking through has just grown beyond what individual builders can realistically do alone?

Agreed — and that’s exactly what I’m trying to understand.

What surprised me wasn’t that PR matters, but that shipping a finished product seems to carry almost no signal by itself anymore.

At that point it stops being about communication skill and starts feeling like a separate coordination layer entirely.

Do you think that’s just how things evolved, or did shipping simply stop being news at some point?

That’s a good way to put it — distribution really does feel like a different craft.

What I’m struggling with is that many products don’t have a “natural hangout” early on. Curious whether people here found one channel worth committing to, or if it was more about stacking small signals over time.

I agree that this model has a lot going for it.

What it does really well is set expectations upfront: you’re buying a version and a defined update window, not an open-ended promise.

Where I think many products stumble is skipping that clarity and retroactively redefining what users thought they bought.

If users know from day one: “this includes X months of updates, after that you can keep using it or pay for more”, most of the trust issues simply don’t exist.

That example actually highlights something important: it’s not just a technical pricing choice, it’s a perception thing.

When users feel like they were nudged into a subscription in a way that feels deceptive, that’s what really dents trust — sometimes more than the subscription itself.

It’s interesting to see how even big companies struggle with the narrative around subscription transitions.

That approach makes a lot of sense to me.

Adding new value and asking people to pay for more feels fundamentally different from taking something away and asking them to pay to get it back.

The moment users feel something was removed, the conversation shifts from value to resentment.

This matches my intuition almost exactly.

Especially the distinction between: paying once to own a version vs paying for an ongoing service.

I think a lot of conflict comes from companies blurring that line after users have already built habits and trust.

The point about security updates vs feature updates is interesting too — that gray area is where many products struggle to be explicit.