Back
Portrait of Geoffroy Danest, smiling, in front of green foliage

I design products, and build the tools around them.

I’m a Senior Product Designer at Fleet, in Paris. I’m almost the only designer there, working with four developers and the marketing team. So I also do part of the PM job, from discovery to shipping, and I push my own features to production.

I’ve loved design for 15 years. In my free time, I build side projects around what I like: sport and running, open data, and automations that save small business owners time.

Navigate the site Summarize with an LLM

Selected work

Product design

Automation

Experience

  • Senior Product DesignerFleet2022–Now
  • Graphic DesignerBayard2020–2022
  • Product Designer & Art DirectorFreelance2018–Now

About

I’m 28 and I’ve lived in Paris for five years. At Fleet, on top of the product, I take care of the design system on my own. I use AI to keep it clean, and I build internal tools so the whole team stays on-brand and talks about new features the same way.

Outside work, I keep building. Right now, it’s a tool for runners and athletes. I also love playing with data: statdefrance is an Instagram page that turns public data from data.gouv.fr into one stat a day, fully automated. It launches on October 19. I also built a back office for micro-businesses: it connects Notion and Gmail to follow up on quotes, answer clients and plan the work on real hours.

And I like to move: road and trail running, cycling, swimming and sailing. Last trip: the whole south coast of Brittany, from Vannes to BrestGaff-rigged sailboat under full sail in the Bay of BrestGaff rigSpotted in the Bay of Brest..

Tools I use every day

  • ClaudeHelped me build this site.
  • Linear
  • Granola
  • Notion
  • Cursor
  • WhatsAppMessage me anytime
    Click the icon to start a chat
  • GitHubWhere my automations live.
  • FigmaIn a relationship for 10 years.
  • Craft
  • StravaPersonal bestsMarathon3:24:19Half marathon1:29:0610K40:29
  • Cal.comBook a meeting
    Click the icon to pick a slot
  • Arcade
  • COROSPersonal bestsMarathon3:24:19Half marathon1:29:0610K40:29

Get in touch

Platform

The Cockpit: where companies run their whole device fleet.

Since 2022, I’ve been the product designer of Fleet, the platform that lets companies lease, manage and renew their IT equipment. I’m in charge of the Cockpit, the app where IT and HR admins handle all their devices. I cover everything: discovery, specs, UI, UX writing and the design system.

  • RoleProduct designer
  • CompanyFleet
  • UsersIT & HR admins
  • ScopeDiscovery to design system
01 · LaunchpadCockpit
LaunchpadThe Launchpad, home of the Fleet Cockpit

The first screen admins see. It shows what needs attention today, like arrivals, departures and deliveries in progress, with shortcuts to the most common actions.

Devices

The heart of the Cockpit. Every device in the company is here, leased through Fleet or bought elsewhere, so admins finally have one list for everything.

02 · EquipmentCockpit
EquipmentEquipment: the list of every device in the company, with its employee, location and MDM status

Every device in the company, leased through Fleet or bought elsewhere. Admins filter by status, user or type, and see at a glance who has what.

03 · Device detailCockpit
Device detailDevice detail: security status from the MDM, configuration and activity of one MacBook

Everything about one device in one place: who has it, its contract, its history, and its status in the company’s MDM.

People

Devices always belong to someone. The employee list is synced with the company’s HR tool, so onboarding and offboarding start from the right place.

04 · EmployeesCockpit
EmployeesEmployees: the list synced with the company’s HR tool, with team, dates and equipment

The employee list, synced with the company’s HRIS. From here, admins onboard, offboard and assign equipment.

05 · Employee detailCockpit
Employee detailEmployee detail: HR information on one side, assigned equipment on the other

Where HR and IT meet: personal info from the HRIS on one side, assigned equipment and deliveries on the other.

Feature

Shopping Lists: faster orders for IT admins.

