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

Lazare Lacroix

Lazare Lacroix

B2B startup cofounder using a competitor

Full-depth AI personas

Why this persona fits the audience

Cofounds a four-person B2B API startup in Paris. Their website chat is already handled through Crisp, and he checks incoming conversations from a Discord webhook because the whole team works in Discord daily.

  • Age: 31
  • Location: Paris, France
  • Occupation: B2B API startup cofounder
  • Income: €95k
  • Education: MSc in Engineering
  • Company size: 4
  • Years in role: 2
““I’d rather debug a failing API at 3 AM than listen to another founder complain about ‘hustle.’””

Lazare Lacroix grew up in Toulouse, where his father was an electronics engineer and his mother a high school math teacher. His perfectionist tendencies emerged early - he custom-built his first PC at 14 using salvaged parts. After earning an MSc in Computer Engineering from CentraleSupélec, he worked two years as a backend architect at a scale-up before cofounding his current company, which builds developer-friendly API interfaces. The startup was born from his frustration with the clumsy workflows he saw at large corporations. Now, at 31, he splits his time between coding sessions and sales calls from their minimalist office in Le Marais. He’s particular about tools - his team’s Discord server has 40+ channels with strict naming conventions - and recently migrated from Crisp to a competitor after crunching data on response times. Lazare avoids investor meetings unless absolutely necessary, preferring to focus on product-market fit. His biggest stressor currently is balancing engineering debt with client feature requests. He measures success not in valuation but in the number of engineers who say ‘this API finally makes sense’. His relationship with money is pragmatic: he pays himself €5k/month before reinvesting profits, and the only credit card in his wallet is a Revolut metal card used solely for company expenses. Status symbols hold no interest, but he takes pride in his team’s perfect uptime metrics from last quarter. His only guilty pleasure? The €500 Aeron chair he rationalized as ‘L4 spinal support’.

Background & daily life

A day in their life

5:45 AM: Lazare’s alarm syncs with the weather app. A light rain means he swaps the road bike for a commuter. 6:30 AM: Two shots of espresso at his kitchen bar, then 30 minutes reviewing code pull requests via Discord mobile. 7:15 AM: 10km ride to the office space in Le Marais, stopping at a boulangerie for pistachio financiers. 8:00 AM-12:00 PM: Lead sprint planning with his team, arguing vehemently but concisely about microservices architecture. 12:00 PM: Lunch is a Girard coffeebar sandwich eaten at his desk while reviewing analytics dashboards. 1:00 PM: Forced walk to Jardin des Rosiers to reset - he hates outdoor meetings but needs the sunlight. 2:30 PM: Headphones on, working on a problematic rate limiting algorithm. 4:00 PM: Reacts to a customer crisis through Discord - a production outage from their chat integration partner, causing a tense 90-minute war room. 6:00 PM: Calls it a day, stopping at a Harry’s Bar for a whisky with his cofounder. 7:30 PM: Reads Indie Hackers forums while his partner cooks dinner. 10:30 PM: Asynchronous engineering discussion via Discord threads before bed.

Lifestyle

Lazare shares a sunlit apartment in the 11th arrondissement with his partner, a UX designer who works remotely. They split chores meticulously - he handles groceries and grocery, she manages weekends. He starts mornings with a precise espresso ritual (La Pavoni machine, single-origin beans, 93°C water) before a 10km bike commute to the office. Health-wise, he skips gyms for city cycling and swim sessions at Piscine Joséphine Baker. Financially cautious, he auto-transfers 20% of salary to a tech ETF and only splurges on high-end headphones (Sennheiser HD 800S) after 6 months of research. Social life revolves around Discord engineering channels and occasional meetups at Le Comptoir Général. He avoids late nights but makes exceptions for key networking dinners in Belleville.

Work life

