We Skipped the Fundraising Playbook
There's a well-worn script for starting a SaaS company. Write a pitch deck. Apply to accelerators. Raise a pre-seed round. Hire fast. Burn through runway. Hope you find product-market fit before the money runs out.
We skipped all of it.
Veldspark Labs is two people: me (CEO/BD) and Kevin (CTO). No investors, no advisory board, no growth team, no office. We fund development with consulting revenue, ship when the product is ready, and answer to nobody but our users.
This isn't a brag. It's a deliberate decision with real trade-offs. Here's what we've learned.
The CEO/CTO Split That Actually Works
Most co-founder conflicts come from overlapping responsibilities. Two business people arguing over strategy. Two engineers debating architecture. Two generalists doing a little bit of everything and getting in each other's way.
Our split has zero overlap:
- I handle everything non-technical: product strategy, market research, business development, customer conversations, content, brand, pricing, partnerships.
- Kevin handles everything technical: architecture, engineering, infrastructure, security, performance, deployments.
We don't vote on decisions. Whoever owns the domain makes the call. I don't have opinions about database schemas. Kevin doesn't weigh in on pricing tiers. We trust each other's judgment because we each have expertise the other doesn't.
This eliminates 90% of the meetings, debates, and politics that slow teams down.
Why We Didn't Raise Money
The standard argument for raising capital is speed. Money lets you hire, and hiring lets you build faster. That's true in theory. In practice, it also means:
- You spend months fundraising instead of building. The average seed round takes 3-6 months of pitching. That's 3-6 months of not shipping product.
- You hire before you know what to build. Early-stage startups routinely hire engineers before they've validated the product. Then they pivot and half the team is working on the wrong thing.
- You answer to people who don't use your product. Board members and investors have opinions. Those opinions take time to manage. That time comes out of your building budget.
- You optimize for growth metrics instead of product quality. When you're burning $50K/month, you need hockey-stick growth charts. When you're bootstrapped, you need happy users.
We had a different advantage: consulting revenue. My consulting work through GVDworks generates enough to fund product development without external capital. It's slower than a funded startup. It's also more sustainable.
The Tools That Make Two People Feel Like Ten
A two-person team can't afford inefficiency. Every tool has to earn its place. Here's our stack and why each piece matters:
Development
- Next.js — Full-stack React framework. One codebase, one deployment, no separate API layer to maintain.
- TypeScript — Catches bugs before they ship. Worth the upfront investment on a team where there's no QA department.
- Prisma — Database ORM that makes schema changes safe. Migrations without prayer.
- Tailwind CSS — Utility-first styling that eliminates the "where does this CSS class live" problem. Kevin can ship UI without waiting on a designer.
Infrastructure
- Vercel — Deploys from git push. No DevOps needed. Preview deployments for every PR.
- Railway — Database hosting with zero configuration. Postgres in production, SQLite in development.
- GitHub — Code, issues, CI/CD. One platform for everything code-related.
AI & Development Velocity
- Claude — Our primary AI development tool. Code generation, debugging, content creation, architecture decisions. This isn't a nice-to-have — it's a force multiplier that lets two people ship at the pace of a much larger team.
- Anthropic API — Powers LIZZY (LeadScoutr's AI agent) and our product AI features.
Communication
- Slack — When we need to talk. Which is less than you'd think.
- Linear — Issue tracking. Clean, fast, no bloat. Every task has a clear owner because there are only two options.
Constraints Breed Focus
When you have unlimited resources, every feature seems worth building. When there are two of you, every feature competes with sleep.
This constraint has made our products better. We can't build everything, so we build the right things. Every feature goes through a simple filter:
- Does this solve a problem we've seen in consulting? If not, it's probably speculative.
- Will users notice in the first week? If not, it can wait.
- Can we build and ship it in under two weeks? If not, we need to scope it down.
Features that survive all three filters tend to be the ones users actually care about. The ones that don't survive tend to be the ones we would have built, shipped, and watched nobody use.
The Anti-Meeting Culture
Kevin and I don't have standing meetings. No daily standups. No weekly syncs. No sprint planning. No retros.
We communicate asynchronously by default. If something needs discussion, we hop on a call — usually 10-15 minutes, rarely longer. When the call is done, we go back to building.
This works because:
- We trust each other. If Kevin says something will take a week, it takes a week. No progress check-ins needed.
- We write things down. Decisions go in Linear tickets or Slack threads, not in someone's memory of a meeting.
- We're both builders. Neither of us enjoys meetings. We'd both rather be shipping.
The average knowledge worker spends 15 hours a week in meetings. We spend maybe 2. Those 13 extra hours per person, per week — that's our competitive advantage.
The Hard Parts
Bootstrapping with two people isn't all upside. Here's what's genuinely hard:
No Safety Net
If Kevin gets sick for two weeks, engineering stops. If I'm unavailable, business development stops. There's no bench. We mitigate this by keeping documentation current and avoiding single-person dependencies on critical paths, but the risk is real.
Saying No Constantly
We get feature requests, partnership inquiries, and "could you also build..." questions regularly. The answer is almost always no. Not because the ideas are bad, but because we can't afford the context switching. Focus is our most valuable asset, and every yes is a no to something else.
Slow When It Matters
Funded startups can throw bodies at problems. Need to ship a feature fast? Hire two more engineers. Need to handle a support spike? Bring on a contractor. We don't have that lever. When something takes longer than expected, we adjust timelines. There's no cavalry.
Marketing Reach
Two people can't generate the marketing volume that a funded startup can. No conference booths, no sponsorship deals, no content teams publishing three posts a week. We rely on the product being good enough that users tell other users. That works — but it's slow.
Would We Do It Differently?
No.
The bootstrapped two-person model isn't right for every product. If you're building something that requires massive upfront investment — hardware, regulatory compliance, deep R&D — you probably need funding.
But for B2B SaaS products that solve known problems for an identifiable audience? Two focused people with domain expertise can compete with funded teams five times their size. Not on marketing spend. Not on feature count. On the thing that actually matters: building something people want to use.
We're still two people. We're still shipping. The model works.