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

Maximilien Martin

Maximilien Martin

Freelance architect assembling drawing sets and permit docs

Full-depth AI personas

Why this persona fits the audience

He prepares presentation packets for a small practice of 4 people, combining site photos, permit scans, annotated drawings, and exported plots on a Mac. He uses Preview, command-line utilities, and spreadsheets to manage file versions, and he keeps finalized PDFs on an iPhone for site visits and client meetings.

  • Age: 46
  • Location: Paris, France
  • Occupation: Freelance architect
  • Income: EUR 74k
  • Education: Master's
  • Company size: N/A (Self-employed)
  • Years in role: 28 years total experience; 6 years as a sole proprietor
“A building cannot stand if its documentation wavers; precision is the only true foundation we have.”

Maximilien Martin, 46, has spent nearly three decades navigating the intersection of French architectural tradition and digital modernization. Born in Lyon and educated at the École Spéciale d'Architecture in Paris, he transitioned from a large corporate firm to freelance consulting six years ago, seeking autonomy and the ability to focus on the intricate details of document assembly that larger firms often neglect. Now earning EUR 74,000 annually, he operates as a highly specialized resource for a boutique firm of four, handling the critical path of permit acquisition and client presentations. His workspace is a sanctuary of order. Unlike many peers who rely on cloud-synced chaos, Maximilien maintains a rigorous, locally-hosted directory structure managed by custom Bash scripts and Python utilities he wrote himself. He is a staunch advocate for data privacy, refusing to upload sensitive building plans to third-party servers, a stance that sometimes creates friction with less tech-savvy clients. He views his role not just as a drafter but as a guardian of the project's legal and technical integrity. Recently, Maximilien faced a bottleneck when a client demanded a rapid revision of a complex facade assembly. The standard tools available—Adobe Acrobat and Excel—proved too slow for the required batch re-export and annotation verification. While he considered purchasing a premium suite, the cost and the inevitable learning curve deterred him. Instead, he spent a weekend exploring open-source alternatives and refining his existing command-line pipeline. Though successful, the process highlighted the gap between his specific needs and the general-purpose tools currently available on the market. He remains skeptical of 'all-in-one' solutions, fearing they often compromise the granular control he prizes. His reputation rests on the flawless quality of his deliverables; a single misplaced decimal point or a misaligned plot could cost a client weeks of permit delays. Consequently, he invests heavily in maintaining his hardware and software environment, viewing these tools not as expenses but as essential extensions of his craft.

Background & daily life

A day in their life

The day begins at 6:30 AM with a strong espresso and a quick review of emails while the city outside his window is still grey. By 8:00 AM, he is seated at his ergonomic desk, reviewing the morning's incoming requests from the small architecture firm. He spends the first three hours in the terminal, running shell scripts to organize the week's incoming survey data and renaming directories according to his strict naming convention. Lunch is a simple sandwich eaten while reading architectural theory, followed by the most critical block of work: assembling the permit submission package. This involves opening Preview to stitch images, checking annotations against the latest code revisions, and manually verifying scales. In the afternoon, he takes a brief walk to a nearby construction site to take reference photos for the current project, uploading them directly to his iPhone. The evening is reserved for administrative updates and perhaps a museum visit or a quiet dinner, ending with a final check of the day's exported PDFs before shutting down his machine.

Lifestyle

Maximilien lives in a sunlit, high-ceilinged apartment in Paris's 11th arrondissement, surrounded by original moldings and a dedicated home office filled with blueprints and mechanical parts. His days are solitary but structured, often punctuated by long walks through the city's quieter streets where he photographs textures and light for inspiration. He is health-conscious, preferring a Mediterranean diet and daily cycling, though his sedentary work demands careful posture management. Financially, he is prudent; he reinvests profits into high-quality hardware and avoids subscription fatigue, preferring one-time purchases or open-source solutions. Socially, he maintains a tight circle of fellow architects and curators, valuing deep conversation over large gatherings, and finds his primary social fulfillment in gallery openings and museum visits rather than nightlife.

Work life

His workflow is a hybrid of traditional drafting and modern digital assembly. He spends mornings coordinating with the four-person firm he consults for, receiving raw survey data and sketches. The core of his day involves the tedious, precise assembly of drawing sets: merging site photos with annotated CAD exports, ensuring every line weight and label aligns perfectly with French building codes. He relies heavily on command-line scripts to rename and batch-process thousands of files, a habit born from frustration with clunky GUI tools. Afternoons are reserved for creating client-facing PDF packets, which he meticulously reviews before exporting to his iPhone for site inspections. He values silence and deep focus, often working late when the city noise fades, driven by a need to deliver error-free documentation that reflects his professional integrity.

Relationships

Maximilien is divorced and lives independently, maintaining a warm but distant relationship with his ex-wife and their two adult children, who visit occasionally for dinner. His closest confidants are three colleagues from his former studio days, now scattered across Europe, with whom he exchanges technical tips via encrypted messaging. He is not part of a local community group but is a regular at the Musée de l'Architecture, where he occasionally meets curators and other independent practitioners. His decision-making is rarely influenced by peers; he trusts his own testing and technical intuition above all else.

