u/martin_at_fullscale

This time around, same instincts, a couple of exits behind me, and traction that people keep telling me looks Series A ready, and I’m still grinding through a seed raise like I have something to prove for the first time.

The VCs I’m talking to like the company. Some of them really like it. Meetings go well, the questions get sharper instead of skeptical, everything feels like it’s building toward something. And then it just doesn’t turn into a check. No clean no, no clear yes, just momentum that stalls right before the finish line.

Some of the pushback is fair, a few of the holes people poked actually needed poking, and I’ve made changes because of it. But there’s a gap between “you found a real risk” and “that’s why we’re passing,” and I keep landing in that gap without anyone explaining what’s on the other side of it.

I keep running the math. Better traction than my last raise. Real revenue instead of a slide and a promise. A track record this time instead of a pitch. And somehow this round is harder than the one where I had none of that.

Genuinely asking anyone who’s raised more than once: did the bar actually move this much in a few years, or is there something I’m too close to see?

I spent two decades in brand marketing at companies like Bacardi and Toyota. I cannot write a for loop from memory. Last year I decided to build my startup’s platform myself instead of hiring a dev shop, and today it’s live in production with paying customers.

The stack, all built through Claude Code and Replit: React/Tailwind frontend, Node/Express backend, PostgreSQL, AWS S3, FFmpeg, Sharp, OpenCV, TensorFlow.js, plus the Claude API in the product itself.

What actually worked for me:
Treat Claude like a senior engineer you’re managing, not a vending machine. My best sessions started with me explaining the business problem in plain English, asking Claude to propose 2-3 architectures, and making it argue against its own first suggestion before we wrote anything.

One feature per session. When I tried to do too much in one conversation, quality fell apart. Small scoped sessions, commit, new session.

Make it explain the code back to you. I don’t merge anything I can’t describe in a sentence. This sounds slow. It saved me weeks, because when things broke at 11pm I actually understood my own system.

Where it hurt: video processing pipelines. FFmpeg flags are a nightmare and Claude would occasionally give me confident answers that were wrong for my specific codec situation. I burned about two weeks on a memory leak in the processing queue that a real engineer probably spots in an hour. That was my tuition.

The uncomfortable truth: I still brought on a part-time CTO to review architecture decisions. AI got me to a real product, but I don’t pretend I have no blind spots.

Happy to answer anything about the workflow, costs, or the moments I almost quit and hired an agency.

Second-time venture-backed founder (multi-time bootstrapped). I’ve run a six-month seed process and kept notes on every piece of hard feedback. Sharing the ones that stung most, because I wish someone had shown me this list before I started.

“***The deck feels early. Where’s the IRR rigor?”***
From an investment liaison I respect. My deck had a big return multiple claim with no math underneath it. I rebuilt the financial model from scratch, five-year ramp, assumption-level detail, sensitivity cases. The multiple claim is now the least interesting slide because the model does the talking.

“***You’re describing a marketplace. Marketplaces at your stage are a graveyard.”***
This one made me realize I was positioning against my own interest. We are a technology platform. The marketplace is one revenue mechanic, not the identity. I rewrote every sentence of the narrative. Categorization is destiny in a first meeting.

“***Your Year 1 revenue is zero. Why should I fund a free product?”***
Fair. I learned to lead with the contracts and pilots that were already signed rather than the freemium curve. Traction reframes everything.

“***Who on this team has done this before?”***
The honest answer was that my technical co-founder was part-time. I stopped dancing around it and now say plainly: he goes full-time the day the round closes, and here’s what he’s shipped part-time. Directness landed better than spin ever did.

Biggest meta-lesson: the feedback that offends you most is usually the most accurate. The stuff that’s wrong is easy to shrug off. The stuff that keeps you up at night is your roadmap.

VCs in here: what’s the feedback you give founders that they most consistently ignore?

I’m a former CMO type. My background is brand marketing, not engineering. Over the past year I built my company’s computer vision platform end to end using AI coding tools, and it’s now in production with real customers and real revenue.

The “anyone can build now” narrative skips the painful parts. I lived all of them, and I’d rather post the ugly version than the highlight reel.

\*\*Things that broke, in order of how much they hurt:\*\*

1. A memory leak in our video processing queue. Two weeks lost. The AI kept suggesting fixes for symptoms instead of the cause. I finally found it by learning to read heap snapshots myself, which I never planned on doing in this lifetime.

2. Database migrations. I once let an AI-generated migration run against production. It worked, but only because we got lucky on ordering. I now stage everything and read every line. Learn from my near-miss.