IT admins kept ordering the same laptops for the same roles, again and again. I led the design of shopping lists in the Cockpit: admins save a setup once, then order it again in one click. Less searching, more orders.

  • RoleLead product designer
  • CompanyFleet
  • Team1 PM, 1 developer, me
  • Timeline2 weeks, July 2026
Cover1 frame
Cockpit · Catalog with shopping listsThe Cockpit catalog with a My shopping lists row: each saved setup can go to the cart in one click

Context

In the Cockpit, admins order devices from a catalog. For each new hire, they searched the whole catalog again, even when the setup was always the same. Ordering took longer than it should.

DiscoveryInterviews with IT and office managers
Companies standardise by roleOne admin had 2 standards, tech and people teams. Another kept 4 setups: 2 Mac, 2 Windows, one per role.
Every onboarding starts from zeroThe admin searches the whole catalog for each new hire, and each order takes longer.

How might we let admins set up each role once, and order it again in one click?

Decisions

Lists sit where admins already shop, and go straight to the cart. Nothing new to learn.

Key decisions4 rules · every state
Lists live in the catalogNo separate menu. Admins see their lists on the catalog home.
One click to the cartA whole setup goes to the cart at once, ready to order.
One list per roleLists follow how companies already think: tech, people teams, office.
Simple firstWe shipped plain lists first and kept finer rules for later.
Every state designed
DefaultNo list yetCreate a listList detailAdd productDeleteEmpty list

Solution

Lists on the catalog home and on their own page. A list page to add, remove or order products, with the whole setup sent to the cart in one click. And a “Save to a list” action on every product page.

From the catalog2 screens
Catalog · no list yetCatalog home before the first list, with an invitation to create one
All shopping listsAll shopping lists page, each list with its products and an Add to cart action
Inside a list3 screens
List detail · with productsList detail with three products, an unavailable product to replace, and Add to cart
Right after creationEmpty list right after creation, with a link to browse the catalog
Delete a listConfirmation before deleting a list
From a product page3 screens
Product pageMacBook Air product page with a Save to a list action next to the configuration
Add to a listPicking a list for the product, with lists that already contain it marked
No list yetAdding a product when the admin has no list yet: create one on the spot

Admins can save a product from wherever they are, even before their first list exists.

Outcome

  • 10%Of customer companies use shopping lists
  • 1 clickFrom a saved setup to the cart
  • 2 weeksFrom kickoff to launch

What I take from it: a small feature can move the main metric. When reordering is one click, admins stop searching and order.

Design system

Fleet Design System: from Figma to production.

The Fleet Design System is the base of the Fleet app, a B2B tool to manage a company’s IT equipment. A design system is only useful if it’s up to date and actually used in the code. So I work on two things: keeping Figma clean, and making sure what I design reaches production as is.

  • RoleDesign system owner
  • TeamSole product designer
  • ScopeThe Cockpit and back office
  • ToolsFigma, Cursor, shadcn, Ariakit
Cover1 frame
Fleet cockpit · HomeThe Fleet cockpit home, built with the Fleet Design System

Maintain

In September 2026, I audited the whole file. The idea: clean up before adding anything new. I fixed what I could right away, and turned the rest into a clear to-do list.

Audit, September 20264 fixes · 5 next steps
Fixes applied
Descriptions everywhereEvery variable and component now says what it’s for.
Primitives hiddenDesigners only see the tokens they should use, not the raw values.
Hard-coded values removedComponents now use tokens instead of fixed values.
Foundations rebuiltColours and typography, rebuilt from the Figma variables.
Prioritised next steps
WCAG contrast on strong tokens & disabled statesLine heightsProperty namingMerge the button setsUnify status systems
Foundations4 sheets · from the Figma variables
Color · primitives

Primitive colours

112 primitives · hidden from designers, only referenced by semantic tokens

