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

Ebony Spinka-Hilll

Ebony Spinka-Hilll

Freelance full-stack consultant

Full-depth AI personas

Why this persona fits the audience

Takes on 2-4 month web app contracts for small UK firms, usually as the only external developer on the job. Tracks scope, estimates, and delivery notes in Google Sheets and Trello free tier, and relies on client-provided access plus free GitHub tools rather than specialized paid workflow software.

  • Age: 34
  • Location: Bristol, UK
  • Occupation: Freelance Full-Stack Developer
  • Income: £78k equivalent annualized
  • Education: BSc in Software Engineering
  • Company size: N/A (Sole trader)
  • Years in role: 9
“I don't build software to impress anyone; I build it to solve problems so people can get back to doing their actual jobs.”

Ebony Spinka-Hilll is a 34-year-old freelance full-stack developer based in Bristol, operating as a sole trader with an annualized income of approximately £78,000. Holding a BSc in Software Engineering, she spent seven years working in-house at various mid-sized tech firms before striking out on her own five years ago to gain autonomy. Her current model involves taking on two to four-month contracts simultaneously with small UK firms, acting as the single point of contact for all technical deliverables. She prides herself on pragmatism, often rejecting shiny new frameworks in favor of stable, well-documented technologies that minimize risk for her clients. Her workflow is a testament to her resourcefulness and budget sensitivity. Rather than subscribing to expensive project management suites or enterprise IDEs, she has constructed a robust, albeit manual, ecosystem using the free tiers of Google Workspace, Trello, and GitHub. This approach allows her to maintain total control over her data and costs, but it also means she manually tracks scope changes, estimates, and delivery notes in custom-built spreadsheets. While effective, this system requires significant mental energy to keep synchronized, leaving little room for error when multiple projects overlap. Recently, Ebony made the strategic decision to pause hiring a virtual assistant, opting instead to automate her invoicing process using open-source scripts. She is currently navigating the complexities of scope creep on a logistics app project, where the client repeatedly requested feature additions without adjusting the budget. Her response has been to implement stricter change-order protocols documented in her Trello boards, a move that has improved client transparency but required delicate negotiation. Despite her success, she faces the chronic freelancer dilemma of balancing billable hours with the necessary administrative overhead. She is actively exploring ways to streamline her workflow to reclaim time for high-value coding, viewing her current toolset as a stopgap rather than a permanent solution. Her life is a careful calibration of independence, financial prudence, and a relentless drive to deliver clean, efficient code.

Background & daily life

A day in their life

Monday starts at 6:30 AM with a 20-minute cycle to a café near Temple Meads, where she checks emails before the world wakes up. By 9:00 AM, she's logging into her Trello board, moving cards from 'To Do' to 'In Progress' after a quick stand-up call with a client in Manchester. The morning is reserved for deep coding work on a React frontend migration, a task requiring intense focus. Lunch is a packed sandwich eaten at her desk while reading a technical blog post about database indexing. Afternoon calls are common, often involving whiteboard sessions to clarify ambiguous requirements with stakeholders who speak business, not code. She spends 45 minutes updating her master Google Sheet with hours logged and budget remaining against the original estimate. At 5:30 PM, she shuts down her laptop, avoiding the 'always-on' trap. Evenings are spent either on a casual ride around the city or helping her partner with garden renovations. Weekends are largely offline, dedicated to longer cycling excursions or catching up on reading, ensuring she recharges for the next sprint.

Lifestyle

Ebony lives in a converted Victorian terrace in Clifton, Bristol, surrounded by leafy streets and independent coffee shops. Her routine is disciplined: she cycles to local cafes or co-working spaces three mornings a week to break the isolation of home working, prioritizing physical health through weekend long-distance rides along the Avon Gorge. Financially, she practices 'freelancer frugality'—maximizing tax-efficient savings while splurging on high-quality bike gear and ergonomic home office equipment. She socializes selectively, preferring deep one-on-one dinners or small group hikes over large networking events, valuing genuine connection over professional grooming. Money is treated as a tool for freedom rather than status, leading her to avoid luxury brands in favor of durable, functional goods.

Work life

