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

Fannie Zemlak

Fannie Zemlak

Technical founder at a small agency using AI-assisted delivery

Full-depth AI personas

Why this persona fits the audience

She runs a 6-person web agency in Manchester that builds internal tools and lightweight SaaS products for local clients. Her team uses a mix of coding agents, reusable starter repos, and manual handoffs to package projects into something deployable, billed, and supportable after launch.

  • Age: 38
  • Location: Manchester, UK
  • Occupation: Agency Director
  • Income: £85k-£120k owner income
  • Education: BSc Information Systems
  • Company size: 6
  • Years in role: 7
“You can generate a thousand lines of code in an hour, but if you can't explain why it works or fix it when it breaks, you haven't built anything useful—you've just made noise.”

Fannie Zemlak is the driving force behind a nimble, six-person web agency nestled in the heart of Manchester's vibrant tech corridor. With a BSc in Information Systems and seven years of experience leading the firm, she has successfully transitioned her business from a traditional service model to a hybrid approach leveraging AI-assisted development. Her agency specializes in building internal tools and lightweight SaaS products for local SMEs, a niche she carved out by recognizing that larger agencies were too slow and expensive for mid-market needs. Fannie's leadership philosophy centers on 'operational clarity'; she believes that for AI to be effective, the human oversight must be even more rigorous than in traditional development. She personally curates the agency's 'starter repos' and defines the protocols for how coding agents interact with production environments, ensuring that what starts as a prototype becomes a robust, billable asset. Despite her technical background, Fannie is not a coder by trade anymore; she is an architect of processes. She spends her days mediating between client expectations and technical reality, ensuring that her team of four developers and two designers are never overwhelmed by the promise of automation. Recently, she made the strategic decision to pause hiring new full-time staff, opting instead to invest in better tooling and training for her existing team to increase throughput. This move reflects her pragmatic approach to growth: she prioritizes profitability and sustainability over rapid expansion. Living in Chorlton with her family, Fannie balances her high-stakes professional life with a grounded personal routine, finding solace in cycling and local community engagement. She is known in Manchester circles not for flashy marketing, but for delivering consistent, high-quality results that keep her clients coming back year after year. Her reputation is built on trust—she doesn't sell dreams; she sells working software that solves real problems.

Background & daily life

A day in their life

Fannie wakes at 6:00 AM in Chorlton, brewing a strong cup of filter coffee before checking Slack and email for any overnight issues from US-based clients. By 7:30 AM, she is cycling to work, listening to a podcast on supply chain logistics. At 9:00 AM, she joins the daily stand-up, focusing less on status updates and more on unblocking her team's AI agent workflows. Mid-morning is dedicated to reviewing pull requests, where she acts as the final gatekeeper for code quality, ensuring that automated tests pass and that the 'starter repo' patterns are being followed correctly. Lunch is usually a quick sandwich eaten at her desk while reading a whitepaper on new LLM deployment strategies. Afternoons are dominated by client calls, where she navigates scope creep with firm but empathetic boundaries, often negotiating down feature requests to fit within the current sprint. She wraps up around 5:30 PM, leaving the office to pick up her children from school, ensuring a hard stop to maintain work-life balance. Evenings are reserved for family, cooking, and winding down, though she occasionally checks logs late at night if a deployment flag goes red.

Lifestyle

Fannie lives in a converted Victorian terrace in Chorlton with her partner, a graphic designer. Their weekends are split between family outings to the Peak District and quiet evenings at home where they cook together and manage household logistics. She is an avid cyclist, riding 40 miles weekly along the Bridgewater Canal to clear her head, which doubles as her primary form of stress relief. Financially, she is conservative; the agency's profits are reinvested heavily into infrastructure before she takes significant dividends, ensuring a safety net for lean months. Socially, she maintains a tight circle of three other agency owners who meet monthly for coffee and honest industry talk, avoiding the hype-driven networking events common in London.

Work life

As the director of a six-person agency, Fannie splits her time equally between high-level strategy, client relationships, and hands-on architecture review. Her days begin with a deep dive into Jira tickets and GitHub pull requests, specifically scrutinizing how AI-generated code integrates with their proprietary starter repos. She manages a team of four developers and two junior designers, relying on a rigid 'AGENTS.md' style documentation process to ensure consistency across projects. The pressure comes from the need to deliver bespoke solutions quickly without burning out her staff or compromising on security for smaller clients. She spends her afternoons in meetings with local manufacturers and retailers, translating their vague operational needs into technical specifications, then stepping back in to manually verify the deployment pipelines before billing cycles close.

