Content
What the pages are made of: the home page's opening and work, the projects, the case study's parts, the writings, the lists, the FAQ, the About page's rows and the footer.
- Source
- What the pages are made of: their sheets in the catalog, tiers
baseandspecific - Checked by
catalog --check(every component here has its sheet) anddesign:audit(no raw colour, size or radius)
Opening
HomeThe home page's opening: the portrait, the title with its marked words, the lead, the two ways on and the key that opens the chat.
polished products
Before, the cursor waitingpolished products
Drawingpolished products
DrawnWords gone over with a marker, in the site's blue. On a first visit Theo's cursor draws it, from where it waits; otherwise it sweeps in once, word by word.
Work
HomeThe work: pictures in two columns, heights alternating, captioned under them. Hovered, a tile is selected as a frame in Figma.
A work tile picked up becomes a folder of its case study's pictures, to drop on the chat bar, which then talks about the project.
Projects
Writings, case studies, the agentProjects between dotted rules, under a case study and a writing. Each row opens its case study; its screens fan out under the pointer.
One row, its screens fanned out, as under the pointer. Always open on a touch screen.
Without the fan, filling the agent's projects card row by row.
A project's mark at 40px, as it comes: no tile.
Case study
Case studies, the agent's pagesPutting benched consultants back on billable work
A case study's opening: the project's name, Draft while it is one, then its title.
- Role
- Product Designer
- Service
- Product design
- Design system
- QA
- Landing page
- Illustration
- Year
- To confirm
Role, service and year under the opening picture, in three columns; stacked on a phone.
Overview
RestThe problem
HoveredA section's short label, the same word as in the contents list. A link to the section: hovered, it turns black and shows its link.
The projects on either side of this one, in the work's order, wrapping round.
- 01
To writeThree or four questions users kept asking.
- 02
To write
- 03
To write
The problem as the product's users asked it, numbered.
- Instead of
- To writeThe option set aside and the one kept.
- I chose
- To write
A decision written as a choice: what was set aside, what was kept, the trade-off if there was one.
To writeA number, a date or a word.
What came of the work: two or three facts on the dotted rule, the value large. No tiles.
Writings
Home, AboutThe writings on the home page, under the shelf: each title on one line.
A writing: its title, its first line in the lighter grey, the arrow. Hovered, a grey block round it and the arrow in ink.
Lists
About, the agent's pagesBefore product design, on About: each show with its date and a link out. Hovered, the row greys and its picture rides by the pointer.
A compact row with a small tile ahead of it, between dotted rules: the writing the agent places on its pages.
The rows' tile for a writing: a document.
FAQ
HomeYes, remote first, from Paris.
A full-time product designer role, in a startup from seed to Series B, or in a larger company's established design team. B2B first.
From November 15, 2026.
I design journeys rather than single screens, and prototype them in code with Claude Code until the flow works. Then I polish it by hand in Figma, screen by screen. Assets I make with AI or by hand.
Not by hand. I build in React with Claude Code and Codex: prototypes that test a journey for real, client landing pages, and this whole site.
No: it's a side role, and a full-time job comes first.
Give the chat your budget: it will tell you whether it's in my range.
Yes: drop the job description on the contact page, and you'll get an honest read, including where I don't fit.
Yes, remote first, from Paris.
A full-time product designer role, in a startup from seed to Series B, or in a larger company's established design team. B2B first.
From November 15, 2026.
I design journeys rather than single screens, and prototype them in code with Claude Code until the flow works. Then I polish it by hand in Figma, screen by screen. Assets I make with AI or by hand.
Not by hand. I build in React with Claude Code and Codex: prototypes that test a journey for real, client landing pages, and this whole site.
No: it's a side role, and a full-time job comes first.
Give the chat your budget: it will tell you whether it's in my range.
Yes: drop the job description on the contact page, and you'll get an honest read, including where I don't fit.
The questions a recruiter asks before writing, in the grey, a 0.5px rule under each. One opens at a time: the plus becomes a minus and the answer comes in out of a blur.
About
About, the agent
I'm Theo, a product designer in Paris. I designed BenchBee and Zenask, from their interfaces to their design systems, and I co-founded Make Me Grow, where we now build our own software.
I prototype journeys in code with AI until they work, for users and for what the product needs, whether that's conversion, activation or retention. Then I polish them by hand, in Figma or Paper. Once a product works and looks right, I turn it into a design system written for AI agents, so engineers ship new features faster and keep the same visual standard.
To me, design is a technical craft resting on taste. Now that AI makes execution accessible to everyone, taste is what sets a product apart: knowing precisely why an interface works, and explaining it in technical terms, to AI agents as much as to a team.
Who he is, at the top of About: his picture, a few lines, and the way to write to him.

