CRM and revenue operations built around your sales process

Records, stages, intake, proposals and signatures that follow the way you sell, with a named next step and a date on every record.

Core capability A working capability of the platform.Configured to your business The mechanism exists; a specific setup is part of a services engagement.

CRM & Revenue Ops

One record per business

From first inquiry to customer, on a single record.

Core capability
What it does
Every company becomes one record that follows the relationship from an unworked list entry, to an open prospect, to a customer account, or to lost. Contacts, notes, files, owner, next action and reminders live on that record.
How it works
Records move through named stages. Notes, uploaded files and an activity timeline sit on each record, and generated documents such as proposals and signed agreements are filed to it automatically. A Highlights card holds the key facts, and an AI summary can draft them from the notes for a person to edit and save.
Problem it solves
The same company living in a spreadsheet, an inbox, a phone log and a billing tool, with nobody holding the whole story.
How it can be customized
Categories, statuses, lead sources and next-action stages are lists you control, so records speak your vocabulary. Which fields and views matter most can be configured for your business.

CRM & Revenue Ops

Stages and next actions

A named next step and a date on every record.

Core capability
What it does
Each record carries a next action and a date. The stage decides which queue a record appears in, which reminder applies and which automation, if any, runs next.
How it works
Next actions are named stages such as “Prepare proposal” or “Collect signatures”. Changing a stage can create a call-back, draft an e-mail, generate a proposal or send a signature request, depending on how the platform is configured. Owners can be changed record by record or in bulk.
Problem it solves
Reps unsure what to do next, and managers unable to see which opportunities are stuck.
How it can be customized
Stage names, their order and the actions tied to them can be configured to your sales or service process. The platform does not impose a funnel.

CRM & Revenue Ops

Website form-fill intake and routing

A website inquiry becomes a working prospect.

Core capability
What it does
Turns a submission on your website into a prospect. The form posts to Mako, which creates the record the way a person would, adds a note with what the visitor said, queues the lead for follow-up and e-mails the owner.
How it works
Each website form gets its own handling card: which owner, which lead source, which next action and whether the lead enters a call queue. A ledger stops the same submission from creating a lead twice, and a master switch turns intake off without touching the website.
Problem it solves
Leads retyped from an inbox hours later, or never.
How it can be customized
Per-form owner, lead source, next action and call-queue enrolment. Your website posts to the intake endpoint using a key you control.

CRM & Revenue Ops

Proposals and quote follow-up

Quote from the record, then make sure someone follows up.

Configured to your business
What it does
Builds a PDF proposal from the data on the record, drafts the cover e-mail, files the PDF back to the record and moves it to a follow-up stage with a date. Follow-up e-mails are drafted for the rep to review.
How it works
A stage change such as “Prepare proposal” starts generation. When a rep sends the proposal from their own mailbox, the platform recognises it and advances the record. A rep can regenerate and send a new version from the record at any time.
Problem it solves
Slow, inconsistent quoting, and quotes nobody follows up.
How it can be customized
Proposal types, pricing inputs, page content and whether follow-ups wait for a person or send automatically can be configured to match how you quote.

CRM & Revenue Ops

E-signature requests

Agreements out for signature, chased and filed.

Core capability
What it does
Sends agreements for signature through Dropbox Sign, tracks the request, reminds the signer and files the signed PDF back to the record.
How it works
A stage can trigger a signature request. The platform checks status, sends reminders on a schedule and, once signed, stores the document on the record and advances the stage.
Problem it solves
Contracts that stall in inboxes with nobody chasing them.
How it can be customized
Which stage requests a signature, which template is used and the reminder rhythm. Requires your own Dropbox Sign account.

CRM & Revenue Ops

Reminders, calendar and invitations

Follow-ups that show up where people work.

Core capability
What it does
Reminders with a date, or a date and time, appear on a Month, Week and Day calendar opened from the header. A reminder with a time can offer to send a calendar invite, and it only sends when the rep says yes.
How it works
Every record can hold a reminder. The calendar reads them across the records a user owns, and a click opens the record. Records are not served to a dialer queue before their reminder date.
Problem it solves
Follow-ups that live in a personal calendar or in someone's memory.
How it can be customized
Who sees which reminders follows the permissions you set. Reminder timing can be tied to stage changes.

CRM & Revenue Ops

Bulk management

Change owner and next action across large sets.

Core capability
What it does
A four-step wizard reassigns owner and next action across very large sets of records at once.
How it works
Choose the records with filters, choose the change, review the result, then confirm. The confirmation click is the deliberate gate, so nothing changes unattended.
Problem it solves
A territory changes or someone leaves, and hundreds of records need a new owner.
How it can be customized
Who may run bulk changes is a permission. The filters you can choose from follow your own categories and lead sources.

See these capabilities with your workflow in mind

Bring your stages, teams and tools. We will show how they map onto the platform.