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

David Thomas

David Thomas

solutions architect in pre-sales at a B2B software vendor

Full-depth AI personas

Why this persona fits the audience

Supports product demos in Paris for prospects reviewing API integrations; he keeps a small library of OpenAPI examples and a paid competitor mock server to mirror customer workflows during calls.

  • Age: 41
  • Location: Paris, France
  • Occupation: Solutions architect
  • Income: €110k
  • Education: MSc in Computer Science
  • Company size: Mid-sized (250-1000 employees)
  • Years in role: 7
“The elegance of a well-designed API is in its ability to connect systems seamlessly; my job is to make that connection undeniable for our clients.”

David Thomas, 41, is a seasoned Solutions Architect operating in the pre-sales space for a B2B software vendor headquartered in Paris. His career trajectory has been a deliberate climb through technical roles, culminating in his current position where he bridges the gap between complex software capabilities and client needs. He holds an MSc in Computer Science from a reputable French university, a foundation that underpins his deep technical acumen. David has been in his current role for seven years, a testament to his satisfaction and proficiency. His income of €110k reflects his specialized expertise and contribution to the company's revenue pipeline. He lives with his wife in Paris, sharing a life that balances professional ambition with personal interests. David’s professional life is characterized by meticulous preparation and a drive for technical perfection, particularly evident in his commitment to crafting flawless product demonstrations. He dedicates significant personal time to curating a comprehensive library of OpenAPI examples and maintains a subscription to a competitor’s mock server service, specifically to meticulously replicate customer workflows during client calls. This commitment to demo polish and technical credibility is paramount, as he understands that showcasing the product's integration capabilities with absolute realism is key to building customer confidence. Recently, he’s been investing more time in understanding the nuances of AI-driven data generation for mock APIs, recognizing its potential to further enhance demo realism and reduce preparation time, a constant challenge in his fast-paced role. He views his role not just as a technical consultant, but as a strategic partner in the sales process, aiming to preemptively address any technical concerns a prospect might have.

Background & daily life

A day in their life

David's typical weekday begins with an espresso and reviewing industry news before his commute on his bicycle to the Paris office. His morning is often consumed by back-to-back client calls, presenting tailored product demonstrations focused on API integrations. He meticulously prepares for these, referencing his OpenAPI examples and competitor mock server. Lunch is usually a quick affair, often at his desk while reviewing prospect requirements or refining demo scripts. Afternoons can involve internal meetings with sales or product teams, collaborating on technical proposals, or dedicating time to building and testing complex demo environments. He strives to leave by 7 PM to have dinner with his wife.

Lifestyle

David lives in a modern apartment in the 11th arrondissement with his wife, a graphic designer. Their routine revolves around busy workdays, often punctuated by late evenings preparing for crucial client presentations. Weekends are for unwinding: leisurely bike rides along the Seine, exploring new cafés, and catching up on jazz records. He’s disciplined with his finances, favoring long-term investments over impulsive purchases, but enjoys a good espresso machine for his home setup. Socially, he prefers smaller gatherings with close friends and colleagues over large parties.

Work life

As a pre-sales Solutions Architect, David's days are a dynamic blend of technical deep dives and client-facing engagement. He spends significant time tailoring demonstrations, ensuring every technical detail is flawless. This involves maintaining a robust personal library of OpenAPI specifications and custom code snippets, alongside a subscription to a competitor's mock server tool for realistic scenario replication. His pressure comes from consistently proving technical value to skeptical prospects and the tight deadlines for complex demo environments. He collaborates closely with sales representatives and product managers, often providing crucial feedback on feature roadmaps.

Relationships

David is married to Sophie, who grounds him and provides a creative counterpoint to his technical world. His professional network is strong, built on mutual respect with peers and a few trusted mentors. He occasionally seeks advice from former colleagues who have transitioned into product management roles.

How they decide

David is a research-heavy decision-maker. He systematically gathers information, compares options, and seeks validation from reliable sources or trusted peers. He prioritizes technical soundness and long-term viability, often weighing pros and cons meticulously before committing.

How they sound

Speaks with a measured, articulate cadence. Uses precise technical language but can simplify for non-technical audiences. Avoids overly casual slang, but might use industry-specific acronyms naturally. His tone is generally calm and confident, rarely raised, even when discussing complex challenges. He often uses phrases like 'From a technical standpoint...' or 'What we've found is...'.

Personality traits

  • meticulous
  • articulate
  • analytical
  • detail-oriented
  • proactive
  • patient
  • methodical
  • calm under pressure
  • curious

Goals

  • Achieve a senior architect role within his company
  • Contribute to open-source projects related to API standards
  • Maintain a healthy work-life balance despite demanding role
  • Become a recognized subject matter expert in API integration strategies
  • Travel more extensively with his wife

Problems & frictions

  • Balancing the need for highly customized demos with tight preparation timelines
  • Dealing with legacy systems and outdated API documentation from prospects
  • Constantly staying ahead of the rapidly evolving B2B software landscape
  • Managing stakeholder expectations across sales, product, and engineering
  • Finding reliable and efficient tools for generating realistic API mocks on the fly

Values

  • customer confidence
  • demo polish
  • technical credibility
  • efficiency
  • problem-solving

Interests

  • APIs
  • product marketing
  • coffee
  • jazz music
  • urban cycling

Media habits

  • TechCrunch and The Register for industry news
  • Follows API-specific blogs and developer forums
  • Listens to podcasts during commute (e.g., Syntax.fm, Software Engineering Daily)
  • Reads Hacker News daily
  • Watches technical deep-dive YouTube channels

Questions & answers

David Thomas’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Swagger Virtual Server (https://beeceptor.com/openapi-mock-server/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    What might stop me from trying Swagger Virtual Server this month is the need for more information on its integration with my existing mock server setup and the competitor tools I use. My current workflow involves meticulously crafting specific scenarios, and I'd need to be confident this new tool can replicate that fidelity. I also need to understand how it handles complex edge cases. Right now, I manually maintain my OpenAPI examples and use a paid competitor service for mirroring customer workflows during calls. Regarding pricing, I'm unsure what a fair monthly cost would be without a clearer understanding of its advanced features and support levels, but I would consider up to $50 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.