Francisque Dumas

Why this persona fits the audience

Splits time across 3 early-stage clients from Paris; each engagement is a small team of 2-6 people, and they keep architecture notes in Notion, Miro, and spreadsheets while implementing directly in VS Code.

• Age: 46
• Location: Paris, France
• Occupation: Fractional CTO and software consultant
• Income: €95k-€130k equivalent from consulting
• Education: Engineering degree from a grande école
• Company size: Clients: 2-6 people per team
• Years in role: 8

“The elegance of a system isn't just in its performance, but in how clearly its structure reflects its purpose.”

Francisque Dumas, 46, is a seasoned software consultant and fractional CTO based in Paris, France. Holding an engineering degree from a prestigious grande école, he spent over a decade in various software development and architecture roles within larger tech organizations before transitioning to independent consulting eight years ago. This shift was driven by a desire for greater autonomy and the opportunity to engage with the foundational challenges of early-stage companies. He now dedicates his time to three distinct early-stage clients, each with small, focused teams of 2-6 individuals. His engagements typically involve defining and refining software architecture, guiding implementation, and mentoring the core technical team. He meticulously documents architectural decisions and project progress using a combination of Notion for knowledge management, Miro for visual collaboration, and spreadsheets for tracking key metrics. His technical work is primarily conducted within VS Code. Francisque's income, derived from these consulting roles, ranges between €95k and €130k annually, reflecting his expertise and the demand for his specialized skills. He is married and has two children, a family life that he consciously balances with his demanding professional schedule. He recently guided one client through a critical pivot in their data ingestion pipeline, opting for a more robust, event-driven architecture over their initial batch-processing approach, a decision he meticulously documented and presented to the board. Another client is currently grappling with scaling their monolithic backend, and he's architecting a strategy for gradual microservice extraction, prioritizing minimal disruption. He values flexibility highly, allowing him to structure his work around client needs and personal commitments, but insists on dedicated blocks for deep, focused work to ensure the quality of his strategic output. His approach to decision-making is deeply rooted in structured analysis and intellectual rigor, ensuring that choices are well-reasoned and defensible, even when faced with the inherent uncertainties of startup environments. He sees his role not just as a technical advisor but as a strategic partner, helping nascent companies build solid foundations for future growth.

Background & daily life

A day in their life

His typical weekday begins around 7:00 AM with coffee and a quick review of overnight client communications. He then dedicates an hour to cycling or a brisk walk before his family's breakfast routine. By 9:00 AM, he's logged into his first client's Slack and VS Code, often starting with a stand-up meeting. The morning is a blur of coding, code reviews, and architectural discussions, usually focused on one client. Lunch is a quick affair, often eaten at his desk. The afternoon might involve a strategy session with another client's founder or a deep dive into a specific technical problem, documented meticulously in Notion. He aims to log off by 7:00 PM to have dinner with his family, but urgent issues can extend his day. Evenings might include reading technical articles or planning the next day.

Lifestyle

Francisque lives with his wife and two children in a Haussmannian apartment in the 17th arrondissement of Paris. His days are a carefully orchestrated balance between intense client work and family life. Weekends often involve cycling trips in the Île-de-France region or exploring new neighborhoods in the city. He's financially prudent, prioritizing long-term security over ostentatious spending, though he appreciates quality craftsmanship. Socially, he prefers smaller, more intimate gatherings with close friends and colleagues over large parties. His health is important; he cycles to maintain fitness and clear his head.

Work life

As a fractional CTO, his work is highly varied, demanding rapid adaptation to new team dynamics and project scopes. He thrives on the challenge of shaping architecture for nascent products, often guiding small, agile teams. His primary tools are Notion for documentation, Miro for collaborative brainstorming, and spreadsheets for tracking progress and resource allocation. He spends significant time in VS Code, not just coding but also reviewing pull requests and ensuring architectural integrity. The pressure comes from managing client expectations, delivering tangible progress with limited resources, and staying ahead of rapidly evolving technological landscapes.

Relationships

He is married to a curator at a Parisian museum, and they share a partnership built on mutual respect for each other's demanding careers. His children are his anchor. His professional network consists of former colleagues from larger tech firms and fellow independent consultants, with whom he exchanges insights and occasional project referrals. He values candid feedback from his clients' lead developers.

How they decide

Francisque is highly analytical and research-driven. He gathers data, maps out potential solutions, and weighs pros and cons meticulously, often using structured frameworks. He seeks input from trusted peers or subject matter experts when facing novel challenges but ultimately relies on his own reasoned judgment. He is not impulsive and prefers to avoid decisions made under duress, though client deadlines sometimes force his hand.

How they sound

Speaks with a measured, articulate cadence, favoring precise language. His French is standard Parisian, with occasional technical jargon that he's usually good at explaining. He avoids hyperbole and overly casual slang, maintaining a professional yet approachable tone. He tends to pause thoughtfully before answering complex questions, ensuring his response is well-considered. He rarely expresses strong emotional opinions, preferring objective analysis.