A tab in your name inside Excel, with your buttons: call the official API of the tool you already use, launch your Python script, check a 40,000-row sheet, follow statuses, import documents, turn out a finished deliverable. What takes you twelve operations becomes one click.
Three ribbons built for three different trades. Each button shows what it does, how it is wired, an extract of the code actually delivered, and the result in the sheet. Switch tabs to switch trade.
What the user sees
Execution log
The code extracts are deliberately shortened (error handling and configuration removed) but faithful to what is delivered: readable VBA and standard Python, commented throughout.
Eight families of functions, which combine. Most projects mix three or four of them: we start from your daily gesture, not from the technology.
If the software you use publishes an API, your ribbon can talk to it directly: no more double entry, no more manual export-import.
Already have scripts that run on the command line? They become buttons, with their parameters taken from the sheet and the result fed back in.
When the computation is heavy or shared by the whole team, we expose it as a small local or server service, which Excel queries like any other API.
The button reads the whole sheet back and tells you what is wrong, before the client, the authorities or the auditor does.
One state per row, dates set automatically, a dashboard that updates itself and reminders that go out on their own.
Your house style, your colour codes, your reading rules — applied in one click to any table, and reversible.
Files arriving by e-mail or through the portal become clean rows, with no copy-and-paste.
The document you redo every week comes out of your own layout, filled in, saved in the right place and ready to send.
The foundation of DossiersLocaux, extended without the 7-tool limit, and wired to the applications you keep open all day.
Cases representative of what is most often asked for. The figures are the ones reported by users after a few weeks of use.
Before: every new client file meant 20 minutes of typing, creating folders and copying the company number across from an official site.
The ribbon: one button creates the standardised tree, another completes the client record from the company registry API, a third checks the sheet (invalid company numbers, duplicates, inconsistent financial years) and a last one turns out the engagement letter as a PDF.
Result: 20 minutes brought down to under 2, and an end to wrong company numbers discovered at filing time.
Before: quantities were recalculated by hand in a workbook, and the client's bill of quantities was copied item by item from a PDF.
The ribbon: the in-house Python calculation engine, until then run on the command line by one person alone, became a service called from Excel; the PDF import fills the framework in 15 seconds.
Result: the whole office uses the same engine, and the rate table is updated in one single place.
Before: rents received were ticked off row by row against the bank statement, then receipts generated one at a time.
The ribbon: statement imported, automatic reconciliation paid / partial / unpaid, colour-coded statuses, bulk generation of PDF receipts and e-mails, graduated reminders with a log.
Result: half a day recovered every month, and no more forgotten arrears.
The usual reflex is to go for dedicated software or a web application. That is not always the right sum.
No 40-page specification for you to write: we start from your current file and from the way you work today.
30 to 45 minutes on the phone. You show your file and your usual operations; we spot what turns into buttons.
FreeEvery button is priced separately, with any network calls listed in black and white for your IT department. You decide what you keep.
Within 48 working hoursYou approve the tabs, the groups, the labels and the icons before a single line of business code is written.
A few daysDelivered in batches of buttons, tested on your real data. You correct course as you go, rather than at the end.
2 to 6 weeks depending on scaleFinal workbook, commented source code, illustrated instructions and a handover session with the team. Then 30 days of corrections included.
30-day guaranteeIndicative prices including VAT, to give you the order of magnitude before you even call us. The real quotation is drawn up item by item, and you are only committed once you have accepted it in writing.
Two or three buttons that settle the most painful gesture.
The most frequent case: the whole chain, from data entry to deliverable.
When a calculation, a model or a heavy process enters the loop.
Our guide details the customUI file, the VBA callbacks, the Office icons and the mistakes that make the tab disappear. Enough to judge for yourself — or to do it yourself if your need fits in three buttons.
Read the guide “Adding your own buttons to the Excel ribbon” →In most cases, no: the ribbon lives in the macro-enabled workbook (.xlsm), you just open it and allow macros once. An installation is only needed if the project embeds a Python runtime or a COM add-in — in which case a silent installer is provided to the IT department, with the list of what it puts down.
Only towards the services you explicitly ask to query, and only with the fields the call needs. A ribbon can perfectly well work entirely offline.
The addresses contacted and the data sent are listed in the quotation: your IT department approves before a single line is written.
That happens often. There is nearly always a way through: importing and exporting files in a watched folder, reading the software's database, driving its interface as a last resort, or going through the files it already produces (PDF, CSV). This feasibility is checked during scoping, before the quotation — and if no clean route exists, we say so rather than sell you a contraption.
You do. The code is delivered open and commented, with no obfuscation, no VBA project password, no licence to renew. You can modify it yourself, hand it to another supplier or share it internally.
The custom ribbon and the VBA do work on Excel for Mac, but several of the building blocks used on Windows do not exist there: Outlook automation, some system calls, driving a third-party application. A Mac project remains possible with an adapted scope, stated clearly in the quotation.
Since the code is with you and commented, nothing seizes up overnight. For outside connections, the API address and version are isolated in a settings sheet, which lets you correct them without touching the code. An update can be ordered by the half-day, with no compulsory maintenance contract.
Yes, both ways: adding buttons to a workbook you already own, or starting from DossiersLocaux and lifting the 7-external-tool limit to graft your own functions onto it. Taking over an existing file is often cheaper than starting from scratch.
Allow 48 hours for the quotation, then 2 to 6 weeks of development depending on scale, with intermediate deliveries: the first buttons are usually usable after ten days.
The one you redo every week, in twelve operations. It is almost always the one that turns into a single button.
✉️ Answer within 48 working hours · Detailed quotation, item by item · No commitment before written acceptance