Live in a week: an honest rollout plan

The question we get asked most often isn’t about features. It’s “how long will this take, and how much of my time is it going to eat?”

It’s a fair question, and the honest answer is that most software rollouts in this industry go badly for the same two reasons: the business tries to switch everything on at once, and nobody was ever told what week one would actually look like. So here it is — day by day, for a business running around twenty techs.

Before day one: two decisions, one list

You need to decide two things before anyone touches the system. First: which workflow hurts most right now — scheduling, quoting or invoicing? That’s the one you go live with. Second: who owns this internally? One person, usually the operations manager. Not a committee.

Then there’s the list: your customers, your sites, and your active jobs. Most businesses can export that from their accounting system in an afternoon. We do the rest of the data work from there.

Monday: configuration, not training

Day one is us and your operations lead in a room — or on a call — setting the system up around how you already work. Job types, your stages, your invoicing rules, who sees what. This is the part that matters, and it’s the part generic platforms skip: we configure to your process rather than asking you to adopt ours.

Time from your side: about half a day.

It’s worth saying what we do rather than what you do. We handle the data import, the configuration, the accounting integration and the sanity-checking afterwards. What we can’t do is make the decisions — how you want jobs staged, what your invoicing rules are, who’s allowed to change a price. Those need someone from your business in the room, which is why one clear owner matters more than a big committee.

If your process is genuinely unusual — and in HVAC&R and electrical it often is, between site access rules, PO requirements and after-hours rates — this is the day we build around it rather than asking you to change it. That’s the difference between software that sticks and software that gets quietly abandoned in month four.

Tuesday: the office team

Schedulers and admin staff learn the board and the job screen. Two hours, hands on, with real jobs rather than demo data. By the end of the session they’re building jobs faster than they were on the whiteboard — that’s the bar, and if we don’t hit it we keep going until we do.

We start with the jobs already in the diary rather than made-up examples, because the questions people actually have are specific: the customer who wants two POs on one job, the site that needs the same tech every time, the recurring job that has to be split across two months. Answering those in the session is what turns training into confidence.

Expect one person to pick it up in an hour and one person to need a second sitting. That’s normal, and worth planning for rather than pretending everyone learns at the same speed.

Wednesday: the techs

This is the day everyone worries about, and it’s usually the easiest. The mobile app takes about forty minutes to explain, mostly because there isn’t much to explain: here’s your day, here’s the job, here’s the site history, here’s how you sign it off.

Techs aren’t afraid of technology. They’re afraid of software that’s slower than the paper it replaced. If the app doesn’t save them time on the first job, they’ll go back to the docket book and you’ll never get them back — so we design for that first job.

The pitch to the crew is short: you stop writing the same thing twice, you stop driving dockets back to the office, and you stop getting rung at 7pm about a job you did on Tuesday. Framed that way, adoption is rarely the fight people expect.

One thing worth deciding in advance: whether techs capture time as they go or at the end of the day. Both work. Not choosing is what causes the mess.

Thursday: run it in parallel

One day of belt and braces. Jobs go into TSMPlus and the old process keeps running alongside. You’ll find the three or four things nobody thought to mention — the customer who needs two POs, the site that’s technically two sites, the after-hours rate. We fix those on the day.

Parallel running for a single day is deliberate. Run it for a fortnight and you’ll have two half-maintained systems and a team that trusts neither. One day is enough to surface the surprises without letting the old process reassert itself.

Friday: live

Friday you invoice out of TSMPlus. That’s the moment it becomes real, and it’s deliberately the end of week one rather than month three — because the invoicing win is the one everybody in the business feels immediately.

Then you stop. Don’t add modules for a few weeks. Let the new normal settle, then pick the next workflow — purchasing, preventative maintenance, asset registers, project costing.

A realistic month two looks like this: purchasing tied back to jobs so your costing is real, then preventative maintenance contracts generating their own work, then asset registers building themselves off the back of both. Each of those is a couple of hours of setup, not another week.

What actually goes wrong

Three things, in our experience. Dirty customer data that nobody wants to own. A business that tries to switch on eleven workflows in week one. And an owner who delegates it entirely and then changes the rules in week three.

None of those are software problems, which is why we’d rather talk about them before you sign than after.

What it costs you in hours

Add it up: half a day for your operations lead on Monday, two hours for the office team on Tuesday, forty minutes per tech on Wednesday, and a day of mild inconvenience on Thursday. Call it a day and a half of real business time across a week.

Compare that with the number most people carry around in their head — a month of disruption and a system nobody uses. That fear is well earned, but it comes from rollouts that tried to change everything at once, usually with a vendor on another continent.

The other number worth putting next to it is what the current process costs every week. If two people spend an afternoon each chasing dockets and re-keying jobs, that’s a day of wages a week, every week, forever. A day and a half once is not a difficult trade.

And if it does go long — because your data was messier than anyone thought, or a key person was away — you’ll hear it from us early rather than discovering it in week five. Telling you the awkward thing quickly is most of what good implementation actually is.

Ask us for a rollout plan for your business — with dates on it — before you commit to anything. Book a demo, or call 0457 228 884.