ToolTorq: The CRM Layer Proanalytica Is Building for ServiceM8

Many trade and field-service businesses use ServiceM8 as the centre of their job operations. Jobs, schedules, field staff and job records live there, which works well in the field.

As the business grows, the office workflow often spreads somewhere else. Client details sit in one spreadsheet, follow-ups in an inbox, documents in shared folders, staff leave in a calendar, and management reports take hours to assemble. People retype the same information because the operational system does not provide the wider CRM and office view they need.

Proanalytica is building ToolTorq to address that gap. ToolTorq is a CRM and staff portal for businesses that already use ServiceM8. It sits on top of ServiceM8 rather than replacing it, giving office, sales and operations teams a more useful way to work with the information around their jobs.

What is ToolTorq?

ToolTorq combines two pieces of software.

The first is a CRM and staff portal. It is designed to give office staff one place to manage clients, contacts, agencies, ServiceM8 jobs, tasks, reminders, staff assignments, leave, timelines, reports, documents, job attachments, communication history, templates, search, scheduling and staff administration.

The second is a custom wrapper around ServiceM8. The wrapper is the technical layer that connects ToolTorq to a business's ServiceM8 account through the ServiceM8 API. It reads the relevant information, presents it in the CRM portal, and writes selected actions back to ServiceM8.

In plain English, a custom wrapper is a purpose-built software layer around an existing system. It gives a business a better way to use that system without forcing the business to abandon it.

The basic flow is:

ServiceM8 account -> secure API integration -> ToolTorq CRM portal

ServiceM8 remains the operational system used by technicians and managers for jobs, schedules, field staff and job records. ToolTorq adds the customer, staff and office workflow that sits around those operations.

Why ServiceM8 businesses need an extra layer

ServiceM8 is strong at job management. The problem is usually not that it is a bad system. The problem is that a growing business has needs that extend beyond a job record.

An office manager may need to see a client's open jobs, previous conversations, outstanding tasks, documents and assigned staff in one place. A sales team may need to track agencies, enquiries and follow-ups. An owner may want a combined view of projects, workloads, leave, communications and reports without asking several people to search through different systems.

When those needs are handled with disconnected tools, duplicate entry creates inconsistent records, messages get buried in email, and reporting becomes a manual exercise. Staff may not know whether someone else has already followed up.

ToolTorq is intended to reduce that duplication and give the office a complete view without changing the system technicians already use in the field.

How the ServiceM8 wrapper works

The ServiceM8 API is the connection point. ToolTorq can retrieve relevant ServiceM8 data through a secure integration layer, organise it for the CRM, and keep the local view synchronised or periodically refreshed.

ToolTorq is being designed to keep a tenant-specific local cache of the data needed by the portal. That cache allows the CRM to load quickly and combine information from clients, contacts, jobs, tasks, staff, documents and communications. It also means the portal can support searches and wider management views without making every screen depend on a fresh request to ServiceM8.

The cache does not change the role of ServiceM8. ServiceM8 remains the operational source of truth for the job information it owns. ToolTorq-specific information can stay in ToolTorq, while selected actions made in the portal can be written back to the ServiceM8 account. The system should describe that boundary clearly rather than imply that every field is mirrored in both directions.

ServiceM8 credentials are kept server-side and encrypted rather than exposed in the browser. The platform is being designed as multi-tenant, so each business can connect its own ServiceM8 account while keeping its users, permissions, configuration and data separated from other businesses.

What the CRM portal adds

ToolTorq is being built around the work office and operations teams already do every day.

Client and contact management: Keep clients, contacts and agencies connected to the jobs and communications that matter.
Tasks and reminders: Give staff a clear place to see follow-ups, outstanding work and internal responsibilities.
Staff coordination: Support assignments, leave, access controls and administration without creating another disconnected register.
Documents and attachments: Bring relevant documents and job attachments into the wider customer and project view.
Communication history: Keep email and SMS templates alongside a record of job-related communication.
Projects and reporting: Combine timelines, reports and dashboards around the customer and operational data.
Search and scheduling: Help staff find the right client or job quickly and create or schedule work through the appropriate workflow.

Each area is meant to remove a repeated handoff between the field, the office, sales and management.

Where AI agents fit

The recent interest in Grok Bot, Muse, Hermes and OpenClaw is part of the same shift from software that stores information to software that can help people act on it. An agent might summarise a customer history, find jobs that need attention, prepare a follow-up or answer an internal question about current work.

ToolTorq gives that kind of agent a more useful office context, but it does not make an agent automatically safe. The agent should not receive a raw ServiceM8 API key or unrestricted access. It should use narrow, approved actions such as finding a client, summarising job history, listing open tasks or preparing a draft message.

Reading a summary and sending a customer message are different risk levels. A sensible workflow can automate the first and require staff approval for the second. Creating, editing or cancelling a job needs its own permission and review rules. The CRM layer, API wrapper, audit trail and human handoff matter just as much as the model chosen for the conversation.

This is also why the model can change without the whole business system needing to be rebuilt. Grok Bot, Hermes, OpenClaw or another agent may suit different environments. ToolTorq is the reusable business and ServiceM8 layer around that choice.

Who is ToolTorq for?

ToolTorq is being designed for growing trade and field-service organisations such as:

electrical contractors;
plumbing businesses;
HVAC companies;
property maintenance teams;
commercial cleaning businesses; and
other service businesses that use ServiceM8 and have growing office operations.

It is not intended to imply that every business needs a custom CRM. A small business with a straightforward workflow may be well served by ServiceM8 alone. The strongest fit is a business with office staff, multiple people managing jobs, repeated data entry, complex reporting requirements, or a need for better visibility across customers and operations.

Why build a reusable CRM instead of another generic system?

Generic CRMs are useful, but they often make a field-service business adapt its process to a different type of work. A ServiceM8 business already has an operational language: jobs, bookings, technicians, checklists, attachments, recurring work and customer history.

Proanalytica is building a reusable ServiceM8 CRM foundation around that reality. The common foundation can support clients, jobs, tasks, communication history, reports and staff workflows. It can then be adapted for a particular business's requirements, such as report generation, quoting, data capture, document generation, custom dashboards or industry-specific workflows.

The business gets a layer shaped around its work, while technicians continue using ServiceM8 in the field.

Current status

ToolTorq is currently being built and refined. It should not be presented as a finished, universally available SaaS platform, and not every listed feature should be assumed to be commercially available to every customer.

The product is Proanalytica's reusable CRM and custom ServiceM8 wrapper foundation. ServiceM8 stays central to field operations, while ToolTorq provides the office workflow around it.

If your business uses ServiceM8 and the office has started to outgrow spreadsheets, inboxes and disconnected tools, talk to Proanalytica about a custom ServiceM8 integration. We can discuss whether a CRM layer, staff portal or narrower workflow improvement is the right next step.

ToolTorq: The CRM Layer Proanalytica Is Building