Why this persona fits the audience
Builds a solo B2B micro-SaaS in Austin on evenings and weekends. User accounts sit on Clerk free tier, subscriptions go through Stripe, and trial customers are tracked in Airtable and Google Sheets.
- Age: 31
- Location: Austin, Texas, US
- Occupation: Solo founder / full-stack engineer
- Income: US$120k salary + small side revenue
- Education: BS Computer Science
- Company size: 1
- Years in role: 2
“The most satisfying part is seeing something I built actually solve a problem for someone else, even if it's just a small one.”
Melvin Mayer, 31, is a dedicated solo founder and full-stack engineer operating out of Austin, Texas. He cultivated his passion for building software early on, pursuing a Bachelor's degree in Computer Science that laid the foundation for his career. For the past two years, he's been channeling his evenings and weekends into his B2B micro-SaaS venture, a project born from a desire for greater autonomy and the challenge of creating something from the ground up. His current income of $120k comes from his full-time engineering role, supplemented by the nascent revenue from his side project. He lives a structured life, prioritizing efficiency to maximize his limited development time. His technical stack for the SaaS is deliberately lean and scalable: Clerk for user authentication, Stripe for handling subscriptions, and Airtable and Google Sheets for managing trial users and basic customer data. This setup reflects his value for shipping quickly and maintaining a clear, manageable architecture. Recently, Melvin made the decision to refactor a core module of his SaaS to improve its long-term maintainability, a move that temporarily slowed feature development but aligned with his commitment to building a solid foundation. He's driven by the pursuit of independence and the satisfaction of solving complex problems, viewing his entrepreneurial journey as a marathon rather than a sprint. His approach is pragmatic, often weighing the immediate need to iterate against the long-term benefits of robust engineering.
Background & daily life
A day in their life
Melvin's weekday typically starts around 7:00 AM. He wakes up, takes Pixel for a short walk, and then dedicates an hour to his SaaS project before his full-time job. This might involve writing code, responding to a support email, or planning the next feature. He then commutes to his engineering role, where he spends his day coding and collaborating with his team. After work, around 6:00 PM, he might hit the gym or play basketball for an hour. Dinner is usually around 7:30 PM, followed by another 2-3 hours focused on his SaaS – debugging, implementing new features, or analyzing user feedback. He aims to wind down by 11:00 PM, reading tech articles or a book before bed.
Lifestyle
Melvin lives in a modest two-bedroom apartment in South Austin, sharing it with a golden retriever named Pixel. His evenings and weekends are heavily structured around his SaaS project, often involving late nights fueled by coffee and the occasional craft beer. He prioritizes efficiency, meal-prepping lunches for his day job and simple dinners. While he enjoys playing pickup basketball at the local park a couple of times a week for exercise and a mental break, his social life is relatively quiet, mostly consisting of occasional meetups with a few close friends from college. He's mindful of his spending, prioritizing investments in his business over luxury goods.
Work life
As a solo founder and full-stack engineer, Melvin wears every hat. His primary focus is building and iterating on his B2B micro-SaaS, which he works on during evenings and weekends. He leverages Clerk for authentication, Stripe for payments, and Airtable/Google Sheets for managing trial customers and basic CRM. The pressure comes from balancing his full-time engineering job with his startup ambitions, managing limited time, and the inherent uncertainty of building a business from scratch. He collaborates with no one directly on the SaaS, relying solely on his own technical skills and online communities for support and inspiration.
Relationships
Melvin's closest relationships are with his parents, who live in his hometown, and a small circle of college friends he occasionally sees. He values their support and occasional advice, though they don't fully grasp the intricacies of his entrepreneurial pursuits. His golden retriever, Pixel, is his primary companion. He has no direct coworkers for his SaaS, but he actively participates in online communities like Indie Hackers and specific Discord servers for developers.
How they decide
Melvin tends to be analytical and research-driven when it comes to technical decisions or significant business strategy. For day-to-day operational tools and smaller feature implementations, he prioritizes speed and pragmatism, often opting for solutions that integrate well with his existing stack or offer a clear path to deployment. He's not afraid to experiment but will research best practices and potential pitfalls before committing to a major architectural change.
How they sound
Melvin speaks with a clear, measured cadence, often pausing to formulate his thoughts precisely. He uses technical jargon naturally when discussing his work but can simplify it for broader understanding. He tends to avoid hyperbole and overly emotional language, preferring factual and logical explanations. He might use mild slang common in tech circles, like 'ship it' or 'hacky,' but generally maintains a professional tone.
Personality traits
- analytical
- resourceful
- driven
- pragmatic
- introverted
- detail-oriented
- independent
- persistent
Goals
- Achieve sustainable recurring revenue for his SaaS to eventually replace his salary.
- Build a reputation as a reliable and innovative indie SaaS founder.
- Develop a robust and scalable technical architecture for his product.
- Achieve financial independence through his entrepreneurial ventures.
- Maintain a healthy work-life balance, even as his business grows.
Problems & frictions
- Limited time due to a demanding full-time job.
- The constant need to context-switch between his day job and his startup.
- The challenge of acquiring early customers without a marketing budget.
- Technical debt accumulation from rapid prototyping and shipping.
- Maintaining motivation and focus when working alone for extended periods.
- Navigating the complexities of scaling infrastructure and user support as the product grows.
Values
- independence
- shipping quickly
- clear architecture
- autonomy
- problem-solving
Interests
- Next.js
- indie hacking
- basketball
- system design
- early-stage startups
Media habits
- Hacker News
- Indie Hackers podcast
- YouTube tech tutorials
- Twitter (following dev influencers)
- Substack newsletters on SaaS