One Product Per Problem
The default advice in SaaS is to build a platform. Combine everything into one tool, cross-sell aggressively, make it hard to leave. That works if you're Salesforce and you have 70,000 employees. It doesn't work if you're two people who ship fast.
We took a different path. Veldspark Labs builds standalone products — each one solves a single problem, runs on its own, and makes money independently. The model is closer to 37signals (the team behind Basecamp and HEY) than it is to any VC-backed platform play.
Why Multi-Product Beats Single-Platform for Small Teams
Platforms are complexity machines. Every new feature interacts with every existing feature. A team of two managing a platform with 50 features is a team drowning in edge cases, integration bugs, and support tickets.
Separate products are simpler. LeadScoutr doesn't need to know about ZenSendr's email templates. ZenSendr doesn't care about LeadScoutr's lead scoring model. They share infrastructure — authentication, billing, design system — but they don't share complexity.
This isn't a philosophical preference. It's a survival strategy. Complexity kills small teams faster than competition does.
The Portfolio Economics
Running multiple products sounds expensive until you look at the shared costs.
Here's what we share across all products:
- Infrastructure: Same deployment pipeline, same hosting setup, same monitoring
- Design system: One component library, one brand, one set of UI patterns
- Authentication and billing: Build once, use everywhere
- AI layer: Shared model integrations, prompt libraries, and data pipelines
- Customer insights: Every support ticket and feature request for one product teaches us about the other
The marginal cost of launching product #3 is a fraction of what product #1 cost. The code isn't shared, but the knowledge is.
Revenue diversification is the other advantage. If one product hits a rough quarter — a competitor launches, a market shifts — the others keep the lights on. A single-product company doesn't have that cushion.
Consulting Finds the Problems
Every Veldspark product starts the same way: I see the same problem across three or more consulting clients at GVDworks.
Not once. Not twice. Three times minimum before we consider building anything.
The consulting pipeline is our unfair advantage. We don't need to guess what people will pay for. We've already watched them pay for custom solutions to these exact problems. We've seen what they've tried before, why it failed, and what they actually need.
Here's the process:
- Identify the pattern. Same pain point, different companies, different industries.
- Validate willingness to pay. Would at least three clients switch from their current solution (or lack of one)?
- Scope the MVP. What's the smallest thing that solves 80% of the problem?
- Build and ship. Two-to-four week sprints. No feature bloat.
- Iterate based on real usage. The first version is always wrong in interesting ways.
- Stabilize, then move on. Once the product sustains itself, start validating the next one.
The Portfolio So Far
LeadScoutr was product #1. The pattern: every consulting client had sales teams wasting hours on manual prospect research, using stale databases, and qualifying leads by gut feel. LIZZY — our conversational AI — replaced that entire workflow with real-time web search and AI-powered qualification.
ZenSendr is product #2. The pattern: SMBs paying $200-400/month for email marketing platforms they use at 10% capacity. Most of them need simple automations, good deliverability, and a list manager — not 500 features with an enterprise price tag.
DataConnectr is in the pipeline. The pattern: data stuck in disconnected tools with no way to sync without hiring a developer or paying for Zapier Pro. We're watching this one closely across five current consulting engagements.
Why We Don't Merge Them
The temptation is always there. "LeadScoutr finds leads, ZenSendr sends emails — why not combine them?" Because the moment you do, you've built a platform. And platforms have platform problems.
Merge two products and now your lead scoring UI needs to account for email campaign metrics. Your email template builder needs to pull from CRM fields. Your pricing model gets complicated — do email customers subsidize CRM customers? Every product decision becomes a negotiation between two different user bases.
37signals understood this with Basecamp and HEY. Both products involve team communication. They could have combined them. Instead, they kept them separate, and both are stronger for it.
Focused products ship faster, break less, and are easier to explain. "LeadScoutr finds your ideal B2B leads" fits on a business card. "LeadScoutr is an AI-powered lead generation CRM with integrated email marketing and data synchronization" requires a brochure.
This Isn't a Roll-Up
Private equity firms build SaaS portfolios by acquiring existing products, cutting costs, and raising prices. That's a financial strategy, not a product strategy.
We build from scratch. Every product uses the same design language, the same AI stack, and the same pricing philosophy (affordable for SMBs, transparent, no per-seat scaling traps). The products feel like they belong together because they were built by the same team with the same opinions.
The difference matters to customers. A PE roll-up gives you five products with five different UIs, five different support teams, and five different billing systems. Our portfolio gives you tools that feel like siblings — different purposes, same DNA.
What Makes This Sustainable
Two things keep this model working long-term.
First, revenue from day one. Every product charges money from launch. No "free until we figure out monetization" phase. This isn't principle — it's pragmatism. Charging money immediately tells you whether you've built something valuable. Free users will say anything is useful. Paying customers will tell you the truth.
Second, staying small on purpose. We're not hiring a 30-person team. We're not raising a Series A. Two people with focus beat ten people with meetings. The 37signals team shipped Basecamp, HEY, and ONCE with a small team because they refused to scale headcount proportionally with revenue.
That's the model. Find real problems, build focused tools, charge fair prices, and don't confuse growth with complexity.