2
6 Comments

Built a production SaaS over 2 years with no funding. Now I’m stuck on distribution.

Two years ago I couldn’t write software.

I was running my own business and kept running into the same problem for over 6 years:

The numbers in my marketing platforms didn’t match the reality in my bank account.

Instead of accepting it, I spent the next two years teaching myself Python, APIs, PostgreSQL, FastAPI, Supabase, OAuth, infrastructure, and analytics.

Today that project is a production platform called Allocera Intelligence.

It’s not another AI tool.

It’s a deterministic decision engine that reconciles hidden acquisition costs and issues campaign directives like SCALE, HOLD, CUT, PAUSE, QUARANTINE, RENEGOTIATE, INVESTIGATE, or FLAG based on actual business economics rather than platform-reported metrics.

Current status:

Built solo
14,000+ lines of code
Production environment live
Pilot client active
Real CRM and ad data flowing
Directives firing automatically
No outside funding
The challenge isn’t building anymore.

The challenge is distribution.

For founders who have already crossed that gap:

What was the thing that finally got people to pay attention to a product that was already working?

on June 23, 2026
  1. 1

    Respect for shipping real software first — that part is already rare.

    At this stage I’ve seen the bottleneck shift from “build more” to “find people who already feel the pain today.” Usually one narrow channel beats broad launch traffic.

    What’s your ICP, and where do they already complain about this problem in public?

    1. 1

      Appreciate the comment. Went to check out your work to see if there was a real conversation to be had here and the LinkedIn and email on your profile are both dead links. Hard to take distribution advice seriously from someone who can't be found.
      For anyone else in the thread who actually wants to dig into this, I'm happy to talk specifics. Two and a half years building this, fully bootstrapped, third version of the model, the first two were on Google Sheets just to prove the concept was viable. The final build is a deterministic cost reconciliation engine, not AI, over 14,000 lines of code across 55 Python files. It runs nightly at 2 AM, pulls verified data from HubSpot, Meta, Google and LinkedIn via OAuth, reconciles the full cost stack including broker fees, refunds, chargebacks and compliance costs that platforms never report, and issues one of eight capital directives per campaign. Scale, Hold, Cut, Pause, Quarantine, Renegotiate, Investigate or Flag. Same data always produces the same directive. No model, no inference, no hallucination. Just math on what actually left your business.
      Real pilot client active. Real CRM and ad data flowing. Directives firing automatically. 98 out of 100 engine health score. Not here for noise.

      1. 1

        fair on the profile links — fixing. distribution advice only lands if people can actually reach you.

  2. 1

    The part I'm not sure about is the jump from "I have a pilot client and a working product" to "this is a distribution problem."

    Maybe it is.

    But I've seen a lot of products where the bottleneck turned out to be something else entirely, and it looked like distribution from the outside.

    What makes you confident that's the constraint right now?

    1. 1

      Fair question. The engine works, pilot client live, real data flowing, directives firing automatically. That part is solved.

      The constraint is network. This industry runs on warm introductions. Cold outreach doesn't land when you're asking for access to ad accounts and CRM data. The trust has to exist before the conversation starts.

      Two years building solo means the product is real but the network isn't there yet. That's the gap I'm closing now.

      1. 1

        That's actually the part I'd be most hesitant to assume yet.

        Not because network effects aren't real in industries like this.

        But because a product can reach the point where distribution becomes the most visible constraint long before it's clear whether it's the most important constraint.

        I've got a few thoughts on that, but it's probably more than I'd try to unpack properly in a thread.

        What's the best email to reach you on?