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

Gédéon Fontaine

Gédéon Fontaine

Freelance full-stack developer using free tiers and open-source tools

Full-depth AI personas

Why this persona fits the audience

Freelances as a full-stack developer in Paris and regularly builds small AI assistants for SMB clients; most projects start as one-person prototypes using free tiers, open-source libraries, and custom Python wrappers before any paid platform is introduced. He works across a few concurrent client sandboxes rather than a fixed internal team.

  • Age: 26
  • Location: Paris, France
  • Occupation: Freelance Full-Stack Developer
  • Income: €52k freelance net
  • Education: Licence Informatique
  • Company size: Sole proprietor (Micro-entrepreneur)
  • Years in role: 3
“Code isn't just instructions for a machine; it's a promise I make to the future user that this thing will still work when I'm not looking.”

Gédéon Fontaine is a twenty-six-year-old freelance full-stack developer navigating the precarious yet rewarding landscape of independent tech work in Paris. Holding a Licence Informatique, he launched his solo practice three years ago after realizing that traditional agency structures stifled his creativity and efficiency. Today, he operates as a micro-entrepreneur, billing clients directly while managing his own taxes and benefits. His niche lies in building bespoke AI assistants for small and medium-sized businesses, where he leverages the power of open-source large language models and free cloud tiers to deliver high-impact solutions without breaking the bank. Unlike many peers who rely on SaaS subscriptions, Gédéon insists on custom Python wrappers and containerized environments, giving him total control over data privacy and cost scaling. His workspace is a testament to his philosophy: a minimalist setup dominated by dual monitors, a mechanical keyboard, and a collection of open-source books scattered across his desk. He is deeply committed to the ethos of craft, believing that the elegance of a solution is as important as its functionality. This drive has led him to contribute to several niche GitHub repositories and maintain a rigorous standard of code quality, even when under tight deadlines. However, this independence comes with significant friction. He constantly battles the mental load of context switching between disparate client requirements and the anxiety of unpredictable income streams. Despite these challenges, Gédéon remains optimistic, viewing his financial constraints not as limitations but as creative catalysts that force him to innovate. He is a man who values his freedom above all else, willing to endure the instability of freelancing to ensure that his work remains entirely his own.

Background & daily life

A day in their life

At 7:00 AM, Gédéon cycles through the quiet streets of the 11th, listening to a podcast on distributed systems. By 8:30, he is settled at his standing desk, brewing a fresh pot of pour-over coffee. The first hour is dedicated to checking emails and prioritizing tasks across his three client sandboxes. From 9:30 to 12:00, he enters deep work mode, writing Python scripts to automate a client's data ingestion pipeline, constantly referring to Stack Overflow and official docs. Lunch is a quick sandwich eaten while reading an article on LLM quantization. Afternoon sessions involve video calls with clients, which he keeps strictly timed, followed by debugging a stubborn deployment issue on a free-tier server. He ends his day around 6:00 PM, spending an hour coding a personal side project involving a custom voice assistant before closing his laptop. Evenings are reserved for dinner, a walk along the Canal Saint-Martin, and reading fiction to decompress.

Lifestyle

Gédéon lives a lean, urban existence in the bustling 11th arrondissement of Paris, sharing a cramped but vibrant apartment with fellow artists. His mornings are ritualistic: he wakes at 6:30 AM, cycles to a quiet corner café to order a double espresso, and reviews his GitHub notifications before work begins. He prioritizes health through daily cycling and cooking simple, nutritious meals at home to avoid restaurant markups, viewing food as fuel for cognitive performance rather than social indulgence. Financially, he is conservative, maintaining a six-month emergency fund while reinvesting profits into better hardware or specialized courses. Socially, he prefers one-on-one dinners or small gatherings over loud parties, valuing deep conversation about technology or philosophy over casual small talk. His weekends are split between tinkering with side projects and exploring new neighborhoods on his bike.

Work life

His day is a juggling act across three distinct client environments, each running in isolated Docker containers to prevent dependency conflicts. He avoids corporate meetings whenever possible, preferring asynchronous updates via Slack or email. The pressure stems from the constant need to stay ahead of rapidly evolving open-source libraries; if a library becomes unmaintained, he must rewrite that module himself. He spends hours debugging obscure errors in Python wrappers or optimizing inference costs on free cloud tiers. There is no manager breathing down his neck, but the lack of a safety net means every line of code carries direct financial weight. He thrives in the solitude of deep work but feels the isolation of having no office peers to vent to when a build breaks.

