Case study · Facility services
From paper task sheets to verified, billable work across seven distribution centers
A cleaning and maintenance contractor won a national retailer's distribution centers and multiplied its headcount in about a year. Tasks were on paper, invoices were rebuilt in Excel, and one person approved everything. We mapped the process, evaluated four tools before deciding to build, and delivered a platform that connects work done, evidence, approval and invoice.
In numbers
7
distribution centers in four states run from one platform
4
tools evaluated against the real process before we recommended building
8
questions every job answers before it can be billed
Who this is for
Owners and directors of multi-site service businesses, in cleaning, maintenance, facilities or field operations, that have grown faster than their paperwork and now bill from reconstructed spreadsheets. You will get the eight questions we use to decide whether a job can be billed with confidence, and the reasoning we applied before recommending that anything be built.
Key takeaways
- Growth broke the process, not the people. Seven sites in four states, each with its own way of recording what got done, and a workforce hired for its hands rather than its keyboard skills.
- Buy was evaluated before build. Four platforms scored against the actual process. Building was a conclusion, not a starting position.
- Approval is the gate. A work order moves to “completed” only with an approval, and only then does it carry a price and evidence to an invoice.
- A platform is only as good as the laptop in front of it. The sites also needed devices, connectivity and a corporate identity.
- Proof became the commercial asset. The company can now show the work rather than promise it.
What happens when a service business grows faster than its paperwork?
The contract that made the company and nearly broke it
The contract that made the company also nearly broke it. Within about a year of taking on cleaning and maintenance for a national retailer's distribution centers, the operation ran across seven sites in four states, each with its own supervisor, its own way of recording what got done, and a workforce hired for its hands, not its keyboard skills.
One person was the bottleneck for every invoice
Recurring services were invoiced from the accounting package. Special projects were invoiced from spreadsheets with little detail. Field tasks were written on paper, collected by each center's supervisor and phoned or emailed in. The chief operating officer supervised and billed everything personally, which meant every invoice waited for one person, and every question from the customer about what exactly was done, by whom, for how long, went back to that same person.
The eight answers a job needs before it can be billed
The customer was paying for services with no uniform evidence that they had happened. The business needed eight answers for every job before it could be billed with confidence: what service, at which center, when it started and ended, who did it, how many hours, what evidence, who approved it, and at what price.
- What service was performed
- At which center
- When it started and ended
- Who did it
- How many hours
- What evidence exists
- Who approved it
- At what price
The constraint that shaped everything after
We spent the first weeks on the floor and in the back office, following a task from the moment a supervisor noticed it to the moment it appeared on an invoice. That gave us the eight questions, the single point of failure, and a constraint that shaped everything after: whatever came next had to be usable by someone who has never used business software.
Should you buy a platform or build one?
Four tools, scored against the real process
Before building anything we evaluated what the market already offered for time and attendance, field teams, accounting and ERP: four platforms, scored against the actual process. Two solved a piece of it well. None connected work, evidence, approval and invoice for a multi-site operation of this shape without adding a second set of manual steps.
Keep what works, build only the missing layer
The recommendation was to keep the accounting package and payroll where they were, and to build the control layer that was missing: a work order as the unit that carries the eight answers, an approval as the only way to complete it, and four roles (administrator, center manager, staff, customer), each seeing only what it needs.
What a platform cannot do on its own
The decision also covered what a platform can't do on its own. The sites needed devices, connectivity and a corporate identity, because a platform is only as good as the laptop and the login in front of it.
What did we build?
- A web application with the four roles, and work orders that carry service, center, times, people, evidence and price, and move to “completed” only with an approval.
- Reports and KPIs by center, person, service and period, replacing the reconstruction that used to happen at invoice time.
- A service desk with weekly client reports and an internal management view of load, hours and backlog, so support stopped being a phone number.
- Devices, connectivity and corporate identity for the seven sites.
The platform runs in production with separate staging.
What has held since?
Managers and owners use the platform to record and approve work at the centers. Invoicing no longer starts from paper: an approved work order carries the price and the evidence the customer will ask for.
| Before | After | |
|---|---|---|
| Field tasks | Written on paper, phoned or emailed in | Work orders that carry the eight answers |
| Invoices | From the accounting package and from spreadsheets with little detail | From approved work orders, with price and evidence |
| Approval | One person, for everything | Centre managers for their centres; the COO for exceptions |
| Evidence | None that was uniform | On every work order, before it can be billed |
Supervision is no longer one person's inbox. Center managers see their own operation; the COO sees all of it and approves exceptions rather than everything.
The company now has something it didn't when it grew: proof. Its position with future customers is built on showing the work rather than promising it, and the platform is what makes that claim true. Adoption figures and billing cycle times are being measured; we'll add them here once the client has a full period behind them.
Questions readers ask
Customer Success Team
Itaca Technologies
Your question isn't here?
Ask it as you'd ask it across the table. The team that does the work reads it and answers with a concrete next step.