Replace the shared Excel file with an internal tool, no code needed.
The call-out, request or equipment file that three people open at once becomes an app: a screen to enter, a list to follow, one account per colleague. Each row lands in a database hosted in France, and IT can read how the tool works in Kubbler.
Updated on
Demo: Clim Est, a fictional air-conditioning and heat pump installer in Metz, and the quote-tracking tool its sales team uses, built with Kubbler.
Three blocks at the door
In the page tree, the team's home page comes down to three blocks: the sign-in banner, the four-step how-to and the sales reps' questions.
The follow-up ladder
The page being edited: the heading "Le suivi des devis de l'équipe" and the four-step ladder, from "plus tard" to "en retard", that every quote sits on.
Where the figures come from
The Monday-figures block (dashboardKpis) calls a single route, GET /quotes/summary, which works everything out from the quotes collection. No total is typed in.
The team's way in
The published tool opens on a "Se connecter" button: access is limited to the sales team, and each person creates an account with their work email.
Clim Est, a demo built with Kubbler.
Clim Est installs heat pumps and air-conditioning around Metz; its five sales reps send about 300 quotes a year. Their tool replaces the devis_2026_v9.xlsx file: every quote carries a next follow-up date, and Monday's dashboard is worked out from the quotes on record.
80 quotes on record: 31 sent, 16 followed up, 19 signed, 14 lost
5 sales reps and 1 director, the only one who sees the Équipe page
A 4-step follow-up ladder, from green "plus tard" to red "en retard"
Clim Est is a fictional company: its quotes, its Moselle customers and its sales reps are demonstration data.
The whole site, page by page
Each thumbnail is a complete page of the demo, as a visitor sees it. On a computer, hover one to scroll through it.
A quote typed up in the evening, in Monday's figures.
What a sales rep does in the tool, screen by screen, and opposite each one, what the person who built it reads in Kubbler.
The list, sorted by follow-up
Every quote the team has out, most urgent first: SCI Les Tilleuls in Metz, €28,700 excl. VAT and eleven days overdue, tops the list. Tabs count the quotes by status, and a menu filters them by sales rep.
The tool's pages, one at a time
The home page open in the Workshop, its page tree on the left. The page picker at the top leads to Tableau de bord, Devis, Nouveau devis and Équipe: a label or a photo gets fixed before the next meeting.
A new quote, with its follow-up date
M. et Mme Weber, Woippy, air-to-water heat pump, €15,900 excl. VAT, sent on 16 October. The J+3, J+7 and J+14 buttons set the first follow-up, here the 23rd, and the box on the right shows the quote as it will appear in the list.
One route behind the figures
In the Mechanisms view, the inspector for the dashboardKpis block shows the page that displays it and the route it calls, GET /quotes/summary, wired to the quotes collection. So the Weber quote counts in Monday's figures the moment it is saved.
The follow-up, logged
Garage Fischer Automobiles, €18,900 excl. VAT, four days overdue. The history keeps Thomas Weber's two calls, including "Accord de principe du gérant"; the panel on the right adds the next one: status, what was said, next follow-up.
80 quotes, row by row
The quotes collection's table: customer, town, project, amount excl. VAT, date sent, status, next follow-up, sales rep. Follow-ups live in a separate collection, and in production both open read-only in Kubbler.
Screenshots: Clim Est, the internal tool of a fictional installer in Metz, built with Kubbler and filled with demonstration data.
Monday's meeting opens on three figures nobody had to work out.
Pascal Hoffmann, the sales director, plugs his laptop into the screen in the small meeting room and reads out the week of 17 to 23 October. The three black arrows at the top, each rep's row underneath: it all comes from the quotes on record, and nothing has been retyped from devis_2026_v9.xlsx. Everyone leaves with their follow-ups for the week.
21 quotes to chase
Of which 9 are overdue and 4 due today; next to them, €170,600 signed in October across 9 quotes, and €562,450 still awaiting an answer.
One row per sales rep
Sarah Klein: €45,700 signed this month on 2 quotes, 11 open quotes worth €99,650, and a bar that sets her against the other four.
Each rep's follow-ups
On her row, the red "3 en retard" tag and "5 à relancer": the list further down the page takes those quotes one by one, the most overdue first.
What IT would check, what your team keeps changing.
Accounts, hosting and backups are shared by every tool built with Kubbler. Fields, screens and lists follow the way your team works, and you are the one who changes them.
Our part
What a file on the shared drive never had, provided and maintained by Kubbler.
One account per colleague
Everyone signs in with their own credentials: email verified at sign-up, password reset and two-factor authentication are provided. No more file password going round by email.
A database in France
At OVHcloud, over HTTPS, reserved for your tool and backed up automatically. Two people can enter data at the same time without overwriting each other's work.
Trials kept apart
A Dev environment to try a new field, a Prod environment for the team, each with its own database: a failed trial touches no real call-out.
Your part
What the team asks for in the Monday meeting, and what you add without opening a ticket.
The fields
A new call-out type, a "part ordered" column, a field made required: you go through "Edit the schema" in the Workshop. A change that would break existing rows creates a new version of the schema.
Screens and lists
A list sorted by day, a screen for the week's schedule, a clearer label: you make the change with the mouse, or describe it to the AI.
Who administers, who enters
The tool knows two roles: administrator for the operations manager, user for the assistant and the technicians. Every screen shows whether it requires signing in.
Monday, 8:30, the file is locked by another user.
The call-out file has lived on the shared drive for years. It is called something like interventions_v14_FINAL.xlsx, it has one tab per month and a "status" column nobody keeps up to date. When the assistant opens it to log a call, the manager can no longer edit it. When a technician calls from the van to ask where to go next, someone hunts for the right row while they wait.
The usual ways out each have their price. The IT project waits its turn behind the group's other projects. Off-the-shelf field service software handles the schedule, but imposes its own screens and is often billed per user. The online tool a colleague put together helps out, until the day they change jobs: nobody knows any more what the Save button does, or where customers' addresses end up.
With Kubbler, you describe the file and how the team uses it; the AI builds the screens, the form and the collection, while accounts, hosting in France and backups come from the shared foundation our team looks after. IT does not have to take your word for it: in the Workshop, it reads the schema of each collection, the chain from the form to the collection, and which screens require signing in. If the person who built the tool changes jobs, whoever takes over reads what exists instead of guessing.
What it costs
One project and 500 sparks a month, the budget that pays for AI generations. Packs can be added if you need more.
With your own domain: €44 excl. VAT a month.
No commitment. The domain name itself is paid separately.
See all pricesWhat to have ready
The current file, however messy: its columns become the tool's fields.
The values that keep coming back: call-out types, urgency levels, technicians' names.
The path of a request: who enters it, who assigns it, who closes it.
Who administers the tool, and who only enters or looks things up.
A contact in IT, if they want to review the tool before it goes live.
Nothing else: no specification, no mock-up.
The questions we get asked.
Including the ones where the answer is "not yet".
Not yet. Kubbler reads neither Excel nor CSV files, and rows already entered do not move into the new collection on their own: ongoing call-outs have to be entered again. Describe the file's columns, the AI derives the collection's fields from them, and you adjust them in the Workshop.
Not finely, for now. The tool knows two roles, administrator and user, with no rights per department or per technician. Kubbler's viewer, editor and admin roles are for the people who build the tool; they do not apply to the people who use it.
No, and no phone notifications either. The tool opens in the phone's browser and adapts to the screen: nothing to install, and the technician sees the same list as the office.
Not yet: there is no company single sign-on (SSO). Each colleague creates an account in the tool, with a verified email and two-factor authentication available.
The Starter plan comes to €29 excl. VAT per month. Hosting the tool is extra: €5 excl. VAT per month while it stays on kubbler.app, €15 excl. VAT per month once it runs on your own domain. No commitment. Colleagues who use the tool have an account in it that takes no Kubbler seat; seats only count the people who build it.
By reading it in Kubbler. Invited as a viewer to your workspace, IT opens the schema of each collection, the chain of mechanisms and the list of screens that require signing in, without being able to change anything. Each invited person takes a seat: the Team plan has three. IT can also export the API description as OpenAPI 3.0, and rely on a DPA (GDPR article 28).
Describe the file the team no longer wants to open.
In the Studio, you explain what the file holds, who fills it in and who reads it. The tool is built from that account; you review it screen by screen, and IT can review it in turn before it goes live.