Navigating co-founder conflict and pivoting to a new SaaS product

Executive overview

A full-time founder hitting zero income confronts simmering resentment toward her part-time co-founder — and nearly ends the partnership. Forcing the conversation early, before meaningful revenue, proved far easier than doing it later.

After resolving the relationship, the team shut down their Rails developer-tooling product, refunded customers, and relaunched as Hello Query — a hosted internal reporting SaaS open to any team with a database.

Having the hard conversation early is the only way to align on goals before stakes make it impossible.

The co-founder conflict

• Colleen stopped consulting (losing ~$20k/month) the same week the conflict peaked
• With Aaron part-time and Colleen full-time, the asymmetry in risk felt deeply unfair at that moment
• She had been talking to everyone except Aaron about the problem for months
• The breakthrough came from a multi-day conversation covering life goals, commitment levels, and what each person actually wanted
• Aaron offered to walk away cleanly; Colleen chose to stay in the partnership
• Post-conversation, both reported the working relationship improved significantly — hidden undercurrents resolved

Why the original product failed

• Refine Rails was a Ruby gem for internal reporting — licensed software, not a SaaS
• Customers buying the license also wanted hands-on implementation help, making it a productized consulting business in disguise
• Developers didn't have a habit of paying for Ruby gems; they expected open source with optional paid support
• No competitors existed — a red flag, not a green one: the market wasn't buying this way
• The product required catching customers at the right moment in their lifecycle; those who truly needed it had already built their own solution
• Customer discovery confirmed the pain point was real but the packaging and positioning were wrong

The pivot: Hello Query

• Shut down Refine Rails, sold the IP to the enterprise client, refunded all customers
• Relaunched as Hello Query (helloquery.com) — hosted internal reporting for teams
• Core value proposition: SQL to CSV, expanding to broader BI-style reporting
• Shifts from one-time licensing to per-seat SaaS — revenue stays recurring
• No longer limited to Rails developers; any team with a database is a potential customer
• Distribution angle: potential add-on partnerships with cloud database providers (e.g. Heroku, Postgres)

Customer discovery and validation

• Inbound interest confirmed the pain: developers manually building reports for non-technical colleagues, then fielding constant adjustment requests
• Existing competitors (e.g. Metabase) are seen as too complicated by target buyers — friction remains high
• One well-funded competitor had built a similar differentiating feature; team had to reconsider their moat
• Lesson from prior pre-sales: audience support and genuine business need are different signals
• New discipline: ask during interviews whether the problem exists at work, not on hobby projects
• Strategy is to pick one vertical first, nail positioning there, then expand

Rob's take on early-stage pivots

• Tiny Seed invested in Colleen and Aaron as founders, not in the specific idea
• Zero MRR after a pivot is a local minimum, not a failure signal
• Companies pivoting this early — before significant revenue — face far less structural risk than those hitting the same wall at $500k ARR
• Misaligned co-founder goals at scale are a common cause of company collapse; resolving them early is the better outcome