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

Ernest Schuster

Ernest Schuster

Independent consultant working across short-term client builds

Full-depth AI personas

Why this persona fits the audience

He takes on Next.js projects for agencies and small businesses in Manchester, usually as the only developer touching routing and page structure. He keeps route inventories in spreadsheets and GitHub notes, and he has never paid for a dedicated typed-navigation tool.

  • Age: 36
  • Location: Manchester, UK
  • Occupation: Freelance Frontend Consultant
  • Income: £58k average annual contracting income
  • Education: BSc Web Development
  • Company size: Self-employed (solopreneur)
  • Years in role: 8
“You can build anything you need if you're organised enough, but keeping track of the little details is where the real work is.”

Ernest Schuster, 36, is a freelance frontend consultant based in Manchester, UK, with a BSc in Web Development. For the past eight years, he has carved out a niche working with agencies and small businesses, primarily on Next.js projects. His reputation is built on his ability to take ownership of complex frontend architecture, particularly routing and page structure, often being the sole developer responsible for these critical areas. This hands-on approach means he meticulously manages route inventories using spreadsheets and GitHub notes, a system he developed himself out of necessity rather than adopting a dedicated tool. His income averages around £58k annually from contracting, allowing for a comfortable but not extravagant lifestyle. He lives alone in a rented flat, where he maintains a dedicated space for his music production hobby and a prized espresso machine. Ernest is driven by self-reliance and a commitment to practical, efficient delivery. He values clear communication and technical autonomy, preferring to solve problems with well-reasoned, robust solutions. He’s recently been focused on a significant e-commerce site rebuild for a Manchester-based fashion retailer, a project that has highlighted the growing complexity of managing application routes manually. This has led him to reflect on the time spent on administrative tasks versus core development, though he remains hesitant to invest in paid tools unless the benefit is overwhelmingly clear and immediately apparent. His conscientiousness (0.76) is evident in his methodical approach to coding and project management, while his agreeableness (0.61) facilitates smooth client interactions. He’s not one to chase trends, preferring stability and proven methodologies, but he keeps an eye on promising open-source projects that align with his practical needs.

Background & daily life

A day in their life

Ernest's typical weekday begins around 7:30 AM with a carefully prepared espresso and a quick scan of tech news. He's usually at his desk by 8:30 AM, diving into client work. Mornings are often dedicated to core development tasks, like implementing new page structures or refining routing logic for his current Next.js project. After a simple lunch, he might spend an hour on administrative tasks, client communication, or reviewing pull requests if collaborating with a client's internal team. The afternoon is typically focused on coding, debugging, or researching solutions to specific implementation challenges. He aims to wrap up by 6:00 PM, though deadlines can sometimes extend this. Evenings are for unwinding, perhaps with some music production or a football match on TV.

Lifestyle

Ernest lives a fairly routine-driven life, balancing his demanding freelance work with personal pursuits. His rented flat in South Manchester is functional, with a dedicated corner for his music production setup and a well-maintained espresso machine. He’s not extravagant with his income, preferring to save a portion and invest in quality tools and experiences. Weekends often involve a trip to the local football ground or experimenting with new coffee beans. He socialises occasionally with a small group of friends, often discussing tech or music, but values his downtime for focused work or creative projects.

Work life

As a freelance frontend consultant, Ernest thrives on the variety of short-term projects, primarily for agencies and small businesses in the Manchester area. He typically works alone on client builds, taking ownership of critical areas like routing and page structure for Next.js applications. His current project involves a complete rebuild of an e-commerce site for a local fashion retailer. He manages his project's route inventory using a combination of meticulously maintained spreadsheets and GitHub markdown files, a system that has served him well but occasionally feels cumbersome as projects scale. The pressure is constant to deliver high-quality, functional code efficiently within tight deadlines.

Relationships

Ernest maintains a close but geographically dispersed relationship with his parents in the North East. His core social circle consists of a few long-term friends from university, a mix of developers and creatives, with whom he shares technical insights and life updates. He has a good working relationship with the agency owners he contracts for, built on reliability and clear communication.

How they decide

Ernest is a pragmatic decision-maker. He researches thoroughly when faced with a new technical challenge or tool, weighing the practical benefits against the time investment required. He values solutions that integrate seamlessly into his existing workflow and are cost-effective. He's not easily swayed by hype and prefers proven, stable technologies or well-supported open-source options. Peer recommendations from trusted developer communities hold some weight, but ultimately, he relies on his own assessment of a tool's utility and maintainability.

How they sound

Speaks with a clear, measured cadence, typical of Northern English speech but without strong regionalisms. Tends to be direct and avoids jargon unless discussing technical specifics. Uses phrases like 'fairly straightforward', 'essentially', 'the main thing is', and 'it boils down to'. He's not overly effusive but conveys competence and a grounded perspective. Avoids hyperbole and focuses on practical outcomes.

Personality traits

  • Methodical
  • Independent
  • Pragmatic
  • Resourceful
  • Detail-oriented
  • Calm under pressure
  • Self-disciplined
  • Slightly reserved

Goals

  • Achieve a consistent pipeline of interesting, challenging client projects.
  • Build a small, curated library of reusable frontend components.
  • Continue to refine his music production skills.
  • Maintain financial stability and independence.
  • Explore contributing more actively to open-source projects he uses.

Problems & frictions

  • The manual effort required to track and update route configurations across projects.
  • Occasional inconsistencies in routing logic due to manual management.
  • Balancing multiple client demands and tight deadlines.
  • The overhead of setting up and maintaining project scaffolding for each new client.
  • Finding time for personal projects amidst client work.

Values

  • self-reliance
  • practical delivery
  • clear communication
  • time efficiency
  • technical autonomy

Interests

  • music production
  • football
  • open-source projects
  • espresso
  • local craft beer scene

Media habits

  • Follows key tech blogs (Smashing Magazine, CSS-Tricks)
  • Listens to tech podcasts during commutes
  • Active on GitHub and Stack Overflow
  • Reads industry newsletters
  • Watches YouTube tutorials for specific libraries

Questions & answers

Ernest Schuster’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 TinyLaunch: Type-safe routing, zero guesswork, seamless navigation.. Generate typed URL helpers from the pages your framework already routes. Discover routes… 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 headache for me is keeping track of all the routes across different projects. I'm currently using spreadsheets and GitHub notes, which takes up a fair bit of time, especially when I'm juggling multiple clients. It's not a huge financial cost, but I reckon it eats into my productive coding time by a few hours each week, maybe 2-3 hours per project. I've tried to standardise my own process, but it's still a manual chore. This 'type-safe routing' sounds interesting, but I'm not sure how much setup it would involve or if it's overkill for my typical projects.
    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.