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

Wayne Torp

Wayne Torp

agency owner and technical director

Full-depth AI personas

Why this persona fits the audience

Founder-operator of a 4-person Manchester web studio serving small SaaS clients. He prefers to assemble interfaces by hand from in-house snippets, keeps subscription spending low, and only standardizes patterns when a client project needs it.

  • Age: 45
  • Location: Manchester, UK
  • Occupation: Agency owner and technical director
  • Income: £78k
  • Education: HND in Multimedia Computing
  • Company size: 4 employees (including himself)
  • Years in role: 12
“If I have to write the same CSS three times, I've already failed; efficiency isn't about speed, it's about never doing the same thing twice.”

Wayne Torp is a fourth-generation Mancunian who carved out a niche in the web development sector by rejecting the industry's shift toward bloated, all-in-one platforms. With an HND in Multimedia Computing from Manchester Metropolitan University, he launched his agency twelve years ago after growing tired of the corporate ladder's inefficiencies. Today, he operates a lean, four-person studio in a converted warehouse in Chorlton, specializing in high-fidelity interfaces for small SaaS startups. Unlike many contemporaries who chase venture-backed scale, Wayne prioritizes margin discipline and total control over the codebase. He is known for assembling interfaces by hand from a meticulously curated library of in-house snippets, refusing to standardize patterns until a specific client project demands a unified design system. This approach allows him to maintain razor-thin margins while delivering bespoke quality that generic templates cannot match. Recently, he made the calculated decision to reject a lucrative offer from a large enterprise client because their required stack would force him to abandon his preferred lightweight tools. He views his income of £78k not as wealth, but as a buffer to sustain his independence. His philosophy is rooted in the belief that true craftsmanship lies in the details others ignore, a stance that keeps his team small but highly skilled. While he is open to technological evolution, he remains deeply skeptical of AI tools that promise to replace human judgment, preferring to integrate them only when they demonstrably reduce repetitive drudgery. For Wayne, the studio is not just a business; it is a testament to the viability of manual precision in an automated world.

Background & daily life

A day in their life

Wayne starts his day at 6:00 AM with a 5k run along the river Irwell, using the time to mentally clear the clutter of the previous day's emails. By 7:30 AM, he is back home, showered and brewing a strong coffee before checking the studio Slack channel for overnight alerts from US clients. At 8:45 AM, he arrives at the warehouse, greets his team, and immediately dives into a complex animation issue for a SaaS dashboard, refusing to delegate the final polish. Lunch is a quick sandwich eaten at his desk while reviewing a competitor's site for design trends. Afternoon hours are spent in client calls, often negotiating scope creep, followed by a session of refactoring legacy code to improve load times. He leaves the office by 6:00 PM sharp to ensure dinner with his family, occasionally staying late only if a deployment fails, preferring to solve problems alone rather than disturb his team.

Lifestyle

Wayne lives in a semi-detached Victorian house in Didsbury, which he shares with his wife Sarah and their ten-year-old son. His routine is rigid; he wakes at 6:00 AM for a run before the city traffic hits, treating physical fitness as non-negotiable maintenance for mental sharpness. Money is managed with military precision; they own their home outright but keep cash reserves high, avoiding unnecessary subscriptions or lifestyle inflation. Evenings are reserved for family dinners or watching Manchester United highlights, rarely involving work unless a critical bug surfaces. He values quiet weekends, often found tinkering with a mechanical keyboard or reading about economic history, preferring analog relaxation over digital scrolling.

Work life

Running a four-person studio means Wayne wears every hat, though his primary focus remains the technical architecture. He spends roughly 40% of his week coding directly, refusing to delegate core interface logic to juniors who lack his specific CSS fluency. The office is a converted warehouse space where the air hums with server noise; he enforces a strict 'no SaaS sprawl' policy, auditing monthly bills personally. Workdays are fragmented between deep-coding sessions for client deliverables and frantic client calls that demand immediate visual changes. He prides himself on a lean operation where no single tool costs more than £20 a month unless it generates direct revenue. The pressure comes not from volume, but from the need to maintain high margins while delivering bespoke quality without burning out the small team.

Relationships

Wayne's social circle is tightly knit within Manchester's tech and football communities. He has a weekly lunch with three other agency owners to swap war stories about difficult clients and pricing strategies, relying on this peer group for validation rather than formal networking events. His wife manages the household finances, acting as a check against his tendency to reinvest too heavily in equipment. He is distant from extended family, viewing them as a distraction from his core mission, but maintains a warm, supportive relationship with his son, prioritizing presence over material gifts.

How they decide

Wayne is a cautious, evidence-based decision-maker who relies heavily on first-hand testing and peer recommendations from trusted industry circles. He rejects impulse buys, preferring to prototype a solution manually before considering any third-party tool. His process involves a rigorous cost-benefit analysis where the 'time-to-value' must be immediate; if a tool requires weeks of setup, he discards it. He is skeptical of marketing hype and will not commit to a recurring expense unless he can see a direct path to margin improvement or time savings within the first two weeks of use.

How they sound

Wayne speaks with a flat, Mancunian cadence, direct and devoid of corporate jargon. He uses precise technical terminology but avoids buzzwords like 'synergy' or 'disruption.' His sentences are short and functional, often ending abruptly once the point is made. He frequently interrupts to correct factual inaccuracies and values brevity over politeness. He avoids expressing uncertainty publicly, framing doubts as questions to the team rather than weaknesses. When discussing money, his tone becomes noticeably sharper, focusing strictly on numbers and outcomes rather than emotional appeals.

Personality traits

  • meticulous about code structure
  • frugal with software budgets
  • direct communicator
  • protective of team autonomy
  • skeptical of 'magic' tools
  • pragmatic problem solver
  • loyal to local network
  • resistant to bloatware
  • hands-on coder
  • calm under deadline pressure

Goals

  • Reduce operational overhead by another 15% through better internal tooling
  • Establish a proprietary component library that can be reused across 80% of projects
  • Secure a long-term retainer contract with a US-based fintech startup
  • Mentor a junior developer into taking over full-stack ownership of a mid-tier account
  • Achieve a fully remote-first hybrid model without losing control over delivery quality
  • Save enough capital to buy a second property as an investment asset

Problems & frictions

  • Time scarcity prevents him from updating his personal code snippets repository
  • Difficulty finding developers who understand the balance between speed and custom CSS
  • Client expectations for 'enterprise-grade' motion graphics vs. budget constraints
  • The administrative burden of managing four distinct tax regimes for international clients
  • Resistance from team members to adopt new workflows that slow down immediate output
  • Keeping up with rapidly changing AI coding assistants without committing to expensive platforms

Values

  • control
  • margin discipline
  • practicality
  • self-reliance
  • craftsmanship

Interests

  • client websites
  • CSS
  • small agency operations
  • mechanical keyboards
  • football

Media habits

  • Twitter/X for dev news
  • Local Manchester business forums
  • Reddit r/webdev
  • Tech podcasts during commute
  • Physical books on design theory

Questions & answers

Wayne Torp’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on Tiny Startups: Collection of the most essential UI the product for web apps. Copy and paste them, or use them with your coding agent via the skill. 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.

    The biggest problem is consistency across client projects. We build most things by hand, which means variations creep in. If this 'Maker launch' tool genuinely offers essential UI snippets that are robust and easy to integrate without needing a full design system upfront, it could save us hours per project on repetitive foundational elements. Right now, that's easily 5-10 hours per small project, which adds up. We've tried establishing internal component libraries, but they become outdated or too specific quickly. I'd need to see how these snippets actually perform and integrate before committing.
    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.