Pick the solution you run. The platform, with CRM included, comes with every plan.See plans and pricing →
About BaseLeap

Industry specific CRM.

Our team comes from enterprise CRM and software. We kept seeing a gap: specialist industries that need software that is professional, strong and secure, with people behind it who give real service, but not all the baggage of an enterprise CRM. That is why we came together to build BaseLeap.

A crew on site, talking through the day's work
Why it exists

For businesses that need serious tools, not an enterprise project.

  1. Too many tools for one business. We kept seeing the same picture: a CRM in one place, scheduling in another, a field service app, a labour hire system and a hire spreadsheet, with people retyping between them. BaseLeap brings them together on one set of records.
  2. Each one a proper industry platform. Field service, labour hire and equipment hire are each built to industry best practice and would stand on their own. Together, they share the customer, the job and the invoice.
  3. Enterprise capability, without the enterprise. Until now, software this complete meant an enterprise product, an enterprise price and an enterprise implementation. Better tooling and AI have changed what a focused team can build, and we use them to put best practice industry software within reach of businesses that do not need the full enterprise stack.

Built by people, and properly tested. BaseLeap is designed and built by a real team. We use modern tooling, AI included, to work faster, but this is not a few weeks of work: it is eighteen months of building, testing and beta testing with real businesses.

The BaseLeap dispatch board, with technicians, their rostered days and the jobs waiting to be assigned
How it is built

Four decisions, the rest follows.

One set of records

Every solution runs on the same organisations, contacts, sites, orders and invoices. A technician’s time becomes an invoice without anyone retyping it.

Configured, not coded

Objects, fields, layouts, record types, validation and workflows are metadata. The system changes in Settings, not in a release.

Secured in the database

Row-level security on every table, per tenant and per licence. The wrong person cannot see the wrong row, whatever the application does.

Built for the field

The mobile app queues work in a dead zone and replays it in order when signal returns. Site is where the product is judged.

What we hold to

Five things you can hold us to.

01

Talk to a real person

Whenever you need to escalate something or talk it through in detail, you can talk to a real person on our team.

02

Say it plainly

If a basic CRM is all you need, we will say so. The case for BaseLeap is the part after that.

03

The field is the product

A feature that does not survive a dead zone on a phone is not finished.

04

Nothing invented

A figure the system cannot defend is not shown. A status is derived from the facts, never trusted from a stored field.

05

Yours to configure

Fields, layouts, picklists, rules and workflows are yours to change, without asking us and without a developer.

Ready when you are.

Create an account, or sign in and pick up where you left off.