vietnamese mud crabsoft-shell crabdifferent species of crab
3
5 Comments

Follow-up: I posted here at "customer zero." You gave me a lot of advice. Here's what I did with it.

A couple of days ago I posted about shipping CoachDesk (a CRM for self-employed personal trainers) and admitting the humbling part — build was easy, I was at customer zero, and "build it and they'll come" was a myth I'd believed.
The replies were genuinely useful. The recurring theme: stop spraying links, and make sure the product is actually worth the distribution effort before you pour energy into distribution. A few of you basically said "your moat is thin, what makes a PT switch?" Fair.
So before I went back to outreach, I went back to the product and built the answer to that question.
CoachDesk now has an AI tier. The bet: PTs don't want another app, they want the admin to do itself. So it now drafts a coach's weekly client check-in replies in their own voice (using the client's actual numbers), writes their progress report summaries, reviews a client's nutrition log, and flags which clients are quietly about to cancel — before they do. Six AI tools, all running through one function I wired to the Anthropic API. Pennies per use.
I also did the unsexy work the first post's comments shamed me into: a reliability audit that found ~96 places an action could fail silently and still tell the user it worked. A billing bug that — embarrassingly — stopped customers from being able to upgrade (i.e. pay me more). Both fixed. And I leaned into a pricing angle the big players can't match: a flat price with no per-client fees, instead of the per-client pricing that punishes trainers for growing. Unlimited clients on the Pro and AI tiers; the entry tier covers up to 15, which is plenty to start.
Honest status update, because that's the whole point of these posts:
– Still effectively at customer zero. Two real trials now (up from "none were even real" last time). One keeps logging back in, which is the most hope I've had.
– So: better product, same distribution problem. Which a few of you warned me would happen if I treated building as the answer to a selling problem. You were right.
What I'm testing now instead of cold link-spam: personalised screen-recording demos sent to specific trainers, actually being useful in PT communities rather than dropping links, and trying to turn that one returning trial into my first real case study.
For those who answered the "first 10 customers" question last time — a sharper version now that the product's stronger: when your wedge was something boring-but-real (like pricing) rather than a flashy feature, how did you actually communicate it? Did anyone win in a niche whose users basically don't hang out online?

on June 7, 2026
  1. 1

    The pricing wedge is hard to communicate cold — "we don't charge per client" only lands once someone's already frustrated with their incumbent's bill. It reads defensive, not as a reason to switch.

    We ran into the same thing with goffer.ai — we make congressional data accessible as a webhook for developers and policy researchers. Saying "cheaper than X" didn't move anyone. What did: showing the actual workflow in a 90-second Loom. "goffer.ai fires a webhook → Zapier catches it → new row in your Airtable tracker per bill event." People could see the admin disappearing before they cared about price. You can set that up with no code at all.

    For PT communities that "don't hang out online" — the Mindbody and Trainerize subreddits and PT certification Facebook groups are quieter but real. The coaches there aren't online-native but they do post specific frustrations. If your AI check-in reply draft solves one of those frustrations, answer the post genuinely and mention CoachDesk once. Worth more than 50 cold DMs.

  2. 1

    It's great that the answers helped you figure it out. I'd like to do the same, but for now I have a new account here. In the future, I'll do as you did, post screenshots, and ask people like you to evaluate the product in its initial version.

  3. 1

    Love that you took the advice and actually acted on it, then came back to share how it went. That loop is what makes this place good.

  4. 1

    I think the interesting part is that you may have fixed the product problem and accidentally created a positioning problem.

    You now have at least three possible wedges:

    flat pricing
    AI admin
    client-retention signals

    The risk is that trainers react positively to all three, but you still don't know which one is strong enough to make them switch.

    I'd be careful about treating "more outreach" as the next experiment before that decision feels clearer.

    There is a big difference between a trainer saying "that's useful" and a trainer saying "I need this."

    Happy to put the tighter wedge decision in writing if useful. That's the part I'd want confidence in before scaling the outreach.

  5. 1

    This is really insightful. I’m curious—what changed the most for you after implementing the feedback from Customer Zero? Would love to hear what surprised you the most.

Trending on Indie Hackers
Most founders don't have a product problem. They have a visibility problem User Avatar 95 comments Day 4: Why I Built a $199 Workspace Nobody Asked For User Avatar 51 comments How to automatically turn customer feedback into high-converting testimonials User Avatar 39 comments Spent months building LazyEats AI. Spent 1 day realizing I have no idea how to get users. User Avatar 30 comments Why Claude Skills Are Becoming Important for Tech Careers User Avatar 25 comments I kept rewriting the same quiz + spaced-repetition code. So I packaged it into an API User Avatar 21 comments