3. Auth. Do not let AI freestyle your authentication. I ripped ours out and rebuilt on a standard library after realizing the custom version had gaps I only understood after reading about session fixation at 2am.

4. My own overconfidence. After three months of wins I started skipping the “explain this code to me” step. That is exactly when bugs started shipping.

What I’d tell any non-technical founder trying this: you can absolutely get to a real product. You cannot get to a real product without becoming at least semi-technical along the way. The tools don’t remove the learning, they compress it.

Ask me anything, including costs, timeline, and the stuff I’d never do again.

I spent two decades in brand marketing at companies like Bacardi and Toyota. I cannot write a for loop from memory. Last year I decided to build my startup’s platform myself instead of hiring a dev shop, and today it’s live in production with paying customers.

The stack, all built through Claude Code and Replit: React/Tailwind frontend, Node/Express backend, PostgreSQL, AWS S3, FFmpeg, Sharp, OpenCV, TensorFlow.js, plus the Claude API in the product itself.

**What actually worked for me:**
Treat Claude like a senior engineer you’re managing, not a vending machine. My best sessions started with me explaining the business problem in plain English, asking Claude to propose 2-3 architectures, and making it argue against its own first suggestion before we wrote anything.

One feature per session. When I tried to do too much in one conversation, quality fell apart. Small scoped sessions, commit, new session.

Make it explain the code back to you. I don’t merge anything I can’t describe in a sentence. This sounds slow. It saved me weeks, because when things broke at 11pm I actually understood my own system.

**Where it hurt:** video processing pipelines. FFmpeg flags are a nightmare and Claude would occasionally give me confident answers that were wrong for my specific codec situation. I burned about two weeks on a memory leak in the processing queue that a real engineer probably spots in an hour. That was my tuition.

**The uncomfortable truth**: I still brought on a part-time CTO to review architecture decisions. AI got me to a real product, but I don’t pretend I have no blind spots.

Happy to answer anything about the workflow, costs, or the moments I almost quit and hired an agency.

I spent two decades in brand marketing at companies like Bacardi and Toyota. I cannot write a for loop from memory. Last year I decided to build my startup’s platform myself instead of hiring a dev shop, and today it’s live in production with paying customers.

The stack, all built through Claude Code and Replit: React/Tailwind frontend, Node/Express backend, PostgreSQL, AWS S3, FFmpeg, Sharp, OpenCV, TensorFlow.js, plus the Claude API in the product itself.

**What actually worked for me:**
Treat Claude like a senior engineer you’re managing, not a vending machine. My best sessions started with me explaining the business problem in plain English, asking Claude to propose 2-3 architectures, and making it argue against its own first suggestion before we wrote anything.

One feature per session. When I tried to do too much in one conversation, quality fell apart. Small scoped sessions, commit, new session.

Make it explain the code back to you. I don’t merge anything I can’t describe in a sentence. This sounds slow. It saved me weeks, because when things broke at 11pm I actually understood my own system.

**Where it hurt:** video processing pipelines. FFmpeg flags are a nightmare and Claude would occasionally give me confident answers that were wrong for my specific codec situation. I burned about two weeks on a memory leak in the processing queue that a real engineer probably spots in an hour. That was my tuition.

**The uncomfortable truth**: I still brought on a part-time CTO to review architecture decisions. AI got me to a real product, but I don’t pretend I have no blind spots.

Happy to answer anything about the workflow, costs, or the moments I almost quit and hired an agency.

Quick background: I run an AI computer vision startup in the sports and creator space. In June I was in Dubai for a government-backed creator economy program, taking family office meetings.

One of those meetings turned into a real offer. 50% of the company. Serious money, serious operator, real distribution in a region we want to be in.

I said no. Here’s the reasoning I used, and the doubt I still carry.

Why I passed:

- 50% at this stage means I’m effectively a co-founder in my own company from that point on. Every major decision becomes a negotiation.

- We had just signed our first Power 4 athletics pilot and landed our first six-figure brand contract. Selling half right when the traction curve bends felt like selling the dip.

- The buyer’s plan and my roadmap agreed on year one and diverged hard on years three through five.

Why I still lose sleep:
- That capital would have removed all runway anxiety for years.

- Regional distribution like that is not something you can just buy later.

There is a version of this where I look back and realize I turned down the best offer I’ll ever get because of ego dressed up as conviction.

Angels here: when you’ve watched founders decline offers like this, how often did it age well? And what separated the ones who were right from the ones who were just stubborn?