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

Romane Martin

Romane Martin

Freelance software consultant

Full-depth AI personas

Why this persona fits the audience

Works independently for SMEs and agencies, producing application architecture diagrams and delivery flowcharts as part of consulting handoffs. Uses draw.io, PowerPoint, and spreadsheet-based notes between client calls.

  • Age: 36
  • Location: Paris, France
  • Occupation: Independent software consultant
  • Income: €72,000 annual self-employment income
  • Education: Master's in Computer Science
“The beauty of software isn't just in its code, but in how clearly we can explain its structure and purpose to those who build it.”

Romane Martin, 36, is an independent software consultant based in Paris, France. Holding a Master's in Computer Science, she carved out her niche by focusing on the often-overlooked but critical aspect of software project clarity: documentation. Romane works primarily with small to medium-sized enterprises (SMEs) and digital agencies, helping them visualize their application architectures and delivery workflows. Her expertise lies in translating complex technical concepts into easily digestible diagrams and flowcharts, which serve as crucial handoffs between client stakeholders and development teams. She is highly conscientious, meticulously organizing her work using draw.io for diagrams, PowerPoint for presentations, and detailed spreadsheets for notes and client communication, all managed between a demanding schedule of client calls. Romane values her independence immensely, cherishing the autonomy her freelance career provides. This allows her to select projects that align with her interest in user experience and practical, deliverable solutions. Her income of €72,000 annually reflects her specialized skills and consistent demand. Recently, she decided to invest in a higher-resolution monitor to improve her efficiency in creating detailed diagrams, a small but significant step towards optimizing her workflow. She also recently declined a larger, more complex project that promised higher pay but lacked clear scope, prioritizing her value of client clarity and manageable workload over sheer volume. Romane is driven by a desire to bring order and understanding to the often-chaotic world of software development, believing that clear documentation is as vital as elegant code. Her approach is grounded in practicality, ensuring that the diagrams she produces are not just aesthetically pleasing but genuinely useful for the development lifecycle. She sees her work as a bridge, connecting business needs with technical execution through visual clarity.

Background & daily life

A day in their life

Romane's typical weekday begins around 7:30 AM with a brisk walk along the Seine, followed by a strong espresso and a review of her calendar. Her mornings are usually packed with client calls, where she actively listens, takes detailed notes in a spreadsheet, and clarifies project scope. Afternoons are dedicated to deep work: meticulously crafting application architecture diagrams in draw.io, refining delivery flowcharts in PowerPoint, and organizing her findings. She breaks for a simple lunch, often a quiche from a local boulangerie. Late afternoon might involve a quick sync with a developer team she's consulting for, ensuring her diagrams align with their implementation plans. Evenings are for winding down, perhaps reading a novel by Proust or catching up on a tech podcast, before preparing for the next day's challenges.

Lifestyle

Romane lives in a cozy, compact apartment in the 11th arrondissement of Paris. She cherishes the convenience of living close to her workspace and local cafes. Her daily routine includes a morning jog around the nearby Canal Saint-Martin, followed by a hearty breakfast of croissants and café au lait. She spends her afternoons immersed in work, punctuated by short breaks to sip espresso at a nearby bistro. In the evenings, she often indulges in French literature, finds time to travel occasionally, and keeps up with her fitness routine at the gym.

Work life

Romane's workdays are structured yet flexible, beginning early with a review of her schedule and emails. She often starts with a client call or a meeting with potential clients to understand their needs. The core of her work involves translating complex technical requirements into clear, visual documentation. This means spending significant time in draw.io, meticulously crafting architecture diagrams and flowcharts, and using spreadsheets to organize notes and project details. She juggles multiple projects simultaneously, each requiring a deep dive into different business domains and technical stacks. The pressure to deliver precise, understandable documentation for handoffs is constant, as it directly impacts the client's development teams.

Relationships

Romane maintains a close circle of friends, mostly fellow freelancers and tech professionals she met through industry events and online communities. Her parents, retired teachers living in Lyon, are supportive but don't fully grasp the nuances of her freelance career. She values their encouragement but relies on her peers for professional advice and commiseration.

How they decide

Romane is a methodical and research-oriented decision-maker. She weighs pros and cons carefully, often creating comparison tables or lists. While she values peer recommendations, she ultimately trusts her own analysis and experience. She is not impulsive and prefers to understand the full implications before committing to a course of action.

How they sound

Romane speaks with a clear, measured cadence, her French accent subtly present. She uses precise, professional language, avoiding slang or overly casual expressions, especially during client interactions. She tends to explain concepts thoroughly, ensuring her listener understands the technical details without being overwhelmed. She might pause to gather her thoughts before answering complex questions, demonstrating her analytical approach.

Personality traits

  • methodical
  • analytical
  • patient
  • empathetic
  • organized
  • detail-oriented
  • independent
  • pragmatic

Goals

  • To build a reputation as the go-to consultant for clear software architecture documentation in the Parisian SME scene.
  • To achieve greater work-life balance by optimizing her workflow and reducing administrative overhead.
  • To travel to Japan and experience its unique blend of tradition and technology.
  • To contribute to open-source projects related to developer tooling.
  • To maintain her financial independence and security.

Problems & frictions

  • The time-consuming nature of manually creating detailed diagrams and flowcharts.
  • Ensuring consistency and accuracy across documentation for diverse client projects.
  • Managing client expectations regarding the complexity and scope of technical documentation.
  • The constant need to stay updated with evolving software development methodologies and tools.
  • Balancing client demands with personal time and avoiding burnout.

Values

  • client clarity
  • independence
  • practical delivery

Interests

  • user experience
  • travel
  • French literature

Media habits

  • reads tech blogs and news sites
  • watches TED talks on UX
  • listens to French audiobooks

Questions & answers

Romane Martin’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying AI Diagram Maker (https://www.aidiagrammaker.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).

    The primary concern for me would be the accuracy and consistency of AI-generated diagrams. Today, I meticulously build my diagrams in draw.io, ensuring every detail is precisely as needed for client handoffs. While the promise of converting text to diagrams in seconds is appealing, I worry about the AI misinterpreting complex requirements or producing diagrams that lack the nuanced clarity my clients depend on. I would need to see robust examples of how it handles intricate application architectures before considering a subscription. I would be willing to pay up to $20 per month, but this is contingent on a thorough trial demonstrating its reliability.
    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.