Applications and dashboards
An application built around the way you work, not the other way round.
When a spreadsheet or off-the-shelf software is no longer enough, I build a targeted application: a space for your customers, a tracking screen for your team, a tool for a specific task. You test it before the handover, and you stay in control.
Does this sound familiar?
Everything lives in a fragile spreadsheet
Several people edit it, and nobody knows which version is the right one.
Your customers write to you about everything
Where is my file? What is the price? Every question goes through an email or a call.
Off-the-shelf software does not fit
Too expensive, too broad, or missing exactly the feature you need.
What happens if nothing changes
- Time goes into looking for information instead of using it.
- Version mistakes and oversights keep happening.
- Your customers wait for answers that a simple page could give them.
These are common situations, not a measurement of your business.
How I build it
- 01
Define the essentials
Who uses the application, for what, and with which permissions. I write the screens and the tests before building.
- 02
Build and test
A first version on your real cases, tested with the people who will use it, errors included.
- 03
Hand over and evolve
Access in your name, documentation and a handover session. Changes are decided together.
What you receive
- An application limited to a specific need, within the scope written in the quote.
- Accounts and access rights defined for each type of user.
- Tests on normal cases and on errors, carried out with you.
- Access in your name, documentation and a handover session.
Examples of applications
- A mobile menu or catalogue you can edit yourself
- A customer portal with case tracking
- A tracking dashboard for the team
- An internal tool for a specific task
The technology is chosen according to the number of users, the data and what you need to be able to edit yourself.
Limits
- An application is built for a defined use: I start small and useful, not with a complete software package.
- Hosting and the services used are billed by their providers, preferably in your name.
- A specialised security audit is covered by a separate agreement if your business requires it.
My commitments
What I commit to on every project.
These rules apply from the first call to the handover.
The price before you decide
Scope, deliverables and price are written in the quote before any work starts.
Accounts in your name
Tools, access and subscriptions stay yours. You can take back control at any time.
A person approves
Important actions, such as sending or publishing, are approved by someone on your team.
No invented figures
Fictional examples are labelled as such. A client project is only shown with the client’s consent.
I tell you when not to build
If a simpler tool is enough, or if nothing should be built, I tell you.
Frequently asked questions
- How long does it take?
It depends on the scope. A first targeted version takes a few weeks to build; the timeline is written in the quote.
- Do I own the application?
Yes. The accounts, hosting and data stay in your name, and you receive the documentation to take back control.
- How much does it cost?
The price depends on the screens, the users and the tools to connect. You receive a written quote before deciding.
Let’s talk
Let’s talk about your application.
Describe the task or the spreadsheet that is causing you trouble. We look together at what can be built, and what can stay simple.
Free 15-minute first conversation, remotely or in Lyon. Every project is quoted individually.