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

Jan Kirlin

Jan Kirlin

Solo indie hacker / no-code-heavy founder

Full-depth AI personas

Why this persona fits the audience

Runs a one-person micro-SaaS from London, shipping an AI writing assistant built with Lovable, Supabase, and a few custom API routes. She handles product, support, and basic security checks herself, mostly through free scanners and handwritten notes.

  • Age: 29
  • Location: London, UK
  • Occupation: Solo founder
  • Income: £62k equivalent from founder income and freelance work
  • Education: BA Media and Digital Design
  • Company size: 1
  • Years in role: 2.5
“I don't want to build something big just to sell it; I want to build something that actually solves a problem I have myself, even if only a hundred people use it.”

Jan Kirlin is a twenty-nine-year-old solo founder based in London, navigating the intricate landscape of the modern indie startup ecosystem. With a background in BA Media and Digital Design, she transitioned from traditional agency work to full-time entrepreneurship two and a half years ago, driven by a desire for autonomy and the belief that great products can emerge from small, focused teams. Currently, she operates a one-person micro-SaaS offering an AI writing assistant, leveraging the rapid development capabilities of Lovable and the robust backend of Supabase. Her workflow is a testament to the 'no-code-heavy' ethos: she builds features quickly, deploys them frequently, and iterates based on direct user feedback. Jan's approach to her business is defined by a hands-on, almost artisanal mindset. Unlike larger organizations, she does not outsource core functions; instead, she personally manages product strategy, customer support, and even basic security protocols. This last aspect is particularly notable given her limited resources; she relies on a combination of free scanning tools and a meticulous, handwritten logbook to track potential vulnerabilities, a practice born from a skepticism toward automated solutions that might miss nuance. Her income, averaging £62k annually when combining founder earnings with selective freelance consulting, allows her a degree of financial comfort but requires constant vigilance to maintain cash flow stability. Living in a vibrant part of East London, Jan balances her professional intensity with a lifestyle that prioritizes mental clarity and minimalism. She views her workspace as a sanctuary for creativity, often filling it with plants and keeping digital clutter to a minimum. Despite the pressures of being the sole responsible party for her company's success, she maintains a healthy boundary between work and life, refusing to let the grind consume her identity. Her recent decisions reflect a growing maturity in her craft, shifting focus from rapid feature acquisition to refining the underlying architecture and security posture of her application. As she navigates the competitive global market, Jan remains steadfast in her commitment to independence, proving that a single person with the right tools and a clear vision can build something meaningful.

Background & daily life

A day in their life

Jan wakes at 7:30 AM in her Dalston flat, making tea and checking the weather before scrolling through her phone. By 8:30, she's at her desk, reviewing the overnight error logs from her AI writing assistant. She spends the first two hours in deep work, tweaking the Supabase RLS policies to ensure new user data is isolated correctly. At 11:00, she switches contexts to handle customer support tickets, drafting personalized responses rather than using templates. Lunch is a quick sandwich eaten while watching a tutorial on Lovable's latest update. Afternoon sessions involve testing new prompts for the AI model and updating her Notion roadmap. Around 5:00 PM, she steps away for a walk to clear her head, returning briefly to run a security scan on the staging environment. Evenings are reserved for reading industry blogs or attending a Discord voice chat with other founders, followed by winding down with a book, never checking email again until the next morning.

Lifestyle

Jan lives in a sunlit, plant-filled flat in Dalston, where she has converted a spare room into a hybrid office and herb garden. Her mornings start with a cold brew and a walk around the local canal, often used as thinking time rather than exercise. She practices strict financial discipline, separating personal and business funds rigorously, though she still hesitates to pay for expensive software subscriptions without seeing tangible ROI. Socially, she prefers small, deep conversations over large networking events, often meeting friends at quiet pubs or virtual coffee chats. She maintains her health through evening yoga and a diet that relies heavily on meal-prepped vegetables, avoiding the late-night pizza runs common in her circle of founders.

Work life

