Service · 2026
We design your web applications & SaaS
Dashboards, back-office, customer portal or SaaS product: we design clear interfaces for everyday use, validated on a prototype before the first line of code.
[ They trust us ]
More than 100 French and European companies trust us
[ Scope ]
What the design of your web application covers
The six parts of visual design, applied to what makes a web application: dense screens, several user profiles and a product that keeps evolving.
- 01
Personas and user journeys
Who logs in, with which role, to get which task done: administrator, business user, end customer. Each profile has its own journeys, mapped before any screen is drawn.
- 02
Visual identity and interface guidelines
Your brand guidelines adapted to the screen, or created if needed: a palette with checked contrasts, type that stays legible on figures and tables, consistent icons.
- 03
Wireframes
The structure of each screen, without the styling: navigation, information hierarchy, where filters and actions go. We validate the logic before the look.
- 04
UI mockups
Every screen in high fidelity in Figma, for desktop, tablet and mobile, with its states: loading, empty, error, success, access denied.
- 05
Wording and microcopy
Labels, buttons, error messages, help and onboarding text: short, precise words in your users' vocabulary, not the database's.
- 06
High-fidelity interactive prototype
The screens linked in Figma so you can move through the application as if it already existed. It is used for user tests, for sign-off by your teams, then as the reference for developers.
[ Web specifics ]
What a web application asks of design
A web application is not a showcase website. We design it for long sessions, screens of every size and users who don't all have the same rights.
- 01Responsive, from wide screens to mobileEach screen is designed from the wide monitor down to the mobile browser. On small screens we set priorities: what stays visible, what collapses, what moves into a menu.
- 02Dense business interfacesDashboards, data tables, filters, search, bulk actions: we organise a lot of information without making it unreadable, for people who use it every day.
- 03Onboarding and empty statesA SaaS product is often discovered alone. First account, empty workspace, feature never used: each case is designed to lead to the first useful action.
- 04Roles and permissionsWhat an administrator sees, what a read-only user doesn't, what appears when a permission is missing: access rules are translated screen by screen.
- 05Design system and componentsColours, type and spacing as tokens, components with all their states (hover, focus, disabled, error): a Figma library built to be carried over into the code.
- 06Accessibility (WCAG)Contrast, text size, visible focus, keyboard navigation, field labels: WCAG criteria are built into the mockups, not fixed afterwards.
- 07Performance from the mockup stageImage formats and weight, number of fonts, a clear heading and page structure: the design choices that affect loading time are made knowingly.
- 08Theming and white labelIf your SaaS serves several organisations or is sold white-label, the design system plans for the variations: logo, colours, type. One product, several identities.
[ Process ]
Five steps, from workshop to development.
Design moves forward through successive sign-offs. Each step ends with a review with you, and no screen goes into development before it has been approved.
- 01
Kickoff workshop
We go through the specification with you: goals, user profiles and their roles, priority screens, existing brand guidelines, the project's technical constraints.
- 02
Journeys and wireframes
We map the journeys and the application's information architecture, then draw wireframes of the key screens. The structure is approved before styling starts.
- 03
Visual direction and design system
The visual direction is tested on representative screens, such as a dashboard or a filtered list. Once approved, it becomes the foundation of the design system.
- 04
Mockups and prototype
Every screen is designed responsive with its states, then linked into an interactive prototype to be tested by your teams and, when possible, by real users.
- 05
Handoff and development follow-up
Annotated mockups, documented components and the prototype go to the developers. The designer then follows development: questions, trade-offs, visual review of the screens.
[ Deliverables ]
What you receive
Concrete deliverables, shared in Figma, usable by your teams and by the developers who take over.
- Personas, user journeys and screen architecture
- Wireframes of the key screens
- Responsive UI mockups (desktop, tablet, mobile) with their states
- Interface guidelines and Figma design system: tokens, components, usage rules
- Interface wording: labels, messages, onboarding text
- High-fidelity interactive prototype
[ Funding ]
20%
of outsourced development costs
Innovation Tax Credit
CII-accreditation: your company can claim a tax credit on the outsourced costs of developing a solution that is new and innovative in its reference market.
50%
of the diagnostic subsidised by Bpifrance
Bpifrance Innovation expert
The “Diag Axes d'Innovation” programme: we help SMEs and mid-caps identify their innovation paths and assess the feasibility of their projects, upstream.
