Home/How it goes
Representative scenario

Six weeks, from the first call to going live.

An energy-renovation company, twelve people, in Wallonia. Here is what it lives with today, what happens week by week, and what its daily work looks like at the end.

This is not a client. It is a representative company, written as close as possible to what the trade actually looks like: renovation grants and their technical annexes, the reduced VAT wording, the works declaration, the electronic invoicing that became mandatory in January 2026. The real delivered projects are on the Projects page.

[ 01 ]Where they start

The company, before

Nothing unusual here: this is the normal state of a company that grew faster than its tools.

BusinessWindow frames, roof insulation and heat pumps, for private homeowners, in Wallonia.
The teamTwelve people: the owner, two sales reps, three installation crews, one person on admin.
What runs the companyOne spreadsheet for quotes and supplier prices, Outlook, three WhatsApp groups (one per crew), a shared calendar, an invoicing tool, and an external accountant.
The subscriptionsThe invoicing tool, online storage, and a quoting tool bought two years ago that nobody opens: it does not carry the supplier prices.
Process timeA quote is built by retyping three supplier catalogues. Site photos stay on phones. The grant paperwork is filled in by hand, file by file, after the installation.
The needKnowing, without calling anyone, where each file stands between the visit, the quote, the deposit, the supplier order, the installation, the final invoice and the grant application.
The scopeAround sixty files open at once, from the first call to the grant payment, sometimes spread over six months.
What can get expensive
  • One technical annex forgotten or one final invoice sent past the deadline, and the client loses their grant. The client remembers that for a long time.
  • The reduced-VAT wording mishandled on an invoice: the company carries the risk as long as the document is not right.
  • A works declaration forgotten the moment a subcontractor sets foot on a site.
  • Since January 2026, invoices between companies must be sent as structured electronic documents. A spreadsheet cannot do that.
  • Only one person knows how the spreadsheet is built. When they are on leave, the company slows down.
[ 02 ]The timeline

Week by week, and what gets delivered each time

These durations are those of a business tool of this scope. They stretch with the scope, never mid-project without you knowing.

01
01 · Week 1First contact and audit of what exists

Half a day in the office, half a day with a crew on site. I look at the quoting spreadsheet, the WhatsApp groups, the inbox, and I time what gets redone by hand. I propose nothing that day.

What gets delivered

An audit note: where the time goes, and what can be fixed without writing a line of code.

Around the table : The owner, admin, one crew lead
02
02 · Week 1Design and specification

We write down what we are building, and above all what we are not. Everyone's constraints go in: the rep wants to produce a quote during the visit, the installer wants three buttons usable with gloves on, admin wants the grant paperwork pre-filled, the accountant wants a compliant invoice.

What gets delivered

A signed-off specification: scope, out of scope, business rules, screens listed.

Around the table : Everyone who will use it
03
03 · Week 2Architecture

The data model, with the client file at the centre: from enquiry to grant payment. The connections to what exists: supplier catalogues, invoicing tool, accountant. And what has to run on a phone with no signal, because a building site does not always have coverage.

What gets delivered

The data diagram, the list of integrations, and every technical choice justified.

Around the table : The owner, me
04
04 · Week 2Quote

The price comes here, not before: I don't price what I haven't described yet. Split by batch, with what is optional and what can wait for a version 2 without holding up go-live.

What gets delivered

A firm quote, batch by batch, with a committed go-live date.

Around the table : The owner
05
05 · Weeks 2-3Prototype

The real screens, clickable, filled with their own data: their last three jobs, their real prices, their real client names. Not a template, not placeholder text. It is the first time they see their company inside a tool.

What gets delivered

A prototype they open on their own phone, outside any meeting.

Around the table : Everyone, on their own time
06
06 · Week 3Presentation and dry run

We replay a complete file in front of the team: the visit, the quote, the deposit, the supplier order, the installation, the invoice, the grant annex. The people who will use it correct things there, while fixing is still free.

What gets delivered

A prioritised list of corrections, and the scope of version 1 locked.

Around the table : The whole team
07
07 · Weeks 3 to 5The development loop

Three identical rounds, one week each. The same URL throughout: they open it whenever they want to see where things stand. No black box, and nothing ships without going through the automated checks.

The loop in detail, below
What gets delivered

A usable version, more complete each time, at the end of every week.

Around the table : Me, plus one point of contact on their side
08
08 · Week 6Deployment and go-live

History imported from the spreadsheet, the tool goes live, team accounts created, a user manual, and half a day of hands-on onboarding with the crews. The tool isn't delivered when it's online: it's delivered when the first real job has gone through it.

What gets delivered

The tool in production, their data inside, the team trained, the code in their own repository.

Around the table : The whole team
[ 03 ]The loop

One week, one round, a version you can open.

This is what replaces the three-month tunnel. At no point do you wait until the end to discover what you bought.

12343ROUNDS
01

I build the week's batch

A batch announced in advance, never a surprise.

02

The pipeline checks it

Types, tests, build: if it doesn't pass, it doesn't ship.

03

They test it for real

On a real file from that week, not on a test fixture.

04

Their feedback enters the next batch

Fixes and adjustments go round again.

[ 04 ]Where they land

The company, after

One place: the client file, from the first enquiry to the grant payment. Everything else follows from that.

What goes away
  • Retyping supplier prices for every quote
  • Three WhatsApp groups acting as the company's memory
  • The spreadsheet only one person can read
  • Hunting for before-and-after photos, file by file
  • Grant paperwork filled in by hand after the installation
What appears
  • A quote built from the price library, sent during the visit, with the legal wording already in it
  • Photos attached to the file straight from the phone, even with no signal on site
  • Grant paperwork pre-filled from what the file already holds
  • Alerts on deadlines: grant cut-off, unpaid deposit, declaration still to file
  • One page showing the owner the state of every file, without calling anyone

And what doesn't change: the team works the way it always did. The tool bent to them, not the reverse.

Does your company look like this?

Describe your situation in two lines. The first call is about finding
where your time goes, not about selling you anything.

contact@amauryandrade.com