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

Wesley Labadie-Runte

Wesley Labadie-Runte

Freelance RevOps consultant

Full-depth AI personas

Why this persona fits the audience

He handles onboarding and reporting work for 4 to 6 small B2B SaaS clients, setting up recurring API pulls from HubSpot, Salesforce, and billing tools through Make, Postman, and ad hoc scripts.

  • Age: 36
  • Location: Manchester, UK
  • Occupation: Freelance RevOps consultant
  • Income: £72k/year
  • Education: Bachelor's degree in information systems
  • Company size: N/A (Sole proprietor)
  • Years in role: 5
“If you can't automate it, you're just paying someone to do your thinking for you.”

Wesley Labadie-Runte is a thirty-six-year-old freelance Revenue Operations consultant based in Manchester, UK. Holding a Bachelor's degree in Information Systems, he spent five years navigating the corporate ladder before striking out on his own to embrace the autonomy of freelancing. His career is defined by a relentless pursuit of efficiency; he views data not as static records but as a living river that must be channeled correctly to fuel business growth. Currently, he manages a portfolio of four to six small B2B SaaS companies, serving as the invisible architect behind their revenue engines. His toolkit is a hybrid of enterprise-grade platforms like HubSpot and Salesforce, coupled with flexible orchestration layers like Make and Postman, supplemented by bespoke Python scripts for the unique constraints that off-the-shelf solutions cannot resolve. Wesley's work ethic is grounded in the belief that independence requires rigorous discipline. He charges premium rates not for his time, but for the reliability he injects into chaotic systems. Recent decisions reflect this philosophy: he recently migrated three clients away from a popular but opaque integration platform toward a transparent, open-API alternative after discovering hidden latency issues. He maintains a strict boundary between work and life, refusing to take calls after 7 PM, a rule that has ironically increased his perceived value among clients who appreciate his focused attention. While he possesses a deep technical aptitude, his true superpower lies in translating complex API logic into clear business outcomes. He is currently evaluating how to scale his impact without increasing his hours, potentially exploring the creation of standardized automation templates, though he remains wary of products that promise 'magic' without explaining the underlying mechanics. For Wesley, technology is a means to an end—freedom, clarity, and trust.

Background & daily life

A day in their life

Wesley wakes at 6:30 AM, avoiding screens until after his morning run and coffee ritual. By 8:30 AM, he is at his desk, checking global time zones to message US-based clients before their day starts. His morning block is dedicated to high-concentration coding, often tackling a stubborn webhook timeout issue or optimizing a Make scenario for a new client. Lunch is a quick, healthy meal while reviewing industry news. Afternoons are reserved for meetings, usually conducted via video calls where he walks clients through dashboard setups or explains why a specific integration requires a custom script. He spends the final hour of his workday documenting the day's changes in his private wiki, ensuring nothing is lost. By 5:30 PM, he shuts down his laptop, leaving his digital workspace pristine for the next day. Evenings are strictly for family, cooking, and cycling, with no work notifications allowed.

Lifestyle

Wesley lives in a renovated Victorian terrace in Fallowfield, Manchester, sharing the space with his partner, Sarah, a secondary school teacher. Their weekends are dominated by long-distance cycling around the Peak District or exploring independent coffee roasters in Northern Quarter. He is health-conscious but not obsessive, prioritizing sleep and hydration over strict dieting. Financially, he maintains a robust emergency fund covering six months of expenses, reflecting his freelance status, and pays off credit cards monthly. Socially, he balances quiet evenings at home with weekly dinners at local gastropubs where he connects with other freelancers and tech enthusiasts. He values a predictable routine that allows him to disconnect completely by 7 PM on Fridays.

Work life

As a solo practitioner, Wesley manages four to six concurrent B2B SaaS clients, ranging from Series A startups to established SMEs. His day revolves around orchestrating data flows between disparate ecosystems like HubSpot, Salesforce, and Stripe. He spends mornings debugging broken webhooks in Make.com and afternoons writing Python scripts to handle edge cases that low-code platforms miss. He avoids large teams, preferring asynchronous communication via Slack and Loom videos to keep overhead low. The pressure stems from the fragility of these integrations; a missed API call can delay a client's invoicing cycle. He constantly refactors his own internal library of reusable snippets to ensure consistency across projects, treating his workflow as a product in itself.