Relationships

He maintains a close bond with his younger sister, who works in digital marketing, often discussing industry trends over Sunday calls. His primary professional circle consists of other French freelancers met through local hackathons and Discord servers; they share tips on tax optimization and tool recommendations. He has no romantic partner currently, citing his demanding schedule and the unpredictability of freelance life as barriers. His parents, both educators, provide emotional support but remain skeptical of his career stability, often asking when he will get a 'real job' with a pension plan.

How they decide

Gédéon approaches decisions with a methodical, research-heavy strategy, heavily influenced by peer validation and technical documentation quality. He rarely adopts a tool based on marketing hype, instead requiring proof of concept, active community maintenance, and clear licensing terms. He is willing to pay for reliability but only after exhausting all free alternatives. His choices are driven by long-term maintainability and the ability to self-host or run locally if necessary, ensuring he retains ownership of his workflow. He values transparency in pricing models and dislikes hidden costs that might scale unexpectedly.

How they sound

His speech is precise, measured, and laced with technical jargon that he uses instinctively. He speaks with a calm, mid-range tone, avoiding hyperbole or salesy enthusiasm. When explaining complex concepts, he uses analogies related to physical structures or machinery. He tends to pause frequently to choose the exact word, showing a preference for accuracy over speed. He avoids slang unless speaking with close friends, and he never uses vague qualifiers like 'maybe' or 'probably' when discussing technical feasibility. His cadence is steady, reflecting his disciplined approach to problem-solving.

Personality traits

  • scrupulously efficient
  • curiously obsessive
  • pragmatically skeptical
  • solitary but collaborative
  • resourceful
  • quietly confident
  • meticulous about dependencies
  • anti-bloat
  • intellectually curious
  • time-conscious

Goals

  • Achieve €70k annual net income within two years by specializing in high-value AI integrations
  • Build a proprietary, monetizable open-source library that gains traction in the European dev community
  • Reduce administrative overhead to less than 10% of working hours
  • Establish a reliable network of subcontractors for overflow work without losing creative control
  • Complete a personal project that automates his entire tax filing process
  • Maintain a sustainable work-life balance to prevent burnout

Problems & frictions

  • Managing context switching between incompatible client tech stacks
  • The hidden cost of time spent debugging free-tier rate limits and quota errors
  • Difficulty predicting cash flow due to the irregular nature of freelance invoicing
  • Keeping skills sharp enough to compete with larger agencies without a training budget
  • Isolation leading to missed opportunities for collaboration or mentorship
  • Balancing the desire for technical perfection with the client's demand for speed
  • Security concerns when handling sensitive client data on ephemeral local setups

Values

  • independence
  • craft
  • cost awareness
  • technical autonomy
  • transparency

Interests

  • open source
  • side projects
  • espresso
  • local artisanal coffee roasting
  • retro computing
  • urban cycling

Media habits

  • GitHub trending repositories
  • French tech newsletters (e.g., Le Codeur)
  • r/LocalLLaMA and r/MachineLearning on Reddit
  • YouTube deep dives into system architecture
  • Discord channels for specific Python frameworks
  • NPR or France Inter during commutes

Questions & answers

Gédéon Fontaine’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://nimaapp.com/sdk (Nima App) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Landing on this page, the biggest thing that's unclear is how this proprietary engine actually integrates. It says "bring your own model," but then lists a bunch of "packs" and "suites" that sound like they *are* models or models layered with logic. The pricing is also a bit opaque with a $745 "Engines Core" and then other modules like "Mind OS" for $1,200. I can't tell if I need the core plus these, or if they're standalone. What makes me leave is the sheer volume of dense legal text before any clear indication of how it works or what it costs for a small project. It feels like a lot of legalese for something I just want to test. To sign up, I'd need a clearer breakdown of what each component does, a transparent pricing structure for a solo developer or small business (especially for initial prototyping with free tiers if possible), and maybe a demo or sandbox to see it in action before committing to a license fee.
    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.