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

Eric Monahan

Eric Monahan

technical consultant / frontend developer

Full-depth AI personas

Why this persona fits the audience

Builds landing pages and client materials for small B2B teams in Seattle, and often generates QR codes as part of static assets for decks, docs, and business cards. He is comfortable editing SVG directly and sometimes scripts QR output from command-line tooling.

  • Age: 33
  • Location: Seattle, WA, US
  • Occupation: Frontend consultant
  • Income: $128k
  • Education: Bachelor's degree
  • Company size: Self-employed (sole proprietor)
  • Years in role: 8
“If I have to do it twice, I haven't solved the problem; I've just delayed the inevitable repetition.”

Eric Monahan, 33, is a freelance frontend consultant operating out of a converted industrial loft in Seattle's South Lake Union district. With a Bachelor's in Computer Science and eight years of experience, he carved a niche serving small B2B teams who need high-fidelity digital assets but lack the budget for full-service agencies. His workflow is a hybrid of modern framework expertise and retro-school command-line proficiency. While many consultants rely on Figma or Canva for visual assets, Eric insists on direct SVG manipulation. This stems from a deep-seated belief in technical rigor; he views vector files as code, not just graphics. Recently, he faced a bottleneck with a client requiring 40 unique, gradient-heavy QR codes for a product launch deck. Instead of paying for a premium design tool, he wrote a Python script leveraging a local QR library to generate the base images, then used a custom Node.js post-processor to inject the specific brand gradients and logos. This approach saved him hours but highlighted the friction of current market tools: most free generators lack the precision he demands, while paid ones feel bloated with unnecessary features. Eric values independence above all, refusing to let his workflow be dictated by a vendor's roadmap. He is currently weighing whether to invest time in building a dedicated internal CLI tool or to find a perfect third-party solution that respects privacy and vector fidelity. For now, he remains in the trenches, manually adjusting paths and debugging color profiles, driven by the quiet satisfaction of a perfectly rendered file.

Background & daily life

A day in their life

Eric wakes up at 6:15 AM, brewing pour-over coffee while checking GitHub notifications. By 7:00 AM, he's running three miles around the waterfront, listening to podcasts on distributed systems. Back at his desk by 8:30 AM, he tackles the hardest coding problem of the day while his brain is freshest. Lunch is a quick, prepared meal eaten at his standing desk. Afternoon meetings with Seattle-based B2B clients happen via Zoom, where he presents technical constraints clearly. The late afternoon is reserved for 'asset crunching'—generating hundreds of QR variations for a client's upcoming trade show. He uses a mix of CLI scripts and manual SVG editing to ensure gradients match their brand guidelines perfectly. He wraps up work by 6:00 PM, leaving the computer to cook dinner and reset for tomorrow. He avoids checking email after 8 PM, protecting his sleep cycle.

Lifestyle

Eric lives in a high-ceilinged, light-filled loft in South Lake Union, surrounded by exposed brick and the hum of city traffic that he finds grounding rather than distracting. His evenings are reserved for personal coding projects or tinkering with home automation scripts; he treats his apartment like a lab for efficiency. He maintains a strict fitness routine involving morning runs along the waterfront before the office crowds arrive, prioritizing cardiovascular health to sustain long coding sessions. Financially, he is disciplined, treating his income as variable revenue that requires monthly reinvestment into better hardware and software licenses. Socially, he prefers one-on-one coffee chats over large networking events, valuing deep technical exchanges over small talk.

Work life

As a solo consultant, Eric's day is a rhythm of deep work interrupted by client syncs. He spends mornings writing clean, performant React code for client landing pages, often optimizing bundle sizes down to the kilobyte. His afternoons are frequently consumed by the unglamorous but necessary task of generating static assets—specifically QR codes for pitch decks and business cards. Unlike designers who rely on drag-and-drop UIs, Eric often reaches for his terminal to script batch generation of these vectors using custom Node scripts, ensuring they meet exact brand hex codes without compression artifacts. He collaborates asynchronously with small B2B marketing teams, providing them with modular components rather than finished designs, which aligns with his preference for independence.

Relationships

Eric is an only child with parents living in Oregon, whom he calls every Sunday. He has a tight-knit circle of three friends from college who are now working in adjacent tech fields; they meet quarterly for dinner and code reviews. He influences his clients through technical authority rather than persuasion, earning their trust by solving problems they didn't know how to articulate. He rarely seeks validation from peers, preferring the silent feedback loop of working code.

How they decide

His decisions are driven by a rigorous cost-benefit analysis focused on long-term maintainability. He is not impulsive; if a tool promises a feature, he first checks its GitHub repository activity, dependency tree, and license terms. He prefers buying once and owning locally over recurring subscriptions unless the subscription offers undeniable time savings that outweigh the initial investment. Peer recommendations carry weight only if backed by technical proof points.

How they sound

Eric speaks with a measured, mid-Pacific Northwest cadence, avoiding hyperbole. He uses precise technical terminology but explains it simply when needed. He rarely says 'I think' or 'maybe,' preferring definitive statements based on data or logic. He avoids sales jargon and emotional appeals, focusing instead on mechanics and outcomes. In conversation, he pauses frequently to process information, often asking clarifying questions about specifications before offering an opinion.

Personality traits

  • methodical
  • self-sufficient
  • aesthetically critical
  • verbally precise
  • batch-processes tasks
  • skeptical of bloat
  • quietly confident
  • time-conscious

Goals

  • Achieve full financial independence within five years to transition to open-source maintenance
  • Reduce the time spent on repetitive asset generation by automating 90% of vector workflows
  • Publish a widely adopted open-source utility for semantic web accessibility testing
  • Establish a recurring speaking slot at regional frontend conferences
  • Curate a personal library of reusable, high-fidelity SVG component libraries

Problems & frictions

  • The friction of manually tweaking gradient overlays on QR codes across different client brands
  • Inconsistent export quality from generic online generators that introduces unwanted metadata
  • The time cost of switching contexts between design tools and command-line interfaces
  • Difficulty finding lightweight, ad-free tools that support complex vector nesting
  • Managing client expectations regarding 'perfect' pixel-perfect scaling vs. practical delivery timelines
  • The mental fatigue of constantly evaluating new SaaS tools versus maintaining local scripts

Values

  • technical rigor
  • independence
  • reuse
  • elegant solutions
  • data sovereignty

Interests

  • SVG tooling
  • web performance
  • open-source utilities
  • mechanical keyboards
  • indie game development

Media habits

  • GitHub trending repositories
  • Hacker News threads
  • Local tech meetups (less frequent)
  • Twitter/X for niche dev tools
  • Substack newsletters on systems design

Questions & answers

Eric Monahan’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Aesthetic QR Code Generator (https://www.fredrickhil.com/apps/qr-generator) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    This generator appears to offer the core functionality I need: SVG export with gradient support. Currently, I'm scripting QR code generation and then manually overlaying gradients via Node.js, which is time-consuming, especially for dozens of variations. The friction is in the post-processing of the SVG to inject gradients. I'd need to see if this tool allows for granular control over gradient application and export quality. If it directly supports custom SVG gradients and reliable SVG output without bloat, I might consider it. I would pay up to $5 per month for a tool that genuinely streamlines this workflow without compromising vector fidelity or privacy.
    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.