base
black#000000
white#FFFFFF
brand
50#F3FDF8
100#E3FFF2
200#C4EEE0
300#9AC7BA
400#96D6BC
500#8BE4C3
600#62BC9E
700#3D9478
800#1F745B
900#01563E
grey
50#F9F9FB
100#EDEDED
200#E3E3E3
300#DBDBDB
400#ABABAB
500#7E7E7E
600#676767
700#4F4F4F
800#393939
900#222222
green
50#E3FFF2
100#C2F5DF
200#93ECC8
300#52DEAD
400#1ECF9B
500#00C087
600#009E6E
700#007D57
800#016849
900#01563E
blue
50#F5F6FF
100#DCE0FC
200#B8B3E0
300#9EA8F0
400#7F8CE6
500#5B68CC
600#3D48A8
700#151A6E
800#252D87
900#0C0362
red
50#FFEBEB
100#FAD0D0
200#F2B0B0
300#E88888
400#D96060
500#D83C3C
600#AA2E2E
700#952828
800#852424
900#7A2222
orange
50#FFEFE0
100#FDDCBC
200#F9C496
300#F2A86C
400#EF9854
500#EE8121
600#B85A18
700#A34D12
800#97430D
900#8D4709
purple
50#F9F6FF
100#F0EDFF
200#E0D8FF
300#D2CAFF
400#9D8BFF
500#684FFF
600#4F35D6
700#3820A8
800#25147A
900#160A52
yellow
50#FFFEF0
100#FFFCE3
200#FFF8C0
300#FFF4CA
400#FFEC87
500#FFDA45
600#D4A800
700#A37800
800#6E5000
900#3D2C00
pink
50#FFF4F9
100#FFE0EE
200#FFCCE3
300#F5BAD5
400#FDA9CE
500#FF99C8
600#D6669F
700#A83D78
800#782055
900#4A0D33
cyan
50#EDF9FF
100#D6F0FF
200#BFE4FA
300#A6D8F5
400#83C8FC
500#5FC2FC
600#2A96D4
700#1170A8
800#084F78
900#022F4A
beige
50#FBF8EF
100#F5EDD8
200#EEE0C0
300#E5D0A5
400#D4B882
500#C4A060
600#A07840
700#7A5830
800#563D20
900#332210
Color · semantic

Semantic colours

60 tokens · the only colours offered in the library, each pointing to a primitive

background
default/maingrey/50
default/subtlebase/white
primary/mainbrand/900
primary/lightbrand/300
secondary/maingrey/900
secondary/lightgrey/300
success/maingreen/500
success/lightgreen/300
success/subtlebrand/100
info/mainblue/500
info/lightblue/300
info/subtleblue/50
warning/mainorange/500
warning/lightorange/300
warning/subtleorange/50
danger/mainred/500
danger/lightred/300
danger/subtlered/50
utilities/row-hovergrey/100
utilities/row-selectedbrand/50
utilities/brandbrand/50
text
default/maingrey/900
default/lightgrey/300
default/contrastTextgrey/500
primary/mainbrand/900
primary/lightbrand/300
primary/contrastTextbase/white
secondary/maingrey/900
secondary/lightgrey/300
secondary/contrastTextbase/white
success/mainbrand/900
success/lightgreen/500
success/contrastTextbase/white
info/mainblue/500
info/lightblue/200
info/contrastTextbase/white
warning/mainorange/600
warning/lightorange/300
warning/contrastTextbase/white
danger/mainred/500
danger/lightred/300
danger/contrastTextbase/white
border
default/maingrey/300
default/stronggrey/500
default/emphasisgrey/700
primary/mainbrand/900
primary/lightbrand/300
secondary/maingrey/300
secondary/lightgrey/300
success/mainbrand/900
success/lightgreen/300
info/mainblue/500
info/lightblue/200
warning/mainorange/600
warning/lightorange/300
danger/mainred/500
danger/lightred/300
danger/ringred/500 · 20%
focus/mainbrand/900
focus/ringbrand/900 · 25%
Typography

