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

Shelley Fay

Shelley Fay

Freelance cloud consultant

Full-depth AI personas

Why this persona fits the audience

She works as a UK-based freelance cloud consultant for 2-10 person startups, usually taking over AWS setup for a few weeks at a time. Each client arrives with partial Terraform, different account structures and a short budget, so she reuses her own templates, notes and checklists across engagements.

  • Age: 39
  • Location: London, UK
  • Occupation: Freelance cloud consultant
  • Income: £650/day contract equivalent
  • Education: MSc in Information Systems
  • Company size: N/A (Solo contractor)
  • Years in role: 7
“Infrastructure isn't just about servers and scripts; it's about buying your team the peace of mind to build the product they actually care about.”

Shelley Fay is a seasoned freelance cloud consultant based in East London, specializing in stabilizing the chaotic early-stage infrastructure of high-growth startups. At 39, she possesses a unique blend of academic rigor, earned through her MSc in Information Systems, and the gritty, pragmatic experience of seven years navigating the volatile waters of the UK tech contracting market. Her career trajectory was defined not by climbing a corporate ladder, but by deliberately choosing autonomy, allowing her to curate a portfolio of clients ranging from fintech disruptors to e-commerce pioneers. She operates out of a modest home office in Dalston, equipped with dual monitors and a mechanical keyboard that clicks softly enough not to disturb her neighbors. Shelley's reputation rests on her ability to diagnose and resolve 'infrastructure debt' quickly. She enters client engagements with a toolkit of her own meticulously crafted Terraform modules, designed to enforce security best practices and cost controls from day one. This approach allows her to deliver production-ready foundations in days rather than months, a critical value proposition for startups operating on razor-thin budgets. Despite her success, she remains acutely aware of the human element in technology; she often finds herself acting as a translator between panicked founders and cold, hard cloud billing data. Her recent decision to cap her contract rate at £650 per day reflects a conscious choice to prioritize sustainable workload management over maximum earnings, ensuring she retains enough energy for her passion project: sailing. She views her work not merely as a service, but as a stewardship of the digital assets that power modern innovation, driven by a deep-seated belief that clarity and trust are the most valuable currencies in the industry.

Background & daily life

A day in their life

Shelley wakes at 5:30 AM for a run along the Regent's Canal, returning just as the city begins to stir. After a quick breakfast and a shower, she logs onto her laptop by 8:00 AM, starting with a review of overnight AWS alerts before diving into deep work. From 9:00 AM to 12:30 PM, she focuses on coding critical infrastructure changes, minimizing distractions by keeping notifications off. A mid-morning coffee break at a nearby independent shop allows her to stretch and reset. Lunch is a packed salad eaten at her desk while listening to a podcast on system reliability. The afternoon is reserved for client meetings, typically involving screen-sharing sessions where she explains complex migration paths to non-technical stakeholders. By 5:30 PM, she shuts down her work computer strictly, leaving time for the gym or a walk with her partner. Evenings are for hobbies—often tinkering with audio equipment or planning weekend sailing routes—and she aims to be asleep by 10:30 PM to ensure she can repeat the cycle fresh.

Lifestyle

Shelley lives in a sunlit, slightly cluttered flat in Dalston, filled with books on systems engineering and framed photos from her sailing trips around the Thames Estuary. She maintains a strict morning routine: an hour of running before work, followed by a strong espresso at a local independent cafe where she checks emails without distractions. Her finances are managed with aggressive discipline; she maximizes pension contributions and keeps a six-month emergency fund to buffer against the irregular nature of contracting. Socially, she balances quiet evenings reading or restoring old radios with weekly drinks at the sailing club, preferring deep conversations over large gatherings. She is health-conscious, tracking sleep and nutrition as rigorously as she tracks server uptime.

Work life

Her work is a blur of rapid context switching between three to four distinct startup environments simultaneously. One day she is untangling a chaotic AWS landing zone for a fintech in Shoreditch; the next, she is refactoring legacy Infrastructure-as-Code for a SaaS team in Clapham. She relies heavily on her personal repository of reusable Terraform modules and standard operating procedures to deliver speed without compromising security. The pressure comes not from volume, but from the urgency of clients who often have no internal DevOps expertise and are terrified of billing spikes. She spends half her week writing code and the other half translating technical debt into plain English for founders who just want their products to launch.

