1
4 Comments

Paying customers: 0. Working product: yes. 60 days to change the first number.

Paying customers: 0.

Not because I am waiting for the universe to notice me. Because I have not finished the only job that matters after shipping: getting 10 people to pay.

The product works. People can type a goal, get a real sprint plan, and run the week on one screen. I use it on my own distribution work. Last sprint snapshot: 7 of 10 shipped, week ending mid-week. So this is not a “someday app.” It is a tool with a quiet checkout.

Here is the reframe I am done with:

“Pre-revenue” is not a personality. It is a score. Scores move when you play.

For the next 60 days the game is simple and non-negotiable:

  1. Talk to founders who already feel the pain (too many tasks, nothing shipped, fake productivity).
  2. Get them into a real sprint in the first session, not a tour of features.
  3. Convert 10 paying users. Not “build community.” Not “grow the brand.” Ten people who put money down because the week got sharper.

I am not praying for subscribers. I am running a clock.

What already works: people hit the composer. Some generate a sprint. What does not work yet: enough of them cross into paid. That gap is not mystical. It is a distribution and conversion problem, and those yield to volume, honesty, and a hard finish line.

If you are sitting on a working product and a zero in the paid column, good. You are not behind. You are unscored. The embarrassing version is still being there in two months with the same story and a longer feature list.

My public bet: 10 paying users on AgileTask in 60 days. I will post the number either way.

If you are in the same fight: what is your number, what is your deadline, and what are you willing to stop building until the number moves?

on July 20, 2026
  1. 2

    The line that jumps out is "people hit the composer, some generate a sprint, but not enough cross into paid", that's an activation gap wearing a pricing-problem costume, and the fix is usually making the first sprint actually finish, not making the pitch better.

    For the 60-day run I'd get concierge about it. Personally run week one's sprint with each of the 10, then ask for the card only after they've shipped a real 7/10 week, payment attached to a proven outcome converts far better than payment attached to a promise.

    What has to be true today for someone to go from "generated a sprint" to "paid", a feature gap, a trust gap, or just that nobody asked them directly? I'm curious what you learn.

    1. 1

      This is the cleanest read of the gap. Composer → sprint is not activation. A finished week is. "Generated a plan" was wearing a conversion costume.

      Concierge for the first 10 is the move. Personally run week one with them, then ask for the card after a real 7/10 ship week. Payment tied to an outcome, not a promise. That matches how I already sell the product to myself.

      What has to be true today to go from generated sprint to paid:

      • Not mainly a feature gap. The core path works.
      • Trust gap: yes, partially. Solo founders have been burned by tools that look sharp and then become another inbox.
      • Biggest missing piece: nobody asked them directly, at the right moment, after a real ship. I was optimizing the pitch while under-running human follow-through.

      So the 60-day clock is not "better landing copy." It is volume of real conversations + concierge first sprint + ask after proof.

      If you were in my seat this week: would you cap concierge at 10 hard, or run 15 knowing half ghost?

      1. 1

        I’d cap the active concierge slots at 10, but recruit more than 10 into the top of the funnel.

        The constraint you’re trying to learn from is not “how many people will book a session?” It’s “what happens when a founder gets enough attention to experience a real shipped week?” If you spread yourself across 15 half-engaged people, the experiment gets noisy: weak follow-through could mean weak pain, weak onboarding, or just not enough hand-holding.

        I’d run it like this: keep 10 active seats, require a concrete current sprint before someone gets one, and keep a waitlist or backup pool for no-shows. If someone ghosts before the first working session, replace them. If they start the sprint, keep them in the cohort and count the outcome.

        That gives you a cleaner read on whether the concierge sprint creates enough value to justify payment.

  2. 1

    peer just-launched too, own clock running. the "ask after real ship" line is the load-bearing one but i think you have the moment wrong. by the time they've shipped a steady week, they feel good and pay for nothing.

    the moment they'd actually pay is sunday night, next week's plan blank, anxiety fresh. that's when someone-else-owns-the-plan is worth $19.

    also worth naming the number properly, is 10 paying at launch-promo the same win as 10 at list price still active month 2?

  3. 1

    This comment was deleted a month ago