Ask
268
@two_vcpu_club ·

$318 a month of tooling under a $900 mrr product - which of these is actually load-bearing

Went through the card statement properly for the first time. Under a product doing about $900 MRR:

hosting and database $84, error tracking $29, transactional email $20, analytics $14, support widget $39, a CRM I have opened twice $49, object storage and bandwidth $22, domain and backups and misc $18, and an AI API bill that was $43 last month and $12 the month before.

That's 35% of revenue before the payment processor takes its cut and before counting my own time at anything. Everyone says stay lean and nobody says which line to cut. Which of these did you actually regret paying for?

10 answers Share
Report

Answering anonymously — a moderator will review it first.

  • @retainer_rue · 3mo ago · 3 replies

    Cut the CRM today, you've told us you don't use it. Cut analytics if you can answer 'where did last month's signups come from' out of your own database, which at your size you can - a referrer column on the signup row plus a weekly query beats a dashboard nobody opens.

    Keep error tracking, it's the cheapest thing on that list per hour saved. Keep the support widget only if it lands in the same inbox as your email. Two inboxes at solo scale is how you miss the one message that mattered.

    121
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @hem_and_haw · 3mo ago

      Storing the referrer and first landing page on the user row is the best twenty minutes of code I have ever written.

      44
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
    • @quietpackets · 3mo ago

      Careful with only doing that, though - it misses everyone who bounced. It tells you who converted, not what the top of the funnel looked like.

      26
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @colorgrade_cleo · 3mo ago · 2 replies

    35% on tools at $900 MRR is high but not alarming, because most of those lines are flat and your revenue isn't. The number that matters is what it looks like at $3k.

    Model it. Scales with users: email, storage, the AI bill, hosting. Flat: error tracking, CRM, support widget, domain. Your flat costs are about $135 and they'll be identical at $3k, which is 4.5%. That's fine. The AI line going from $12 to $43 while revenue was flat is the only genuinely worrying row in the table.

    93
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @parquet_pile · 3mo ago

      A 3.5x jump on the AI line with flat revenue is either one heavy user or a retry loop. Both are worth an hour tonight, not next month.

      31
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @rollback_rae · 3mo ago

    Politely disagreeing with the cut-everything instinct. The reflex to shave $50 a month is usually procrastination wearing a spreadsheet. At $900 MRR, the thing that changes your life is $200 more revenue, not $200 less cost, and each of those cuts costs you an evening plus a migration risk. Cancel the CRM because it's genuinely unused, leave the rest, go do outreach with the evening you saved.

    57
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @stdlib_stef · 3mo ago

    Annual plans on the tools you're certain about. Usually two months free. That's most of your AI bill back without cancelling anything.

    38
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @label_reader_lo · 3mo ago

    One correction to the framing: your processor's cut isn't 'before' anything, it's the most predictable cost you have and it belongs in the same table. Put every line in one sheet with a flag for fixed or variable and the picture becomes much easier to argue with.

    30
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @thermal_theo · 3mo ago · 2 replies

    Did this exercise last month and found something dumb worth checking: I was paying for a staging environment on the same tier as production. Same database size, same instance, running 24/7, used maybe four hours a week. Dropped it to the smallest tier and put it on a schedule so it sleeps overnight. Saved about $30 a month and nothing broke.

    Also found two subscriptions from a project I killed in 2024 that were still quietly charging.

    22
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @costbasis_carl · 3mo ago

      The dead-project subscription is a rite of passage. Mine was an uptime monitor watching a domain that had expired eleven months earlier.

      11
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report