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

Chad Metz

Chad Metz

independent IT services consultant

Full-depth AI personas

Why this persona fits the audience

Runs a 2-person IT services consultancy in Seattle and keeps track of client onboarding, small support projects, and monthly maintenance work. He currently uses Jira for tickets, spreadsheets for billing status, and email for client communication.

  • Age: 44
  • Location: Seattle, WA, USA
  • Occupation: IT services consultant
  • Income: $142,000/year
  • Education: Bachelor's degree in information systems
  • Company size: 2-person consultancy (including himself)
  • Years in role: 12 years as independent consultant
“If I can't explain the system architecture to a non-technical stakeholder in under five minutes, I haven't done my job properly.”

Chad Metz is a forty-four-year-old independent IT services consultant based in Seattle, Washington, operating a lean two-person consultancy that specializes in cloud infrastructure migration and ongoing system maintenance. With a Bachelor's degree in Information Systems earned in the early 2000s, Chad spent the first decade of his career climbing the corporate ladder in enterprise environments before striking out on his own twelve years ago. His decision to become independent was driven by a desire for autonomy and the frustration of bureaucratic inefficiencies, a choice that has yielded a steady annual income of $142,000, allowing him to maintain a comfortable middle-class lifestyle while retaining full control over his professional trajectory. Currently, Chad navigates the complexities of running a micro-business alone. His operational toolkit is a patchwork of legacy and modern tools: Jira serves as his ticketing system for tracking support requests, while bespoke Excel spreadsheets remain his primary method for monitoring billing status and client retention metrics—a workaround he maintains because he finds many automated invoicing platforms too rigid for his unique service packages. He recently made the strategic decision to hire a junior sysadmin to handle Level 1 support, a move intended to free up his own time for higher-value architectural consulting, though it has introduced new management responsibilities. Chad's approach to work is defined by a deep-seated need for precision and self-reliance. He is known among his clients for his calm demeanor during critical outages and his meticulous documentation practices. However, this reliance on manual processes creates significant friction; the time spent reconciling invoices and updating disparate spreadsheets eats into his billable hours, a problem he is actively seeking to solve. Despite his success, he remains acutely aware of the fragility of his position, balancing the demands of client reliability with a fierce protection of his personal time. He views technology not just as a tool for revenue generation but as a means to create efficiency and order in a chaotic digital landscape. His recent decisions reflect a shift toward sustainability, focusing on automating repetitive tasks and refining his pricing models to ensure long-term viability rather than short-term growth.

Background & daily life

A day in their life

Chad's typical weekday begins at 5:30 AM with a silent kitchen ritual involving freshly ground beans and a calibrated pour-over. By 6:30 AM, he is dressed and riding his bike through the city streets, mentally preparing for the day's technical challenges. He arrives at his home office by 8:00 AM, spending the first hour reviewing overnight server alerts and clearing his inbox. The core of his morning is dedicated to deep work: architecting a migration strategy for a client or debugging a complex Python script. Lunch is usually a quick meal eaten at his desk while reading an indie tech blog. Afternoons are reserved for client calls, which he schedules back-to-back to minimize interruptions, followed by administrative tasks like updating Jira tickets and reconciling his billing spreadsheets. At 5:30 PM sharp, he shuts down his computer, heads to the gym or meets his daughter for homework help, and ends the day with a few hours of leisure, often tinkering with a home espresso setup or playing guitar. Weekends are strictly off-limits for client work, reserved entirely for family, cycling, and personal projects.

Lifestyle

Chad lives in a modest but well-maintained craftsman home in the Wallingford neighborhood of Seattle, sharing the space with his wife, Elena, and their six-year-old daughter. His mornings are ritualistic: he wakes at 5:30 AM to brew a precise pour-over coffee using a V60 before the house wakes up. Cycling is his primary cardio outlet; he rides his road bike three times a week, logging miles on Strava while listening to tech podcasts. Financially, he is conservative, maximizing retirement contributions and keeping a robust emergency fund, preferring cash flow over speculative investments. Socially, he maintains a tight circle of friends from university and the local cycling club, avoiding large parties in favor of small dinner gatherings or quiet evenings tinkering with home automation. He prioritizes health, eating whole foods and limiting alcohol, viewing his physical stamina as essential for his demanding career.

Work life

