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

Betty Stehr

Betty Stehr

Early-stage CTO / cofounder

Full-depth AI personas

Why this persona fits the audience

One of two founders at a London startup shipping a compliance SaaS in Next.js. The team currently pays for a competitor boilerplate and extends it for auth, billing, and transactional email inside the same codebase.

  • Age: 35
  • Location: London, UK
  • Occupation: CTO and cofounder
  • Income: £110k salary + equity
  • Education: MSc Software Engineering
  • Company size: 2
  • Years in role: 2
“I don't build software to look good in a pitch deck; I build it so it doesn't break when the world actually starts using it.”

Betty Stehr is a 35-year-old software engineer turned cofounder, currently serving as the CTO of a London-based startup specializing in compliance SaaS. Holding an MSc in Software Engineering from Imperial College London, she entered the entrepreneurial space three years ago with a co-founder, driven by a frustration with the fragmented nature of regulatory technology. Their mission is to simplify compliance for mid-sized enterprises through a robust, automated platform built on Next.js. Despite being in the early stages, the company is already generating revenue, though the technical foundation is precarious. They are currently extending a purchased competitor boilerplate for authentication, billing, and transactional email, a decision made for speed but now creating significant maintenance overhead. Betty finds herself constantly wrestling with the limitations of this third-party code, often rewriting sections to ensure security and scalability. Her leadership style is defined by a relentless focus on reliability and measurable progress; she believes that technical debt is the silent killer of startups. Professionally, she is highly respected for her ability to translate complex compliance requirements into clean, maintainable code. However, the pressure of wearing both the hat of architect and chief debugger is mounting. She is actively researching ways to migrate away from the boilerplate to a custom solution, a move that will require a temporary slowdown in feature delivery but promises long-term stability. Personally, Betty is grounded by her disciplined running routine and a partnership that understands the demands of building a company. She views money not as a status symbol but as fuel for execution, and her ultimate goal is to build a product that stands the test of time, even if it means moving slower than her competitors.

Background & daily life

A day in their life

The alarm goes off at 5:30 AM. Betty wakes up instantly, makes black coffee, and heads out for a 45-minute run along the canal, listening to a podcast on regulatory changes. By 7:30 AM, she is back, showered, and logging into Slack. Her first hour is dedicated to checking overnight server alerts and responding to critical customer tickets. At 9:00 AM, she joins a stand-up with her co-founder, where they review the previous day's deployment metrics and discuss a blocker in the payment gateway integration. The bulk of her morning is spent in VS Code, refactoring a module to decouple the email service from the auth logic, a task that requires careful attention to edge cases. Lunch is eaten quickly at her desk while reading industry news. Afternoon meetings involve discussing Q3 roadmaps and preparing a demo for a potential investor. Late afternoon is reserved for deep work on the new infrastructure plan, followed by a final review of pull requests before leaving the office by 7:00 PM to meet friends or continue running.

Lifestyle

Betty lives in a converted warehouse flat in Shoreditch, a space that doubles as a secondary workspace when the office is closed. Her routine is rigidly structured around her 5:30 AM runs along the Regent's Canal, a non-negotiable habit that grounds her before the workday begins. She eats healthily but pragmatically, often prepping meals on Sundays to avoid decision fatigue during the week. Financially, she balances a high income with a cautious approach to spending; while she invests heavily in her career, she avoids luxury purchases that don't offer tangible utility or long-term value. Socially, she maintains a tight-knit circle of fellow founders and engineers, preferring deep conversations over large networking events. Her weekends are split between running longer distances and occasional board game nights with her partner.

Work life

As the sole technical lead alongside her co-founder, Betty's day is a constant toggle between high-level architectural strategy and gritty debugging. The current setup involves maintaining a paid competitor boilerplate, which has become a source of friction due to its opaque internals and bloated dependencies. She spends mornings reviewing system logs and product analytics to ensure the compliance engine meets client SLAs, then shifts to code reviews and sprint planning by early afternoon. The pressure is immense; with only two people, any outage or bug fix directly impacts revenue and trust. She advocates for strict documentation and measurable milestones, often finding herself mediating between her co-founder's product vision and the reality of their limited engineering bandwidth.

Relationships

Betty shares her life with a partner who works in digital marketing; they navigate the highs and lows of startup life together, often debriefing after dinner. Her professional network is concentrated in London's fintech and SaaS scene, where she relies on peer advice more than formal mentorship. She trusts her co-founder implicitly regarding business strategy but remains the primary gatekeeper of technical decisions. Outside of work, she values relationships that are low-drama and high-trust, often avoiding colleagues who lack operational discipline.

How they decide

Betty approaches decisions through a lens of risk mitigation and data validation. She rarely acts on impulse, preferring to gather evidence, run small-scale experiments, and consult historical metrics before committing resources. She is skeptical of 'magic bullet' solutions and demands transparency in how tools integrate with existing systems. While she values speed, her default mode is cautious iteration, ensuring that every change aligns with long-term reliability goals rather than short-term wins.

How they sound

Betty speaks with a crisp, articulate British accent, favouring precise terminology over jargon. Her cadence is steady and deliberate, pausing frequently to ensure clarity rather than rushing to fill silence. She uses phrases like 'let's quantify that' or 'what's the failure mode?' to ground abstract discussions. She avoids hyperbole, emotional appeals, or vague promises, preferring concrete data points and actionable steps. In conversation, she listens intently, often summarizing what others say before offering her perspective.

Personality traits

  • Methodical
  • Direct communicator
  • Process-oriented
  • Pragmatic optimist
  • Detail-obsessed
  • Time-blocked
  • Analytical
  • Resilient under pressure
  • Data-driven
  • Systematically curious

Goals

  • Refactor the legacy boilerplate into a custom, lightweight core within the next fiscal year
  • Achieve SOC 2 Type II certification for the compliance SaaS platform
  • Scale the engineering output to support a sales-led expansion without adding headcount immediately
  • Establish a clear exit strategy or acquisition target within five years
  • Maintain a sustainable work-life balance to prevent burnout during the Series A push

Problems & frictions

  • Technical debt accumulating rapidly due to reliance on an external, unmodifiable boilerplate
  • Difficulty isolating billing logic from the main application flow, causing deployment risks
  • Limited bandwidth to implement custom features requested by enterprise clients
  • Inconsistent documentation from the third-party provider hindering team onboarding
  • Pressure to deliver 'production-ready' features while managing fragile legacy code
  • Balancing immediate revenue needs against long-term architectural health

Values

  • reliability
  • team alignment
  • measurable progress
  • technical debt management
  • operational clarity

Interests

  • startup ops
  • product analytics
  • running
  • infrastructure architecture
  • regulatory tech trends

Media habits

  • Weekly 'Startup School' podcast during morning runs
  • Engineering blogs on Vercel and PostHog
  • LinkedIn updates from other UK SaaS founders
  • Substack newsletters on compliance automation
  • Twitter/X threads on Next.js performance

Questions & answers

Betty Stehr’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying NextSaasPilot (https://www.nextsaaspilot.com/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    While the idea of a pre-built boilerplate is appealing, especially given our current situation with the competitor's product, what gives me pause is the 'lifetime updates' claim. We've encountered issues with previous boilerplates where "lifetime" meant limited support or updates that weren't compatible with newer Next.js versions. We're currently spending a significant amount of time refactoring and decoupling our email and auth logic because the existing solution is too rigid. I'd need to see concrete evidence of how adaptable this is and what the actual update cadence and support structure looks like before considering a switch. We're currently paying a competitor an undisclosed amount, but if this offered genuine flexibility and long-term maintenance, I might consider up to $49 per month.
    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.