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

Martin Heidenreich

Martin Heidenreich

Self-taught developer launching a first paid side project

Full-depth AI personas

Why this persona fits the audience

Works as an IT support analyst in Chicago and is building his first paid web app after hours. He learned Flask from tutorials, has no previous experience buying dev kits, and is currently stitching together authentication, Stripe checkout, and a simple admin dashboard for a beta launch.

  • Age: 27
  • Location: Chicago, IL, US
  • Occupation: IT support analyst
  • Income: USD 74k salary
  • Education: Associate degree + self-taught coding
  • Company size: Mid-sized enterprise (500-1000 employees)
  • Years in role: 3
“I'd rather build something broken and real than wait forever for the perfect plan to appear.”

Martin Heidenreich is a 27-year-old IT support analyst residing in the Logan Square neighborhood of Chicago, Illinois. Born into a working-class family, he earned an Associate degree in Computer Information Systems before diving into the workforce, eventually settling into a stable role handling technical support for a regional logistics firm. Despite earning a solid $74,000 annually, Martin feels a persistent pull toward entrepreneurship, driven by a desire to create tangible value rather than merely maintain existing systems. His journey into software development began entirely through self-directed learning; he consumed countless YouTube tutorials and documentation pages, mastering Python and the Flask framework without formal university instruction in web development. Currently, he is navigating the treacherous waters of his first commercial venture: a B2B web application designed to streamline inventory tracking for small businesses. Unlike seasoned founders, Martin has zero prior experience purchasing specialized development kits or managing cloud infrastructure budgets. He is currently in the critical phase of integrating authentication services, setting up Stripe for recurring payments, and manually constructing a rudimentary admin dashboard. His days are split between the mundane, often frustrating reality of corporate IT support—resetting passwords and fixing printer drivers—and the high-stakes, solitary grind of coding late into the night. Financial prudence is a core tenet of his life; he meticulously tracks expenses and hesitates to spend money on tools unless he is convinced they offer immediate, irreplaceable utility. This constraint fuels his current dilemma: how to bridge the gap between his limited budget and the professional-grade requirements of a market-ready product. Martin is defined by his persistence and a quiet, methodical optimism. He views his side project not just as a potential income stream, but as a proving ground for his skills and a testament to his ability to persist despite the overwhelming odds faced by solo founders. Every line of code he writes is a step away from the safety of his salaried job and toward the uncertain, exhilarating horizon of independence.

Background & daily life

A day in their life

Martin wakes up at 6:30 AM, immediately checking emails and news feeds before heading to the gym for a quick run. He arrives at the office by 8:45 AM, spending the morning triaging support tickets and attending stand-up meetings. Lunch is usually a quick sandwich eaten at his desk while scrolling through GitHub updates. Afternoon meetings drag on, leaving him feeling mentally fatigued by the time he clocks out at 5:15 PM. Instead of going straight home, he stops at a grocery store to buy ingredients for dinner. By 7:30 PM, he is back in his home office, putting on noise-canceling headphones to block out household noise. From 8:00 PM to midnight, he codes furiously, debugging a Stripe webhook issue and updating his admin dashboard. He eats a cold dinner while working, only taking short breaks to stretch or check his phone. He finally winds down around 12:30 AM, reviewing his to-do list for the next day before falling asleep.

Lifestyle

Martin lives in a modest, slightly cluttered two-bedroom apartment in Logan Square, sharing the space with a graphic designer roommate who often brings over friends on weekends. His evenings are a rigid mix of decompression and intense focus; he alternates between playing competitive basketball at a local rec center and tinkering with Raspberry Pis or home server setups in his spare room. Money is tight, so he cooks elaborate meals from scratch to save cash and tracks every subscription expense. Socially, he prefers small gatherings of close friends over large parties, often bonding over shared hobbies like gaming marathons or discussing the latest tech trends. He prioritizes health, running three times a week, though his sleep schedule often suffers due to late-night coding sessions.

Work life

