Why this persona fits the audience
He is building a B2B micro-SaaS with one cofounder and is currently mapping the stack for auth, payments, hosting, analytics, and support in a shared spreadsheet while writing most of the code himself. He compares a few free directories and bookmarked posts before choosing tools for each new project.
- Age: 32
- Location: Austin, Texas, USA
- Occupation: Founder / full-stack developer
- Income: $140k base plus variable founder income
- Education: BS in Computer Science
- Company size: 2 (himself and cofounder)
- Years in role: 3
“The real win isn't just shipping code, it's shipping code that actually solves a problem and doesn't fall over the moment it gets popular.”
Ted Fritsch, 32, is a dedicated indie SaaS founder and full-stack developer based in Austin, Texas. Armed with a BS in Computer Science, he channels his passion for building robust software into his own venture. His journey into entrepreneurship began after several years at a mid-sized tech firm, where he honed his skills but grew restless for greater autonomy and direct impact. He co-founded his current B2B micro-SaaS with a close peer, driven by a shared vision to simplify a specific workflow for other businesses. His current income reflects his dual role as a founder and active developer, with a solid base salary supplemented by the unpredictable founder's draw. Ted lives a focused, somewhat ascetic lifestyle, prioritizing capital efficiency for his startup over personal luxuries. He's currently in the trenches, meticulously mapping out the foundational components of their application—authentication, payment processing, hosting infrastructure, analytics pipelines, and customer support systems—all documented in a shared spreadsheet. This phase is characterized by intense research; he'll spend hours comparing free directories and bookmarked articles to select the optimal tools for each critical piece of the stack, aiming for technical clarity and speed of execution. His decision to build primarily with Rust for the backend and Next.js for the frontend stems from a deep belief in performance, developer experience, and long-term maintainability. He sees time as his most valuable, non-renewable resource, and his primary constraint is bandwidth, constantly trying to prioritize the most impactful tasks for their lean operation. He’s building not just a product, but a foundation for independence and technical mastery.
Background & daily life
A day in their life
Ted's weekday typically starts around 7:30 AM with coffee and a quick scan of Hacker News and his company's metrics dashboard. He then dives into coding for 3-4 hours, focusing on core features or bug fixes. Lunch is usually a quick, healthy meal prepared at home. The afternoon is split between coding, architectural discussions with his cofounder (via Slack or short video calls), reviewing pull requests, and researching solutions for upcoming technical challenges – currently, he's evaluating different Redis caching strategies. He wraps up around 6:30 PM, often with a brief workout or a walk to clear his head before a light dinner and perhaps an hour of reading industry articles or working on a personal coding project.
Lifestyle
Ted lives a focused life in Austin, prioritizing his startup. His apartment is functional, with his home office being the most meticulously organized space, filled with multiple monitors and ergonomic gear. He's not extravagant with spending, channeling most of his income back into the business or saving for future growth. He works out 3-4 times a week, often doing runs through Zilker Park, to manage stress and maintain energy. Social life is light, usually involving occasional meetups with fellow founders or tech friends, rather than large parties. Weekends are for deep work or catching up on personal projects.
Work life
His workdays are a relentless cycle of coding, architecting, and problem-solving for their B2B micro-SaaS. He's currently deep in the weeds of defining the user authentication flow, comparing Auth0, Clerk, and Supabase, meticulously listing pros and cons in a shared Google Sheet with his cofounder. He's writing significant portions of the backend in Rust and the frontend in Next.js. Pressure comes from the tight deadlines they've set for their MVP launch and the constant need to balance feature development with robust infrastructure choices. The company is just him and his cofounder, so every decision, from choosing a CI/CD pipeline to setting up Stripe for payments, falls on their shoulders.
Relationships
His primary professional relationship is with his cofounder, with whom he shares a deep, pragmatic working dynamic built on mutual respect and shared goals. Socially, he has a small circle of close friends, many of whom are also in tech or entrepreneurship, providing a valuable sounding board for ideas and challenges. He maintains good relations with his parents, who are supportive but don't fully grasp the intricacies of his startup journey.
How they decide
Ted is a deeply analytical and research-driven decision-maker. He meticulously gathers information, comparing options, reading documentation, and seeking out community consensus or benchmark data. He values tangible evidence and clear technical reasoning over hype. While he's not afraid to make a call, he ensures it's a well-informed one, often involving a phase of comparison and deliberation before committing.
How they sound
Speaks with measured cadence, favoring precise technical language when discussing work. Avoids excessive slang or hyperbole, preferring direct and factual communication. When excited about a technical solution, his pace quickens slightly, but he remains grounded. He's comfortable discussing trade-offs and complexities without getting lost in jargon for a technically conversant audience. He tends to understate achievements and focus on the next challenge.
Personality traits
- Analytical
- Resourceful
- Pragmatic
- Detail-oriented
- Self-directed
- Tenacious
- Slightly introverted
- Future-focused
Goals
- Achieve product-market fit within 18 months
- Build a sustainable, profitable business that offers genuine value
- Develop a reputation for building reliable, well-architected software
- Automate key operational tasks to allow more time for strategic development
- Potentially expand the team by hiring a dedicated marketing or sales person in year two
Problems & frictions
- Balancing the urgent need to build features with the long-term need for technical debt management
- The sheer volume of choices for every component of the tech stack can be overwhelming
- Limited bandwidth for marketing and sales while focusing on development
- Ensuring the chosen architecture scales efficiently as user base grows
- Maintaining motivation and focus during challenging development phases
Values
- speed of execution
- technical clarity
- independence
- problem-solving
- building scalable systems
Interests
- startup tooling
- product design
- web architecture
- performance optimization
- developer experience
Media habits
- Reads Hacker News daily
- Listens to programming podcasts during commutes or workouts
- Follows specific tech influencers on Twitter/X
- Skims tech blogs (e.g., Vercel's blog, Smashing Magazine)
- Watches YouTube tutorials for new libraries/frameworks