Typography

Poppins · 13 text styles · 4 weights

h1FleetSemiBold 48/56
h2FleetSemiBold 40/48
h3FleetSemiBold 32/40
h4FleetSemiBold 24/32
h5FleetSemiBold 20/24
h6FleetSemiBold 18/24
body1FleetRegular 16/24
body1 SemiBoldFleetSemiBold 16/24
body2FleetRegular 14/20
body2 SemiBoldFleetSemiBold 14/20
captionFleetRegular 12/16
caption SemiBoldFleetSemiBold 12/16
buttonFleetMedium 16/16
AaLight · 300
AaRegular · 400
AaMedium · 500
AaSemiBold · 600
Size

Size

Radius, stroke and an 8-pt spacing scale

Radius
small · 4
medium · 8
circle · 999
Stroke
small · 0.5
medium · 1
large · 2
Space
space/0,252
space/0,54
space/18
space/1,512
space/216
space/324
space/432
space/864

Generated from the Figma variables: 112 base colours, 60 tokens, 13 text styles and the size scale.

Build

Form fields were the messiest part of the app. I designed one family of inputs, now the reference, then tested it on a real flow of the product.

The inputs family8 components · 7 states
Components
Text InputSelectPhone InputEntity InputSearchDate InputDate pickerTextarea
States, shared by the whole family
DefaultHoverFocus & SelectedFilledErrorDisabledRead-only
Design decisions
One Focus & Selected stateFocus and open are the same state. Simpler to design, simpler to build.
Tokenised focus ringA focus ring in the brand colour, and a red one for errors.
Separate error lineThe error has its own line, so it never hides the help text.
Inputs · 7 states
Text InputLabel
Enter text
Label
Enter text
Label
Enter text
Label
Entered text
Label
Entered text
Error messageLabel
Entered text
LabelEntered textSelectLabel
Select
Label
Select
Label
Select
Label
Selected option
Label
Selected option
Error messageLabel
Selected option
LabelSelected optionPhone InputPhone
06 12 34 56 78
Phone
06 12 34 56 78
Phone
06 12 34 56 78
Phone
06 12 34 56 78
Phone
06 12 34
Invalid phone numberPhone
06 12 34 56 78
Phone06 12 34 56 78
Date picker · states and example

Calendar day

242424242424

Date picker

TodayTomorrowIn 1 weekIn 1 month
September 2026
MoTuWeThFrSaSu311234567891011121314151617181920212223242526272829301234567891011

Example

Delivery date
29/09/2026
TodayTomorrowIn 1 weekIn 1 month
September 2026
MoTuWeThFrSaSu311234567891011121314151617181920212223242526272829301234567891011
Buttons & checkbox3 components
Checkbox
CheckboxType somethingType somethingType somethingType somethingType somethingType something
primary-button
primary-buttonActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionwarning-button
secondary-button
secondary-buttonActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionActionAction

Every button comes in filled, outline and ghost, in two sizes, with or without an icon, plus disabled and loading.

Ship

My goal: what ships in production looks exactly like what I designed, no guessing. So I write the docs for people and for AI, and I see the path to code as part of the design work.

From Figma component to production4 practices
Descriptions written for AIEach component lists its layers, states, tokens, props, keyboard and accessibility rules. Cursor reads it straight from Figma.
Ready-to-use promptsPrompts the devs can copy: check the component, build it on shadcn with Ariakit, run the checklist.
Built on shadcnThe components are built on top of shadcn, with Ariakit, and live in production.
Beyond FigmaI also put the design system in Claude Design, so sales and account managers can make on-brand material on their own.
Feature

Support AI Copilot: 30% fewer support tickets.

I redesigned the AI assistant in the Fleet app. It answers simple questions on its own, knows when to stop, and passes the conversation to a person in one click, with all the context.

  • RoleProduct designer
  • CompanyFleet
  • SurfaceSupport flow
  • PartnersSupport, ops, engineering