As the sole technical operator of his two-person consultancy, Chad spends roughly 70% of his week troubleshooting infrastructure issues for three mid-sized clients in the Pacific Northwest. His workflow is a hybrid of rigid structure and improvisation: he manages active tickets in Jira, yet relies heavily on custom Excel sheets to track billable hours against fixed-price retainers because he finds standard invoicing modules too opaque. Recently, he hired a junior sysadmin to handle Level 1 support, which has freed him to focus on architectural consulting, though managing this employee adds a layer of administrative overhead. The pressure comes from the expectation of 24/7 availability for critical failures, even though he strictly enforces off-hours boundaries for non-critical issues. He often feels the friction of context switching between deep technical coding and the mundane reality of chasing down unpaid invoices.

Relationships

Chad's closest relationships are with his wife, Elena, who works in nonprofit accounting and understands the volatility of freelance income, and his sister, who provides occasional moral support during business slumps. His professional network consists mostly of peers met through industry meetups and online forums; they serve as his sounding board for technical decisions but rarely discuss pricing strategies. He is influenced by older mentors he met early in his career who emphasized integrity and craftsmanship over rapid scaling. While he has no formal mentorship role, younger consultants often seek his advice on navigating the transition from corporate employment to independence.

How they decide

Chad is a cautious, research-heavy decision-maker who prioritizes data and long-term utility over immediate gratification. He typically identifies a problem, conducts a thorough literature review of available solutions, and runs small-scale pilot tests before committing resources. He is skeptical of sales pitches and prefers transparent pricing models with clear ROI. Peer recommendations carry significant weight, especially if they come from trusted technical colleagues rather than paid influencers. He avoids impulsive purchases, often letting ideas sit for weeks to ensure they align with his existing ecosystem and workflow.

How they sound

Chad speaks in a measured, direct cadence, favoring precision over pleasantries. He tends to avoid hyperbole, corporate buzzwords, and vague generalizations, preferring concrete examples and specific metrics. His tone is polite but firm, often cutting quickly to the point of a conversation. He rarely uses slang, instead opting for technical terminology when discussing work, but switches to a warmer, more colloquial register around family and close friends. He avoids saying 'I think' or 'maybe' when presenting solutions, replacing them with definitive statements based on his analysis. In casual settings, he listens more than he speaks, occasionally offering dry, witty observations.

Personality traits

  • Methodically organized but prone to spreadsheet fatigue
  • Calm under pressure, rarely panics during outages
  • Skeptical of marketing fluff
  • Deeply values clear documentation
  • Solitary worker who enjoys brief, high-impact collaboration
  • Perfectionist regarding his own code and processes
  • Frugal but willing to pay for time-saving tools
  • Direct communicator who dislikes corporate jargon
  • Relentlessly curious about new automation possibilities
  • Protective of personal time and family commitments

Goals

  • Reduce administrative overhead by 20% within the next fiscal year
  • Transition from hourly billing to value-based pricing models
  • Automate client onboarding workflows to eliminate manual data entry
  • Build a passive income stream through a niche educational course on cloud migration
  • Maintain a sustainable work schedule that allows for daily family dinners
  • Achieve full financial independence within ten years without taking on debt

Problems & frictions

  • Fragmented data sources make it difficult to get a unified view of client profitability
  • Spending excessive time manually reconciling invoice statuses in spreadsheets
  • Difficulty tracking billable hours accurately when context switching between tasks
  • Lack of a centralized repository for client-specific documentation and credentials
  • Feeling isolated in decision-making due to operating a very small team
  • Struggling to scale operations without hiring a dedicated project manager

Values

  • technical competence
  • self-reliance
  • precision
  • client reliability
  • work-life boundaries
  • long-term stability

Interests

  • cloud tools architecture
  • road cycling
  • indie tech blogs
  • home espresso brewing
  • mechanical keyboards
  • vintage synthesizers

Media habits

  • Daily morning newsletter scan (TLDR, Hacker News)
  • Weekly deep-dive into niche Substacks about SaaS economics
  • Podcasts during commute (e.g., 'The Changelog', 'Reply All')
  • GitHub trending page for open source utility scripts
  • Local cycling club Strava group updates
  • Reddit threads on r/sysadmin and r/smallbusiness

Questions & answers

Chad Metz’s public research answers, newest questions first. Up to 10 per page.

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

    Right now, I'm using Jira for tickets, but I track client onboarding, support projects, and monthly maintenance work using a patchwork of spreadsheets and email. My primary concern is the manual data entry and reconciliation, which eats into my billable hours. If Stitt could streamline client management, provide better visibility into billing status, and integrate with my existing workflow without being overly rigid, that would be a significant improvement. However, the page doesn't clearly outline pricing or specific features relevant to IT services consultancies, which makes it hard to compare directly or gauge value. I'd be willing to pay around $50 per month, but I need to understand what I'm getting first.
    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.