← The journalSERVICES / FIELD GUIDE

ERP for service businesses, not just factories

Why a consultancy, agency, engineering firm or field service company needs an ERP built around people's time, projects and contracts, and what to leave out.

Pedestrians in Shibuya with directional camera-motion blur.SERVICES / SUNDIAL
Photography: Ayumi Kubo / Unsplash ↗ · Sundial motion treatment
THE PRACTICAL TAKEAWAY

A service business sells time and expertise. Its system has to connect the deal, the project, the hours, the invoice and the support that follows, and it can skip most of the stock and production machinery that factory ERPs lead with.

ERP grew up in factories

ERP was born in manufacturing. Its first job was working out how much material to buy for a production schedule, and most ERP products still show that ancestry: the menus open on stock, BOMs and warehouses. A consultancy or a field service company opens one of these systems and concludes, reasonably, that ERP is not for them.

So service businesses assemble their own stack instead. A CRM for deals, a project tool for tasks, a timesheet app, an accounting package, a helpdesk, and a spreadsheet that tries to tie them together. Each tool is fine. The gaps between them are where the money goes: hours logged but never billed, projects that lose money without anyone noticing until year end, renewals missed because the contract lived in someone's email.

What a service business actually runs on

Strip it back and a service business has five things to keep straight. Deals: who might buy, what, and at what price. Projects and contracts: what was sold, its scope and its terms. People's time: who worked on what, and whether it is billable. Money: invoices, collections, expenses and the cost of the team. Support: what happens after delivery, often under a service agreement.

These five are tightly linked. The quotation sets the price; the project inherits it; timesheets consume it; invoices bill it; support continues it. When they live in separate systems, every link is a manual copy, and each copy is a chance to lose something.

One flow, from first call to final payment

In Sundial the chain is one set of linked records. A lead becomes an opportunity in Sales & CRM. The opportunity gets a quotation. The accepted quotation becomes a sales order, and the sales order starts a project in Projects & Services with tasks, a team and an expected value.

People log time against the project from their phone or laptop. Each timesheet line carries a billing rate and a costing rate, so the same entry feeds the invoice and the project's margin. Invoices are raised from timesheets for hourly work, from the sales order for milestones, or on a repeating schedule for retainers. Payments land against those invoices in Finance & Accounting, and bank reconciliation closes the loop.

After delivery, customer issues come in through Support, with service level agreements that set response and resolution targets. Because the customer is the same record everywhere, the account manager preparing a renewal sees the open issues and the unpaid invoices on the same screen as the opportunity.

Utilization and capacity, without surveillance

The question every service business owner asks is whether the team is busy on the right work. Timesheets answer it, as long as they are treated as a planning tool rather than a punishment. Billable hours divided by available hours, by person and by team, tells you whether you can take on the next project or need to hire.

Keep the number honest by logging non-billable work too: pre-sales, training, internal projects. A team that looks under-utilized is sometimes simply spending its time on proposals that should be priced into the next deal.

Look forward as well as back. Open projects with remaining estimated hours, set against the team's capacity for the next few weeks, show the crunch before it arrives.

What you can leave out

A service business does not need production planning, BOMs or multi-warehouse stock, and it should not have to look at them. Sundial is one system with modules you switch on as you need them; a consultancy might run Sales & CRM, Projects & Services, Finance & Accounting and Support and never see a work order. If you sell some hardware alongside services, Inventory is there when that day comes, on the same customer and the same books.

Purchasing still matters, in a smaller way: subcontractors, software, travel. Buying handles purchase orders and supplier invoices, and anything bought for a project is booked to it, so the project margin includes it.

Sundial's redesigned workspace matters here more than in a factory. Service teams are used to modern, fast tools, and they will not log time in a system that feels like an accounting package from twenty years ago. The workspace keeps every screen in one calm design on desktop and phone, and we are building Sundial so that people can ask plain-language questions such as which projects are over budget this month, with an agent preparing the answer for a person to check.