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?
The line that stood out to me was:
"Better product, same distribution problem."
I think a lot of founders (myself included) underestimate how often building feels like progress while actually avoiding the harder problem.
I launched a Cyblux GDPR Generator on Product Hunt today and had a similar realization. It's tempting to think one more feature, one more improvement, or one more week of development will change everything.
But at some point the bottleneck stops being the product and becomes distribution, trust, and positioning.
The fact that one trial user keeps coming back feels more important than almost anything else in this post. I'd probably spend more time understanding that person than building another feature.
Looking forward to your next update.
Congrats on launching on Product Hunt today — that's the genuinely nerve-wracking bit done. And yeah, you've named the trap precisely: building feels like progress because it has a finish line and a dopamine hit, while distribution just sits there being hard and unrewarding. So I keep 'improving the product' as a way of not doing the scary thing. One more feature is the founder's version of cleaning the house to avoid the real work.
You're right about the trial user too — it's become the loudest signal in this whole thread, and I'd been treating it as a hopeful little metric rather than the actual lead it is. Spending real time understanding that one person instead of building feature number whatever is the plan now.
Will post the next update when there's something honest to report — good or bad. Rooting for the GDPR Generator; that's a properly real pain you're solving
The iteration report format you are using here is underrated. Most posts are either "I built this" or "I got advice" - rarely "here is what I actually did with the advice."
For us building goffer.ai (legislative data webhooks for compliance teams), the most valuable advice from early users was that they did not want a dashboard. They wanted the data to come to them. That shifted our whole delivery model from a web app to webhooks + Zapier/Slack.
The no-code integration path ended up being 80% of what people actually wanted. Useful signal for any B2B tool: the delivery mechanism matters as much as the data.
The most useful sentence in this whole post is your own: better product, same distribution problem. You asked the thin-moat question and then answered it by building again, which is the comfortable move. At customer zero you can't actually know the moat was the blocker, because you have no customers telling you why they didn't switch. The AI tier might be great, but don't let it become another place to hide from selling.
On communicating a boring-but-real wedge: you don't communicate pricing, you communicate money in their pocket. Something like "per-client pricing punishes you for growing. Go from 15 clients to 50 with us and your bill doesn't move, that's roughly $X a year you keep." Run it as a direct, named comparison against whatever they use today. Wedges get sold by side-by-side math, not by being mentioned.
On the niche that isn't online: trainers absolutely cluster, just not where you're looking. They're in gyms, on Instagram, in cert communities, and in trainer WhatsApp and Facebook groups, and they trust other trainers far more than they trust an app. Your personalised screen-recording demos to specific trainers are exactly the right instinct, so do ten times more of that. Better yet, go offline: get one respected trainer to 50 clients on your flat price, document the money saved, and let them refer their peers. Niches that don't hang out online are won one delighted user and one referral at a time. That returning trial isn't a metric, it's your first case study. Treat them like a design partner.
The line that's going to sit with me is 'don't let it become another place to hide from selling.' You're right that I can't actually know the moat was the blocker — I diagnosed a thin moat and then fixed it by building, which is the move that feels productive and conveniently isn't selling. I'd dressed it up as responding to feedback, but you've named the more honest version: I retreated to the thing I'm good at. The test of whether the AI tier mattered isn't that I built it — it's whether a real trainer tells me it's why they stayed. I don't have that data yet, so the moat question is still technically open.
The 'money in their pocket' framing is sharper than where I'd got to — not 'flat pricing' but 'go from 15 to 50 clients and your bill doesn't move, that's roughly $X a year you keep,' run as a named side-by-side. Wedges get sold by math, not by being mentioned. Stealing that.
And the design-partner framing of the returning trial is the reframe I needed — not a metric to feel hopeful about, a person to build the next version alongside and document the saved money with, who then refers their peers. That's now the plan. Genuinely one of the most useful comments on here — thank you for not just being nice about it.
Hannah, it's inspiring to see how you applied community feedback to enhance CoachDesk, love that you’re focusing on adding real value with the AI tier. How are you planning to gather user feedback on these new features? It might be helpful to consider whether you can create case studies from early adopters.
Thank you — though honest caveat: I'm gathering feedback on the AI features mostly in theory right now, because I don't have anyone actively using them yet. That's the real bottleneck — the features exist, the users to test them don't.
So the plan is less 'survey my adopters' and more 'create the first one.' My one trial user who keeps logging back in is the obvious starting point — get them genuinely using the AI tools, sit with them while they do it, and turn that into the first real case study rather than guessing what trainers want from the outside. The whole thread's pushed me toward going deep on that one person rather than chasing breadth, and feedback is exactly why — one trainer actually using it tells me more than fifty signups who never touch it. Appreciate the nudge on case studies; it keeps coming up because it's clearly the move
The demo-in-onboarding change is the right call. If a trainer sees their own voice handed back in minute 3, the sale is basically done before the pricing page loads. On beta users: since you're in PT communities, the move I'd try is responding to specific pain posts with something personal, not a link. Two sentences that show you understand the exact situation. That's what gets a DM.
Exactly — if the demo does its job in minute 3, the pricing page is just confirming a decision they've already made, not making the case. That's the order I'd been getting wrong.
And the two-sentences-not-a-link move is the bit I keep having to physically restrain myself from skipping — the instinct is to drop the link because it feels like 'doing something,' but a link is a pitch and two sentences that prove you understand their exact situation is a conversation. The DM comes from being recognised, not from being sold to. Going to hold myself to no-link-first. Thanks for this
The flat-price-vs-per-client-fee wedge is underrated, "we don't punish you for growing" is a positioning a big player structurally can't copy without torching their own revenue model. To your question about communicating a boring-but-real wedge: the trick is to make the pain visible, not the feature. Don't say "flat pricing," say "here's your bill at 40 clients on them vs us." And for niches that aren't online, one returning trial who keeps logging in IS your case study, I'd go deep on that one person and let them recruit the next two. :)
The bit you've said that nobody else did — that it's a positioning the big players structurally can't copy without torching their own revenue model. That's the part that makes it a real moat rather than just a nicer price: per-client fees aren't a choice they can drop, they're the engine, so 'we don't punish you for growing' is something they literally can't say back. That reframes it from a pricing tactic to a structural advantage.
And you're echoing what's become the loud consensus of this whole thread — show the bill at 40 clients, not the word 'flat,' and go deep on the one returning trial as the case study who recruits the next two. At this point that many people independently saying it isn't advice anymore, it's marching orders. Thank you :)
The line "if I treated building as the answer to a selling problem. You were right" is something every developer needs to tattoo on their arm.
Here is the brutal reality of the PT niche: your pricing angle (no per-client fees) is an incredible retention mechanism, but a terrible acquisition hook. Why? Because a PT who is stressed about customer zero doesn't care about a "scaling penalty" they don't have the scale yet to feel that pain.
To win users who aren't online, you have to sell the immediate, acute pain relief of your new AI features (e.g., "Stop spending your Sunday nights writing client check-ins"). Save the flat-rate pricing pitch for when they are onboarding and realized they just unlocked unlimited scale.
This cuts against most of the thread and I think you might be right. Everyone's been helping me sharpen the pricing wedge, but you've pointed out the thing underneath it: a PT at customer zero hasn't felt the scaling penalty yet, so 'no per-client fees' is solving a pain they don't have. It's a brilliant reason to stay and a weak reason to arrive.
Which splits my messaging cleanly: lead acquisition with the acute, this-Sunday pain — 'stop spending your Sunday nights writing client check-ins' — and hold the pricing pitch for onboarding, when they suddenly realise growing won't cost them more. Hook on relief, retain on fairness. I'd been trying to make one message do both jobs.
That's genuinely reframed my whole funnel. Acquisition pain and retention pain aren't the same pain — thank you for being the one to say it.
Bravo, Hannah. You're doing it!
Thank you — needed that today. Onwards.
My biggest takeaway is that progress often looks smaller than we expect. It's easy to focus on revenue and ignore the fact that better positioning, clearer messaging, and deeper customer conversations are all forms of traction too.
That's a healthier way to read it than I've been managing. I keep measuring myself against the revenue line and feeling like nothing's moving, when actually the positioning got sharper, the messaging got more honest, and I'm about to have my first real customer conversation. None of that shows up as a number yet, but it's the stuff the number eventually comes from. Needed the reminder — thank you
The gap between "useful" and "I need this" is where most early stage products live longer than they should.
Your returning trial is not just hope. That person is already telling you which version of the product is worth staying for. The question is whether you know exactly why they keep coming back. That one answer is worth more than any outreach campaign right now.
On the offline niche problem PTs trust other PTs before they trust any tool. Win one trainer in a gym and the back office conversation does the selling for you. No cold DM beats that.
You've put your finger on the same two things the thread keeps converging on — and at this point the repetition is the message. The useful-vs-need-this gap is exactly where CoachDesk is sitting, and my one returning trial already knows which version is worth staying for. I just haven't asked them properly yet. That's on me, and it's the next thing I do.
And the win-one-trainer point keeps coming up because it's clearly right — PTs trust other PTs, so the back-office conversation does the selling I can't. Thanks for reinforcing it; consensus this strong isn't something I'm going to argue with
The "users don't hang out online" niche is the one I keep ending up in too (building a Whatsapp agent for small businesses). What's been working for me: skip communities entirely and go 1:1 — find 20 specific operators, DM them with a personalized loom showing their actual workflow improved. Slower but the conversion is wildly different. For PTs you could probably hit gym owners and propose CoachDesk as their staff retention tool.
The 1:1 personalised Loom approach is exactly where I've landed too — slow, unscalable, and apparently the only thing that actually converts in niches like ours. Twenty specific operators with their own workflow shown back to them beats a hundred broadcast posts. Reassuring to hear it's working for you, because it does feel painfully slow while you're doing it.
The gym-owner angle is the bit that's new to me though. Pitching CoachDesk to the owner as a way to keep their self-employed trainers happy and less likely to leave — that flips the whole sale. One conversation puts it in front of every PT in the building, and it reframes the product as the owner's retention tool, not just the trainer's admin tool. That's a much bigger lever than going trainer-by-trainer. Going to think hard about how that pitch actually reads to an owner.
How are you finding the 20 operators for your WhatsApp agent — sourcing them somewhere specific, or just hunting them down one by one?
Building the moat before going back to distribution is the right call. The 'which clients are about to cancel' feature is the one that will close deals — that's not 'I have AI', that's 'I know which of your clients is quietly ghosting you before they actually leave'.
One thing worth testing: the 'in their own voice' check-in reply angle is a big differentiator but it needs to be shown, not described. A PT who reads that feature description will be sceptical until they see their own reply drafted back at them. If you can get that demo moment into the first 3 minutes of onboarding, that's your activation event right there.
How are you finding beta users at the moment — PT communities online or more direct outreach?
I know which of your clients is quietly ghosting you before they leave' — that's the sentence. Miles better than anything on my pricing page. You've done in one line what I've been talking around for weeks: it's not 'I have AI,' it's a fear named out loud.
The activation-event point is the one I'll act on fastest. You're right that 'drafts replies in your own voice' is pure scepticism until a trainer sees their own voice handed back — describing it does nothing, the demo is everything. Getting that moment into the first three minutes of onboarding instead of leaving it for them to discover is a real change. Adding it.
Honest answer on beta users: I'm mostly not finding them yet — that's the whole problem behind this post. I've ruled out cold DMs and link-spam, so what's left is being genuinely useful in PT communities and personalised screen-recording demos to specific trainers. Plus turning the one trial who keeps logging back in into a real case study. So: more direct-and-useful than broad reach, but I'd be lying if I said it was working at volume yet. That's the bit I'm trying to crack
The 96 silent failures line is the part I'd turn into the wedge, trainers dont buy an AI tier first, they buy something that wont quietly drop a client check-in. I've seen founders explain pricing with a Notion table when what lands is the moment the old tool punishes growth, people usually test that with Loom, Hotjar, or ScoresPulse style post-trial pulses to hear the exact objection in the customer's own words. ngl if one returning trial is still showing up, I'd interview that person until the pricing sentence almost writes itself.
The reliability-as-wedge angle is one nobody else has said, and it might be the truest. You're right — no trainer wakes up wanting an 'AI tier.' They want to trust that the thing they handed their client admin to won't quietly fail and cost them a client without telling them. The 96 silent failures aren't a bug-fix footnote, they're the actual product promise: this won't drop the ball on your behalf. That's a more honest wedge than any feature, because it's the fear underneath all the features.
And yeah — the returning trial. The consensus across this whole thread is deafening at this point, so I'll say what everyone's telling me back to them: interview that person until the pricing sentence writes itself. That's the plan.
ScoresPulse-style post-trial pulse to catch the objection in their own words is a good shout too — appreciate the specific tooling, not just the principle
"Build is not the answer to a distribution problem"
— this landed hard. I shipped my first app today
and I'm already feeling this tension. Thanks for
the honest follow-up. Following your journey.
Congrats on shipping today — that's the genuinely hard part done. And yeah, that tension hits fast: the build has a clear finish line and distribution never does, so it's so tempting to keep building because at least it feels like progress. The thing I'm learning the hard way is that the discomfort of 'I don't know how to get users' doesn't go away by adding another feature — it just gets postponed.
What did you launch? Always good to compare notes with someone hitting the same wall at the same time
Love that you came back with a follow-up — that loop is rare and it's exactly what makes this community work. What piece of the advice ended up making the biggest difference?
Thank you — honestly the loop is selfish on my part, coming back forces me to actually do something with the advice instead of nodding and forgetting it.
Biggest difference by a mile: the reframe that I'd fixed a product problem and handed myself a positioning one. I'd convinced myself building the AI tier was progress, when really I'd just given myself three possible wedges and no idea which one makes a trainer actually switch. That one comment stopped me reaching for 'more outreach' as a way to avoid the harder decision. Closely followed by everyone independently pointing at my one returning trial user as the real asset — when that many people say the same thing, it's not advice, it's a signal.
That's a really honest unpack — and the "three wedges, no idea which one converts" trap is so common it should have a name. The fact that multiple people independently pointed at your one returning trial user is the signal worth obsessing over. You already have your answer in the room; now it's just about doubling down on whatever made that one person come back. Excited to see where you take it.
The pricing wedge communication problem is fundamentally a value visibility issue. Features are tangible — you can show them. Pricing fairness is a feeling — and feelings need anchoring to land. The way to communicate 'no per-client fees' isn't to explain the pricing model. It's to show the trainer the exact moment the old model punishes them — 'you just hit 20 clients, congratulations, your bill just doubled' — and then contrast it with yours. Make the pain of the alternative visceral before introducing your solution.
On the offline audience question — personal trainers who don't hang out online are reachable through the environments where they actually exist. Gym owner WhatsApp groups, PT certification communities, continuing education workshops. The person who reaches them first with genuine value owns that channel. A one-page PDF diagnostic — 'Are you losing clients silently?' — left at a gym front desk gets more attention than any cold DM.
Your one returning trial is your most valuable asset right now. That person is your case study, your testimonial and your referral engine simultaneously. I'd invest everything in understanding exactly why they keep coming back.
You're the third or fourth person to land on the same three things — make the pricing pain visceral before naming my solution, reach PTs where they actually are, and pour everything into the one returning trial. When that many sharp people independently point at the same conclusions, that's not advice any more, that's a signal I'd be stupid to ignore. So those are now the plan, not the maybe.
The new thing you added that nobody else did — the one-page 'Are you losing clients silently?' diagnostic left at a gym front desk. That's clever because it's the retention pain in physical form, sitting exactly where my buyer already is, and it asks a question they can't not answer in their head. Going to make that. Thank you.
The pricing wedge lands best when you name the moment the competitor's model bites, not the price tag itself. Per-client pricing punishes the exact thing a growing PT is proud of, which is having more clients. So lead with that feeling: you shouldn't get taxed for being good at your job. Then make it concrete with their own numbers, like "at 40 clients you're handing your CRM a few hundred a month just to exist, here it's flat." The number does the arguing for you.
I'm building a personal finance app where the wedge is similarly unsexy, no bank linking and a flat price against YNAB's subscription. The thing that actually moved people wasn't "cheaper," it was the specific anxiety the incumbent created (handing a third party your bank login). Boring wedges sell on the pain they remove, not the feature list.
On the niche that doesn't hang out online: your screen-recording demo instinct is right. The trainers worth winning are usually inside other structures, certification cohorts, gym back offices, the WhatsApp group their mentor runs. Showing up useful in one of those beats any amount of public posting. And that one returning trial is your real asset right now. I'd put everything into turning that single person into a case study with real before and after admin-time numbers, because that story is what you hand to the next ten.
'You shouldn't get taxed for being good at your job' — that's the line I've been circling and never quite caught. I kept framing it as a price comparison when the real thing is the feeling: per-client pricing punishes the exact thing a growing PT is proud of. Lead with the feeling, then let their own number do the arguing. 'At 40 clients you're paying a few hundred a month just to exist; here it's flat.' I don't have to sell it — the maths does.
Your YNAB parallel makes it click — people didn't switch because you were cheaper, they switched because of the specific anxiety the incumbent created. Boring wedges sell on the pain they remove. Same shape as mine: nobody switches CRM for 'flat pricing,' they switch to stop being penalised for growing.
And you're the third person in this thread to point at the returning trial as the real asset — at this point I'd be an idiot to ignore the consensus. Turning that one person into a case study with actual before-and-after admin-time numbers is now the plan. That story is what I hand to the next ten, instead of me guessing on their behalf. Genuinely useful comment — thank you.
On the offline-niche part, PTs cluster, just not where founders look. They trust other trainers and their gym owner way more than any ad. Win the one trainer others copy and the whole gym follows. In offline niches you grow through whose opinion they already trust, not reach.
'Win the one trainer others copy, and the gym follows' — that reframes the whole acquisition model from reach to trust. I've been thinking in terms of how many trainers I can get in front of, when the real question is which one trainer carries the others. One respected coach in a gym is worth more than a hundred cold impressions.
Which is partly why my one returning trial user matters so much — if they're the kind of trainer others look to, getting them genuinely happy isn't one customer, it's a doorway. Going to find out who they actually are in their gym. Thanks for this — it's the missing piece in how I was thinking about the offline communities
"Better product, same distribution problem" — this line should be printed on every founder's wall.
The billing bug that stopped customers from upgrading is painfully relatable. Sometimes the thing blocking revenue is embarrassingly close to the surface.
On your wedge question — flat pricing in a per-client world is actually a strong message, but it only lands when the person you're talking to has felt the per-client pain. So the targeting becomes everything. Find the trainer who just hit 20 clients and watched their bill jump — that's your buyer.
Launched my own thing today too. Distribution is exactly where I'm focused. Following your journey. 🙌
Find the trainer who just hit 20 clients and watched their bill jump' — that's the sharpest targeting note I've had. My pricing message isn't wrong, it's just aimed at everyone instead of the one person actively feeling the pain right now. The trainer who's growing and getting punished for it is the buyer; everyone else is 'that's nice.' Completely changes who I go looking for.
And yeah — the billing bug being the thing literally blocking my own revenue still stings. Closest call there is.
Congrats on launching today — that's the scary part done. Distribution being where you're focused means you already know the real fight isn't the build. What did you ship?
Shipped Signal Brief — a free weekly newsletter for developers and AI practitioners. Cuts 500+ stories down to the 5 that actually matter, every Monday.
Issue #1 is live. Just hit #3 on Shipit today too.
thesignalbrief.co
The iteration report format you are using here is underrated. Most posts are either "I built this" or "I got advice" - rarely "here is what I actually did with the advice."
For us building goffer.ai (legislative data webhooks for compliance teams), the most valuable advice from early users was that thThe iteration report format you are using here is underrated. Most posts are either "I built this" or "I got advice" - rarely "here is what I actually did with the advice."
For us building goffer.ai (legislative data webhooks for compliance teams), the most valuable advice from early users was that they did not want a dashboard. They wanted the data to come to them. That shifted our whole delivery model from a web app to webhooks + Zapier/Slack.
The no-code integration path ended up being 80% of what people actually wanted. Useful signal for any B2B tool: the delivery mechanism matters as much as the data.ey did not want a dashboard. They wanted the data to come to them. That shifted our whole delivery model from a web app to webhooks + Zapier/Slack.
The no-code integration path ended up being 80% of what people actually wanted. Useful signal for any B2B tool: the delivery mechanism matters as much as the data.
The delivery-mechanism point is the one I keep underrating. 'They didn't want a dashboard, they wanted the data to come to them' — that reframes how I should think about my AI tools entirely. Right now my retention flag lives inside the app, which means a PT only sees it if they log in. But the whole value is catching a client before they drift — so the flag should come to the trainer, not wait for them. A WhatsApp or push that says 'Sarah's gone quiet, here's a check-in draft' is worth ten times the same thing buried in a dashboard.
So same lesson, different shape: for you the data needed to leave the web app; for me the alert needs to. Going to rethink where my AI output actually surfaces. And thank you for the format note — honestly the iteration report is just me being too scared to claim a win, so I report the homework instead. Nice to hear that's the useful version.
Still at customer zero with two trials —
that one user who keeps logging back in?
That's your signal. Don't lose them.
I'm Minchul, 57, former construction manager from Korea.
Built Slash it — an Email Decision OS.
Also at customer zero, also figuring out distribution.
Following your journey — we're in the same boat right now.
Minchul — genuinely glad you commented. Construction manager to Email Decision OS at 57 is a better founder story than mine, and 'customer zero figuring out distribution' might as well be both our bios right now.
You're right about that one returning user — they're the only data point I actually trust at the moment, and I'm trying not to scare them off by being too eager. Slash it sounds like a sharp idea — an Email Decision OS is exactly the kind of boring-but-real wedge people underrate. Good to have someone in the same boat to compare notes with — let's check in on each other's progress as we go
Same boat, same grind. Let's do it. Rooting for your one returning user — that's where it starts.
The boring wedge lands differently depending on who is comparing. With pricing, the customer already knows the pain -- they just have not seen your number next to the competitor's number.
What worked in similar positioning: lead with a specific scenario, not the feature. Not "flat pricing" but "if you go from 10 clients to 30, your software bill stays the same." The customer fills in the math.
On the offline community problem: PT certification courses and continuing education events. Not to sponsor -- just to find the group chats. Personal trainers with businesses small enough to care about per-client fees share referrals and tool recommendations in WhatsApp groups and local gym networks. One referral inside that group outweighs 50 cold emails.
The returning trial is your lever. Get them on a call, ask what made them come back, and whatever they say -- that is your pitch language.
If you go from 10 clients to 30, your bill stays the same' — that's the line. I've been stating the feature ('no per-client fees') and making the reader do the translation. You've just done the translation for them, and it reframes the wedge from defensive to aspirational: it rewards growth instead of apologising for price. Stealing it.
The certification-course and local-gym WhatsApp angle is smart too — that's where the trainers small enough to feel per-client pricing actually talk, and a referral inside a group like that carries weight no cold email ever will.
And you're right that the returning trial is the lever. Getting them on a call and using their own words as the pitch language is exactly the move — that one person can tell me more about why CoachDesk matters than another month of me guessing. That's my next action.
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.
This is the unlock, thank you. You've named exactly why my pricing copy reads flat — 'no per-client fees' is an answer to a frustration the reader hasn't felt yet, so it lands as defensive. Showing the admin disappear before price ever comes up completely flips the order. My retention-flag tool is the obvious thing to Loom that way: 'client goes quiet → CoachDesk flags them → you send one message → you keep the client.' They feel the save before they ever think about cost.
The goffer.ai webhook→Zapier→Airtable example is a perfect template for that, even though my product's a different shape. Going to record one this week.
And the community point is the bit I needed — I'd written off some of those spaces as 'not online enough' to bother, which was lazy. Answering a specific frustration genuinely and mentioning CoachDesk once is a completely different thing to dropping links, and I know which one I'd respect as a reader. Appreciate you taking the time on this one.
That Loom sequence you described is exactly the pitch: client goes quiet, CoachDesk flags it, you send one message, client stays. Record that once. Send it 50 times. The pricing page doesn't need to do the selling if the demo already did.
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.
Honestly don't wait as long as I did — I sat on it convinced it wasn't 'ready,' and the feedback I got at the messy early stage was worth more than anything I'd have gotten polished. Post it rougher than feels comfortable. People here are kind about the product and brutal about the thinking, which is exactly the right way round. Tag me when you do — happy to be one of the people who takes a proper look
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.
Means a lot — and honestly the only reason I came back to share is that the first round of replies were too good not to act on. This place keeps me honest in a way posting wins on Instagram never will.
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.
This is the comment I needed and didn't want. You're right — I fixed a product problem and handed myself a positioning one, and 'more outreach' is me reaching for the thing I know how to do instead of the decision I'm avoiding.
My gut says the retention signal (flagging who's about to cancel) is the only one that crosses from 'useful' to 'I need this' — because losing a client is a number a PT feels in their bank account, whereas flat pricing and AI admin are both 'nice' until something forces the switch. But gut isn't confidence, and I haven't pressure-tested it against a real trainer yet.
And yes — I'd genuinely take you up on putting the wedge decision in writing. That's the exact thing I'd rather get right before I spend a single hour on outreach. Happy to take it wherever's easiest for you
That's exactly why I'd want to separate the thread discussion from the actual decision.
The useful part is not whether retention signals sound strongest today. It's pressure-testing whether that wedge can reliably carry the positioning, outreach, and switch decision without creating new confusion elsewhere.
That tends to work much better as a focused written pass than a thread exchange.
Drop your email and I'll send it over there.
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.
Honestly? The most surprising thing was how much I'd convinced myself building was the answer to a selling problem. New AI tier, reliability audit, the lot — and I'm still basically at customer zero, just with a better product. The bigger gut-punch was the reliability audit turning up a billing bug that was quietly stopping people from upgrading. So my 'feedback' was partly just discovering I'd been blocking my own revenue. Cheap lesson, in the end — fix the thing that lets people pay you before you go chasing more of them.