Platform

One set of records. Every solution on top.

Base CRM is included with every tenant. The solutions switch on per licence and share its organisations, contacts, orders and invoices — so nothing is copied, and what secures and shapes one record secures and shapes them all.

Get Started See the five solutions
BaseLeap — Dashboard The BaseLeap CRM dashboard, showing pipeline value, won value, quotes accepted and win rate
Base CRM

A complete CRM, included with every tenant.

Organisations and contacts, leads and pipeline, quotes, orders, invoices, payments, purchase orders and inventory. A full customer and revenue system in its own right, and the same set of records every solution is built on.

Customers & pipeline

Everyone you deal with, and every deal you are chasing.

  • Organisations & contacts
  • Leads and lead conversion
  • Opportunities, pipelines & forecast
  • Quotes with rate cards and discounts
  • Marketing lists and sent email

Quote to cash

What was agreed, what it cost, and what has been paid.

  • Orders and agreements
  • Invoices and payments
  • Purchase orders, pushed onto the job
  • Inventory and products
  • Client PO required before close

Reporting & day to day

What is happening now, what needs attention, and what the numbers say.

  • Dashboards and custom reports
  • Needs Attention and approvals
  • Activity, tasks, events and calendar
  • Cases and incident records
  • Resources, rosters and dispatch
Under the CRM

Secured in the database. Shaped by configuration.

Two things decide whether a business system survives its second year: whether the wrong person can ever see the wrong row, and whether changing a field needs a developer. BaseLeap answers the first in the database and the second in metadata.

The whole platform, on one page. Who uses it, through what, and the layers underneath: solutions on Base CRM, Base CRM on automation, automation on the platform.

And in more detail: what every request passes through, what shapes the screen, and where it lands.

Security — what every request passes through

Enforced by the database on every row, not by the page that asked for it.

Tenant isolationRow-level security on every table. Your rows are invisible to every other tenant, whatever the app does.
Pack entitlementSolution tables are gated in the same policies. No licence, zero rows.
Role and permissionOwner, Admin, Manager, Agent, Technician, with per-module permissions.
Restricted technician viewField staff see their own jobs and no pricing, by policy.
One policy, in the database

Metadata — what shapes the screen

Standard and custom objects in one registry. Data, not code.

Objects and fieldsCustom fields on any object; custom objects of your own.
Record typesA layout, a status flow and a QA stage per type.
Page layoutsTabs, regions and sections, edited on a canvas.
Validation rulesBlocking checks that outline the field they failed on.
Workflows and approvalsTriggers, conditions, actions; steps with a quorum.
Changed in Settings, not in a deploy

Surfaces — where it lands

Every surface reads the same registry, so a field added once appears everywhere.

Record pages and forms
Lists, saved views and bulk actions
Reports, dashboards and subscriptions
The field app
The client portal
AI agents, read-only, over MCP
Same records, every screen

Security model

Protection that does not depend on the application remembering to filter.

  • Every tenant-scoped table carries a tenant id, enforced by row-level security
  • Solution tables additionally require the entitlement, in the same policy
  • Approvals re-checked server-side: ownership and self-approval
  • Restricted access for field technicians, opt-in per user
  • Private file storage with signed, expiring links
  • Field-level audit trail on core records, with a History tab

Users, roles and licences

Who can see what, and what you are paying for.

  • Five roles: Owner, Admin, Manager, Agent, Technician
  • Per-module permissions beneath the role
  • Approval groups, separate from roles: whose signature counts
  • Licences per user per solution, with usage against the plan
  • Invitations and password reset by email
  • Client portal identities for customers who approve timesheets

Objects, fields and layouts

The system matches the business, not the other way round.

  • Custom fields on any standard object, no deploy
  • Custom objects with their own pages, lists and relationships
  • Page layouts on a canvas: tabs, regions, sections, per record type
  • Record types with their own status flow and QA stage
  • Reference lists and dependent picklists
  • Validation rules that mark the field, not just a toast

Automation

Rules that run without anyone remembering to.

  • Workflows on record events, schedules, webhooks or by hand
  • Actions: email from a template, update or create a record, create a task, notify someone
  • Every run logged, step by step
  • Approval processes with steps, a quorum and value ladders
  • Checklist templates attached to any record, with owners and due dates
  • Certificate-expiry reminders that reach a real person

Reports and dashboards

Over standard and custom objects alike, built by the people who need them.

  • Report builder with matrix and joined reports
  • Formula and bucket fields
  • Dashboards on a canvas
  • Scheduled subscriptions by email, full-dataset PDF
  • Folder permissions
  • Needs Attention: one inbox for what is waiting on you

Administration

Everything about the business itself, in one Settings area.

  • Organisation, regional settings: timezone and currency
  • Billing, licences and cost centres
  • Customisation: fields, layouts, record types, reference data
  • Discounts, pricing and invoicing settings
  • Integrations: web-to-lead, web-to-apply, maps, email delivery
  • File management, data quality, duplicate merge, in-app guides
Integrations

What it talks to.

Everything below is live today. The honest gaps are at the bottom.

Email

Sent from the record, through a transactional email service, with the plumbing a real inbox needs.

  • Email from any record, with templates
  • Bulk email to lists and segments
  • Unsubscribe links and a suppression list
  • Bounce and delivery events written back
  • Invitations and password resets
  • Approvals answered from the email itself

Web forms and inbound

Your website posts straight into the CRM. No middleware.

  • Web-to-lead: an embeddable form or a POST endpoint
  • Web-to-apply: careers-page applications into a requisition or the talent pool
  • Honeypot, rate limiting and a domain allowlist on both
  • Inbound webhooks that start a workflow
  • Tokens you rotate yourself
  • A preview-and-test tab before you embed it

Maps and addresses

Google Maps behind every address on every record.

  • Address autocomplete on create and edit
  • Coordinates captured and kept on the site
  • A map on any record with an address
  • Every site plotted together
  • Geocoding that refuses a guess: only exact, rooftop matches are saved
  • Route planning is on the roadmap, not the page

Data in, data out

Yours to load and yours to take.

  • CSV import: upload, map columns, review, result
  • Add new, update existing, or both, matched on an external id
  • CSV export from any list
  • Full-dataset export as a job, not a spreadsheet you babysit
  • Retention that is a policy, not a hope
  • Custom objects import and export like standard ones

AI agents

An MCP server so an assistant can read your CRM, and only read it.

  • Global search over every object
  • Read-only by design: an agent cannot change a record
  • The same row-level security as a signed-in user
  • Works with any MCP-capable assistant
  • Per-tenant, per-entitlement, like everything else
  • Write tools are deliberately not there yet

Client portal

Your customers act on their own records without an account on yours.

  • Timesheet approval from an email link
  • Portal identities separate from your users
  • Service reports readable by the client
  • Every action written back with who and when
  • No access to anything but their own records
  • An approver console is the next step

Not yet: a live accounting sync (Xero, MYOB) — today you export; SMS; and a public REST API. Each is on the roadmap and none is on this page as if it were done.

Ready when you are.

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

Get Started → Sign in