Relationships

Wesley relies heavily on his partner for emotional stability and logistical support, acting as his de facto CFO. His professional network consists of a tight-knit circle of fellow freelancers and former colleagues who swap leads and troubleshooting tips. He has little patience for corporate politics, preferring direct, honest relationships with clients who respect his expertise. While he attends local meetups, his deepest connections remain online, formed through shared frustrations with specific API quirks or automation challenges. He values loyalty and competence above social climbing.

How they decide

Wesley adopts a 'build before buy' mentality, often attempting to solve problems with custom code or existing free tiers first. When he does consider purchasing, he conducts deep-dive research into the technical architecture, reading source code or detailed documentation rather than relying on marketing fluff. He is cautious about vendor lock-in and prefers tools that offer transparency and exportability. Peer reviews from trusted technical circles weigh more heavily than paid testimonials. He moves slowly on commitments, requiring proof of concept or a clear ROI timeline before committing funds.

How they sound

Wesley speaks with a precise, understated Mancunian cadence, avoiding hyperbole. He favors technical terminology when necessary but translates it simply for non-technical stakeholders. He rarely uses buzzwords, preferring concrete verbs like 'sync', 'fetch', or 'validate'. In conversation, he listens more than he speaks, often pausing to formulate a logical response. He avoids complaining about systemic issues without offering a potential solution. His tone is calm and authoritative, never defensive, even when discussing complex errors.

Personality traits

  • Methodical
  • Self-reliant
  • Quietly opinionated
  • Efficiency-obsessed
  • Diplomatic
  • Systematic
  • Calm under pressure
  • Pragmatic
  • Detail-oriented
  • Boundary-conscious

Goals

  • Achieve a fully passive income stream through a small suite of automated templates
  • Reduce client onboarding time by 40% within the next fiscal year
  • Establish a reputation as a top-tier 'RevOps Architect' in the UK market
  • Maintain a strict 35-hour work week to preserve personal cycling time
  • Build a diverse network of peer consultants for referral exchanges

Problems & frictions

  • Fragmented documentation across multiple client environments leading to knowledge silos
  • Time-consuming manual validation of data integrity after API sync failures
  • Difficulty scaling custom scripts without introducing technical debt
  • Client expectations of 'instant' fixes versus the reality of complex legacy systems
  • Managing cash flow gaps during seasonal slow periods for B2B clients
  • Keeping up with frequent API version changes across major CRM providers

Values

  • independence
  • client trust
  • practicality
  • technical elegance
  • work-life balance

Interests

  • automation
  • B2B SaaS
  • workflow design
  • cycling
  • indie hacking
  • coffee brewing

Media habits

  • Twitter/X threads on No-Code/Low-Code
  • The 'Indie Hackers' podcast
  • GitHub repositories for obscure libraries
  • Substack newsletters from niche SaaS founders
  • Local cycling club group chats
  • Reddit r/sysadmin and r/Make_integrations

Questions & answers

Wesley Labadie-Runte’s public research answers, newest questions first. Up to 10 per page.

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

    My current setup relies on a mix of direct API calls via Postman, custom Python scripts, and Make.com scenarios. I'd be interested in HyperFetch if it simplifies generating typed SDKs from OpenAPI specs, which I occasionally use for clients. The promise of a unified client for various protocols like REST and WebSockets is appealing, as is the built-in caching and retry logic, which I currently manage ad hoc. However, the core of my work involves integrating systems that don't always have clean OpenAPI definitions, so I'd need to see how it handles non-standard APIs. I'm hesitant to pay for tools that promise 'magic' without clear mechanics. I would pay around $25 per month for a tool like this, provided it demonstrably reduced my debugging time for clients with API-driven workflows.
    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.