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

Marta Ratke

Marta Ratke

Two-person product studio co-founder

Full-depth AI personas

Why this persona fits the audience

She co-runs a 2-person studio in London that is turning one client's internal reporting idea into a SaaS prototype in Rails. The current stack already includes a competitor starter kit, a shared Linear board, and a contractor who handles front-end polish.

  • Age: 39
  • Location: London, UK
  • Occupation: Co-founder, product studio
  • Income: £110k salary equivalent plus studio profit
  • Education: MEng Software Engineering
  • Company size: 2
  • Years in role: 4
“In this business, the only thing that matters is whether the code you ship actually solves the problem without breaking tomorrow.”

Marta Ratke is a seasoned software engineer turned entrepreneur, currently steering a nimble two-person product studio in the heart of London's tech scene. With an MEng in Software Engineering from Imperial College London, she spent eight years in corporate roles building enterprise-grade systems before launching her own venture four years ago. Driven by a desire for autonomy and a belief in the power of craftsmanship, she now partners with a single co-founder to deliver bespoke B2B software solutions. Her current primary focus is transforming a client's internal reporting concept into a scalable SaaS prototype using Ruby on Rails. The studio operates with surgical precision, leveraging a competitor's starter kit as a foundation while maintaining a rigorous development workflow managed via a shared Linear board. Marta personally oversees the backend architecture, ensuring the system is robust enough to handle complex data relationships, while coordinating with a specialized contractor to refine the user interface. Despite her technical expertise, she prides herself on being a pragmatic strategist, often making tough calls to cut scope or delay features to ensure quality. She views her role not just as a coder, but as a guardian of client trust, believing that reliability is the ultimate currency in the software world. Her life outside work is grounded in routine and nature; she is a dedicated dog owner who finds solace in the daily rhythm of urban cycling and long walks through London's parks. Financially, she balances her £110k equivalent income with careful reinvestment strategies, aiming to build a sustainable business that can eventually support a larger team without sacrificing the intimate, high-quality service model she cherishes. Marta represents the modern solo-founder archetype: technically competent, ethically driven, and relentlessly focused on delivering tangible value.

Background & daily life

A day in their life

Marta wakes at 6:30 AM, immediately brewing pour-over coffee while checking the weather and her dogs' feed schedule. By 7:15 AM, she is out the door, cycling through Shoreditch to avoid the Tube crowds, listening to a tech podcast or just enjoying the silence. She arrives at her home office by 8:45 AM, logging into her terminal first thing to review overnight CI/CD pipeline logs and check for any server alerts. From 9:00 to 12:00 PM, she engages in deep work, refactoring the authentication module for the client's new reporting dashboard. At 12:30 PM, she takes a long walk with her dogs, using this time to mentally decompress and plan the afternoon's client call. The afternoon is reserved for asynchronous communication, reviewing PRs from the front-end contractor, and preparing slide decks for the upcoming stakeholder meeting. She closes her laptop promptly at 5:30 PM, never bringing work home, spending the evening cooking dinner, reading fiction, or watching films with her partner. Before bed, she journals three things she learned that day and sets priorities for tomorrow.

Lifestyle

Marta lives in a converted warehouse space in East London, surrounded by exposed brick and the hum of the city. Her mornings are non-negotiable: 6:30 AM wake-up, followed by a brisk run or cycle to work, often stopping at a local independent coffee shop before the commute. She prioritizes health through consistent movement rather than intense gym sessions, often fitting short yoga flows into her lunch break. Financially, she practices disciplined frugality despite her comfortable income, reinvesting heavily back into the business while maintaining a robust emergency fund. Socially, she is selective, preferring deep conversations with a small circle of trusted peers over large networking events. Her weekends are split between dog walking in Hampstead Heath and hands-on tinkering with personal hardware projects, always seeking to disconnect from screens to recharge her creative battery.

Work life

Her days are a tightrope walk between strategic oversight and deep technical execution. As the primary architect, she spends her early hours writing core Ruby code, ensuring the backend logic for their client's reporting engine is bulletproof. By mid-morning, she shifts to managing the contractor handling the front-end, reviewing pull requests and clarifying UX requirements via their shared Linear board. Afternoons are dominated by client calls, where she translates vague business needs into concrete technical specifications without over-promising. The pressure is constant but manageable; the two-person dynamic means there is no one else to hide behind, requiring her to wear every hat from CTO to project manager. She values clean code and reliable deployment pipelines above all, viewing technical debt as a betrayal of client trust.