As cofounder of a four-person B2B API builder, Lazare’s days oscillate between architectural decisions and customer code reviews. His team operates entirely in Discord, using structured voice channels for standups and threads for async debugging. He recently migrated from Crisp to their current chat solution (a competitor) after running A/B tests on response efficiency. Current pain points include integrating Slack webhooks for enterprise clients and managing rate limits without extra engineering. He schedules 4-hour deep work blocks where he bangs away at code, wearing noise-canceling headphones to block out Parisian street noise. Major pressures include avoiding scope creep with Marché des Capuchines and juggling sales ledges with infrastructure reliability. He prides himself on never letting an engineering request sit unanswered overnight.

Relationships

Lazare sees his three cofounders as his closest collaborators and confidants, bonded over late-night debugging sessions. His « godfather » in tech, a former CTO at Token, occasionally advises him over espresso. His partner grounds him, though she teases his tendency to analyze personal decisions like product roadmaps. His network includes fellow founders from Station F, but he’s selective about who he lets into their Discord workspace. He maintains a patchy relationship with his older brother, a civil servant who doesn’t understand startups.

How they decide

Research-heavy but decisive - he’ll spend 12 hours benchmarking tools, then commit with minimal regret. Prefers six 15-minute customer interviews over a single lengthy survey. Dislikes committee-style decision-making but values his cofounders’ input. When pressured, defaults to ‘no’ until proven otherwise. Rarely changes his mind post-commitment unless presented with irrefutable data.

How they sound

Speaks in crisp, clipped French with frequent English sprinkled in during technical discussions. Uses precise analogies (e.g., “This integration is like duct tape on a pressure valve”). Avoids vague terms like ‘kind of’ or ‘maybe’. Pauses thoughtfully after criticism. Has a dry sense of humor that often misses its mark. Prefers direct questions over open-ended ones. Occasionally defaults to engineering jargon but always asks for clarification when unsure. His partner describes his speaking style as ‘a debate moderator running out of time’.

Personality traits

  • Process-driven but impatient with waste
  • Prefers async communication for deep work
  • Quick to trust but slow to forgive when trust is broken
  • Obsessed with removing friction from workflows
  • Takes pride in the team's Discord culture
  • Hates unnecessary meetings but enjoys deep technical debates
  • Trades sleep for momentum when the startup is in sprint mode
  • Reflects on workdays to tighten systems
  • Enjoys mentoring younger engineers but hates small talk
  • Struggles with work-life balance during fundraising cycles

Goals

  • Achieve 100 paying customers by year-end
  • Improve their API’s uptime to 99.99%
  • Build a product analytics dashboard that actually informs decisions
  • Train a new intern to handle tier-1 customer support
  • Save €50k in operational costs by Q3 2024

Problems & frictions

  • Customers frequently ask for features they don’t have bandwidth to build
  • Discord’s mobile interface makes urgent debugging inefficient
  • Their current chat solution’s UI feels

Values

  • structure
  • speed
  • team alignment
  • autonomy
  • efficiency

Interests

  • product analytics
  • espresso
  • tech meetups
  • French cycling culture
  • minimalist design

Media habits

  • TechCrunch for news
  • Indie Hackers for founder chats
  • Discord for work
  • Instagram for cycling inspiration
  • Spotify for instrumental playlists while working

Questions & answers

Lazare Lacroix’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Deskcord (https://deskcord.chat) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Deskcord better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, we use Crisp for our live chat, integrated through a Discord webhook. It works fine for us because the entire team operates in Discord daily, and Crisp's interface is straightforward. The workflow is seamless: visitors chat on our site, and their messages appear as threads in Discord, which we respond to directly. The main benefit of Deskcord would be its native Discord integration, potentially reducing latency in responses since everything is handled within the same platform. However, I’m not sure if Deskcord offers the same granular control over notifications and thread management that we’ve set up with Crisp. If Deskcord can match or improve our response times and fit into our existing Discord channels without additional setup, it could be worth switching. That said, we’re cautious about changing tools unless there’s a clear productivity gain. Right now, we’re comfortable with Crisp, but if Deskcord were free or very low-cost, we might trial it. Beyond that, it’d have to justify the financial overhead. As for pricing, I’d be hesitant to pay more than $5/month for something that essentially replicates our current system, unless it proves significantly better in usability or speed.
    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.