Internal product project
Intranet Vauban
Design internal tools that adapt to teams, rather than asking teams to adapt to tools.
Intranet Vauban was not designed as a mere document portal, but as a platform of business tools. Each module addresses a concrete pain point: tracking a campaign, approving an invoice, generating an email signature, computing a commission, importing after-sales requests, centralizing data or streamlining an internal process.
Intranet Vauban
Dashboard
Spend
€ 248k
+4%
Leads
1,326
+12%
AS bookings
412
+7%
Campaign steering
7 dPending approvals
- Invoice #1284 — Print shopPending
- Expense — A. MartinApproved
- PureTech campaignTo publish
01 · Context
When standard tools complicate life on the ground
In many companies, teams end up stacking tools: one for expenses, another for leads, another for expense claims, another for signatures, an Excel file for commissions, a shared folder for documents, and then emails to fill the gaps. The result: data scatters, processes become fragile, employees waste time and adoption remains uneven.
Costly external tools
Licenses, maintenance, setup, training.
Business processes bypassed
Teams have to change the way they work.
Scattered data
Excel files, emails, exports, multiple platforms.
Fragile adoption
An imposed tool is rarely an adopted tool.
02 · Approach
Start from the real process, not the vendor's datasheet
The approach is to observe usage, identify pain points, then design simple modules around existing working habits. The tool becomes a natural extension of the team. It doesn't replace business expertise: it structures it, speeds it up and makes it more reliable.
Before
- Isolated Excel files
- Approvals by email
- Manual exports
- Different tracking per team
- Costly external tools
- Long, low-engagement training
After
- A centralized interface
- Modules designed per team
- Structured data
- Faster actions
- Less re-entry
- Easier adoption
03 · Modules
An intranet built as a suite of business tools
One platform per team, with focused, independent modules. Select a service to explore its tools.
Marketing
The Marketing module centralizes the tools needed to steer campaigns, track budgets, produce internal assets and standardize group communications.
Previews
The interface in action
04 · Benefits
An intranet can become an operational advantage
Natural adoption
Tools are designed around existing processes. Teams don't have to unlearn the way they work: the interface simply streamlines what they already do.
Time saved
Less re-entry, fewer back-and-forths, fewer scattered files. The time saved goes into higher-value tasks.
Potential savings
Building a focused internal tool can avoid piling up external licenses, setup fees, long training sessions or oversized solutions.
More reliable data
Information is centralized, structured and historized. That reduces errors and makes steering easier.
Employer brand
The company shows it listens to field pain points and invests in concrete solutions to improve teams' daily work.
Fewer imposed tools, more useful ones
The goal is not to digitize for the sake of it, but to build interfaces that are useful, quick to grasp and directly connected to daily missions.
Productivity
Fewer repetitive tasks.
Steering
More readable, actionable data.
Costs
Fewer unnecessary external solutions.
Internal culture
A sense of being heard and improving continuously.
05 · Method
A simple method: listen, prototype, test, improve
- 01
Identify a business pain point
Too many files, too much data entry, poor visibility, slow approvals.
- 02
Understand the real process
Observe how teams actually work, without imposing a theoretical model.
- 03
Design a simple module
Build a focused interface with only the useful features.
- 04
Test quickly
Put the tool in users' hands to adjust fields, filters, statuses and exports.
- 05
Improve continuously
Evolve the tool based on feedback and new needs.
Skills mobilized
Between strategy, product, automation and employee experience
My role
Design, structure, prioritize, engage
I designed the intranet as an operational answer to teams' needs: pain-point identification, module structuring, interface design, use-case prioritization, automation logic, adoption thinking and positioning of the project as an internal lever.
06 · Demo
An intranet designed as a living product
Intranet Vauban embodies a simple conviction: the best internal tools are not necessarily the most complex or the most expensive. They are the ones that understand the trades, respect useful habits, remove friction and give teams the means to work better.
Explore the demo
A functional demonstration built as an internal product prototype.
Next project
Vauban Classic