Cover1 frame
Fleet Copilot · 3-step pipelineThe three steps of the Fleet Copilot: data reception, prompt analysis and optimization, response display

Context

The old chatbot gave generic answers and had no way to open a ticket. When it failed, users had to start over somewhere else, and support got tickets with no context.

Two goals: quick answers to simple questions, and fewer tickets for the support team.

BeforeIsolated chatbot
Before: user message, basic chatbot with a generic response, then a manual ticket where the user starts over

Discovery

I went through past tickets to find the questions that came back the most, then talked with ops and support about how they handle a request. With the devs, we chose what the AI could use as sources.

Discovery3 inputs
Past ticketsTo find the simple questions that come back again and again.
Ops & support interviewsHow a request is handled today, and what an agent needs to take it.
Data sourcesHelp Center, Linkup for web search, and Zendesk templates.
Design principles3 rules
Know when to stopWhen the bot can’t answer, it says so and hands over to a person.
A ticket is always one click awayOpening a ticket is never hidden.
Context travelsThe agent gets the whole conversation. The user never repeats themselves.

Solution

Three steps, with a way out. The request is sorted first, then analysed with prompts made for each ticket category, then the Copilot answers. If that’s not enough, one click creates the ticket and the agent gets the full conversation.

AfterAI copilot with escalation path
After: data reception, prompt analysis and response display, with a ticket created with full context if the user is not satisfied
The support flow3 screens
1 · CategorySupport form: choosing the device and the category of the request
2 · Your requestSupport form: subject, message and attachments
3 · Fleet CopilotFleet Copilot answering a firewall question, with the option to create a ticket

The Copilot answers right after the request. “Create my ticket” is always one click away.

Outcome

  • −30%Support tickets, solved by the Copilot before reaching the team
  • FasterAnswers on simple questions
  • Full contextSent to the agent with every ticket
Feature

International Delivery: one catalog to equip teams in any country.

I designed one catalog for every country. Fleet clients order equipment for anywhere in a single checkout, with the right price, delivery time and keyboard for each country. Today, more than half of Fleet’s revenue comes from abroad.

  • RoleProduct designer
  • CompanyFleet
  • SurfaceCatalog & checkout
  • PartnersOps, finance, sales
Cover1 frame
Product page · Delivery countryDelivery country selector on a product, with the delivery time updated to 2 to 5 business days

Context

Clients could only order online for their own country. Anything abroad went through sales: slow, manual, and a pain for clients and for ops.

BeforeNo self-service abroad
Before: a global order need leaves the platform, goes through sales by email and calls, and ends in a manual order that takes days

Discovery

I talked with ops and finance about how they handled these orders by hand, tested with clients, and listed everything that changes from one country to another. The tests showed something the catalog couldn’t do: one order often goes to several countries.

Key insights3 decisions
Country on the productOrders mix countries, so you pick the country on each product, not for the whole catalog.
One switch, the real offerChange the country and the price, delivery time and keyboard update together, before you add to cart.
Addresses checked in the cartEach country is matched to a saved address, or you’re asked to add one. No failed orders.

Solution

One catalog for every country. Each product has a delivery country that updates price, delay and specs live. At checkout, each destination is checked against your saved addresses, and missing ones are flagged before you order.

AfterCountry-aware catalog
After: product card with a country selector, a cart with items for several countries, and address matching
Catalog to checkout3 screens
1 · ProductProduct page of a MacBook Air with its configuration
2 · Delivery countryThe delivery country selector on the product, with the delivery time
3 · Delivery addressesCheckout: each device matched to a delivery address, with a missing address flagged

One order, several destinations: each device gets its address and its delivery time.

Outcome

  • 50%+Of Fleet’s revenue now comes from abroad
  • MinutesTo order abroad instead of days, without sales
  • Less opsFewer orders to handle by hand

