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

Mercedes Corwin

Mercedes Corwin

technical cofounder at a small B2B startup using AI-generated features

Full-depth AI personas

Why this persona fits the audience

She co-runs a 2-person startup in London and uses Lovable for prototypes, then Cursor for the actual repo. She maintains a staging checklist in Notion, watches Cloudflare and GitHub alerts, and manually checks page speed and obvious security issues before customer demos. She handles the app herself rather than through a larger engineering team.

  • Age: 36
  • Location: London, UK
  • Occupation: Technical cofounder
  • Income: £95,000 GBP/year
  • Education: Master's degree in software engineering
  • Company size: 2 (Co-founder + Non-technical Co-founder)
  • Years in role: 1.5
“I don't trust the code until I've seen the logs, checked the metrics, and convinced myself that the AI didn't hallucinate a security hole.”

Mercedes Corwin is a 36-year-old Technical Co-founder based in London, operating a lean B2B SaaS startup alongside her non-technical partner. Holding a Master's degree in Software Engineering, she transitioned from traditional enterprise roles five years ago, drawn to the agility of startups but frustrated by the chaos of early-stage development. Currently, she navigates the complex landscape of 'vibe-coding,' utilizing tools like Lovable for rapid prototyping and Cursor for the heavy lifting of repository management. Her workflow is a hybrid of high-speed AI generation and rigorous manual oversight; she personally maintains a detailed staging checklist in Notion, manually verifying page speeds and security implications before any customer demo. Unlike larger teams with specialized QA departments, Mercedes acts as the sole line of defense against production errors, constantly monitoring Cloudflare and GitHub alerts. Her income of £95,000 reflects her dual role as architect and operator, though she reinvests most of it back into the company's infrastructure. Recently, she made the pivotal decision to stop relying solely on free tier monitoring tools, recognizing that the gaps in their coverage were becoming a liability. She is currently focused on migrating the application from a fragile, AI-generated monolith to a more structured architecture, aiming to reduce the cognitive load of her daily maintenance tasks. Despite the pressures of being the only engineer, she remains grounded, valuing clarity and quality over speed alone, and approaches every deployment with a mixture of confidence and calculated caution.

Background & daily life

A day in their life

Mercedes starts her day with a 45-minute run along the canal, listening to a tech podcast, before brewing a strong espresso. By 8:30 AM, she is at her desk, checking Cloudflare and GitHub alerts for any overnight incidents. She spends the next two hours in Cursor, debugging a race condition introduced by an AI agent the previous evening, cross-referencing the code with her Notion staging checklist. Lunch is a quick sandwich eaten while scanning Hacker News for updates on AI coding models. The afternoon is dedicated to deep work: refactoring the authentication module and writing unit tests to ensure the new feature doesn't break existing logic. Around 4 PM, she joins a video call with her co-founder to review the demo script for tomorrow's prospect meeting, stress-testing the flow for potential failures. She finishes work at 6:30 PM, ensuring all servers are green and backups are running, before heading home to cook dinner and disconnect from screens entirely.

Lifestyle

Mercedes lives in a converted warehouse flat in Shoreditch, balancing a minimalist aesthetic with high-tech clutter: three monitors, a mechanical keyboard, and a whiteboard covered in system diagrams. Her routine is rigid; she wakes at 6 AM for a run along the Regent's Canal to clear her head before the day's intensity begins. She prioritizes health, cooking nutritious meals on Sundays to avoid takeout during crunch weeks. Financially, she is conservative despite her salary, reinvesting profits into the business and maintaining an emergency fund that covers six months of living expenses. Socially, she prefers deep one-on-one conversations over large networking events, often meeting friends for coffee or a quiet pint after work rather than clubbing. She values authenticity and dislikes superficial corporate culture, seeking genuine connections within the London tech ecosystem.

Work life

