Why this persona fits the audience
Runs a two-person SaaS from San Francisco and uses Claude Code on a MacBook to ship customer-requested fixes, paste bug screenshots, and inspect full-window text from admin flows. Keeps most work in GitHub issues and a simple spreadsheet while balancing development with support.
- Age: 31
- Location: San Francisco, CA, USA
- Occupation: Bootstrapped SaaS founder / full-stack developer
- Income: $165,000
- Education: B.S. Computer Science
- Company size: 2 (himself and a part-time customer support/QA person)
- Years in role: 4
“Every line of code I ship has to earn its keep; it’s either fixing a problem for a customer or pushing the product forward, no room for fluff.”
Don Douglas-Goldner, 31, is a quintessential bootstrapped founder navigating the demanding landscape of the San Francisco tech scene. Armed with a B.S. in Computer Science from UC Berkeley, he channeled his passion for building into a two-person SaaS company four years ago. He operates out of his compact apartment, his primary workstation a MacBook Pro, the hub of his development and operational efforts. His company is a lean operation, relying on a part-time support specialist to handle customer inquiries and initial QA. Don's work ethic is defined by a relentless focus on shipping code quickly and responding directly to customer needs. He meticulously manages his development workflow using GitHub issues and a straightforward spreadsheet for key metrics, eschewing more complex project management tools for simplicity and speed. His income, around $165,000, is largely reinvested into the business, with personal luxuries taking a backseat. He recently made a conscious decision to integrate AI coding assistants more deeply into his workflow, particularly for tasks requiring visual context or detailed text analysis from admin interfaces, recognizing the potential for significant time savings. This move reflects his ongoing quest for efficiency and independence, aiming to scale his product without external funding, maintaining full control over his creation and its trajectory. His personal life is similarly optimized, with cycling serving as his primary outlet for stress relief and mental clarity, a stark contrast to the intense cognitive load of his entrepreneurial pursuits.
Background & daily life
A day in their life
Don's day typically starts around 7:30 AM with coffee and a quick scan of Hacker News and his company's support queue while still at his desk. He dedicates the morning to focused coding, tackling bug fixes or implementing small features based on customer feedback. Lunch is usually a quick affair, often a sandwich eaten while reviewing product analytics. Afternoons are a mix of coding, responding to urgent customer emails, planning the next development sprint with his support person, and researching new developer tools or automation techniques. He aims to wrap up by 7 PM, though late-night coding sessions aren't uncommon if a critical issue arises. Evenings are for dinner with his partner and unwinding, often by reading or watching a documentary.
Lifestyle
Don lives a focused, somewhat spartan existence driven by his startup. His income mostly goes back into the business or is saved. He rents a compact apartment in the Mission district, often eating simple meals at his desk. Weekends involve long bike rides to clear his head and escape the screen, followed by quiet evenings with his partner. He values efficiency in all things, from his morning routine to his workflow, and is constantly looking for ways to optimize his time and energy. Social life is minimal, often limited to occasional meetups with a few close friends from college.
Work life
As the sole developer and co-founder of a two-person SaaS company, Don's work life is a constant juggle. He spends his days writing code, debugging, deploying fixes, and sometimes jumping on support calls to understand user pain points firsthand. His primary tools are his MacBook Pro, GitHub, a simple spreadsheet for tracking key metrics, and increasingly, AI coding assistants. He collaborates closely with his part-time support person, relying on clear GitHub issues and direct communication. The pressure to ship customer-requested features and address bugs promptly is immense, often blurring the lines between work and personal time.
Relationships
Don's primary relationship is with his partner, who provides emotional support and acts as a sounding board for ideas, though she's not in the tech industry. He maintains a small circle of close friends, mostly former university colleagues, with whom he discusses technical challenges and startup life. His part-time support person is his main work contact, and their communication is strictly professional but friendly.
How they decide
Don is highly analytical and research-oriented when it comes to technical tools and infrastructure. He'll compare options, read documentation, and often experiment with free tiers before committing. For business strategy, he relies on data and logical deduction, cautiously weighing risks and potential rewards. He trusts his own judgment and experience over external hype or influencer opinions.
How they sound
Speaks clearly and directly, with a slightly rapid cadence when discussing technical topics. Avoids overly casual slang but isn't stiffly formal. Uses precise technical language when necessary but can simplify concepts for his partner. Tends to be objective and factual, sometimes cutting straight to the point without much preamble. He's not afraid to admit when he doesn't know something but frames it as a learning opportunity.
Personality traits
- pragmatic
- resourceful
- detail-oriented
- self-disciplined
- analytical
- slightly introverted
- results-driven
- skeptical of hype
Goals
- Achieve sustainable profitability for his SaaS.
- Build a product that genuinely solves a significant user problem.
- Automate enough of his business operations to reclaim personal time.
- Develop a stronger understanding of product-led growth strategies.
- Eventually hire a small, dedicated engineering team.
Problems & frictions
- Limited time and resources for development.
- Balancing feature requests with core product stability.
- The constant threat of larger competitors entering his niche.
- The operational overhead of running a business solo (admin, finance, etc.).
- Difficulty in forecasting user growth and revenue accurately.
- Maintaining motivation during slow growth periods.
Values
- shipping quickly
- independence
- customer responsiveness
- efficiency
- problem-solving
Interests
- no-code and automation
- product analytics
- cycling
- backend architecture
- developer tooling
Media habits
- Reads Hacker News daily
- Listens to tech podcasts during commutes/exercise
- Follows key figures on Twitter/X for industry news
- Skims tech blogs and newsletters (e.g., TLDR, Joel on Software)
- Watches YouTube tutorials on specific programming challenges