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

Ricky Kemmer

Ricky Kemmer

indie hacker with a custom-built stack

Full-depth AI personas

Why this persona fits the audience

He ships a productivity extension from Manchester and has enough JavaScript to wire payments himself, but the current setup is still a custom authentication flow plus webhooks. He sells yearly access to a few dozen users and keeps costs under close watch.

  • Age: 39
  • Location: Manchester, UK
  • Occupation: Independent developer
  • Income: £58k
  • Education: Self-taught
  • Company size: Sole trader (1)
  • Years in role: 6
“I built this because I couldn't find anything that didn't try to take my data or charge me for features I'd never use.”

Ricky Kemmer is a thirty-nine-year-old independent developer based in Manchester, UK, who carved out a niche in the crowded productivity software space by building a browser extension that solves a specific workflow bottleneck for small teams. Unlike many peers who rely on pre-packaged SaaS platforms, Ricky operates with a fiercely customized stack, writing his own JavaScript middleware to handle authentication and payment processing via webhooks. This approach stems from a deep-seated need for control and a distrust of third-party black boxes that might change terms or prices overnight. Since launching his product six years ago, he has grown a loyal base of a few dozen users, primarily in the US, UK, and EU, generating steady but modest income that allows him to maintain a comfortable middle-class lifestyle without the stress of venture capital pressure. His journey began after being laid off from a mid-sized agency, where he realized he preferred the autonomy of building his own tools over managing client expectations. He is entirely self-taught, having spent thousands of hours consuming documentation, participating in GitHub forums, and deconstructing open-source projects. This background has made him exceptionally proficient in JavaScript but also deeply cynical about the industry's tendency to over-engineer solutions. He currently earns approximately £58,000 annually, a figure he monitors closely against his operating costs, which he keeps artificially low through careful resource management and a minimalist office setup. Ricky's recent focus has been on stabilizing his fragile custom authentication flow, which, while functional, requires constant vigilance to prevent race conditions during checkout. He is currently weighing the pros and cons of migrating to a more robust payment provider versus continuing to patch his existing system. Despite the technical challenges, he remains committed to the indie path, valuing the direct connection with his users and the ability to pivot quickly. For Ricky, success is not measured in millions of dollars, but in the elegance of his code, the reliability of his service, and the freedom to wake up each day knowing he is the architect of his own reality.

Background & daily life

A day in their life

Ricky wakes up at 6:30 AM, avoiding the noise of the morning commute by working from home. After a quick coffee and checking the overnight server logs for errors, he spends the first two hours of his day writing code, tackling the most cognitively demanding tasks like refactoring the payment gateway. Lunch is a solitary affair, often eaten while reading technical documentation or listening to a podcast about software engineering history. The afternoon is reserved for customer support emails, which he treats as critical feedback loops rather than distractions. By 4 PM, he shifts to administrative duties, updating his financial spreadsheets and reviewing subscription metrics. Evening is strictly for personal projects or relaxing with retro gaming, ensuring he doesn't burn out. He goes to bed around 11 PM, ready to repeat the cycle if a production alert triggers.

Lifestyle

Ricky lives in a quiet corner of Didsbury where he can hear the rain on the slate roof without distraction. His evenings are rarely social; they are spent calibrating his home lab server or tinkering with a restored Commodore 64. He is frugal by necessity and design, meticulously tracking every penny in complex spreadsheets that rival enterprise accounting software. Health-wise, he is sedentary but aware of it, often compensating with long walks along the Manchester canal. He values silence and order, finding peace in the rhythm of code execution rather than human interaction. Money is not just currency to him; it is a measure of efficiency and validation for his independence.

Work life

His workspace is a dedicated room in his home, dominated by three monitors displaying raw logs and terminal windows. As a sole proprietor, there are no colleagues to coordinate with, only a constant dialogue with his own codebase. He manages everything from customer support tickets to deployment pipelines alone. The pressure is self-imposed but intense: one bug could cost a client's trust, and a billing error could eat into his thin margins. His days are spent deep in the weeds of JavaScript, debugging custom auth flows and optimizing database queries. He works irregular hours, often coding late into the night when the city is quiet, driven by the need to keep his system running smoothly without external dependencies.

Relationships

Ricky is married to Sarah, an accountant who manages their household finances with a precision he admires but rarely matches. They have no children yet, preferring the freedom of their current lifestyle. He maintains a small circle of three other indie developers he meets monthly at a local pub, mostly to discuss architecture and share war stories. He has little patience for corporate networking events, finding them superficial. His primary influence comes from online communities where technical competence is valued over status, and he respects those who build things that actually work.

How they decide

Cautious and data-driven. Ricky rarely makes impulsive decisions regarding technology or finance. He prefers to run small experiments, analyze the resulting metrics, and iterate before committing resources. He is skeptical of marketing claims and relies heavily on peer reviews, open-source documentation, and his own testing environments. If a solution isn't transparent about its underlying mechanics or pricing model, he will likely reject it immediately, regardless of how feature-rich it appears.

How they sound

Direct, precise, and devoid of fluff. He speaks in short, declarative sentences, often using technical jargon casually but accurately. He avoids hyperbole, superlatives, or emotional language, preferring factual descriptions of cause and effect. There is a slight Mancunian cadence to his speech, but it is understated. He tends to pause before answering questions that require speculation, preferring to say, 'I don't know the specifics, but the logs suggest...' rather than guessing. He rarely uses buzzwords, viewing them as indicators of low substance.

Personality traits

  • meticulous
  • resourceful
  • introverted
  • pragmatic
  • self-reliant
  • anxious about uptime
  • stoic
  • analytical
  • independent
  • cynical about hype

Goals

  • Stabilize revenue to cover a six-month emergency fund without dipping into personal savings
  • Refactor the legacy authentication module to reduce maintenance overhead by 40%
  • Achieve a consistent £7k monthly recurring revenue to justify expanding the product line
  • Build a fully automated CI/CD pipeline that requires zero manual intervention
  • Reduce cognitive load by documenting all internal processes for potential future outsourcing

Problems & frictions

  • The custom payment webhook logic occasionally desynchronizes during high traffic spikes
  • Difficulty isolating bugs in the browser extension environment across different Chrome versions
  • Lack of time to market new features due to spending 60% of the week on infrastructure maintenance
  • Feeling isolated as the sole decision-maker with no peer group to validate technical choices
  • Managing customer churn while maintaining a 'fair pricing' philosophy for small teams
  • Balancing the mental energy required for creative problem-solving against repetitive sysadmin tasks

Values

  • control
  • frugality
  • problem solving
  • resilience
  • autonomy
  • transparency

Interests

  • indie software
  • home labs
  • retro games
  • spreadsheets
  • mechanical keyboards
  • UK industrial history

Media habits

  • Indie Hackers podcast
  • r/programming and r/webdev subreddits
  • NPR and BBC Radio 4
  • GitHub issue trackers
  • Local Manchester tech meetups
  • Personal RSS feeds of dev blogs

Questions & answers

Ricky Kemmer’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at ExtensionPay (https://extensionpay.com): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    ExtensionPay's pricing is a 5% transaction fee with no monthly costs. For a few dozen users, this could be acceptable if it's less than what I'm spending patching my current system. I'd need to see how this compares to my current costs, which are minimal. A no-brainer would be if the total cost was less than £20 per month, including transaction fees. If it climbed to over £100 per month, I'd stop considering it. I'd expect a stable, reliable system that requires minimal maintenance and handles all payment processing, including taxes and currency conversions.
    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.