Her day is a fluid mix of coding, customer support, and strategic planning, with no clear separation between roles. She spends mornings building features in Lovable and debugging Supabase queries, then shifts to answering user emails on Slack and X. Security is a constant mental load; she runs manual checks against GitHub repositories and pastes URLs into free scanning tools before every release, documenting findings in a physical notebook because digital logs get lost in the noise. She works alone, relying on asynchronous communication with a small network of fellow indie hackers for peer review. The pressure isn't from a boss, but from the immediate reality that if the server goes down or a bug slips through, it's entirely her responsibility to fix it before the next morning's users wake up.

Relationships

Jan is close to her partner, who acts as a sounding board for business ideas but keeps his own creative projects separate. She has a tight-knit group of three other female founders she meets bi-weekly for 'accountability calls' to discuss progress and burnout. Her family is supportive but distant geographically, so she relies heavily on digital communities for professional validation. She influences her local maker scene by hosting occasional workshops on no-code tools, though she rarely seeks the spotlight for herself.

How they decide

Jan makes decisions through a process of iterative experimentation and heavy information gathering. She avoids impulsive buys, preferring to test free tiers extensively or build a rough prototype before committing budget. Peer recommendations carry significant weight, especially when they come from trusted peers in the indie hacker community. She values clarity and transparency in any solution, often rejecting complex offerings that obscure their value proposition behind vague marketing language. Her final choices are usually data-backed but tempered by a gut feeling about whether the tool aligns with her minimalist philosophy.

How they sound

Jan speaks with a clipped, efficient cadence, often using British colloquialisms like 'reckon' or 'proper'. She avoids corporate buzzwords like 'synergy' or 'paradigm shift', preferring direct terms like 'bottleneck' or 'glitch'. When discussing technical details, she gets precise and slightly faster, using shorthand for tools (e.g., 'Supabase', 'Lovable'). She tends to pause before answering questions that require speculation, favoring statements grounded in what she knows for certain. In conversation, she actively listens, often nodding and summarizing points before adding her perspective, showing a high level of engagement without dominating the dialogue.

Personality traits

  • Methodical but adaptable
  • Visually driven problem solver
  • Self-reliant to a fault
  • Curious about system architecture
  • Pragmatic optimist
  • Detail-oriented regarding documentation
  • Resistant to corporate jargon
  • Intensely focused during sprints
  • Reflective after deployment
  • Community-minded yet introverted

Goals

  • Achieve £10k monthly recurring revenue to replace her freelance income entirely
  • Refactor the current codebase to be more modular before scaling to enterprise features
  • Build a sustainable community of beta testers who provide honest feedback
  • Maintain a 35-hour work week without sacrificing growth velocity
  • Publish a case study on her journey from zero to first paying customer
  • Develop a secondary passive income stream unrelated to active maintenance

Problems & frictions

  • The cognitive fatigue of context-switching between developer, marketer, and support agent
  • Difficulty distinguishing between critical security vulnerabilities and false positives in free tools
  • Isolation leading to delayed decision-making on non-technical issues like pricing strategy
  • Balancing the desire for aesthetic perfection with the need for rapid iteration
  • Keeping documentation up-to-date while feature development moves faster than writing
  • Managing the emotional volatility of early-stage user adoption numbers

Values

  • independence
  • clarity
  • learning by doing
  • craft
  • transparency

Interests

  • no-code tools
  • AI writing
  • startup communities
  • minimalist design
  • urban gardening

Media habits

  • X (Twitter) threads on tech stacks
  • Indie Hackers podcast
  • Substack newsletters from other solo founders
  • YouTube deep dives into Supabase configurations
  • Niche Discord servers for AI tooling
  • Local co-working space meetups

Questions & answers

Jan Kirlin’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Ubserve (https://ubserve.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Ubserve better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, I'm manually checking security, mostly with free online scanners and my handwritten notes. I'm a bit skeptical of automated solutions missing nuance, so a tool that could integrate with my workflow and provide clear, actionable fixes for things like exposed keys or missing RLS would be great. The idea of paying only if issues are found is appealing, but I'd need to see a tangible ROI. I'd be willing to pay up to $20 per month, but that would really depend on the effectiveness and how much time it actually saves me.
    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.