Built around real delivery and billing rules
Contract types, exclusions, recurring services, work types, roles, queues and accounting mappings need to reflect what you sell and how you deliver it.
I help MSPs repair and improve the contracts, recurring services, work types, time capture, projects, billing and reporting that sit behind reliable service delivery and profitability.
An established Autotask portal can contain years of inherited configuration, inconsistent data and workarounds. The useful starting point is to separate what Autotask can do from how it has been configured and how people use it.
That makes it possible to fix the root cause without rebuilding everything or asking technicians to compensate for poor system design.
Contract types, exclusions, recurring services, work types, roles, queues and accounting mappings need to reflect what you sell and how you deliver it.
Approvals, time entry, project handover, procurement and billing checks need clear owners and usable data. Configuration alone will not correct a process nobody follows.
Design managed-service and T&M contracts, recurring services, exclusions, quantities and billing rules so work does not fall into avoidable exceptions.
Set work types, minimums, increments, contract coverage and technician expectations so time can support billing, utilisation and profitability.
Improve queues, statuses, project setup, handover and completion rules so delivery teams receive the context they need and work closes cleanly.
Align products, services, billing codes and accounting mappings, then build reporting around revenue, cost, labour and contract performance.
Review configuration, data and working practices. Identify immediate risk, practical corrections and the dependencies that need wider decisions.
Configure contracts, services, work types, billing, projects, mappings and automation. Use guarded bulk changes where manual correction would be slow or inconsistent.
Work through priorities over time, test the effect of each change and help managers build the routines that keep Autotask dependable.
Use the Blueprint when Autotask symptoms cross quoting, CRM, accounting or ownership and the implementation cannot yet be priced responsibly.
Use a defined project when the target, dependencies and acceptance criteria are clear enough to design, configure and test as one release.
Use retained support when changes need to be sequenced around live operations and priorities will develop as better data becomes available.
“We are extremely fortunate to have enlisted the expertise of Ben Spector as our AutoTask Consultant during our company’s transition to AutoTask and Zomentum. Ben’s extensive experience in the field proved to be invaluable, as he guided us seamlessly through the implementation process.”Bill Hunt, CEO, HTML Global
I have used and consulted on Autotask for many years across service desk, projects, contracts, exclusions, work types, recurring services, procurement, accounting and profitability.
Usually not. I first identify which configuration, data and process decisions are causing the problem. A controlled repair is often safer than a wholesale rebuild.
Yes. A defined contract, recurring-service or billing project can be scoped separately when the dependencies are clear.
Yes. I work on the product, service, billing-code and accounting mappings around both QuickBooks and Xero, while keeping the accounting system's role clear.
Where the API supports it, guarded bulk changes can be safer and more consistent than manual editing. Every change needs a dry run, exact scope and rollback evidence.
Share the symptom, the area of Autotask involved and what the business needs to trust afterwards. I’ll help you work out the most sensible starting point.