As an IT support analyst for a mid-sized firm, Martin spends his days troubleshooting hardware issues, resetting passwords, and guiding non-technical staff through software glitches. The environment is high-volume and often repetitive, requiring patience and clear communication rather than complex engineering. He uses ticketing systems like Jira and ServiceNow daily, navigating a sea of low-priority tickets while managing occasional critical outages. The pressure comes from strict SLA metrics and the need to remain approachable despite the frustration of users who lack basic digital literacy. While the work provides stability, it leaves him mentally drained by 5 PM, making his transition to personal development projects a deliberate act of reclaiming his intellectual energy.

Relationships

Martin maintains a close bond with his younger sister, who works in marketing and occasionally gives him feedback on his app's landing page. He relies heavily on his immediate circle of three college friends for moral support, often venting about code bugs over beers. His relationship with his manager is professional but distant; they respect his technical competence but don't engage with his entrepreneurial ambitions. Online, he feels most connected to anonymous communities on Discord and Reddit where he can ask specific technical questions without judgment, finding solace in the shared struggle of self-taught developers.

How they decide

Martin is a cautious researcher who relies heavily on community validation and empirical evidence before committing resources. He rarely makes impulsive purchases, preferring to spend weeks reading documentation, watching video reviews, and comparing feature sets against free alternatives. He trusts peer recommendations from trusted forums more than traditional advertising and is deeply skeptical of anything that promises 'instant success' without effort. His decisions are driven by a need for long-term value and reliability, often leading to delayed action until he feels absolutely certain the tool will solve his specific problem without introducing new risks.

How they sound

Martin speaks with a measured, Midwestern cadence, avoiding overly technical jargon unless necessary. He tends to be precise and concise, often pausing to formulate his thoughts carefully. He avoids sounding arrogant or dismissive, preferring phrases like 'I'm still learning' or 'It seems like...' when discussing complex topics. He uses colloquialisms sparingly, mostly related to tech culture ('that's a hack', 'spaghetti code'). He never rushes his sentences and often admits uncertainty openly, valuing clarity over speed in conversation.

Personality traits

  • Methodical
  • Cautiously optimistic
  • Resourceful
  • Detail-oriented
  • Slightly anxious about time management
  • Pragmatic
  • Introverted but socially capable
  • Persistent
  • Budget-conscious
  • Self-reliant

Goals

  • Successfully launch a revenue-generating micro-SaaS product within the next six months
  • Master advanced backend architecture patterns beyond basic Flask tutorials
  • Build a network of peer developers outside of his current corporate circle
  • Achieve financial independence through side income streams
  • Complete a full-stack certification to validate his self-taught skills
  • Maintain a consistent workout routine without sacrificing coding progress

Problems & frictions

  • Difficulty balancing full-time job demands with late-night side project momentum
  • Uncertainty about which deployment infrastructure offers the best cost-to-performance ratio
  • Feeling isolated in the development process without a dedicated team or mentor
  • Fear of making costly mistakes in payment gateway integration or data security
  • Struggling to find time for marketing and user acquisition strategies
  • Overwhelmed by the sheer volume of conflicting information in online tutorials

Values

  • self-improvement
  • frugality
  • persistence
  • practical skills
  • autonomy
  • efficiency

Interests

  • coding tutorials
  • gaming
  • basketball
  • maker projects
  • home automation
  • productivity optimization

Media habits

  • YouTube deep-dive technical channels
  • r/learnpython and r/sideproject subreddits
  • Twitter/X tech circles
  • Podcasts during commutes
  • GitHub trending repos
  • Local sports team news

Questions & answers

Martin Heidenreich’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://pythonstarter.co/ (PythonStarter) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Honestly, the "Start today, launch tomorrow" headline is a bit much, but the idea of not rebuilding authentication and Stripe integration from scratch is really appealing. I've been wrestling with that for weeks. What's unclear is exactly how customizable the database structure is – I'm using Postgres now, but I don't want to be locked into their exact schema. The testimonial is nice, but I'd feel better seeing a live demo or more examples of the admin dashboard functionality. If there was a clear way to see how to integrate my specific business logic without a ton of refactoring, I'd definitely consider signing up, especially with that $100 off offer.
    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.