The business half, already joined up.
These run in our own production deployment today. What differs between projects is which of them you switch on, and how far your records differ from the defaults.
Contacts and pipeline
Contacts, organisations, opportunities and the stages they move through, named the way your business names them. A stage can be a booking, where the client picks a time from the hours you set.
Payments and invoicing
Card payments, invoices and recurring plans, with your accounting kept in step rather than re-keyed.
Registrations and access
Invitations, member areas and case records, with access decided per record rather than by one blunt role on a user account.
Marketing
Each campaign gets tracked links and a budget, and reports the enquiries and sales it brought in against what it cost.
Reporting
Reporting over your real records, in the same system, rather than a monthly reconstruction.
An assistant that knows it
Because content and customers share a database, an assistant can answer from your own business, through an audited boundary.
We change the records, not just the labels.
Renaming a field is configuration. Adding the fields your industry needs, and the relationships between them, is a data-model change. It's the thing a generic CRM can't do without professional services and a fork.
Where the line sits
- The records themselves, with your fields and relationships
- Your pipeline stages, named the way your team says them
- Which capabilities are switched on
- Apps of your own, layered on top
- Identity, permissions and the access model
- Payments, billing and the accounting link
- The upgrade path, maintained centrally for every client
- The deployment recipe, the same as every other deployment
Your customisations live in your own application, in places the core knows about. That is what lets you take improvements to the platform without losing the changes that make it yours.
A free call, then Project Discovery at $900 plus GST.
Discovery ends with your project generated from the brief and shown to you, and the $900 is credited against the build if you go ahead. The build is quoted from the brief, because it depends on your records, what you're migrating, and how much of the above you need.
| Starting point | Typical business | What it usually involves |
|---|---|---|
| Starter | Service business | One pipeline, standard records, payments and invoicing |
| Professional | Sales team | Several pipelines, reporting, campaign tracking |
| Enterprise | Custom business system | Swapped models, your own process, links to systems you already run |
The same platform in every case. Discovery decides which you're in, and the build is quoted from it.
How it starts
Your project brief
Tell us how you sell, who deals with a customer, and where the current tools get in the way. We send back a written brief, free.
A discovery call
Free, thirty minutes, to talk the brief through with the person who'd do the work.
Project Discovery
Which capabilities are on, and where your records differ from the defaults. You read and correct the brief, then see your project generated from it. $900 plus GST, credited against the build.
Your own application
Built from that brief onto infrastructure you control, with the keys yours from the start.
Tell us how you sell.
The most useful first conversation starts with your records: what a customer is to you, and what has to be true before one counts as won.