International companies now order as easily as local ones.

Social media

@statdefrance: one official stat a day, from dataset to post, without me.

An Instagram page that turns data.gouv.fr datasets into one surprising stat a day. Picking the data, making the visual, writing the caption and posting: it’s all automated. I just check the week ahead.

  • RoleDesign & build
  • TeamSolo
  • StackPython, Claude
  • LaunchOct 19, 2026
Cover3 frames
Feed · Light
Housing27%

of primary homes are more than 50 years old.

Source: Insee · data.gouv.fr
Story · Dark
Transport4 h 12

lost in traffic every month in the Paris region.

Source: Cerema · data.gouv.fr
Feed · Dark
Energy1 in 3

kilowatt-hours used in France goes to heating.

Source: SDES · data.gouv.fr

Sample posts. The figures are illustrations, not published stats.

Context

France publishes thousands of open datasets on data.gouv.fr, and almost nobody reads them. I love data, and I wanted a small daily post that makes it readable in three seconds.

My rule: it runs on its own, every day, for free. If I have to think about it, it doesn’t work.

Editorial rules10 themes · 3 rules
Themes, aligned with data.gouv.fr
HealthEmploymentHousingEducationEnergyAgricultureSecurityCultureTransportPublic accounts
Rules for every post
One dataset, onceEach post uses a dataset never used before.
Tied to the newsThe stat echoes what people in France talk about that week.
Source on the postThe source and data.gouv.fr are on every visual.

Pipeline

Every morning, a script picks a dataset, Claude finds the stat and writes the caption, Python draws the visual, and the post goes live on Instagram. Once a week, I check the next posts in a simple conversation with Claude: yes, no, or redo.

Daily pipeline5 steps · 1 human check
GitHub Actions cron · every morning, Paris time
01 · DataPick an unused dataset
02 · ClaudeFind the stat, write the caption
03 · PillowRender feed & story PNG
04 · DriveBack up the files
05 · Graph APIPublish at 9:00
Weekly checkI check the week in one Claude conversation. No dashboard, no Notion.
No extra costGitHub Actions runs it, my existing Claude plan does the AI.
Open codeAll the code is on a public GitHub repo.

Launch

  • 9:00One post every day, published on its own
  • 1 / weekCheck by me, in one Claude conversation
  • 0 €Extra cost on top of the tools I already pay for

The page goes live on October 19. I’ll add the results here after the first weeks. In the meantime, follow it on Instagram.

Freelance

Micro-business Back Office: 5 to 7 hours back every week for people who work alone.

A tool for people who run their business alone. It sits on top of the Notion and Gmail they already use, tells them what to do next, and plans their work on their real hours. I built it first with a painting restoration studio in Paris.

  • RoleDesign & build
  • ForIndependents
  • StackNotion, Gmail, Claude
  • First userAtelier Billioud
Cover1 frame
Web · Home
atelier · home
AAtelierPainting restoration
Navigation
Home
To-do12
Planning
Projects11
Claude
Settings
Reading Notion… · 22 h ago
Synced with your account
HomeSync
WEDNESDAY 14 OCTOBERGood afternoon, dear Léa
To-do

Actions on your projects, your emails and your tasks.

12 actions to do
Planning

The timeline of your projects, week by week.

2 projects in progress today
Projects

Every record, by status, linked to Notion.

11 active projects
Ask Claude

Your questions about projects, planning, clients.

Searches and answers, changes nothing

Context

When you work alone, you do three jobs: the craft, the sales and the admin. For the restorer I built it with, every project follows the same steps: first contact, photos, quote, approval, receiving the painting, restoration, return and invoice. A restoration can take a few days or several months.

Her follow-up lived in three places that didn’t talk to each other: Notion for projects and clients, Gmail for emails, and her head for planning and follow-ups. Quotes weren’t followed up, emails slipped through, and she couldn’t see her workload: can I take a new painting? What will I invoice in the next months? Admin was eating her workshop time.