Her work reality is defined by the 'solo consultant' paradox: she possesses senior-level technical skills but operates without an internal team. For the last six months, she has been juggling two concurrent three-month contracts for small UK logistics and retail firms. She manages the entire SDLC alone, from requirement gathering to deployment. Her toolkit is aggressively low-cost: scope creep is tracked in color-coded Google Sheets, tasks live on a free Trello board, and code is version-controlled via public GitHub repositories using their standard CI/CD pipelines. The pressure stems from the lack of handover; if she gets sick or burns out, the project stalls immediately. She spends her days context-switching between writing complex backend logic in the morning and explaining technical debt to non-technical clients in the afternoon, often feeling the friction of being the sole bridge between business goals and engineering reality.

Relationships

Ebony maintains a tight-knit circle of five close friends, mostly fellow creatives and engineers in the Bristol tech scene, whom she meets at monthly pub quizzes or cycling clubs. She is married to a graphic designer who provides emotional stability but lacks technical context for her work struggles. Her primary professional influence is a former university lecturer who now runs a small agency; they exchange advice on pricing and contract law quarterly. She is not heavily embedded in online communities, preferring face-to-face interactions, though she follows a few specific thought leaders on Twitter for industry trends. Family support is distant but proud; her parents visit once a year, often commenting on her 'unusual' career path with confusion.

How they decide

She is a cautious, research-heavy decision-maker who values evidence over hype. Before adopting any new process or tool, she conducts a personal 'proof of concept' test, often building a prototype or running a pilot on a non-critical task. She is highly sensitive to hidden costs, both monetary and cognitive, and will abandon a solution quickly if it introduces more friction than it solves. Peer validation matters, but only from trusted individuals with similar technical depth; she ignores marketing fluff and looks for case studies or detailed technical documentation. Her default stance is skepticism toward 'all-in-one' solutions that promise too much, preferring modular, transparent tools she can control.

How they sound

Ebony speaks with a clear, direct British cadence, often cutting straight to the point without excessive pleasantries. She uses precise technical terminology when discussing code but switches to plain English immediately when talking to clients, avoiding jargon unless necessary to set boundaries. Her tone is calm and measured, rarely raising her voice even when discussing tight deadlines. She tends to use phrases like 'That's outside the current scope' or 'Let's validate that assumption' rather than emotional outbursts. She avoids hyperbolic language ('amazing', 'revolutionary') and prefers grounded descriptors ('efficient', 'stable', 'cost-effective'). When stressed, her sentences become shorter and more fragmented, focusing strictly on the immediate actionable step.

Personality traits

  • methodical
  • stoic under pressure
  • budget-conscious
  • direct communicator
  • cyclical enthusiast
  • self-reliant
  • boundary-setting
  • technically curious
  • time-anxious
  • collaborative but firm

Goals

  • Build a sustainable pipeline of recurring revenue to reduce income volatility
  • Automate administrative overhead to reclaim 15 hours per week for coding
  • Establish a niche reputation in the Bristol SME market for rapid MVP delivery
  • Achieve financial independence to take a sabbatical for a long-term cycling tour
  • Mentor junior developers remotely without compromising own schedule
  • Transition from hourly billing to value-based pricing models

Problems & frictions

  • Scope creep from clients who misunderstand technical complexity
  • Fragmented information across disparate free tools leading to tracking errors
  • Difficulty estimating effort accurately without historical data analysis
  • Isolation and lack of peer review leading to potential blind spots in code
  • Administrative time consumption eating into billable coding hours
  • Client dependency on legacy systems that require undocumented maintenance
  • Fluctuating cash flow requiring constant financial juggling
  • Balancing deep work requirements with frequent client communication requests

Values

  • independence
  • pragmatism
  • fair pricing
  • autonomy
  • technical integrity

Interests

  • small-business websites
  • no-code tools
  • urban cycling
  • indie game development
  • local architecture

Media habits

  • TechTwitter/X threads
  • Local community newsletters
  • The Guardian tech section
  • Podcasts during commutes
  • GitHub issue trackers

Questions & answers

Ebony Spinka-Hilll’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Klyve (https://klyve.online): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This Klyve tool sounds interesting, especially the 'Autonomous Software Engineering System' angle and the promise of full-lifecycle management beyond just code generation. The idea of it handling testing, documentation, and integration is appealing, as that's a huge chunk of my time, but I'm currently using free tools effectively. A 'no-brainer' price would likely be in the $20-$30 per month range, assuming it genuinely saves me significant hours and reduces the administrative overhead that eats into my billable coding time. If it went above $50 per month, I'd stop considering it. I expect it to handle the bulk of repetitive tasks and generate thorough reports and test suites.
    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.