Relationships

Fannie is married to David, a creative director who understands the volatility of running a small business. They share the mental load of parenting, often discussing school schedules over Sunday breakfast. Her closest professional confidants are Sarah, who runs a design studio in Leeds, and Mark, a backend architect in Liverpool; these three meet every other Tuesday for 'unstructured' coffee chats where they vent about client scope creep. She has no strong relationship with distant relatives but is deeply embedded in the Manchester 'Maker' community, frequently attending local hackathons not to pitch, but to listen and learn about emerging hardware trends.

How they decide

Fannie operates on a 'verify then commit' basis. She rarely adopts a new tool based on marketing hype alone. Instead, she requires a clear demonstration of how a solution fits into her existing stack, specifically looking for documentation quality, API reliability, and pricing transparency. She tends to consult her two senior developers for technical validation before making any purchasing decision, effectively democratizing the buy-in. If a tool promises efficiency but lacks a clear migration path or if the vendor seems unstable, she will default to the manual method rather than risk breaking a live client project. She values peer recommendations from trusted networks over influencer endorsements.

How they sound

Fannie speaks with a distinct Mancunian accent that softens only when she's in formal boardroom settings. Her cadence is direct and efficient, rarely wasting words on pleasantries unless necessary for rapport building. She avoids jargon like 'disruptive' or 'paradigm shift,' preferring concrete terms like 'scalable,' 'maintainable,' and 'reliable.' When explaining technical constraints, she uses analogies related to construction or logistics. She is comfortable with silence during conversations, allowing space for others to formulate thoughts. She rarely says 'I don't know' without immediately following up with 'but I'll find out by tomorrow morning.'

Personality traits

  • methodical planner
  • pragmatic optimist
  • boundary-setter
  • detail-obsessed
  • efficient communicator
  • resilient under pressure
  • mentorship-oriented
  • tech-skeptical but curious
  • locally rooted
  • time-poor but focused

Goals

  • Achieve a stable £150k+ annual revenue run rate without increasing headcount beyond eight people.
  • Standardize the internal 'AI-to-production' workflow to reduce manual handoff time by 40%.
  • Launch a fully productized, subscription-based internal tool suite for non-tech SMEs.
  • Secure a long-term contract with a major regional retailer to stabilize cash flow.
  • Establish a mentorship program for junior female developers in the North West.

Problems & frictions

  • Fragmented tooling creates friction when moving from prototype to production deployment.
  • Difficulty scaling the quality assurance process as the volume of AI-generated code increases.
  • Balancing the need for rapid iteration with the requirement for strict data compliance.
  • Managing the cognitive load of switching between strategic leadership and detailed technical reviews.
  • Finding reliable, affordable third-party APIs for authentication and billing that integrate smoothly.
  • Preventing 'prototype rot' where experimental features never make it into the final product.

Values

  • client trust
  • operational clarity
  • practical innovation
  • sustainable pacing
  • financial prudence

Interests

  • agency operations
  • no-code and low-code tools
  • small business software
  • productized services
  • Manchester tech scene
  • cycling

Media habits

  • The Verge and TechCrunch for industry shifts
  • Local Manchester business forums
  • Twitter/X for developer tool updates
  • Spotify 'Deep Focus' playlists while coding
  • Substack newsletters on SaaS metrics

Questions & answers

Fannie Zemlak’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://stacknaut.com (Stacknaut) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Landing on Stacknaut, the core value proposition is immediately clear: turning coding agent outputs into production-ready software. What's a bit unclear is the exact nature of the "production SaaS repo" – is it a full boilerplate, or more of a framework? I'd also be curious to see pricing for the full product, beyond the free AGENTS.md kit. What would make me sign up is a clear demonstration of how it integrates with our existing starter repos and streamlines our current process of manual handoffs. The promise of reducing the 40+ hours of boilerplate work is compelling, especially with the explicit mention of auth, billing, and deployment handled. However, I'd need to see tangible evidence of its reliability and how it fits our bespoke client needs before committing.
    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.