The goal: put everything in one place without changing her habits. Notion and Gmail stay as they are, the tool adds what was missing.

To-do, built from Notion and Gmail4 lists
Web · To-do
atelier · to-do
AAtelierPainting restoration
Navigation
Home
To-do12
Planning
Projects11
Claude
Settings
Notion read just now
Synced with your account
To-doSync
My tasks
Add a task — e.g. Order a 55×46 stretcherAdd
▶ Done (1)
New requests 1· Quote requests from clients with no Notion record yet.
Looking for new requests…
Quotes to send 1· Projects in “Initial contact”.
Lucas - Small seascape
Hugo LucasInitial contact
First contact: the client is waiting for your quote.
✓ Quote sentAsk for photosOpenNo follow-up
To reply 4· The client wrote last.
Henry - Garden viewReceived 5 d ago
Nadia HenryArchive
The client replied 5 days ago: waiting for your answer.

You5 d agoHello Madam, I hope you are well. I’m following up about the quote for the restoration of your painting…

n.henry@email.com5 d agoHello, thank you for your quote. In the end I won’t need the restoration. Kind regards…

Restoration request - “Orchard in spring” · 3 messagesSee thread →
Reply with ClaudeDoneChange project
Bonnet - Ripped landscapeReceived 2 d ago
Louis BonnetQuote sent
The client replied 2 days ago: don’t let it wait.

You2 d agoHello Sir, I’m following up about the preliminary quote I sent you…

It tells her what to do and when: answer a client, follow up on a quote, plan a painting, organise a return, send an invoice.

How it works

The tool reads the inbox and recognises each client from their email address, then links the emails to the right project, even across several threads. Change a status or a date in the tool and Notion is updated: nothing to type twice. It also reads the quote and invoice PDFs (amount and hours) to track what’s quoted, invoiced and still to invoice.

From request to invoice5 stages · 6 building blocks
Project stages, synced with Notion
01 · GmailFirst contact
02 · GmailPhotos & quote, follow-ups
03 · ClientQuote approved
04 · PlanningReceived, in restoration
05 · PDFReturned & invoiced
What it connects
Emails matched by clientEach address is linked to a client, each thread to the right project.
Two-way Notion syncChange a status or a date in the tool, it’s saved in Notion.
Quotes & invoices readAmounts and hours from the PDFs show what’s quoted, invoiced and left to invoice.
Planning constraints
Real workshop daysProjects are placed on real working days and hours, based on the estimate.
AbsencesTrips and holidays block the days and push the next projects.
Admin timePart of each week is kept for admin, so the planning stays realistic.
PlanningQuarter view
Web · Planning
atelier · planning
AAtelierPainting restoration
Navigation
Home
To-do12
Planning
Projects11
Claude
Settings
Notion read just now
Synced with your account
PlanningSync
WeeksMonthsQuarterTodayDays without workshopAbsencesStatuses
Projects
In restoration 3
Faure - Harbour at dusk6 Oct → 24 Oct · 31 h
Portrait of a lady13 Oct → 27 Oct · 18 h
Lacquered screen28 Oct → 3 Nov · 11 h
Quote approved 2
Still life with lemons24 Nov → 5 Dec · 22 h
Village church7 Jan → 21 Jan · 19 h
Quote sent 5
Bonnet - Ripped landscapeno dates
Girard - Flower bouquetno dates
Robin - Family portraitno dates
Fabre - Saint Jerome (?)no dates
Mallet - Two panels on oakno dates
Initial contact 1
Lucas - Small seascapeno dates
Restoration done 1Show
AugSeptOctNovDecJan 2027FebMar
Faure - Harbour at dusk
Portrait of a lady
Lacquered screen
Still life with lemons
Village church
TodayTrip ✈Christmas ✦

