AutoCAD, email and an Excel sheet: the hidden cost of coordination in Italian technical firms
In Italian architecture and engineering firms the problem isn't a lack of technical skill: it's that this skill is often held back by an operational structure that can't keep pace. AutoCAD for production, email for coordination, Excel for deadlines: three powerful tools, used together to do things they were never designed for.
This isn't about abandoning AutoCAD, which remains the right tool for technical production. It's about all the work around it: coordination, deadlines, communication with the client, and the hidden cost of doing it without a structured system.
The patterns we see most often
- The Excel deadline sheet is never updated at the right moment: when a deadline slips, the knock-on impact on the other activities stays invisible until someone discovers it by hand.
- Emails become the project archive: decisions, variations and client requests end up in threads that after a few months no one can follow anymore.
- The owner acts as the project switchboard: without a central system, they're often the coordination hub, a bottleneck that doesn't scale.
What doesn't need to change, and what does
AutoCAD stays where it is, project files stay where they are (server, NAS, cloud), emails for client communication can stay. What needs to be added is a coordination layer: a place where tasks, deadlines, dependencies between activities and the progress of each project live, not to replace the existing tools but as the project's nervous system. In the technical firms we've worked with, introducing Wrike as a coordination layer didn't require changing the technical tools: it required moving the management of "who does what and when" from email and Excel to a system designed specifically for that.
How much not having a coordination system costs
Before an implementation we ask professionals to track, for one week, the time spent on pure coordination: looking for files, chasing updates, answering "where's the project at?", sending alignment emails. In the 4 technical firms we analysed, the average result is between 4 and 7 hours a week per professional: on a team of 8 people, between 32 and 56 hours a week lost to organisational overhead, which translates into lost billable hours or delays that hit client satisfaction.
Related articles
How an engineering firm runs 12 projects in parallel without missing a deadline
Before Wrike, the owner spent 2 hours a week on the phone just to find out where each project stood. Here's how we structured the system and what changed in 4 months.
When standard software isn't enough: the 3 signs it's time to consider custom software
An Excel file holding five different systems together, too many SaaS subscriptions that don't talk to each other, processes that bend to the tool's limits instead of the reverse: three signs to recognise.
Facing a similar problem in your company?
Tell us about your situation in a free exploratory call. Short, no commitment.
Book a consultation