Hello Query reborn: AI pivot, solo founder resilience, and product direction

Executive overview

After a co-founder split, Colleen Schnettler rebuilt her shipping muscle with a throwaway project, then returned to her original problem with a leaner, AI-assisted angle. The result is a relaunched Hello Query — now an AI-assisted SQL report builder for internal BI users — shipped solo and put in front of real users within weeks.

Rebuilding momentum through small, deliberate bets is how solo founders survive the pre-product-market-fit desert.

The co-founder breakup and rebound project

• Post-split stress triggered an impulse to abandon everything — the idea, the name, the direction.
• Colleen built getpodcastleads.com to reactivate her shipping muscle and experiment with AI APIs (Deepgram, OpenAI).
• She knew before building it that the economics wouldn't work: podcasters pay $20 for a $200 sponsor lead.
• The project wasn't a failure — it restored confidence and hands-on fluency with AI APIs.
• Treat it as a deliberate rebound: short-term, intentional, no regret.

Returning to Hello Query with a narrower scope

• After the rebound project, Colleen asked: is two years of immersion in internal reporting a sunk cost or an unfair advantage?
• She concluded it's still an unfair advantage — the problem is real and people pay to solve it.
• New product: AI-assisted SQL report builder, still branded Hello Query, but rebuilt solo.
• Users connect their database; natural-language questions are converted to SQL, run, and results are exportable to CSV or Google Sheets.
• Reports can be scheduled and sent to teams on a recurring basis.
• Early discovery: she expected developers to be the primary users, but everyone wants to put it in front of non-technical teammates instead.

Shipping fast and gathering real signals

• Instead of theorising whether users would connect production databases, she just launched and found out.
• A tweet with a GIF got real users; developers in her network were a useful entry point into companies.
• Developers are often the ones being asked to pull reports — they become internal champions.
• Fast feedback cycles are a dopamine loop that sustains motivation; shipping publicly accelerates the loop.
• Build-in-public's real benefit is the feedback loop, not the audience as a customer source.
• Beware: Twitter/indie-hacker audiences give developer feedback, which may not match your actual target buyer.

The curse of the audience

• Two competing directions: internal BI tool vs. AI layer on top of marketing analytics (Google Analytics, Mixpanel, etc.).
• The marketing analytics direction would generate immediate excitement from her network — but that's the problem.
• Curse of the audience: your existing followers engage out of affinity, not genuine intent to pay.
• Second curse: burning your audience on an MVP that isn't ready means they won't give you a second look.
• Colleen is leaning toward the internal BI path: one large company has already approached her, and enterprise BI buyers pay premium prices.
• Marketers have many tools already and likely don't need another analytics layer.
• Neither path is clearly right yet — the job is to gather more data on both, not to decide prematurely.

Emotional runway and the pre-PMF grind

• Bootstrapped companies fail when the founder runs out of motivation, not money.
• Emotional runway is the ultra-marathon framing: sustain output over years, not weeks.
• Colleen balances draining customer conversations with restorative coding sprints (~1 week shipping, then follow-up).
• Momentum compounds: shipping generates feedback, feedback generates motivation, motivation generates more shipping.
• Pre-product-market-fit is the hardest phase to systematise — decisions are made with the least information and the most ambiguity.
• The honest state at episode six: uncertain, not yet revenue-generating, but not ready to quit.