Ben interviews Josh Pigford about Maybe.co's journey from startup to open source project. They discuss tech stack decisions, challenges of personal finance software, and transitioning to Rails. Key takeaways include rebuilding software, targeting Mint users, and exploring moonshot ideas.
Choosing the right tech stack is crucial for project success.
Running out of runway can lead to difficult decisions and pivots.
Making a codebase public can drive community engagement.
Deep dives
Josh Pigford's Entrepreneurial Journey and Transition from Bear Metrics to Maybe
Josh Pigford transitioned from selling his company Bear Metrics for four million dollars to starting a new company called Maybe, focusing on financial planning and analysis. Despite funding and efforts, the team realized they overbuilt the product without sufficient validation.
The Unconventional Move and Positive Response to Publicly Sharing the Product
Feeling nostalgia for their work, Josh Pigford made Maybe public by stripping it down to its core and shared it online. The announcement tweet attracting attention with the claim 'This is what a million dollars in fintech software looks like'. The response was surprisingly positive with little negative feedback on the valuation.
Rapid Community Interest and Engagement
Within 24 hours of the public share, Maybe gained significant interest with thousands of GitHub stars and a rapidly growing community. Despite the product's incomplete status and complex infrastructure requirements, people were actively engaging and contributing ideas.
Transition to a React and Next.js Framework
Josh Pigford decided to rebuild Maybe from scratch using a React and Next.js framework. The transition involved removing complex infrastructure dependencies, such as Plaid, and refactoring the codebase to align with the revised product direction.
Strategic Shift Towards Budgeting and Modular Features
Instead of focusing solely on wealth management, Maybe shifted its focus to budgeting tools. The goal was to cater to the ex-Mint customers facing a gap in financial tools. The new approach involved modular features based on different financial life stages, with a long-term view towards user retention throughout their financial journey.
In this episode, Ben interviews Josh Pigford, founder of Maybe.co, about the company’s journey from VC-backed startup -> closed startup -> open source project -> funded open source project. They discuss JavaScript and Rails trade-offs, the challenges of building a personal finance software, and the operational difficulties of building a business based on open source software.
Links
Tuple.app - The best app for pair programming Maybe.co - The fintech startup Josh founded NodeJS - The starting framework for Maybe.co Ruby on Rails - The new framework for Maybe.co
Key Takeaways
Choosing the right tech stack is crucial for the success of a project.
Running out of runway can force difficult decisions and pivots.
Making a codebase public can generate interest and community engagement.
Replacing third-party dependencies can be challenging but necessary.
Rebuilding a software project requires careful planning and decision-making. Building a personal finance app involves challenges such as managing pull requests and issues in open source development.
Transitioning to Rails can provide a more stable and efficient framework for building a complex application.
The decision to rewrite the app from scratch allows for better decision-making and faster progress.
Targeting Mint users with a budgeting tool presents an opportunity to capitalize on a fragmented market.
Detangled, a project that simplifies legal documents, has the potential for commercial success. Moonshot ideas can be exciting and worth pursuing, even if the specific angle is unclear.
ChatGPT has the potential to generate usable results, either through heavily massaged prompts or prewritten blocks.
Tools like detangle can augment conversations with lawyers, providing insights and helping users know what questions to ask.
There are commercial opportunities in selling services like detangle to companies that don't have full-time counsel.
Finding the right balance between passion and traction is important when deciding which projects to pursue.
Chapters
(00:00) - Introduction
(01:21) - Making the Codebase Public
(07:21) - Community Engagement and Pull Requests
(12:17) - Ripping Out Functionality
(15:03) - Replacing Data Aggregator
(16:10) - Building a Personal Finance App
(17:39) - Challenges of Open Source Development
(21:08) - Managing Pull Requests and Issues
(23:35) - Struggles with React Next.js
(27:45) - Choosing Rails for Development
(32:40) - Targeting Mint Users with Budgeting Tool
(35:45) - Modular Use Cases
(38:53) - Open Source Contributions and Bounties
(40:47) - Next Steps
(45:16) - Detangled: Simplifying Legal Documents
(48:32) - Exploring Moonshot Ideas
(48:58) - The Potential of ChatGPT
(49:45) - Augmenting Conversations with Lawyers
(50:21) - Commercial Opportunities
(50:53) - Balancing Passion and Traction
(51:20) - Closing Remarks
Get the Snipd podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share & Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode