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

Eduardo Lesch

Eduardo Lesch

Small agency owner

Full-depth AI personas

Why this persona fits the audience

Runs a four-person digital studio that delivers brochure sites and one-off campaign pages for local businesses. He already has a routine built around cPanel, FTP, staging checklists and shared launch notes, and spends much of his week coordinating rather than writing code.

  • Age: 49
  • Location: London, UK
  • Occupation: Agency owner
  • Income: £75,000
  • Education: BA in Media Studies
  • Company size: 4 full-time employees
  • Years in role: 12
“In this business, if you can't predict the outcome, you haven't done your homework yet.”

Eduardo Lesch is a forty-nine-year-old agency owner based in South London, navigating the complex intersection of creative services and pragmatic business management. Born in Manchester and educated in Media Studies at a mid-tier London university, Eduardo entered the digital sector just as the web was transitioning from static HTML to dynamic platforms. Over the last twelve years, he has grown a modest but profitable studio from a one-man operation into a four-person team specialising in brochure sites and campaign landing pages for local enterprises. Unlike many tech founders driven by rapid scaling, Eduardo prioritises stability and profitability, viewing his agency as a steady vessel rather than a rocket ship. His working life is characterised by a deep-seated need for order. He has spent years refining a rigid workflow involving cPanel, FTP transfers, and exhaustive staging checklists. This system, while effective, consumes a significant portion of his week, leaving little room for actual development. Recently, he made the difficult decision to hire a junior developer to handle basic maintenance, aiming to free up his own time for client acquisition, though the transition has introduced new layers of coordination overhead. Eduardo is financially secure, earning approximately £75k annually, but remains acutely aware of the fragility of small business economics. He treats money with caution, preferring to keep cash reserves high rather than taking risks on speculative investments. Outside of work, Eduardo finds solace in the predictable rhythms of sailing. He owns a small keelboat and dedicates his weekends to the water, seeking the quiet focus that contrasts sharply with the chaotic demands of client emails. He is also an avid consumer of financial media, believing that understanding macroeconomic trends helps him better advise his clients. Despite his success, he feels a lingering tension between his desire for efficiency and the reality of managing human error in a fast-paced digital environment. He is not looking for a magic bullet, but rather a reliable tool that integrates seamlessly into his existing, highly structured ecosystem without introducing uncertainty.

Background & daily life

A day in their life

Eduardo wakes at 6:30 AM, avoiding the immediate temptation of email. He spends the first hour on the treadmill and listening to a finance podcast, mentally preparing for the day's logistical challenges. By 8:00 AM, he is at his desk in the London studio, checking the overnight server logs and reviewing the team's progress on the current batch of brochure sites. A quick stand-up meeting at 9:30 AM clarifies priorities, focusing on the urgent delivery for a local retail chain. Mid-morning is spent debugging a staging environment issue, meticulously cross-referencing his FTP logs against the client's requirements. Lunch is a solitary affair, often a packed sandwich eaten while reading industry news. Afternoons involve client calls, where he navigates scope creep with diplomatic firmness, and ends with updating the master launch checklist. He leaves the office by 6:00 PM sharp, heading home to be present for dinner, leaving work anxieties at the door.

Lifestyle

Eduardo lives in a renovated Victorian terrace in Clapham, balancing the chaos of city life with a disciplined home routine. His weekends are split between managing family logistics and escaping to the Thames Estuary for weekend sailing sessions, where he values the silence and lack of digital distraction. He is health-conscious but not obsessive, preferring brisk walks and occasional gym sessions over intense training regimes. Financially, he is conservative; while he earns a comfortable income, he prioritises reinvesting in the business and maintaining a substantial emergency fund rather than flashy consumption. Socially, his circle is tight-knit, consisting mostly of fellow small business owners and old university friends, gathered primarily for dinners or pub visits where conversation turns to market trends and personal finances rather than gossip.

Work life

As the sole proprietor of a four-person studio, Eduardo’s day is less about coding and more about orchestration. He manages three designers and a junior developer, ensuring client deliverables meet strict deadlines without compromising quality. His workflow is rigid: morning meetings to align on priorities, followed by deep work reviewing staging environments via cPanel and FTP before lunch. Afternoons are dedicated to client calls, contract negotiations, and updating internal launch checklists. He despises ambiguity; every project requires a signed brief, a defined scope, and a documented handover protocol. The pressure comes from the constant need to balance cash flow with client expectations, often requiring him to act as both creative director and accountant. He relies heavily on spreadsheets and shared notes to maintain accountability across the team.

