Every job, every asset,
every invoice
Field service, equipment management and a real CRM underneath. One system from the first call to the final invoice. Add solutions as you grow, with no developers required.
Field service, equipment management and a real CRM underneath. One system from the first call to the final invoice. Add solutions as you grow, with no developers required.
Run by crews across mining, construction, mechanical services and hire
Every tenant runs Base CRM. The rest switch on per licence, so a field service business and a labour hire business run the same platform, configured differently.
One order from the first call to the invoice: quoted, dispatched, done on site in the offline app, checked at QA and billed from what was actually logged.
The client’s requirement, the people placed against it, the FIFO roster they work, the timesheets it produces and the invoice at month end.
One record per asset: what it is, where it is, what it is due for, what has been done to it, and whether it is out on hire.
Roles, candidates, pipelines and compliance, kept on the same organisations, contacts and sites as the work they are being hired for.
The foundation every solution sits on. Organisations, contacts, leads, pipeline, quotes, orders, invoices and payments — one set of records, so the layers above never need their own copy.
Organisations and contacts, leads and pipeline, quotes, orders, invoices, payments, purchase orders and inventory. A full customer and revenue system in its own right, not a contacts tab bolted onto a job scheduler, and it is the same set of records every solution is built on.
Every record in the chain below is standard BaseLeap CRM. Nothing here is an add-on.
Captured, qualified and assigned against an organisation and contact.
Staged pipeline with forecasting, so you know what is actually coming.
Priced from rate cards and inventory, printed and sent from the record.
Becomes a service order, a hire or an assignment. The work itself.
Built from the time, parts and charges that were logged against the job.
Reconciled and closed, with the client PO checked before anything ships.
BaseLeap is built for workforce-heavy and asset-heavy businesses, and for the billable-time firms that serve them. The same platform is configured to fit each of them — a plant fleet and an AV hire warehouse run the same hire register.
Crews, plant and compliance across remote sites. Rosters and swings on one side, the asset register and its service history on the other.
Projects, subcontractors and site work on one set of records, with purchase orders pushed onto the job.
Work orders, servicing schedules and field crews. Every visit, report and part held against the machine.
Quote to completion, with the job on the phone in the van and the invoice built from the time and parts logged.
Earthmoving, access, generators, tools and site sheds. What is out, with whom, when it is due back and what it is due for.
Sound, lighting, staging, screens and marquees. A catalogue, a rate card, bundles, availability and a return — the same hire register as a plant fleet, for a different kind of kit.
Place people, roster them, approve their hours and bill the month. The placement and the assignment are one record.
Engineering, consulting and billable teams. Engagements, consultants on assignment, the master schedule and the bench, with timesheets approved and invoiced from rate cards.
Two to three sentences about the outcome: what was slow or lost before, and what changed. Specific beats glowing.
A second client, ideally from a different solution: labour hire if the first was field service.
A third. If one of the three mentions the field app or the invoice, keep that one.
For a basic CRM — organisations, contacts, a pipeline, a few custom fields — yes, and quickly. We would rather say that plainly than pretend otherwise.
What is in here is a different animal, and it is not vibe-coded. Multi-tenant row-level security, field work that survives a dead zone and replays in order, FIFO rosters, timesheets that become invoices without retyping, maintenance schedules, approval chains and compliance expiry are the parts that demo well in an afternoon and take years of real operational use to get right. Our team has built enterprise CRM before and has worked in these industries, and most of what is here exists because somebody hit the problem on a job.
The build is also the cheap part. What you own afterwards is the bill that never stops: security patching, backups you have actually tested restoring, browser and mobile OS upgrades, and somebody who can answer the phone at 6am when the crew cannot clock on — and who still remembers why any of it works the way it does. A licence is a known figure per user per month, with hosting, support, upgrades and every new feature inside it. A system you build is an open-ended claim on developer time, and it competes with the work that actually earns you money.
The honest test: if the CRM is your product, build it. If it is what runs your business while you do something else for a living, licence it. See pricing.
Create an account, or sign in and pick up where you left off.
Prefer to talk it through? Call us and a real person answers — no phone tree, no ticket before a conversation.
