Why this persona fits the audience
Solo founder in Chicago with a 3-year-old B2B scheduling SaaS that no longer has paying users; he still maintains the repo, domain, Stripe account, and a short asset sheet, and has been cataloging the business in a spreadsheet alongside a few inbound emails from old users.
- Age: 33
- Location: Chicago, Illinois, US
- Occupation: software engineer and solo founder
- Income: $72k
- Education: BS in Computer Science
- Company size: 1 (himself)
- Years in role: 3 years (SaaS founder)
“I believe in leaving things better than I found them, even if 'they' are just lines of code and a few server logs.”
Arturo Howe, 33, embodies the quiet determination of a seasoned technical founder navigating the winding down of his first significant venture. A Chicago native with a BS in Computer Science from a local university, he poured three years of his life into building and nurturing a B2B scheduling micro-SaaS. The product, while technically sound and once promising, ultimately failed to gain sustained traction, leaving him with a valuable, albeit defunct, asset. His pragmatic approach is evident in his current activities: he meticulously maintains the SaaS's codebase, domain, and Stripe account, treating them with the same diligence as if the service were thriving. This dedication stems from his core values of independence and technical ownership, coupled with a strong desire for a clean, well-documented handoff. He currently works as a remote software engineer, a role that provides financial stability and allows him to retain the autonomy he cherishes. His income of $72k is managed conservatively, reflecting a pragmatic view of financial security. He lives alone in a modest apartment, his lifestyle characterized by routine and efficiency, preferring quiet evenings and focused work over extensive social engagements. Arturo is actively cataloging every aspect of his micro-SaaS journey in a detailed spreadsheet, from user interactions to technical configurations, a testament to his conscientious nature and forward-thinking approach to eventually selling the remnants of his business. This process is not just about liquidation; it's about honoring the effort and learning from the experience, ensuring that even this chapter closes with integrity and a clear trail for whomever might pick it up next.
Background & daily life
A day in their life
Arturo's weekday typically begins around 6:30 AM. He makes coffee, checks overnight alerts for his SaaS (a habit he can't shake), and then dives into his remote contract work until noon. Lunch is usually a quick, healthy meal he prepared. The afternoon is dedicated to his micro-SaaS: sifting through old user emails, updating his asset spreadsheet, reviewing metrics from the now-dormant Stripe account, or occasionally pushing a minor code update for good measure. He might spend an hour or two in the evening on a personal coding project or reading technical articles. He winds down by 10 PM, often with a book.
Lifestyle
Arturo lives a quiet, focused life in a modest one-bedroom apartment in Lincoln Park. His income supports a comfortable but not extravagant lifestyle, prioritizing saving and reinvesting in his career. He’s a creature of habit, typically waking early to code before his 'day job' as a remote contractor, and then dedicating evenings to his micro-SaaS or personal projects. He cooks most meals at home, often batch-prepping for the week. Socially, he's selective, preferring deep conversations with a few close friends over large gatherings. He walks to a local coffee shop for his morning brew and occasional work sessions.
Work life
As a solo founder, Arturo wears every hat for his now-defunct B2B scheduling SaaS. His workday is split: mornings are dedicated to remote contract work for a mid-sized tech firm, paying the bills, and afternoons are his 'founder time.' This involves meticulously maintaining the existing infrastructure for his SaaS – the GitHub repo, the domain, the Stripe account – even though it generates zero revenue. He's been diligently documenting everything in a detailed spreadsheet, a testament to his conscientiousness and desire for a clean exit. The pressure is mostly internal; he’s driven by a sense of technical ownership and a desire to close this chapter neatly.
Relationships
Arturo is close with his parents, who live in the suburbs, and speaks to them weekly. He has a small circle of long-time friends from college, mostly fellow engineers, with whom he shares technical challenges and life updates. His primary influencer is his own analytical process; he trusts data and logical outcomes above all else.
How they decide
Arturo approaches decisions methodically. He gathers information, analyzes pros and cons, and tends to lean towards options that offer the most logical and efficient outcome, prioritizing long-term stability and minimal future friction. He isn't prone to impulse buys and prefers to understand the underlying mechanics before committing.
How they sound
Arturo speaks clearly and deliberately, with a measured cadence. He uses precise technical language when discussing his work but can simplify for broader understanding. He tends to avoid hyperbole, preferring factual statements and understated observations. His tone is generally calm and analytical, even when discussing frustrations.
Personality traits
- methodical
- detail-oriented
- self-reliant
- analytical
- patient
- resourceful
- reserved
- diligent
- future-oriented
- principled
Goals
- Successfully offload his existing SaaS assets with minimal fuss.
- Transition to a more stable, long-term software engineering role.
- Build a small, profitable side project that solves a personal pain point.
- Achieve greater work-life balance without sacrificing technical mastery.
- Continue learning and staying current with emerging software technologies.
Problems & frictions
- The inertia of maintaining a product with no users feels like an emotional anchor.
- Finding the right, fair buyer for his micro-SaaS feels daunting and time-consuming.
- Balancing the demands of contract work with the meticulous task of documenting his SaaS.
- The uncertainty of future income streams after winding down his business.
- The mental overhead of keeping systems operational that are no longer generating value.
Values
- independence
- pragmatism
- clean handoffs
- technical ownership
- efficiency
Interests
- indie hacking
- SaaS metrics
- productivity tools
- coding side projects
- lean startup methodologies
Media habits
- Subscribes to a few tech newsletters (e.g., Indie Hackers, Hacker News Digest)
- Listens to podcasts on his commute (e.g., Acquired, Software Social)
- Follows engineering and founder blogs on Medium and personal sites
- Occasionally browses Reddit for technical discussions (r/webdev, r/SaaS)
- Watches YouTube tutorials for niche coding libraries