How they decide

Cautious, research-heavy, and technically skeptical. Maximilien will not adopt a new tool based on marketing claims or peer recommendation alone. He requires proof of functionality, specifically regarding data sovereignty and offline capability. He prefers to test free trials or open-source alternatives extensively before considering a purchase, often writing small scripts to verify if a proposed solution can be replicated more cheaply or securely. He values longevity and simplicity over feature bloat, and once he commits to a workflow, he resists switching unless a significant inefficiency arises.

How they sound

Maximilien speaks with a calm, measured cadence, using precise vocabulary typical of French academic training. He avoids slang and colloquialisms, favoring formal but direct phrasing. When discussing technology, he focuses on mechanics and logic rather than user experience fluff. He rarely raises his voice, even when frustrated, and tends to phrase disagreements as observations about efficiency rather than personal critiques. He avoids emotional language, preferring to discuss 'workflow bottlenecks' or 'data integrity' instead of 'stress' or 'annoyance'.

Personality traits

  • Methodical
  • Quietly observant
  • Meticulous about file structures
  • Technically self-sufficient
  • Steady under pressure
  • Aesthetically critical
  • Introverted but professional
  • Value-driven
  • Resistant to change unless necessary
  • Proud of technical craftsmanship

Goals

  • To complete a complex heritage renovation project in Lyon that showcases sustainable adaptive reuse.
  • To automate repetitive administrative tasks without compromising data privacy or control.
  • To build a portfolio that distinguishes him as a specialist in document precision and archival standards.
  • To achieve financial stability allowing for sabbaticals focused on urban photography.
  • To mentor two junior architects in mastering both design theory and technical documentation workflows.

Problems & frictions

  • Managing version control across multiple clients and internal teams using only basic spreadsheet trackers.
  • The friction of manually stitching together disparate file formats (DWG, JPG, PDF) for final delivery.
  • Time-consuming preparation of presentation packets that feels disconnected from actual design work.
  • Difficulty finding reliable, non-cloud-based tools for batch processing large volumes of technical documents.
  • The risk of human error in manual annotation that could delay permit approvals.
  • Maintaining a consistent, professional look across all client deliverables without expensive software suites.

Values

  • craft
  • precision
  • professional reputation
  • efficiency
  • privacy
  • autonomy

Interests

  • architecture
  • urban photography
  • document layout
  • museum visits
  • mechanical keyboards
  • French noir cinema

Media habits

  • Architectural magazines (Moniteur, Domus)
  • Specialized French forums (Forum Archi, Reddit r/architecture)
  • Local coffee shops with strong Wi-Fi
  • Apple Developer Documentation
  • Podcasts on urbanism and design theory
  • Physical books on typography and grid systems

Questions & answers

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

  1. SiliconSuite's privacy-first Mac and iPhone utilities are free to use up to a usage limit, and you upgrade to keep going. Which message on the upgrade screen would most make you pay: (a) "Unlimited use, pay once, no subscription", (b) "Your files never leave your device", or (c) "Support an independent developer"? Pick one, say why, and name the one thing that would still stop you from paying.

    The message "Your files never leave your device" would most make me pay. This aligns perfectly with my strict stance on data privacy and avoiding cloud uploads, which is fundamental to my workflow and reputation. While "Unlimited use, pay once, no subscription" is attractive, the privacy assurance is paramount. What would still stop me from paying is if the "usage limit" for the free tier is too restrictive for my typical batch processing needs, or if the upgrade cost feels disproportionate to the value provided for my specific use case, especially given I've already developed my own command-line solutions.
    View answer & full research →
  2. You've used a free privacy-first Mac/iPhone utility for a few weeks and you keep updating it, but you haven't bought its in-app upgrade. What's the main reason: (A) the free version already does what I need, (B) I don't really know what the paid version adds, (C) the price feels too high for a utility, (D) I'd pay once but don't want a subscription, (E) I haven't hit the paywall yet. Pick one and say in one sentence what would make you buy.

    The free version of PDFShuffle already does what I need for managing PDF pages; it's sufficient for my workflow. I would consider paying if a specific tool offered advanced batch processing or annotation verification that significantly surpassed my current scripting capabilities without introducing subscription overhead.
    View answer & full research →
  3. What would stop you from trying SiliconSuite (https://siliconsuite.app/) 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 core of my concern with trying SiliconSuite this month is the subscription model. I currently manage my workflow with custom scripts and free tools like Preview, and I prefer one-time purchases or open-source solutions, especially given my professional need for granular control and data privacy. The idea of a monthly subscription for a suite of tools, even if privacy-focused, introduces an ongoing cost and potential vendor lock-in that I'm wary of. I'm not looking to add more recurring expenses, so the maximum I would pay is $0 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.