Relationships

Eduardo maintains a supportive but demanding relationship with his wife, Sarah, who handles the household finances and provides a grounding influence on his workaholic tendencies. His two children are the centre of his emotional world, though his schedule often limits their interaction to evenings and weekends. Professionally, he has a strong, albeit transactional, network of suppliers and printers, but few true peers; most other agency owners are either too small to relate to his scale or too large to care about his struggles. He looks up to a former mentor who ran a successful design firm until retirement, using that figure as a benchmark for longevity and ethical business practices.

How they decide

Eduardo is a methodical, risk-averse decision-maker who prefers data and proven processes over intuition. He rarely adopts a new tool or strategy without a thorough trial period, detailed documentation review, and peer validation. When considering a change, he weighs the long-term stability and cost implications heavily, often creating a 'kill criteria' list beforehand to ensure a solution doesn't introduce unforeseen complications. He is not swayed by marketing hype or aggressive sales tactics; instead, he responds to clear, concise evidence of reliability, uptime guarantees, and straightforward pricing models. His decisions are made slowly but executed with absolute certainty once reached.

How they sound

His speech is measured, articulate, and distinctly British, avoiding slang or hyperbole. He speaks with a cadence that suggests he is constantly editing his thoughts for clarity and precision. In conversation, he avoids vague terms like 'maybe' or 'soon', preferring specific dates and percentages. He rarely raises his voice, even under pressure, and tends to use phrases like 'let's establish the parameters' or 'the data suggests'. He is uncomfortable with emotional outbursts or overly casual banter in professional settings, keeping interactions polite but somewhat distant.

Personality traits

  • Methodical
  • Pragmatic
  • Detail-oriented
  • Diplomatic
  • Cautious
  • Structured
  • Reliable
  • Reserved
  • Efficiency-focused
  • Risk-averse

Goals

  • To stabilise the agency's revenue streams so they are no longer dependent on one-off campaigns.
  • To delegate operational tasks completely, allowing time for high-level strategic planning.
  • To achieve a specific net profit margin of 30% within the next fiscal year.
  • To mentor his junior developer into a senior role capable of running projects independently.
  • To acquire a larger commercial property for the office to reduce reliance on co-working spaces.
  • To complete a solo sailing circumnavigation of the British Isles within five years.

Problems & frictions

  • Frequent friction caused by inconsistent file naming conventions among junior staff leading to deployment errors.
  • The administrative burden of manually uploading and verifying hundreds of static files across multiple client domains.
  • Difficulty tracking version history when clients request last-minute changes after a site has gone live.
  • Limited bandwidth to onboard new tools due to fear of disrupting established, albeit manual, workflows.
  • Challenges in communicating technical constraints to non-technical local business owners who expect instant results.
  • Keeping up-to-date with security protocols for older legacy sites without spending excessive hours on maintenance.

Values

  • predictability
  • profitability
  • accountability
  • professionalism
  • stability

Interests

  • sailing
  • finance podcasts
  • photography
  • classic British cars
  • whisky tasting

Media habits

  • The Daily Telegraph (print)
  • Bloomberg Markets & Finance podcast
  • Local sailing club newsletter
  • Industry-specific Slack communities
  • Architectural Digest
  • Financial Times Weekend magazine

Questions & answers

Eduardo Lesch’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Static (https://static.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Static 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).

    Currently, we manage our site deployments manually, involving cPanel, FTP, and detailed checklists. This process is quite robust but very time-consuming, taking up a significant portion of my week. While Static.app's one-click hosting sounds appealing for its simplicity, I'm concerned about how it would integrate with our existing, highly structured workflow. The promise of speed and ease is attractive, but I'd need to see how it handles our specific staging and handover protocols without introducing new complexities or potential for error. I'm hesitant to adopt anything that might disrupt our established system. The pricing model isn't entirely clear for our typical usage, but based on the mention of $6/month, I'd consider paying up to $30 per month if it truly streamlined our process without adding risk.
    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.