Relationships

Shelley is married to a graphic designer named Mark, who provides a grounding counterpoint to her high-speed tech world. They share a dog named Barnaby and spend weekends exploring the Kent coast. Her professional network is tight-knit, consisting mostly of fellow contractors and CTOs she has worked with previously; these are the people she calls when she needs a second opinion on a complex architecture decision. She is active in a small London-based women-in-tech sailing group, which serves as both her social circle and her primary source of peer support outside of work.

How they decide

Shelley operates on a 'measure twice, cut once' philosophy. She is research-heavy and rarely makes decisions based on hype or marketing fluff. Instead, she validates concepts through proof-of-concept tests, scrutinizing documentation for depth and community activity. While she values peer recommendations, her final approval always hinges on whether a solution aligns with her core principles of clarity and long-term maintainability. She is willing to invest time upfront to avoid technical debt later, preferring a slightly higher initial cost if it guarantees stability.

How they sound

Her speech is precise and measured, devoid of corporate jargon unless necessary to bridge gaps with clients. She speaks with a clear Received Pronunciation accent but softens it with a warm, approachable tone when discussing problems. She avoids hyperbolic language like 'revolutionary' or 'game-changing,' preferring terms like 'robust,' 'scalable,' or 'maintainable.' When explaining technical constraints, she uses analogies drawn from sailing or mechanics rather than abstract theory. She pauses frequently to ensure understanding, often asking, 'Does that make sense?' rather than assuming agreement.

Personality traits

  • methodical
  • calm under pressure
  • pragmatic
  • meticulous about documentation
  • direct but polite
  • self-reliant
  • obsessive about version control
  • resilient
  • curious
  • boundary-conscious

Goals

  • Build a fully automated, self-healing CI/CD pipeline for her own consulting business
  • Complete a solo circumnavigation of the British Isles within two years
  • Achieve financial independence by age 45 through diversified passive income streams
  • Mentor two junior engineers annually to help them transition into senior roles
  • Publish a definitive guide on 'Terraform Hygiene for Startups'
  • Reduce weekly working hours to 30 while maintaining current revenue

Problems & frictions

  • The cognitive load of constantly resetting mental models for new, messy client infrastructures
  • Difficulty pricing high-value architectural advice when clients expect low-cost fixes
  • Maintaining deep focus amidst frequent Slack interruptions from anxious startup founders
  • Keeping personal knowledge base updated without it becoming a maintenance burden
  • Isolation of remote work leading to missed networking opportunities with peers
  • Balancing the need for rapid delivery with the ethical obligation to warn clients about future costs

Values

  • independence
  • clarity
  • client trust
  • efficiency
  • intellectual honesty

Interests

  • cloud architecture
  • sailing
  • indie coffee shops
  • analog photography
  • marathon training
  • restoring vintage audio gear

Media habits

  • The Cloud Weekly newsletter
  • Local sailing club bulletin boards
  • Twitter/X technical threads
  • Podcasts during commute
  • Architectural Digest
  • Specialist Stack Exchange forums

Questions & answers

Shelley Fay’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Baseline One (https://vancerbaseline.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Baseline One 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, I rely on my own extensive collection of Terraform modules, supplemented by detailed checklists and personal notes. It's a system I've built and refined over years, tailored to the specific needs of small startups with tight budgets. Baseline One's promise of "production-ready AWS Terraform foundation in minutes, not months" is compelling, especially the automated compliance controls for SOC2 and GDPR. That would certainly save me time and reduce the potential for manual errors. However, my current setup is highly customized to my clients' varied account structures and my own preferences for control. The main hurdle would be understanding how easily your modules integrate with existing, often messy, Terraform codebases and whether they offer the same level of flexibility. It’s the 'doing it by hand' aspect that I’ve honed into an efficient process. I’d need to see how it truly handles varied client starting points and if the "live updates" mean significant architectural shifts I'd have to manage. I'm not looking to pay for something that might introduce more complexity than it solves.
    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.