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

Caribert Berger

Caribert Berger

Freelance developer who has never paid for a starter

Full-depth AI personas

Why this persona fits the audience

He builds client MVPs for founders in Paris, often in Rails, and is currently turning one client's AI support-ticket helper into a sellable web app. He works alone and usually starts from his own checklist, GitHub snippets, and free gems rather than any paid boilerplate.

  • Age: 33
  • Location: Paris, France
  • Occupation: Freelance web developer
  • Income: €62k
  • Education: Master's in Information Systems
  • Company size: Sole proprietorship (one-man band)
  • Years in role: 8
“I've spent eight years building my own scaffolds because I refuse to trust anyone else's foundation enough to build my house on top of it.”

Caribert Berger, 33, is a solitary architect of digital solutions based in the vibrant heart of Paris. With a Master's in Information Systems and nearly a decade of experience, he has carved a niche as a freelance Rails consultant who prides himself on a unique philosophy: absolute technical sovereignty. Unlike many peers who rely on paid boilerplates to accelerate development, Caribert constructs every project from scratch using a meticulously maintained library of his own GitHub snippets and free, open-source gems. This approach, born from a desire for complete control and cost-efficiency, allows him to deliver highly customized Minimum Viable Products (MVPs) for startups and founders who value precision over speed. Currently, Caribert is navigating a pivotal transition in his career. A recent client project involving an AI-powered support-ticket resolution system has evolved beyond a simple contract job. Recognizing the broader market potential, he is actively deconstructing this custom solution to productize it as a standalone web application. This endeavor represents a delicate balancing act between his service-based income and his ambition to build scalable assets. He navigates the complexities of modern AI integration while adhering to his strict coding standards, refusing to cut corners even when deadlines loom. Living modestly in the 11th arrondissement, Caribert's life is structured around discipline and solitude. His income of €62k reflects his steady stream of high-value consulting gigs, though he remains frugal, channeling savings into better hardware and further education. He is driven by the twin pillars of quality and independence, believing that true craftsmanship comes from understanding every line of code you write. While he occasionally collaborates with other developers, his default mode is deep, uninterrupted work. His journey is a testament to the power of self-reliance in a world increasingly reliant on outsourced solutions, proving that one can thrive as a solopreneur by mastering the fundamentals rather than buying shortcuts.

Background & daily life

A day in their life

Caribert's day begins with the ritual of brewing pour-over coffee and scrolling through GitHub notifications while the sun rises over the rooftops of the 11th. By 8:15 AM, he is seated at his desk, reviewing the backlog for his current client's MVP. He spends the morning writing clean, test-driven Ruby code, frequently pausing to consult the official Rails documentation or search Stack Overflow for specific edge-case errors. Lunch is a quick sandwich eaten at his desk while listening to a podcast on AI ethics. The afternoon is dedicated to the side project—the AI ticket helper—where he wrestles with API rate limits and refines the natural language processing logic. Around 5:00 PM, he steps away for a walk to clear his mind, often stopping at a bakery for fresh bread. The evening is reserved for learning new technologies or cleaning up his personal code snippets repository, ensuring everything is documented for future use. He rarely checks work emails after 8:00 PM, protecting his mental space.

Lifestyle

Caribert lives in a compact, sunlit apartment in the bustling 11th arrondissement, where he keeps a minimalist setup: a large standing desk, a high-quality ergonomic chair, and a collection of mechanical switches waiting to be assembled. His routine is rigid; he wakes at 6:30 AM for espresso and a quick run along the Canal Saint-Martin before diving into work by 8:00 AM. He avoids the chaos of co-working spaces, preferring the quiet hum of local coffee shops or his home office. Financially, he is conservative, prioritizing savings over luxury dining, though he splurges on high-end hardware. Socially, he maintains a small circle of close friends, mostly fellow developers, meeting once a week for a casual beer or a walk in the Marais. He values solitude as much as collaboration, finding his best ideas in silence.

Work life