Projects by stage, on real workshop days. Hatched columns are days off.

Design

Simple and warm, like the studio. Claude drafts the emails (a follow-up, a photo request, a reply), and she checks and sends them herself from Gmail. In its own tab, Claude searches Notion and Gmail to answer her questions. It only reads, it never changes anything.

Projects & Claude2 frames
Web · Projects
atelier · projects
AAtelierPainting restoration
Navigation
Home
To-do12
Planning
Projects11
Claude
Settings
Notion read just now
Synced with your account
ProjectsSync
Initial contact1
Lucas - Small seascapeHugo Lucas—No dates
Quote sent5
Bonnet - Ripped landscapeLouis Bonnet38 hNo dates
Girard - Flower bouquetSophie Girard—No dates
Robin - Family portraitMarc Robin—No dates
Fabre - Saint Jerome (?)Inès Fabre64 hNo dates
Mallet - Two panels on oakPaul Mallet—No dates
Quote approved2
Still life with lemonsÉlise Martin—24 Nov → 5 Dec
Village churchThomas Roy—7 Jan → 21 Jan
In restoration3
Faure - Harbour at duskJulien Faure31 h6 Oct → 24 Oct
Portrait of a ladyClaire Blanc18 h13 Oct → 27 Oct
Lacquered screenAna Costa11 h28 Oct → 3 Nov
Restoration done1
Winter huntYves Picard42 h2 May → 30 Sep
Archive7Hide
Market in TangierThomas Roy—9 Dec → 18 Dec
Web · Ask Claude
atelier · claude
AAtelierPainting restoration
Navigation
Home
To-do12
Planning
Projects11
Claude
Settings
Notion read just now
Synced with your account
Ask ClaudeSync

Ask Claude

Not Monet, but it knows your paintings by heart. Ask about your projects, your planning, your clients or your emails: it can also search your emails and Notion. It only reads: it changes nothing.

What do I need to deliver before the end of the month?Which quotes are still waiting for an answer?Do I have time for a 20 h painting in November?
Your question about the studio…

Outcome

  • 5–7 hOf admin saved every week, the goal for anyone working alone
  • 0Double entry: changes go straight to Notion
  • 1View of what’s quoted, invoiced and left to invoice

Next: open it to other people who work alone the same way: craftspeople, designers, consultants, anyone who sells with quotes.

Brand

Fleet Brand System: a brand anyone at Fleet can use, without a designer.

Beyond the product, I take care of Fleet’s brand. In 2026 I rebuilt it twice: first as a visual language for the new website, then as a design system Claude can read. Now anyone at Fleet can make on-brand slides and one-pagers without going through design.

  • RoleBrand owner
  • CompanyFleet
  • Year2026
  • ToolsFigma, Claude

A visual language

It started with the website redesign. I built a set of illustrations around Fleet’s 9 core themes: onboarding, offboarding, catalog, logistics, inventory, security, storage, repair and second life. Each theme comes in two versions: a symbolic one, and one showing the product in context.

The product versions use real pieces of the Cockpit, staged on the brand background, so marketing visuals always show what the product actually does.

Every visual shares the same background recipe: deep green, a subtle dot texture and a soft rim light. One rule: a green gradient never appears without its texture.

  • 47 → 23Images on the new website, turned into 23 illustration masters
  • 9Themes, reused across pages
  • 2Versions per theme: abstract and product

A brand Claude can read

Then I turned the brand into a design system Claude can use: colors, typography, logos, backgrounds, illustrations and photos, plus written guidelines on how to use them in slides and documents.

From that system, I generated a 29-slide brand book: positioning, voice, foundations, imagery and applications. It documents the brand, and proves the system works.

Outcome

Anyone at Fleet can ask for a one-pager or a short deck and get an on-brand file in minutes, in a single conversation. For example, a one-pager for a product launch.

Next: training the account managers, so sales decks are made without a designer, on the same system.