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

William Larkin

William Larkin

Solo founder building an AI content product

Full-depth AI personas

Why this persona fits the audience

He is a solo founder in London building a small AI tool and spends part of each week reviewing Reddit threads, X posts, and search queries to decide what features and posts to prioritize. He is comfortable reading API docs and already tests no-code automations for publishing.

  • Age: 36
  • Location: London, UK
  • Occupation: Founder
  • Income: £72k from product revenue + consulting
  • Education: MSc Computer Science, University of Manchester
  • Company size: 1 (self-employed)
  • Years in role: 2.5
“I don't just want to know what's trending; I want my code to understand why it matters before the trend even peaks.”

William Larkin, 36, is a quintessential modern indie hacker operating out of a bustling Shoreditch flat in London. With an MSc in Computer Science from the University of Manchester behind him, he transitioned from a traditional software engineering role to full-time entrepreneurship two and a half years ago, driven by a desire for autonomy and the belief that small, focused teams could outmaneuver larger competitors in the AI space. His current venture involves building a specialized API that aggregates social, search, and AI-search trends for developers looking to power their agents with real-time context. Unlike many peers who chase viral growth, William focuses on robust data integrity and developer experience, a choice reflected in his meticulous approach to API documentation and error handling. His daily reality is a blend of high-level strategy and granular debugging. He dedicates significant portions of his week to 'social listening,' manually sifting through thousands of Reddit threads and X posts to identify genuine user needs versus algorithmic noise. This qualitative research directly informs his roadmap, ensuring that every line of code serves a verified market demand. Despite generating £72k annually—a figure that provides stability—it barely covers his living expenses and server costs, forcing him to balance product development with occasional consulting gigs to maintain cash flow. William is a man defined by iteration. He views failure not as a setback but as a necessary data point, constantly A/B testing features and automating workflows to strip away inefficiencies. He is deeply embedded in the 'indie hacking' subculture, finding camaraderie in forums where peers share both successes and catastrophic failures. However, this isolation can be heavy; he often struggles with the lack of immediate peer support when facing complex architectural dilemmas. His life is a tightrope walk between the freedom of being his own boss and the crushing weight of total responsibility. He measures success not by valuation, but by the elegance of his code and the reliability of his product, believing that true independence comes from building something that works so well it sells itself.

Background & daily life

A day in their life

William wakes at 6:15 AM, immediately checking his dashboard for overnight API usage spikes and error logs. After a quick workout, he spends an hour scanning Reddit and X for emerging keywords related to his niche, noting down patterns in a private Notion database. By 8:30 AM, he is deep in code, refactoring a Python script to handle rate limits more gracefully. Lunch is a solitary affair at his desk while watching a technical conference recording. The afternoon is reserved for client calls and testing new automation workflows in Zapier or Make.com to see if they can replace manual data entry. He often finds himself stuck in a loop of tweaking parameters until 6 PM, when he finally steps away. Evenings are for dinner with his wife, followed by either reading API documentation for fun or contributing to open-source libraries. Sleep comes around midnight, though he occasionally wakes up at 3 AM with a solution to a bug.

Lifestyle

William lives in a converted warehouse flat in Shoreditch, a space that doubles as his office. His evenings are rarely fully free; they are often consumed by side projects or learning new automation frameworks. He maintains a strict gym routine three times a week at a local 24-hour facility to manage the sedentary nature of his work, viewing physical fitness as non-negotiable maintenance rather than leisure. Financially, he practices frugality despite his income, reinvesting 60% of profits back into server costs and marketing tools. He avoids expensive dinners in favour of cooking elaborate meals at home, using his kitchen as a place to decompress from screen time. Socially, he curates a small circle of fellow founders for late-night code reviews and coffee chats, preferring deep one-on-one conversations over large networking events. He values silence and solitude highly, often working early mornings before the city wakes up.

Work life