Relationships

Marta's support system is a blend of professional peers and close personal friends. She has a weekly sync with her co-founder, a former university classmate, to align on business strategy and prevent burnout. Her network is dense with other London-based indie makers, often met at local meetups or online Ruby communities. She relies heavily on her partner for emotional grounding and household management, allowing her to focus intensely during work blocks. While she is friendly with many, she maintains strict boundaries between her professional persona and private life, rarely discussing work details with family to ensure her evenings remain truly restful.

How they decide

Marta is a deliberate, evidence-based decision-maker who avoids impulse buys. She typically gathers data from multiple sources, comparing technical documentation, community feedback, and peer recommendations before committing to any new tool or vendor. She values transparency and clear pricing models, often running small-scale proofs-of-concept to validate utility before full adoption. Once she identifies a solution that meets her rigorous standards for reliability and craftsmanship, she moves quickly to integrate it, preferring to stick with a robust system rather than constantly chasing the latest shiny object. Her decisions are driven by long-term value and risk mitigation rather than short-term convenience.

How they sound

Her speech is precise, articulate, and efficient, reflecting her engineering background. She tends to speak in complete sentences, avoiding filler words like 'um' or 'like'. She uses industry-standard terminology fluently but explains complex concepts in plain English when speaking to non-technical stakeholders. There is a calm, steady cadence to her voice, rarely raising it even in moments of stress. She avoids hyperbole, preferring qualifiers like 'likely', 'potentially', or 'based on the data'. She is direct about timelines and capabilities, often saying 'we can't do that yet' with a polite but firm tone, valuing honesty over appeasement.

Personality traits

  • Methodical
  • Direct communicator
  • Analogous thinker
  • Process-oriented
  • Steady under pressure
  • Pragmatic optimist
  • Detail-obsessed
  • Collaborative leader
  • Time-bound
  • Ethically driven

Goals

  • Achieve a stable monthly recurring revenue (MRR) that allows hiring a third full-time developer within 18 months.
  • Complete the current client's reporting SaaS with zero critical bugs at launch.
  • Build a proprietary library of Rails components that can be reused across future client projects to reduce setup time by 40%.
  • Establish a reputation as a 'trusted advisor' for B2B founders, leading to inbound referrals rather than cold outreach.
  • Maintain a 35-hour work week consistently to preserve long-term mental health and family time.

Problems & frictions

  • Balancing the immediate need for feature delivery with the long-term necessity of refactoring legacy code.
  • Finding reliable, high-calibre freelance contractors who understand the nuances of modern Rails architecture.
  • Managing scope creep from clients who constantly request new features during the prototyping phase.
  • The cognitive load of switching contexts between coding, client management, and business administration.
  • Limited bandwidth to experiment with new technologies due to the pressure of fixed-scope contracts.
  • Keeping the studio financially liquid while waiting for milestone payments from enterprise clients.

Values

  • reliability
  • client trust
  • pragmatism
  • craftsmanship

Interests

  • Rails startups
  • B2B software
  • product strategy
  • dog walks
  • urban cycling
  • industrial design history

Media habits

  • Ruby Weekly newsletter
  • Lobsters discussion threads
  • Local indie maker podcasts
  • Twitter/X for engineering discourse
  • Linear community updates
  • Substacks on B2B SaaS metrics

Questions & answers

Marta Ratke’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Lightning Rails (https://lightningrails.com): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    A one-time purchase for $189 seems like a reasonable starting point for something that could save significant development time. If it truly delivers on shipping an app in hours rather than weeks, especially with the AI integration, I'd consider it a 'no-brainer' around the $150-$200 mark. Anything significantly above $300 for a one-time purchase would make me pause. I'd expect a robust, well-documented boilerplate that handles the core SaaS infrastructure seamlessly, plus the AI agent functionality to be genuinely helpful and not just a gimmick. I'm not looking for a monthly subscription for this type of tool; I'd rather pay a higher one-time fee for lifetime access.
    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.