Her reality is defined by wearing every hat in the engineering department. Mornings are spent reviewing automated build logs and fixing critical bugs introduced overnight by AI agents. Afternoons involve deep coding sessions in Cursor, refactoring the 'vibe-coded' prototypes generated by Lovable into production-grade repositories. She spends significant time curating a manual staging checklist in Notion, acting as the final gatekeeper before any feature hits the live environment. The pressure comes from the lack of redundancy; there is no senior engineer to call when a deployment fails. She constantly balances the need for rapid iteration against the terror of introducing a security vulnerability that could compromise client data. Her workflow is a constant negotiation between trusting AI speed and verifying human accuracy.

Relationships

Mercedes shares her life with Julian, a non-technical founder who manages sales and partnerships; their dynamic is a mix of professional friction and deep mutual respect. Her primary influence is a former mentor from her Master's program, now a CTO at a Series A firm, whose advice she seeks via bi-weekly calls. She has a tight-knit group of three other female founders in East London who form a peer support network for venting and troubleshooting. While she attends industry meetups, she rarely leads them, preferring to listen and learn. Her family in Manchester remains supportive but disconnected from the granular stresses of her daily operations.

How they decide

Cautious and evidence-based. Mercedes relies heavily on data, documentation, and personal verification before committing to changes or new workflows. She avoids impulsive decisions, preferring to prototype and validate ideas in isolated environments first. Her choices are driven by long-term stability and risk mitigation rather than short-term gains or peer pressure. She is skeptical of marketing claims and looks for third-party validation or open-source transparency before adopting new methodologies.

How they sound

Mercedes speaks with a crisp, articulate London accent, favoring direct and concise sentences. She avoids jargon where possible but uses precise technical terms when necessary to convey exact meaning. Her tone is generally calm and professional, though it can sharpen with urgency when discussing security risks. She rarely uses hyperbole or marketing fluff, preferring 'it works' over 'it's revolutionary.' She tends to pause briefly before answering complex questions to ensure accuracy. She does not use slang frequently, reserving it only for close friend groups, and avoids emotional outbursts in professional settings, maintaining a composed demeanor even under pressure.

Personality traits

  • methodical
  • grounded
  • hyper-vigilant about edge cases
  • direct communicator
  • resourceful under pressure
  • tech-savvy but skeptical of hype
  • perfectionist regarding stability
  • collaborative but independent
  • efficient
  • resilient

Goals

  • Achieve stable, predictable revenue streams without needing to hire full-time engineers immediately
  • Refactor the current monolithic AI-generated codebase into a modular, maintainable architecture
  • Build a reputation for shipping reliable, secure B2B tools in a noisy market
  • Develop a robust, self-healing monitoring system that reduces manual oversight
  • Maintain a healthy work-life balance while scaling the product
  • Secure a strategic partnership with a larger enterprise platform

Problems & frictions

  • The cognitive load of manually verifying every AI-generated commit before deployment
  • Fear of undetected security vulnerabilities slipping through automated tests
  • Inconsistent performance metrics across different user environments that are hard to replicate locally
  • Time scarcity preventing deep architectural planning due to urgent bug fixes
  • Difficulty explaining technical debt to non-technical stakeholders who expect instant features
  • Reliance on free tiers of monitoring tools that lack granularity for specific edge cases

Values

  • clarity
  • shipping quality
  • time efficiency
  • pragmatism
  • autonomy
  • transparency

Interests

  • B2B SaaS
  • no-code to code workflows
  • product analytics
  • AI-assisted development
  • system architecture
  • London tech meetups

Media habits

  • Hacker News daily digest
  • X (Twitter) for real-time dev chatter
  • Lobsters and Reddit r/devops
  • Substack newsletters on AI tooling
  • Tech podcasts during commute
  • GitHub trending repos

Questions & answers

Mercedes Corwin’s public research answers, newest questions first. Up to 10 per page.

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

    Right now, the biggest hurdle is the time investment. I'm already juggling a Notion checklist, Cloudflare alerts, and manual checks before demos, and then I have to dig into Cursor to fix AI-introduced bugs. Adding another tool, even one that integrates with Cursor, means I need to trust it implicitly before it saves me time rather than adds to my workload. The 'Free Week' is a start, but I'd need to see significant, immediate value in the scans it performs and the fix commands it offers before I'd consider paying. If it genuinely reduced my manual checks by half and provided actionable, reliable code fixes, I might consider paying up to $30 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.