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

Myron Upton

Myron Upton

Independent API consultant

Full-depth AI personas

Why this persona fits the audience

Runs a small API consulting practice from Edinburgh and configures gateway setups for two SME clients at a time. He keeps each client’s routes, auth rules, and deployment notes in separate spreadsheets and Git repos, switching between open-source gateways depending on the stack.

  • Age: 47
  • Location: Edinburgh, UK
  • Occupation: Independent API Consultant
  • Income: £90k/year
  • Education: BSc in Electronics and Computing
  • Company size: Self-employed
  • Years in role: 5
“The real satisfaction comes from building something robust and reliable that just works, day in and day out, without fuss.”

Myron Upton, 47, is an independent API consultant based in Edinburgh, UK, who carved out his niche after a decade working in various software engineering roles for established tech firms. His BSc in Electronics and Computing provided a solid foundation, but it was his growing fascination with the intricate dance of data exchange and service integration that led him to specialize in APIs. He established his consultancy five years ago, valuing the autonomy and direct client relationships it offered over the corporate ladder. Myron currently juggles two SME clients, meticulously configuring their API gateway setups. His approach is deeply pragmatic; he maintains detailed spreadsheets for each client's routes and authentication rules, and uses separate Git repositories for deployment notes and scripts. This hands-on, documentation-heavy method reflects his conscientious nature and his commitment to client trust. He’s adept at navigating the diverse landscape of open-source API gateways, selecting the most appropriate tool for each client's specific stack and budget constraints. While he enjoys the intellectual challenge, he's also keenly aware of the administrative burden this manual approach entails. Myron is financially responsible, earning a comfortable £90k annually, which allows him to maintain his lifestyle and save diligently, though he prioritizes experiences and continuous learning over ostentatious displays of wealth. He sees his work not just as a job, but as a craft, where attention to detail and a deep understanding of underlying principles are paramount. His decision to remain independent stems from a desire to control his work, his time, and his technical direction, a stark contrast to the often-bureaucratic environments he previously navigated. He views each client engagement as an opportunity to apply his expertise and build lasting, functional solutions, reinforcing his commitment to technical excellence and client satisfaction.

Background & daily life

A day in their life

Myron's typical weekday begins around 7:30 AM with a strong cup of tea and a review of his schedule. He dedicates the morning, usually until lunchtime, to focused work on his primary client – perhaps configuring a new set of API routes or refining authentication policies. After a light lunch, he might switch to his second client, tackling a different set of technical challenges, like optimizing a deployment script or investigating a performance bottleneck. He attends virtual tech meetups or browses technical forums in the early evening. He aims to wrap up work by 6 PM, leaving time for a home-cooked meal, a bit of reading, or preparing his next home brew. He prioritizes a clear separation between work and personal time.

Lifestyle

Myron lives in a comfortable 2-bedroom flat in Edinburgh's Stockbridge area, enjoying the proximity to local shops and the Water of Leith walkway. His weekdays are structured around client work, often starting with a strong coffee and reviewing his task list. Evenings are for unwinding, perhaps with a home-brewing experiment or reading tech journals. Weekends are reserved for longer hikes in the Pentland Hills or exploring the Scottish countryside by bike. He's financially prudent, saving a good portion of his income, but doesn't shy away from investing in quality tools or experiences that enhance his work or leisure. He values his independence and the flexibility his career affords him.

Work life

Myron thrives on the autonomy of running his own API consulting practice. He currently manages two SME clients, dedicating focused blocks of time to each. His days are a mix of deep technical work – configuring gateway routes, setting up authentication mechanisms, and troubleshooting deployment issues – and client communication. He meticulously documents everything, using separate spreadsheets for client-specific configurations and Git repositories for deployment scripts. The challenge lies in context-switching between different client stacks and open-source gateway technologies, ensuring consistency and security for each. He often finds himself deep in documentation or online forums, seeking the most robust and efficient solutions.

Relationships

Myron maintains a small but close circle of friends, mostly met through university or tech meetups. He has a good relationship with his sister and her family, visiting them for Sunday dinners occasionally. His primary professional influence comes from online communities and respected figures in the API development space, though he values the direct feedback from his clients.

How they decide

Myron is a cautious and research-driven decision-maker. He thoroughly evaluates options, weighing pros and cons based on technical merit, long-term stability, and client suitability. He relies on documentation, community consensus, and his own practical experience. He avoids hasty choices and prefers solutions that are well-understood and maintainable.

How they sound

Speaks with a measured, clear cadence, typical of educated Scottish professionals. Avoids overly casual slang but uses precise technical terminology. His tone is generally calm and analytical, occasionally showing enthusiasm when discussing a particularly elegant technical solution. He tends to be direct and avoids hyperbole, preferring factual statements. He might use phrases like 'essentially', 'in essence', 'the crux of the matter', or 'from a practical standpoint'.

Personality traits

  • analytical
  • resourceful
  • communicative
  • reserved
  • proactive
  • detail-oriented
  • methodical
  • independent

Goals

  • To build a reputation as the go-to API consultant for SMEs in Scotland.
  • To achieve a sustainable work-life balance, allowing ample time for personal pursuits.
  • To continuously expand his knowledge of emerging API technologies and security best practices.
  • To eventually mentor junior developers interested in API architecture.
  • To save enough for a significant down payment on a small cottage outside the city.

Problems & frictions

  • Juggling the demands of two distinct client projects simultaneously.
  • Keeping up with the rapid evolution of API gateway technologies and best practices.
  • The administrative overhead of managing client documentation and version control manually.
  • Finding reliable, scalable solutions for smaller clients with limited budgets.
  • Occasional isolation as a solo consultant, missing informal peer technical discussions.

Values

  • autonomy
  • pragmatism
  • client trust
  • technical excellence
  • work-life balance

Interests

  • hiking
  • home brewing
  • tech meetups
  • reading
  • cycling

Media habits

  • The Verge
  • TechCrunch
  • BBC News
  • API-focused podcasts
  • Stack Overflow

Questions & answers

Myron Upton’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Arelio API Gateway (https://www.digitalapi.ai/product/arelio-api-gateway) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The primary thing that would stop me from trying Arelio API Gateway this month is the lack of clarity on specific pricing beyond the "per 100k transactions" model. Today, I meticulously manage routes and auth rules in spreadsheets and Git repos for each of my two SME clients, which is quite manual. While the idea of built-in features like a developer portal and monetization is appealing, understanding the associated costs for my specific usage is crucial. Without a clear per-month breakdown, especially for my current client load, it's hard to assess affordability. I would need to see how this translates to my typical usage before committing. My maximum would be around $300 per month, given my income and the need to budget carefully for my practice.
    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.