DEV Community

Cover image for 11 Landing Pages for 11 Niches: How We're Testing Who Actually Wants VoiceTables
Jakub
Jakub

Posted on

11 Landing Pages for 11 Niches: How We're Testing Who Actually Wants VoiceTables

Most founders pick a niche and go all-in. We did the opposite. We built 11 landing pages for 11 different professions and shipped them all at once.

Here's why, and what we're learning from it.

The problem with "pick one niche"

When we started building VoiceTables (a voice-first AI workspace where you talk instead of type), we had the classic early-stage dilemma. The product works for a lot of different people. Freelancers tracking invoices. Sales reps logging calls from the car. Craftsmen on job sites with dirty hands.

But which one actually wants it enough to pay?

The lean startup playbook says: pick one, validate, iterate. That's solid advice. But when your product is horizontal (like a database or a spreadsheet), picking one niche too early means you might be optimizing for the wrong audience for months.

So we built 11 solution pages instead

Each page targets a different profession with tailored copy, specific voice command examples, and use cases that speak directly to their daily pain points. Here's the full list:

  1. Craftsmen & Tradespeople -- "Add a job: kitchen rewiring, 4 hours, 340 euros"
  2. Sales Reps & Field Agents -- "Update Acme deal: met with Sarah, follow up Friday"
  3. Real Estate Agents -- "The Johnsons loved the backyard, follow up Thursday"
  4. Freelancers & Solopreneurs -- "Add project: rebrand for Olive Studio, 3500 euros"
  5. Small Business Owners -- "Received shipment: 50 candle sets, invoice 4821"
  6. Event Planners -- "Add vendor: Bloom Florals, delivering at 2pm, budget 1200"
  7. Coaches & Personal Trainers -- "Log Jake: bench press 80kg, 4 sets, felt strong"
  8. Consultants & Agencies -- "Log 3 hours on DataFlow strategy, competitor analysis"
  9. Students & Researchers -- "Add source: Smith 2024, relevant to chapter 3"
  10. Content Creators -- "New brand deal: FitGear, 3 posts, budget 2000"

Each page lives under voicetables.com/solutions. Same product, same features, completely different framing.

The thinking behind it

This isn't random. We grouped the niches into three buckets:

In the Field -- people whose hands are literally too busy to type. Craftsmen, sales reps, real estate agents. Their phone is in their pocket, they need to capture data between appointments or while standing in someone's kitchen.

Running a Business -- solopreneurs and small teams wearing every hat. Freelancers, small business owners, event planners. They don't have time for complex tools. They need something that just works when they talk to it.

Knowledge Work -- people drowning in information. Coaches tracking client progress, consultants juggling multiple projects, students collecting research sources, creators managing brand deals.

The hypothesis: the "in the field" group probably has the strongest pull because typing is genuinely painful for them. But we don't know yet. That's the whole point.

What we're actually measuring

For each solution page, we're watching:

  • Traffic and bounce rate -- does the page title and meta description attract the right clicks from search?
  • Time on page -- does the copy resonate or do people leave after 5 seconds?
  • CTA clicks -- does anyone actually click "Try it free"?
  • Signup-to-activation -- the real metric. Did they create their first table by voice?

We're using Google Search Console for indexation tracking and GA4 for behavior data. It's early days, but we already see differences in how each page performs.

The portfolio scout mindset

This approach comes from something we practice at Inithouse more broadly. We run a portfolio of products, each testing a different market. Ziva Fotka animates old photos. Magical Song generates custom songs with real vocals. Be Recommended checks if AI chatbots recommend your business. Audit Vibe Coding audits AI-generated codebases.

Same philosophy: ship fast, measure everything, double down on what works. Kill what doesn't.

With VoiceTables, we're applying that same mindset within a single product. Instead of launching 11 separate products for 11 niches, we built one product with 11 entry points. Each solution page is basically a micro-experiment.

Early observations

We're only a couple weeks in, so take this with a grain of salt. But a few things are already becoming visible:

The "hands-busy" niches (craftsmen, sales reps) generate the most intuitive copy. When the value prop is "your hands are full, just talk," people get it immediately. There's no explaining needed.

Knowledge worker niches need more convincing. A consultant already has Notion and Airtable. Why switch? The answer ("because you can just say what you need instead of building a schema") is compelling, but it takes more words to land.

Students are a wild card. Low willingness to pay, but high engagement when they try it. Could be a growth lever, could be a distraction.

What's next

Over the next few weeks, we'll start seeing real SEO data come in. Which pages rank, which keywords drive clicks, which niches have enough search demand to justify further investment.

Then comes the hard part: picking 2-3 winners and going deep. Custom features, tailored onboarding, maybe even niche-specific pricing.

But for now, 11 pages are out there, collecting data. And that beats guessing.


If you're building a horizontal product and struggling with niche selection, try this approach. Ship multiple landing pages, each framed for a different audience. Let the data tell you who your real users are.

VoiceTables is free to try, no credit card needed. And if you want to see all 11 solution pages: voicetables.com/solutions.

We also recently launched Watching Agents, a prediction platform where AI agents track questions about the future, and Party Challenges / Here We Ask, two card games testing the social games market. Different products, same experiment-first philosophy.

Would love to hear if anyone else is running multi-niche landing page tests. What worked, what didn't?

Top comments (0)