How a bootstrapped invoicing app taught me to build without a model

Executive overview

In 2005, Rob Walling made an $11,000 offer to acquire .NET Invoice, a struggling product generating just $100-200/month—based on due diligence that was incomplete. What followed was a crash course in product ownership: fixing critical bugs, tripling the price, learning SEO and sales, and eventually scaling the product to $2,000-5,000/month from nothing. This story reveals the mindset of a founder trying to build without precedent, operating in an era when no one yet had a template for bootstrapped SaaS.

Core insight: The biggest limitation was not capital or market size—it was the absence of a working model to copy.

The pre-internet business blueprint problem

• Raised on business magazines (Entrepreneur, Red Herring) that showcased venture-backed companies and IPOs
• No examples of solo founders or teams bootstrapping a product profitably
• Friends & family round felt impossible; didn't know anyone with capital
• Defaulted to thinking funding was a necessary step, even for modest revenue goals
• Cost of inaction: years lost to the assumption that a business had to follow the VC template

Finding and acquiring .NET Invoice

• Discovered product via a developer's portfolio; invoicing software targeting small business owners
• Developers averaging $700-1,000/month in revenue; six months of sales history; ranked well for keywords
• Made an $11,000 offer (verified against $10,000 counteroffer); nearly all liquid capital in business bank account
• Due diligence was superficial: verified screenshots and traffic, saw code samples, but didn't validate whether sales numbers were sustainable
• Reality: developers had spiked revenue with launch emails; true baseline was closer to $200/month

The product disaster and recovery

• Code was alpha-stage with critical math errors in an invoicing tool (the one job it had to do)
• Customers were angry and felt oversold; returned many support requests
• Worked 60-hour weeks nights and weekends for six weeks fixing dozens of bugs simultaneously
• Eliminated the "unsupported version" distinction and provided support across the board
• Tripled price from $98 to $295/month on an experiment; next month still sold three copies at the higher price
• Key insight: willingness to stay in the game was fueled by putting his back to the wall financially

Scaling the product via marketing and pricing

• Built the first real skill set: SEO, Google AdWords, copywriting, customer support, lightweight sales
• Avoided phone sales by making it clear upfront; wanted inbound leads only
• Revenue climbed to $2,000-5,000/month most months; best month reached ~$5,000
• Realized the niche early: .NET developers who wanted to control their own data or use it as a code base
• Market was small but defined; this was where Walling learned the power of niches, B2B, and higher price points

The partnership question and diverging paths

• Pitched the idea to a colleague with strong business acumen and sales skills; expected a yes
• Colleague countered: his remote agency was more profitable and required less capital investment
• Pushing back on the colleague's point, Walling argued an agency doesn't build lasting equity
• Colleague's insight proved durable: finding good people was harder than selling; product growth requires heavy upfront investment with ongoing threats from free competitors
• Walling pushed for boots-on-ground execution; colleague wanted a business plan first
• This divergence revealed different operating styles, not a fatal flaw—they had misaligned visions of freedom and growth

The broader pattern: building without precedent

• Venture funding was presented as inevitable in tech media, even for modest bootstrapped goals
• No published playbooks for profitable product businesses outside the VC lens
• Joel Spolsky and Basecamp HQ were rare exceptions discussed in this period
• The uncertainty was paralyzing: can this actually work at this scale without funding? Should we even try?
• Walling's answer: build first, learn second, adjust as you go—not a business plan, but boots on the ground

Lessons woven through the journey

• Price sensitivity is overstated; customers will pay for better quality and support
• Fixing one critical failure can buy you time and goodwill
• Niches are not a constraint; they're a moat for bootstrapped products
• Relationships matter more than any business outcome; protect them fiercely
• Back-to-the-wall pressure can fuel execution when you've bet real capital
• Knowing yourself is the real prerequisite: are you building for freedom or for maximum growth?

What happened next

• Built a portfolio of products over the following years; shifted into SaaS
• Eventually brought on a business partner (a mutual friend of the original colleague) on a 50-50 basis
• As Walling's focus shifted to his book, podcast, and Microconf, .NET Invoice became a secondary asset
• Partner model evolved; eventually gave full ownership to the partner as synergies faded
• In hindsight, the solo path would have been more aligned with Walling's actual strengths (marketing and SEO, not high-touch sales)