different species of crabsoft-shell crab
9
26 Comments

Starting a Small SAFE Round After Analyzing $10M+ in Contract Value

Starting a Small SAFE Round After Analyzing $10M+ in Contract Value

Not because “AI is hot.”

Mainly because I’m starting to see a consistent pattern:
people upload contracts when the financial risk is real.

Over the last months:
• 90+ contracts analyzed
• $10M+ in total contract value reviewed
• agreements ranging from ~$40K to $6.7M+

Started as a simple experiment.
Now seeing repeat usage, real workflows, and consistent behavior patterns before contracts get signed.

Still very early.
Still learning fast.

Recently started reaching out to a few angels/operators around the space and would genuinely love to hear what worked for other founders during their first SAFE round.

LinkedIn:
https://www.linkedin.com/in/meirambek-mukhametkalievich-2b72272a4/

Project:
https://vidicontract.tech

on May 6, 2026
  1. 1

    Raising a SAFE round can definitely be a grind, especially as a solo founder. I actually know a few solo founders with early SAFE experience who'd probably be happy to answer your questions for free.

    1. 1

      Appreciate that - would genuinely love to hear their perspective. Happy to connect and continue the conversation on LinkedIn as well 🙌

      1. 1

        There's a supportive community called "replyz" where you can reach exactly the kind of people you're looking for. Just search who you want to connect with and you'll get real, detailed responses from them. Only thing is, you should also share your own insights with others too. It's what keeps the place running. Feel free to ask questions if you have any!

  2. 1

    I write checks at the pre-seed/seed stage and the pattern you found is the kind of thing I want to see before the deck even loads. "People upload contracts when financial risk is real" is a usage signal, not a feature claim, and that's what investors actually trust at this stage. A few things that make first SAFE rounds easier: pick your cap based on the next round's defensibility (not current narrative), close one or two operator angels first so each new conversation has social proof, and keep the round small enough that you don't dilute past 15 to 20 percent before real traction. Happy to take a look if useful: https://www.henson.vc/submit-your-pitchdeck

    1. 1

      Appreciate the insight - especially the point about usage signals vs. feature claims. Makes a lot of sense. Happy to continue the conversation on LinkedIn as well:
      https://www.linkedin.com/in/meirambek-mukhametkaliuly-2b72272a4/

  3. 1

    The data angle here is exactly right for a fundraising narrative. What you've built isn't just a product — it's a proprietary dataset of real contract behavior at the point of financial risk. That's the kind of moat that actually shows up in due diligence conversations.

    One thing worth doing before you close the round: make sure the behavioral patterns you're describing ('people upload when financial risk is real') are structured as queryable metrics, not just qualitative observations. Investors in B2B SaaS often push for cohort retention and usage frequency breakdowns at the contract level — having that answerable in SQL vs. 'I'll pull it manually from our dashboard' makes a meaningful difference in how the story lands.

    90+ contracts across a $40K–$6.7M range also gives you a decent sample to segment by deal size and see if the behavior patterns differ at different risk thresholds. That kind of segmentation is where the real fundraising story usually lives.

    For anyone building data layers on top of contract or transaction-heavy workflows — I put together a free SQL interview Q&A guide that covers many of the query patterns relevant to this kind of behavioral analysis: https://growthwithshehroz.gumroad.com/l/vgiex

  4. 1

    this looks useful!!

    1. 1

      Thanks!! Appreciate it 🙌

  5. 1

    90+ contracts, $10M+ in value — that's solid traction to build a round around. The pattern you noticed ('people upload contracts when financial risk is real') is the kind of insight you only get from actually watching users, not guessing.*

    Quick question — what's the smallest SAFE check you're finding most helpful?
    5k?10k? And are you targeting angels who already know the space, or generalist operators?

    I'm building Bexra — Helping entrepreneurs find, build & grow. Still pre-launch, but raising is somewhere in my future. Curious how you approached it.

    1. 1

      Still figuring that out honestly - keeping the round relatively small and focused for now.

      Leaning more toward people who understand B2B workflows and real operational pain points rather than broad hype-driven investing.

  6. 1

    $10M+ in contract value analyzed — that's serious signal. You're clearly data‑driven, which makes your SAFE round more credible than most "AI is hot" pitches.
    One question: before you raise, have you validated VIDI Contract's own market demand and positioning the same way you validate contracts for your users?

    That's exactly why I built TrendyRevenue – AI validation in 10 seconds: market demand, competitor gaps, revenue potential, trends. If you're adding new features (e.g., automated redlining, obligation extraction) or targeting a new niche (e.g., procurement vs legal), run it through the free tier first (one analysis, no card). It'll tell you which direction has real search intent vs just founder intuition.

    The Pro plan ($39/mo) adds source‑cited competitor gaps (exact review snippets from G2/Capterra), revenue modeling, and SERP intent — the evidence you'd want before betting your SAFE round on a pivot.

    You already know: data > gut. Apply that same rigor to your own roadmap. Investors will notice.

    Good luck with the round — and respect for sharing real numbers. Following.

    1. 1

      Appreciate it.

      Right now I’m trying to validate more through direct usage and conversations than external market-scoring tools.

      The behavior patterns around when and why people upload contracts have been a much stronger signal so far.

  7. 1

    Strong early traction — especially because contract review only happens when the financial risk is meaningful. $10M+ analyzed and repeat workflows emerging is a solid validation signal. Excited to follow VidiContract
    as it grows

    1. 1

      Appreciate it - that’s exactly the pattern starting to become more visible now.

  8. 1

    The strongest signal here is not volume.
    It’s that people are only pulling this into workflow when the downside is real.

    That usually means the product is already being evaluated less like “AI contract analysis” and more like pre-signing risk infrastructure.

    That distinction matters.

    Once legal / finance starts touching real-dollar decisions, the product stops being judged like a useful AI layer and starts being judged like trust software.

    That is usually the point where the current name starts capping perceived weight.

    vidicontract.tech explains what it does.
    But it also keeps it framed as a narrower tool layer.

    If this keeps moving upstream into real pre-signing risk review, the product likely wants a name that can carry more trust than description.

    Davoq.com would hold that much better once the product grows past the current framing.

    1. 1

      Because it’s still early.

      The contract value is useful signal, but I care more about validating consistent real-world behavior and workflows first than optimizing for a larger round too soon.

      1. 1

        That makes sense.

        At this stage, workflow validation matters more than round size.

        But that actually strengthens the naming point later.

        If the consistent behavior is:
        people upload contracts when real money is at risk

        then the product is not just “AI contract analysis.”

        It is becoming the trust layer before signing.

        That’s a much heavier category.

        So I’d validate the workflow first, but keep an eye on when the current name starts making the product feel narrower than the risk it is actually handling.

        1. 1

          Yeah, that’s pretty close to how I’m thinking about it right now.
          Still focused on validating the behavior/workflow side first before over-optimizing branding.

          1. 1

            That’s fair.

            But I’d separate “branding” from “trust framing.”

            You don’t need to over-optimize the brand right now.

            But if the workflow you’re validating is tied to real contract risk, the name is already part of how serious the product feels before someone uploads anything sensitive.

            That matters even during validation.

            Because with contracts, users aren’t just testing features.
            They’re deciding whether this feels credible enough to trust with something financially exposed.

            So I’d validate behavior first, yes.

            But I wouldn’t treat the name as a later cosmetic layer.

            In this category, the name is part of the trust test.

            1. 1

              I get the point, I’m just not convinced the name is the main thing driving trust that early.

              From what I’ve seen so far, people care much more about whether the product helps in a real situation than whether the branding feels perfect.

              1. 1

                I agree it’s not the main thing.

                Product proof matters most.

                But the name affects whether people give the product a serious enough chance before that proof happens.

                That’s the distinction.

                In low-risk tools, users can ignore the name and just try it.

                With contracts, the first question is different:
                does this feel credible enough for me to upload something sensitive?

                So yes, the product has to win in the real situation.

                But the name decides how much trust you get before the user reaches that situation.

                That’s why I’d treat it as part of validation, not something after validation.

  9. 1

    That's a pretty rare position to be in - $10M+ in contracts usually means you've got real leverage with VCs, so what's driving the decision to keep the SAFE small rather than negotiate a bigger round?

    1. 1

      Appreciate that - just to clarify, the $10M+ is total contract value reviewed through the platform, not revenue.

      Still very early and intentionally keeping the SAFE small while validating repeat behavior, workflows, and where the strongest pull actually comes from.

      Trying to stay focused and build carefully before expanding further.

  10. 1

    makes sense - seeing real usage before raising changes everything
    looks like you’re raising based on signal, not hype, that’s a strong position early

    1. 1

      Appreciate it - that’s exactly the goal right now.

  11. 1

    If anyone here has experience with early SAFE rounds, angel outreach, or building investor relationships as a solo founder - would genuinely love to connect and learn.

    Always open to conversations with people building in AI, B2B SaaS, or workflow infrastructure.

Trending on Indie Hackers
I built an AI that turns an idea into a live business in under 10 minutes. Here’s what 1,000 launches taught me User Avatar 89 comments Building a startup costs $0. Your tooling budget costs $500K. Here's why. User Avatar 44 comments Building Noodle, a keyboard-first REST client for the terminal User Avatar 34 comments Stop losing deals in the gap between "sounds good" and getting paid User Avatar 33 comments "Looks Good to Me" Is Quietly Killing Your Feedback Loop User Avatar 33 comments 787 tools for developers. 5 for nurses. Two weeks of tracking 14,000 indie launches. User Avatar 29 comments