Ask
420
@flat_rate_finn ·

consulting pays $6.2k a month, the product makes $210 - how do people actually taper without falling off a cliff

Two clients on retainer, roughly 25 hours a week, $6.2k. The product is a smaller version of something I built for one of them, it's been live seven months, and it makes $210 MRR from 14 customers.

The gap is so wide that 'go full time on the product' isn't a decision, it's a fantasy. But the product only grows in the hours I'm not billing, and I have maybe six good hours a week.

For people who made this cross: did you drop a client, raise rates to work fewer hours, or take a lump of savings and set a date? What actually happened, rather than what you planned?

10 answers Share
Report

Answering anonymously — a moderator will review it first.

  • @pgpolicy_nadia · 9mo ago · 3 replies

    Raised rates. That's the whole strategy and it's the one nobody wants to hear. Went from hourly to a fixed monthly fee for a defined scope, roughly 40% more money for about 60% of the hours, and one of the two clients said no. The one who said yes is the one I still work with four years later.

    That freed a day and a half a week, and a day and a half is a completely different animal from six evening hours. You can do sales calls, you can answer support during business hours, you can think. Evenings are for code. Days are for the business.

    187
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @gio_castellan · 9mo ago

      'Evenings are for code, days are for the business' is the actual insight here. My product was stuck for a year because everything customer-facing needs daylight.

      61
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
    • @supa_okonkwo · 9mo ago

      Also, the client who says no is information. Mine said no and then came back four months later at the new rate.

      34
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @probe_to_ground · 9mo ago · 2 replies

    Set a floor and a date and make them boring. Mine was: I go part-time on services when the product covers my fixed personal costs for three consecutive months, and I stop entirely when it covers those plus 30%. Writing the number down mattered more than the number itself, because $210 to $6,200 feels impossible and $210 to $2,400 is a target.

    Also: 14 customers at $15 average is a pricing statement as much as a growth statement. Doubling the price with 14 customers is a much shorter path to $2,400 than getting to 160 customers at the current price, and you'll lose fewer of them than you fear.

    143
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @boom_pole_bex · 9mo ago

      Went from $12 to $39 with 20 customers. Lost three. Revenue more than doubled and support volume dropped, because the ones who left were the heaviest and the worst fit.

      48
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @two_week_notice · 9mo ago

    Don't drop a client without a date and a number written down first. You'll fill the free time with product work that doesn't compound and then panic in month three.

    62
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @label_reader_lo · 9mo ago · 2 replies

    Pushing back on the framing that consulting is the obstacle. It's the reason your product exists and it's your best source of customers. The people who cross successfully usually don't taper - they change what the consulting is. Stop selling hours and start selling implementations of your own product at a high price. Same clients, same skill, but now every engagement makes the product better and creates a reference.

    The failure mode I've watched several people hit is quitting services entirely at $2k MRR and then spending a year doing panic freelancing at worse rates than before.

    96
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @two_vcpu_club · 9mo ago

      This is the version I'd recommend to anyone with a services background. A productised implementation is a real business and it doesn't feel like giving up.

      39
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @layer_shift_lu · 9mo ago · 2 replies

    Nine months into the same situation so no crossing story yet, but one thing helped more than expected: I moved all client work onto three fixed days and made those days genuinely unavailable for the product, and the other two genuinely unavailable for clients.

    Before that, everything bled into everything and I did about four real hours of product work a week while feeling busy constantly. Same total hours, roughly triple the output, and the clients haven't noticed or cared which days I work.

    31
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @sear_after_sam · 9mo ago

      Blocking the calendar is the easy half. Telling clients your response time on the other days is the half that makes it stick.

      17
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report