Eight ready mechanisms, seven controls — palette, typography, density, corners, motion, light, structure — and one demonstration interface that answers on click. Pick a mechanism, change what does not look like you, send us the address: it reopens exactly your screen. If none of the eight fits, we build one.
Eight design mechanisms, adjustable on screen: palette, typography, density, corners, motion.
Open the workshopFor each trade, a practitioner's dashboard that opens for real and can be handled: a real move, a master indicator, a living moment. A bid desk, a public-procurement department, a workshop and its flows, a health centre, a product-and-revenue cockpit. Fictional data, stated as such; the move itself is the trade's own. The brand page of each of these houses is shown at the Studio, under “Creation, Design & Model catalogue”.
It shows where a brand slips, channel by channel, and opens the exact gap to fix — down to the 41 off-template product shots on the online store.
Who it is forIdentity studios, brand teams, houses running several channels at once.
HTML · CSS · SVG · JavaScript sans dépendance · bilingue · deux régimes
designed on 6 September 2026
It sorts 34 lots published within a 62 km radius, calls go / no-go with a written reason, and runs the countdown to the next submission.
Who it is forContractors, engineering practices and trades bidding for public work.
HTML · CSS · SVG · JavaScript sans dépendance · bilingue · deux régimes
designed on 6 September 2026
It filters 214 plots down to 7, reads what the local plan allows, and flags the planning notice posted 120 m from a tracked plot.
Who it is forDevelopers, land promoters, property traders and anyone assembling schemes.
HTML · CSS · SVG · JavaScript sans dépendance · bilingue · deux régimes
designed on 6 September 2026
It shows the room live on a Saturday at 19:42 — 62 covers seated out of 86 — the day's takings by venue, the evening's bookings and the margin on every dish.
Who it is forRestaurateurs, hoteliers and retailers running several sites.
HTML · CSS · SVG · JavaScript sans dépendance · bilingue · deux régimes
designed on 6 September 2026
It holds occupancy by ward, appointment waits, the day's theatre list and compliance deadlines — aggregates only, never a patient.
Who it is forClinics, health centres, group practices and coordinated care structures.
HTML · CSS · SVG · JavaScript sans dépendance · bilingue · deux régimes
designed on 6 September 2026
Secures the framework agreements reaching their term: three expire with no renewal procedure started, and the closest one falls in forty-seven days.
Who it is forA local authority procurement team preparing its monthly award committee.
HTML · CSS · SVG · JavaScript sans dépendance · bilingue · deux régimes
designed on 6 September 2026
Says where today's constraint is: a press is down, overall equipment effectiveness falls to 71.4%, and assembly now sets the output of the whole plant.
Who it is forAn operations manager starting a shift who must resequence before noon.
HTML · CSS · SVG · JavaScript sans dépendance · bilingue · deux régimes
designed on 6 September 2026
Recovers the version of a text that applied on the day of the transaction, shows what had changed just before, and says how many files depend on it — while the statutory deadline timeline runs.
Who it is forAn accountancy or law firm that must answer about a past date, not about the current state of the rule.
HTML · CSS · SVG · JavaScript sans dépendance · bilingue · deux régimes
designed on 6 September 2026
Ties recurring revenue back to actual behaviour: three paying accounts have stopped logging in, and the funnel shows the drop-off is not at import but at inviting a teammate.
Who it is forA growing software publisher choosing between acquiring more and retaining better.
HTML · CSS · SVG · JavaScript sans dépendance · bilingue · deux régimes
designed on 6 September 2026
Each piece opens full size, exactly as it runs; the live models are driven by hand.
Products designed then kept in reserve, each drawn for one trade and its morning gesture — plus the two dashboards that steer them, an executive's day and a salesperson's funnel. The versions set aside are here too, shown for what they taught.
An executive view at instant T: today's opportunities, files in go, contracts at risk, next deadline counting down, briefing. Every indicator is a probability, never a promise.
Who it is forAn executive who wants the state of their watch on one page, every morning.
designed on 6 July 2026
Detection, qualification, response, win: a funnel by stage with volumes and conversion rates, average days per stage, pipeline value.
Who it is forA sales management that tracks public prospecting like a private pipeline.
designed on 6 July 2026
“Your first public contract is within reach”: an informal voice, four figures, three layers — detect, prospect, anticipate — and one action per screen.
Who it is forA very small construction business that has never answered a tender.
designed on 6 July 2026
“I bid, but I rarely win”: success rate, lost contracts and why, the cross-reference graph — data that explains the loss before promising the win.
Who it is forAn SME of ten to fifty people that wants to win more often, not bid more.
designed on 6 July 2026
Six layers of watch, volumes by territory, the competition graph and an assistant that answers plainly: the screen of a team handling dozens of files.
Who it is forA mid-sized company with a dedicated team and targets by region.
designed on 6 July 2026
The radar turned towards studies: contracts by type, lots, buyers' history — the material that feeds a framing note.
Who it is forAn owner's adviser or programming firm that documents its studies with facts.
designed on 6 July 2026
Spot where public investment is accelerating — permits, budgets, facilities — to arrive before the private market.
Who it is forA developer, a planner who picks municipalities on signals, not rumours.
designed on 6 July 2026
Sell to the right site at the right time: contracts awarded in one's speciality, the winning company, the likely date materials are ordered.
Who it is forA distributor, a manufacturer selling to the companies that have just won.
designed on 6 July 2026
Spot who is about to hire before everyone else: the contracts won that call for crews, by territory and by trade.
Who it is forA recruitment firm, a construction-specialised staffing agency.
designed on 6 July 2026
Each piece opens full size, exactly as it runs; the live models are driven by hand.
A page does not begin at its first paragraph: it begins with the movement that introduces it. A converging cloud, a counting spiral, a map that rises, a file taken apart line by line — openings and waiting screens that say something instead of filling time.
A converging cloud of particles; every grain is an entity in the base, with a name, a sector, a use on hover. The scene the galaxy of sources comes from.
Who it is forA firm that wants to show the scale of its material without a table.
designed on 6 July 2026
A spiral of points and a rising counter: the public-procurement radar in a single movement.
Who it is forA page opening, a presentation, a trade show.
designed on 6 July 2026
The map of départements as a relief of points, filterable by layer, a national counter: the version that set the map's vocabulary.
Who it is forA national player that has to show coverage.
designed on 6 July 2026
An example company at the centre, its facts in orbit — capital, headcount, contracts, executives — linked by threads of light. The 360 profile as a hologram.
Who it is forA sales demonstration that has to fit in one image.
designed on 6 July 2026
A tender file read line by line — object, criteria, documents, deadlines — down to the verdict: go or no-go, with its score. “We read it before you do.”
Who it is forA bid team that wants to see what a file holds before opening it.
designed on 6 July 2026
Each piece opens full size, exactly as it runs; the live models are driven by hand.
A product is drawn as a skeleton before it is coded: the questions the screen must answer, the order they arrive in, and what stays out. Two skeletons — a buyer's workstation and the plan of a multi-world site — laid out before the first line, and re-read at every screen since.
A French firm of international reach, a wireframe globe, zones of operation: the page reduced to its structure.
Who it is forA firm deploying its trades on several markets.
designed on 20 July 2026
“What demands your attention”: the questions a buyer asks, each with its figured answer and its gesture — the workstation drawn before the code.
Who it is forA procurement department, public or private, that wants a tool that answers instead of displaying.
designed on 20 July 2026
Each piece opens full size, exactly as it runs; the live models are driven by hand.
What an executive must understand, and what the specialist opens the panel to find.
Metadata-driven forms, enforceable validation and interoperable exchange.
eForms SDK, UBL/XML, Schematron rules, TED CVS validation and AS4 exchange where required.
A site for two audiences in two languages, an index that returns the rule in force on the day of the facts, a configurator that redraws itself live: what we built, what it produced, and what was hard. Names removed, volumes kept.
TRACK RECORD · REAL ASSIGNMENTS, NAMES WITHHELD
Our own house — a firm with three practices, two audiences that are not looking for the same thing, and two languages.
When · Summer 2026, in production and reworked weekly.
What we did
We designed and built this site end to end: architecture, design, copy, three-dimensional scenes, and the English mirror. English is not a button that repaints the page — it is a set of URLs of its own, without which no search engine ever sees it.
What it produced
A two-world site, fully bilingual, where every English page has its own URL and its reciprocal link to the French one. Seven automated checks guard the release, chained behind a single command: background regimes, stylesheets, brand charter, text tones, structured data, per-language URLs, sub-page substance. The first defect stops the chain — it is a refusal, not a warning.
What was hard
The English already existed, but as a display state: no URL served it. Two states of one document are not two documents — the tag that links languages links URLs, and it had nothing to link. The URLs had to be split before we could hope to be read outside France.
Teams that must cite the rule applicable on the day of the events, and to whom a search engine always returns the latest version.
When · 2026, in production.
What we did
We indexed a versioned body of rules so that a search returns the version in force on a chosen date, not the most recent one. The vintage is a dimension of the index, not a filter bolted on afterwards.
What it produced
An index searchable by text and by date, kept separate from the warehouse it serves, and rebuildable without touching the one in service.
What was hard
The first rebuild deleted the old index before building the new one — and it could not finish: there was not enough disk space. Its own log gives the time of deletion, an hour and twenty minutes before it was stopped. Destroying before knowing whether you can rebuild is not a rebuild: it is a deletion followed by hope. Its replacement measures free space first and builds alongside; it can no longer touch what exists.
Brand and product teams that settle a visual direction on screenshots, then discover in development that the real rendering does not match.
When · Summer 2026, live.
What we did
We built a configurator that recomposes an entire interface live — typography, palette, density, corner radii, stroke weights — in the very code that ships to production. What is settled on screen is what is delivered: there is no translation step between the mock-up and the product.
What it produced
A single scene, mounted by the public page and by its reduced preview without being duplicated, and an exportable brief carrying the settings chosen.
What was hard
A configurator that lives beside the product ends up lying. This one shares its components with the site: the day a component changes, the demonstration changes with it — or it stops compiling, which is exactly the intended behaviour.
No client name is published, with or without their consent. We publish no win rate: it is not measured, and an unmeasured figure is not a reference.
Choose an incident: the journey shows what holds, what degrades and what must be recovered.
We design the smallest product slice that already delivers a complete service: user intent, data, decision, feedback and usage evidence. It is not a disposable prototype; it carries the contracts that allow the rest to be added.
The executive sees the nominal journey, degraded path and recovery. Value lies in what the user can complete, not in screen count or a demonstration that fails outside the perfect scenario.
State, contract, incident, degradation and recovery
Bounded context, ubiquitous language, aggregate, invariant and domain event set the vocabulary before the screen exists.
Explicit state machine: authorised transitions, preconditions, idempotent commands and an audit log.
Vertical slice linking interface, application logic, persistence, API contract, authorisation, tests and telemetry.
Progressive enhancement, empty/loading/error/offline states and recovery after interruption.
Design system tied to code: typed tokens, components, variants, properties, documentation and visual regression tests.
WCAG 2.2: semantic structure, focus order, name/role/value, target size, contrast, reflow, errors and alternatives — checked by a repeatable test suite and human review.
Core Web Vitals in field data: LCP, INP and CLS at the 75th percentile; lab and field are never conflated.
OpenAPI, backward-compatible versioning, consumer-driven contract tests and a schema evolution strategy.
Characterisation, unit, integration, end-to-end and accessibility tests, each tied to the risk it covers.
Feature flag decoupled from deployment, expand/contract migration, canary, rollback and a dated removal of the flag.
SLI/SLO, error budget, distributed trace, correlated logs and alerts oriented on user-facing symptoms.
ADR, SBOM, dependencies, runbook, reversibility, access and proof of restoration in the handover file.
Evidence discipline: an uninstrumented event remains N.F. — it never becomes an implicit success; keyboard, reduced motion, slow connection and dependency failure belong to the reference scenario.
The slice demonstrates a journey that has been tested and traced within its declared scope; it replaces neither the client’s real business rules, nor a human accessibility audit, nor field measurement under real conditions. Any transition without an instrumented trace remains N.F., never an implicit success.
Four questions we ask on every file in this domain. Each comes from an incident someone paid for — us, or a client before us.
A screen that helps no decision is a decorative dashboard. Every screen we design starts from the decision it serves, then the data that grounds it, and only then the form.
If nobody asks it — A beautiful interface, full of figures nobody uses.
No hard-coded figure: every number is wired to its source or carries its date in the same sentence, and a missing value is shown as missing — never as a zero.
If nobody asks it — A frozen number that never ages and turns wrong all at once, with nothing to flag it.
We deliver the system with its executable checks, its handover documentation and its repair instructions printed by the very tool that reports the failure — not in a manual someone would have to think of looking for.
If nobody asks it — A product that depends on its author, hence on a single point of failure.
A serious product has guardrails: it refuses to write when the count is off, it refuses an entry that contradicts a business rule, it says what it does not know. We design the refusals together with the features.
If nobody asks it — A database that accepts everything, and data nobody can vouch for any more.
A file rarely draws on a single discipline.