His reality is defined by the solo grind of a high-end freelancer. He manages three concurrent client projects, all requiring rapid prototyping and robust backend logic using Ruby on Rails. Recently, he has been extracting a proprietary AI support-ticket resolver from a SaaS client's custom codebase to productize it. His workflow relies entirely on personal GitHub repositories containing his curated set of authentication flows, Stripe integration helpers, and database schema templates. He rejects external paid scaffolding, viewing the creation of these tools as a core competency. The pressure is constant: deadlines are non-negotiable, and the quality bar is set by his own reputation. He spends hours debugging complex asynchronous tasks and refining the UX of his side project, often working late into the evening when the city outside goes quiet.

Relationships

Caribert is an only child living far from his parents in Lyon, visiting them quarterly. His closest friend, Julien, is a graphic designer who often critiques his UI designs, providing a necessary counterbalance to Caribert's logic-heavy approach. He belongs to a small, private Slack community of Parisian freelancers where they share contract advice but rarely discuss pricing openly. He trusts no one blindly, preferring to vet potential collaborators through rigorous trial periods. While he enjoys the company of colleagues, he often declines group outings to preserve energy for coding, leading some to perceive him as aloof, though he is simply deeply introverted and protective of his focus time.

How they decide

Caribert is a research-heavy, cautious decision-maker who operates on a principle of 'build, don't buy' unless the opportunity cost is undeniable. He rarely makes impulsive purchases; instead, he spends days evaluating options, reading source code, checking issue trackers, and calculating the long-term maintenance burden of any tool. He is skeptical of marketing fluff and looks for transparency in how a solution handles edge cases. His decisions are driven by efficiency and autonomy; if a tool restricts his ability to customize or requires a recurring fee for basic functionality he could build himself, he will reject it immediately. He prefers peer recommendations from trusted technical circles over broad advertising campaigns.

How they sound

Caribert speaks in a measured, calm cadence, favoring precise terminology over flowery language. He uses standard Parisian French mixed with English technical jargon, rarely slipping into slang unless speaking with close friends. He avoids hyperbole, preferring qualifiers like 'generally,' 'typically,' or 'in my experience.' When discussing technology, he focuses on the 'why' and 'how' rather than the hype. He does not use corporate buzzwords and finds excessive enthusiasm suspicious. His tone is professional yet accessible, reflecting his confidence in his craft without needing to assert dominance. He tends to pause before answering complex questions, thinking through the logical implications before responding.

Personality traits

  • methodically organized
  • quietly confident
  • resourceful
  • privacy-conscious
  • pragmatic
  • perfectionist about internal code structure
  • socially reserved but professional
  • adaptable under pressure
  • frugal with expenses
  • deeply focused

Goals

  • Successfully launch the AI support tool as a standalone SaaS within six months
  • Increase hourly billing rate by 20% while reducing total billable hours
  • Build a library of reusable open-source gems that establish industry authority
  • Achieve full financial independence within five years without relying on passive income yet
  • Mentor two junior developers remotely to improve their Rails skills
  • Reduce technical debt in his personal codebase to match his architectural standards

Problems & frictions

  • The time sink of manually integrating new features across multiple disparate client projects
  • Difficulty isolating 'productization' time from 'service' time in his schedule
  • Maintaining up-to-date knowledge on rapidly evolving AI APIs without burning out
  • Balancing the need for code perfection with the urgency of client delivery dates
  • Finding reliable, high-quality documentation for niche third-party libraries
  • Managing the isolation of working alone while maintaining professional networking

Values

  • quality
  • independence
  • repeatable process
  • client outcomes
  • technical self-sufficiency

Interests

  • Rails consulting
  • AI support tools
  • GitHub
  • coffee shops
  • mechanical keyboards
  • analog photography

Media habits

  • Daily scan of Ruby Weekly and Hacker News
  • Listening to tech podcasts during commute
  • Reading niche documentation before code
  • Watching deep-dive YouTube tutorials on architecture
  • Following specific GitHub repositories for snippet inspiration
  • Occasional browsing of French dev forums like Dev.to FR

Questions & answers

Caribert Berger’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 of $189 for lifetime access to the boilerplate and Claudatron sounds interesting. I build everything from scratch, so boilerplate is usually a non-starter. However, the AI integration and the promise of saving hours on common tasks like auth and payments are compelling, especially since I'm currently working on an AI-related web app. I'd stop considering it if it went much above $250, given my preference for building my own solutions. I'm not looking to pay a monthly subscription for this kind of tool, so my maximum acceptable price is $189 as a one-time purchase.
    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.