2
6 Comments

Building a due diligence service for first-time SaaS buyers

I'm Raj, building a due diligence service for first-time SaaS buyers.

The problem I'm solving:

People buying their first SaaS business get burned because they don't know what red flags to check. Sellers inflate revenue, hide customer concentration risk, and don't mention tech dependencies.

What I'm doing:
Offering 30-min DD reviews that check:

  • Revenue verification (Stripe export analysis)
  • Customer concentration risk
  • Traffic sustainability
  • Tech dependencies
  • Risk translation ("what could go wrong")

Why I'm posting:
I'm doing 5 free audits this month to learn what buyers actually care about.

If you're evaluating a SaaS deal right now and want a second opinion, comment or DM me.

Also curious: what red flags have you seen when buying/selling that most people miss?

posted to Icon for group Startups
Startups
on May 7, 2026
  1. 1

    The due diligence gap for first-time buyers is real - they're often making a 0-100K decision based on a Stripe screenshot and a Loom walkthrough. That's not enough to underwrite the risk.

    The seller side of this is also broken: most solo founders trying to exit don't have the data organized to make due diligence easy. Revenue per customer, NRR trend, churn reasons, client concentration risk - these are things a buyer needs, but they're rarely structured in a way that tells a clean story. Archaeology instead of reporting.

    What changes the outcome: founders who've been tracking their revenue properly from the start. A dashboard that shows MRR, NRR, client attribution, and churn history turns a stressful due diligence process into a data room you already have.

    Building a revenue dashboard into a Solopreneur OS for exactly this reason. Not because everyone is planning to sell - but because the same visibility that makes your business well-run also makes it sellable if you ever want to.

    What's the most common gap you see on the seller side - missing historical data, inconsistent accounting, or something in how the business is documented?

  2. 1

    The customer concentration risk piece is where most sellers get surprised. They've never systematically tracked which clients account for what percentage of revenue because it all just 'felt fine' while it was growing.

    This is actually a systems problem upstream of the due diligence event. Solo founders at $0-5K MRR who don't have a revenue database that links clients to projects to tasks have no way to answer 'what percentage of our MRR is client X?' without doing a manual spreadsheet reconstruction.

    I'm building a Notion OS for solopreneurs specifically to have this data before they need it: six linked databases (clients, projects, tasks, revenue, decision log, weekly review). Revenue entries link to client records, so concentration risk is visible in real time, not reconstructed for a DD package.

    For your service: do you see buyers walking away from deals more because of the hard flags (inflated Stripe numbers) or the soft ones like customer concentration and tech dependency?

  3. 1

    I know a couple of first-time SaaS buyers who are currently evaluating a deal, and they might be willing to answer your questions for free. Happy to pass them along if you'd like.

  4. 1

    This is a real trust problem.

    First-time SaaS buyers do not just need more checks.
    They need confidence before they wire money.

    The strongest part here is not the 30-minute review.
    It’s risk translation.

    That’s the piece buyers actually pay for:
    “what could go wrong, and how serious is it?”

    If you build this beyond free audits, I’d be careful with the brand layer too.

    A due diligence product has to feel credible before the buyer shares deal data.

    Beryxa.com would fit this direction well if you ever want it to feel more like a serious SaaS acquisition trust layer than a lightweight audit service.

    1. 1

      I was so focused on building the best DD checklist that I forgot nobody cares how good the checklist is if they don't trust sharing their deal data with you first.

      Risk translation is exactly what I should be leading with. Not "we check 50 data points" but "we tell you what could go wrong and how serious it is." That's what someone actually pays for when they're nervous about wiring $50K.

      And yeah, the brand layer matters from the start, not after launch. Everything has to feel credible before someone even reaches out. If it looks like "indie hacker side project," nobody's sharing confidential deal info.

      Beryxa.com is a solid direction I haven't committed to a domain yet but something in that vein makes sense. Needs to feel established and serious even on day one.

      1. 1

        Exactly.

        If someone is wiring $50K, they are not buying a checklist.
        They are buying confidence.

        That is why the brand has to feel serious before the audit even starts.

        “DD checklist” sounds like a tool.
        “Risk translation” sounds like protection.

        That is the frame I’d build around.

        And since you have not committed to a domain yet, this is the right time to avoid locking into something too lightweight.

        Beryxa.com fits because it does not sound like a side project or checklist tool.
        It has room to become the trust layer around SaaS acquisitions.

        That matters a lot if buyers are going to share deal data, financials, and acquisition context.

Trending on Indie Hackers
How I built an AI workflow with preview, approval, and monitoring User Avatar 62 comments Show IH: I'm building a lead gen + CRM tool for web designers targeting local businesses without websites — starting with Spain User Avatar 55 comments I built a URL indexing SaaS in 40 days — here's the honest story User Avatar 35 comments I built a desktop app to move files between cloud providers without subscriptions or CLI User Avatar 27 comments Show IH: I built an AI agent that helps founders find the right people User Avatar 24 comments After 4 landing page rewrites, I finally figured out why my analytics SaaS wasn't converting User Avatar 21 comments