Theo Toussaint
Product designer
Theo Toussaint
Open to full-time rolesPortrait, name and role, the certificate's seal beside the name. In the agent's contact card, his status in place of the role.
Experience
Mar 2026 – Oct 2026
BenchBeeProduct Designer
A platform where IT consultancies place their consultants between missions with other firms and recruitment agencies, used daily by more than 100 of them. I redesigned the whole product in 14 days: 20 user flows and the interface. I anonymised consultant profiles so firms couldn't poach each other's people, and built a design system that developers and AI agents follow, so the team ships faster without losing the look.
Feb 2026 – Aug 2026
ZenaskProduct Designer
Zenask built AI agents that sell in coaches' DMs. I designed the whole product on my own, from the strategy to the design system, and it reached $10K in monthly recurring revenue in five months, bootstrapped. One of its key features came from my recommendation: insights drawn from the conversations, each opening the change it suggests.
Dec 2023 – Now
Make Me GrowCo-founder, Product Designer
A four-person design and product agency. We started in late 2023 designing for e-commerce brands and influencers: landing pages on Webflow and Framer, Shopify themes built for conversion, Klaviyo email sequences. Then we began automating our own processes and built internal tools for it, and that's how I moved to software. Today we're building a product for organisations that run VAE, the French process that turns work experience into a diploma. I design it, prototype it in code and interview the people who'll use it, 27 so far.
Where he works and worked: the dates in the label's column, then the mark, the name and his role, and what he does there.
Readings
His books, covers only, four to a row; a cover not yet in is drawn from the title.
Tools
- FigmaInterfaces & systems
- PaperDesigning with agents
- ClaudePrototypes in code
- CodexPrototypes in code
- LinearIssues & roadmap
- Figma WeaveAI image & video
- PhotoshopRetouching
- After EffectsMotion
About's row: its label in the left column, what it holds in the right one. Here the tools, two to a line.
- FigmaInterfaces & systems
- PaperDesigning with agents
- ClaudePrototypes in code
- CodexPrototypes in code
- LinearIssues & roadmap
- Figma WeaveAI image & video
- PhotoshopRetouching
- After EffectsMotion
The tools with their logos as they come, and what each is for. As many columns as the room allows: on the agent's pages.
Paris, France
About's last line, under a hairline: where he is, the time zone, and the time there.
The time in Paris and the zone's name with its offset, worked out in the browser: nothing until the page has loaded.
Text
Every pageI'm Theo, a product designer in Paris. I designed BenchBee and Zenask, from their interfaces to their design systems, and I co-founded Make Me Grow, where we now build our own software.
Text with company names and their logos inline, as About's first paragraph.
A company's name with its logo: a link to its site where it has one, greyed under the pointer.
A small label in the grey: a project's services, a writing's subjects, Draft.
Writings
A section's heading in a writing and on the agent's pages: 22px, 24 from tablets up.
2px dashes, 1px thick, every 5px, in the rule's grey: between rows and over groups.
The page: its text column centred, with 16px gutters; pictures run wider.
Footer
Every pageWhat closes every page: his status, Contact, then the ticket, its Admit one stub to tear off. Shown whole: its tear is drawn in WebGL over the window.
Bars drawn from his name, always the same, on the ticket's stub. Nothing to scan.































