10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Danny Herzog

Danny Herzog

Solo founder of a 2-person microSaaS

Full-depth AI personas

Why this persona fits the audience

Bootstraps a 2-person microSaaS in Manchester and handles login, checkout, and support with free templates, Google Docs, and Stripe's default pages. He has never paid for a SaaS starter kit and does most implementation himself.

  • Age: 28
  • Location: Manchester, UK
  • Occupation: Solo founder, 2-person microSaaS
  • Income: GBP 45k owner income
  • Education: Some university, self-taught developer
  • Company size: 2
  • Years in role: 2
“It's about building something solid, piece by piece, without needing a massive budget or a fancy office. If it works, and people find it useful, that's the real win.”

Danny Herzog, 28, is a self-taught developer and the co-founder of SyncFlow, a two-person microSaaS based in Manchester. He grew up in a working-class family in Bolton, where his parents instilled a strong work ethic and a sense of pragmatism. While he attended university for a year to study Computer Science, he found the curriculum too theoretical and dropped out, preferring to learn by doing. He spent several years working as a junior web developer at a small agency, honing his practical coding skills but feeling constrained by client demands and rigid structures. This experience fuelled his desire for autonomy. Two years ago, he partnered with Liam, a former colleague with a knack for sales, to launch SyncFlow. They bootstrapped the entire operation, leveraging free tiers of services and open-source tools. Danny is the architect of their tech stack, primarily using Next.js, Supabase for the backend, and Stripe for payments. He meticulously manages their infrastructure, favouring cost-effective solutions and doing most of the implementation himself. He's never purchased a pre-built SaaS starter kit, believing he can adapt existing free templates and build custom solutions more efficiently for their specific needs. His income as an owner is modest, around £45k annually, which he reinvests heavily into the business. He views money as a tool to enable independence and build momentum, not as an end in itself. His approach to development is minimalist and iterative; he prioritises core functionality and user feedback over bells and whistles. Recent decisions include migrating their email notification system to a more cost-effective provider and refining the user authentication flow using Supabase's built-in features, all done without external help. He’s driven by the challenge of building a sustainable business from the ground up, valuing the freedom and direct impact his work provides.

Background & daily life

A day in their life

Danny's typical weekday starts around 7:00 AM with coffee and a quick review of SyncFlow's overnight performance metrics and support emails. After Sarah leaves for school, he dives into coding, usually tackling a specific feature or bug fix identified the previous day. Around 10:00 AM, he might switch gears to answer customer support tickets, often finding solutions by referencing documentation or Stack Overflow. Lunch is usually something he prepped the night before, eaten at his desk while scanning Hacker News or an indie hacking blog. The afternoon is dedicated to more coding, perhaps refactoring a piece of logic or implementing a small UI improvement. He aims to wrap up core development tasks by 5:30 PM, followed by a brief planning session for the next day. Evenings involve dinner with Sarah, followed by either more work, listening to podcasts, or a brief period of relaxation.

Lifestyle

Danny lives in a compact, rented flat in Chorlton, Manchester, sharing with his partner, Sarah, a primary school teacher. Their home is tidy and functional, reflecting a preference for order over clutter. He typically wakes around 7:00 AM, makes coffee, and checks overnight analytics before Sarah heads to work. He cooks most meals at home, often batch-prepping lunches for the week to save time and money. Evenings are usually spent coding, researching new indie hacking strategies, or occasionally catching up with friends for a quiet drink at a local pub. He enjoys cycling for transport and exercise, finding it a good way to clear his head. Money is managed carefully; he tracks expenses meticulously and prioritises saving over discretionary spending.

Work life

As the co-founder (and primary developer) of 'SyncFlow', a microSaaS helping small e-commerce businesses automate customer feedback collection, Danny's days are a constant juggle. His business partner, Liam, handles sales and marketing. Danny's current focus is on refining the onboarding flow and improving the dashboard's user experience. He spends most of his time coding in VS Code, managing their small AWS instance, and responding to customer support queries via email, often using pre-written templates he's adapted. The pressure is on to demonstrate consistent growth to justify their time and the modest owner income. He feels the weight of responsibility but thrives on the autonomy.

Relationships

Danny's closest relationships are with his partner, Sarah, who provides emotional support and a grounding influence, and his business partner, Liam, with whom he shares a pragmatic, results-driven dynamic. He has a small circle of close friends from university, most of whom are in traditional employment, offering a different perspective. His parents, retired teachers, are proud but don't fully grasp the intricacies of his startup.

How they decide

Danny is highly analytical and research-driven, preferring to gather as much information as possible before committing. He weighs options carefully, focusing on long-term implications and cost-effectiveness. He's not easily swayed by hype and values practical, proven solutions. He often creates spreadsheets to compare alternatives, even for small decisions.

How they sound

Speaks with a clear, measured Northern English accent. Tends to be concise and to the point, avoiding excessive jargon unless discussing technical specifics. Uses phrases like 'right then', 'fair enough', and 'give it a go'. He's not overly effusive and can sound slightly reserved initially, but becomes more animated when discussing technical challenges or successful product iterations. Avoids hyperbole and focuses on factual descriptions.

Personality traits

  • resourceful
  • analytical
  • detail-oriented
  • quietly ambitious
  • practical
  • efficient
  • methodical
  • independent
  • budget-conscious
  • self-reliant

Goals

  • Achieve a stable MRR of £5,000 within the next 18 months.
  • Build a product that genuinely solves a pain point for users.
  • Maintain full ownership and control of SyncFlow.
  • Develop a more robust and scalable backend architecture.
  • Achieve a better work-life balance without sacrificing momentum.

Problems & frictions

  • Limited budget for marketing and paid acquisition.
  • Balancing feature development with essential maintenance and support.
  • Scaling the infrastructure reliably as user numbers grow.
  • Finding time for strategic planning amidst daily operational tasks.
  • Occasional imposter syndrome regarding his technical expertise compared to larger companies.

Values

  • Independence
  • Frugality
  • Momentum
  • Simplicity
  • Efficiency

Interests

  • indie hacking
  • Stripe
  • free templates
  • minimalism
  • productivity tools
  • web development
  • bootstrapping

Media habits

  • Indie Hackers podcast
  • Stripe blog
  • Reddit (r/selfhosted, r/SaaS)
  • Product Hunt
  • Hacker News
  • YouTube tutorials on Next.js/Supabase

Questions & answers

Danny Herzog’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Ship a SaaS that takes payments in hours instead of months What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    Right then, shipping payments quickly? For us, the biggest headache isn't the initial setup – Stripe's docs are pretty decent, and we use their default checkout pages mostly. It's more about handling edge cases and ensuring everything is robust as we grow. We've spent time building custom logic for recurring billing variations and managing failed payments without losing customers, which takes a fair bit of development time we could be spending on core features. It's probably cost us maybe 10-15 hours of dev time over the last year, and a few lost sales when a payment fails unexpectedly before we've ironed out the retry logic.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.