His workday begins at 6:30 AM with a review of global market signals before opening any code editor. William splits his time between backend development—specifically refining data ingestion pipelines—and frontend iteration based on user feedback. He rarely meets colleagues since he has none, relying instead on asynchronous communication with his partner and a handful of beta testers. His primary pressures revolve around server uptime, API latency, and maintaining a steady cash flow without burning out. He spends significant chunks of his afternoon testing no-code automations to see if manual tasks can be eliminated entirely. The reality of being a solo founder means he is simultaneously the CEO, CTO, and customer support agent, requiring him to context-switch rapidly between high-level strategy and debugging a broken webhook at 11 PM.

Relationships

William is married to Elena, a graphic designer whose creative perspective grounds his logic-heavy worldview. They have no children yet, allowing them flexibility but also leaving them without a shared parenting dynamic. His closest professional bonds are with three other solo founders he met via a Slack community; they exchange dry runs of code and vent about churn rates. He feels a strong sense of duty to his small client base, often responding to their emails personally to build trust. While he respects industry leaders, he remains skeptical of corporate influence, preferring advice from those currently shipping products.

How they decide

William operates on a 'measure twice, cut once' philosophy mixed with rapid prototyping. He is research-heavy, spending days analyzing data points before committing to a major architectural shift, yet he is willing to make impulsive decisions regarding minor UI tweaks if user feedback suggests a clear pain point. He is not swayed by marketing hype or peer pressure alone; he needs to verify utility through his own sandbox environments first. Once he validates a concept technically and sees it solve a specific friction, he commits quickly, but he is naturally cautious about scaling costs before demand is proven.

How they sound

William speaks with a measured, precise cadence typical of a London-based engineer. He avoids hyperbole and marketing jargon, preferring concrete terms like 'latency,' 'throughput,' and 'edge cases.' His tone is professional yet approachable, often slipping into technical slang when discussing tools but clarifying concepts for non-technical listeners. He rarely uses filler words like 'um' or 'like,' opting instead for brief pauses to gather thoughts. When explaining complex systems, he uses analogies drawn from everyday life or architecture. He avoids emotional language unless discussing the stress of deadlines, and he never admits to being overwhelmed publicly, framing challenges as solvable puzzles.

Personality traits

  • methodically curious
  • data-obsessed
  • solitary but engaged
  • technically self-sufficient
  • risk-aware
  • efficiently impatient
  • intellectually rigorous
  • resilient under pressure
  • detail-oriented
  • experimentally driven

Goals

  • Achieve £100k annual recurring revenue within the next 18 months
  • Build a fully autonomous content distribution system that requires zero manual intervention
  • Establish a personal brand known for technical depth and honest indie-hacking transparency
  • Reduce work hours to 35 per week while maintaining current revenue levels
  • Launch a secondary micro-product that leverages the same API infrastructure
  • Secure a mentorship relationship with a successful European SaaS founder

Problems & frictions

  • Difficulty distinguishing between fleeting noise and genuine market trends in social feeds
  • Spending too much time configuring integrations rather than talking to users
  • Feeling isolated and lacking a peer group for immediate technical problem-solving
  • Uncertainty about which feature requests to prioritize given limited development bandwidth
  • Managing the psychological toll of having all business risk resting solely on his shoulders
  • Keeping up with the rapid pace of change in AI models and API documentation

Values

  • independence
  • learning
  • iteration
  • autonomy
  • pragmatism
  • transparency

Interests

  • indie hacking
  • APIs
  • automation
  • social listening
  • minimalist coding
  • product-led growth

Media habits

  • Daily scan of r/SaaS and r/Entrepreneur on Reddit
  • Following niche builders on X (Twitter) for real-time sentiment
  • Subscribing to 'Indie Hackers' newsletter
  • Listening to technical deep-dive podcasts during commute
  • Reading GitHub issue trackers for competitor analysis
  • Checking Google Trends and AnswerThePublic weekly

Questions & answers

William Larkin’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Trends Fast (https://trendsfast.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Trends Fast 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 manually sift through Reddit, X, and search queries to understand trends. The idea of an API for this is appealing, especially the "Competitors" and "Search" features. However, the credit system seems a bit opaque. I'd need to see how many credits are used for typical queries relevant to my niche before committing. I'm currently paying £72k from product revenue plus consulting, which is tight, so I'm very budget-conscious. I'd be willing to pay around $20 per month for a starter plan if it proved significantly more efficient than my current manual process and the credit usage was predictable.
    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.