Ristrutturare per Te — built for dusty boots, not enterprise dashboards.
A bilingual workforce management tool for a residential renovation firm — designed around how a real construction team actually moves through a day.
A multilingual team needed software they could actually use.
Ristrutturare per Te is a renovation firm in Padova working on residential projects across the region — kitchens, bathrooms, full apartment refurbishments. Like much of the trade in northern Italy, the workforce is mixed: Italian project leads, Arabic-speaking workers, a handful of specialists who speak both.
The problem wasn't unusual. Existing construction software is built for office managers, not site workers. Dense interfaces. Long forms. English-only labels. Features for things nobody asked for. Meanwhile, the actual coordination — who's on which site, what was finished today, which materials are running low — was happening through phone calls, paper notes, and a memory bank held mostly by one or two people. Information was lost daily.
The brief was simple in shape, demanding in detail: a tool the workers themselves would use, in their own language, on the phones they already carry — and a tool the office could trust to give them an honest picture of what's happening on every site.
The tool has to fit the hand using it. Not the other way around.
Three roles, two languages, one shared truth.
We built around a simple principle: every screen should be designed for who's actually looking at it. A worker on a site doesn't need the same information as a project manager in the office, and neither needs what the owner sees in the reporting layer. Three tiers, three experiences, one underlying system.
Workers — what's mine, what's done.
The worker view is intentionally narrow. Today's tasks. The site address. A clock-in button that uses GPS to confirm the worker is where they say they are. Photo upload for finished work. Material requests in two taps. No dashboards, no analytics, no clutter — just the next thing to do, in Italian or Arabic, depending on the user's preference.
Masters — the project leads.
Masters coordinate teams across sites. Their interface shows live status of every active project, who's on each site today, what's been completed, what's blocking. They assign tasks, approve material requests, and answer the daily question every project lead asks: where are we, really?
Superadmin — the office layer.
For ownership and finance. Project margins, hours by site, invoicing-ready breakdowns, materials spend over time. The view that lets the business see itself clearly enough to make decisions — without anyone having to compile a spreadsheet on a Saturday.
Bilingual from the first commit.
Italian and Arabic weren't bolted on — they were a foundational requirement that shaped every decision: typography that reads cleanly in both scripts, layouts that respect right-to-left reading, terminology that translates accurately rather than literally. A worker should never feel like the tool is fighting them in their own language.
A team that uses the software — willingly, daily, in its own language.
The hardest measure of any internal tool is the simplest: do people actually use it? When the answer is yes, everything else follows — because every clock-in, every task update, every photo of finished work feeds into the same system the office relies on for reporting and billing. When the answer is no, you have an expensive logging app that nobody's logging in.
From day one, the workers used it. Not because they had to — because the friction of using it was lower than the friction of not using it. Material requests that used to require a phone call became two taps. Hours that used to be reconstructed from memory at the end of each week became automatic. The office finally has the truth of what's happening on every site, in real time.
The system continues to evolve. Reporting layers are deepening. Integrations with accounting are next. The work, like construction itself, is unfinished by design.
The tools we used.
Software for trades is usually designed in cities for people who never get on site. We tried the opposite.
Building something spreadsheets can't hold?
Tell us about your team and how they actually work. We'll be honest about whether a custom tool is the right answer.