The pipeline
From a name nobody has called yet to a deal you have won — and everything that has to happen in between.
The CRM dashboard
Where your pipeline stands right now — leads coming in, deals in play, and what your team did today. Read it before you open anything else: it tells you whether the problem today is new leads, stalled deals, or follow-ups nobody made.
My Day
One list of what you personally owe someone today — calls to make, follow-ups due, tasks landing. A salesperson should be able to work the whole morning from this screen alone. If it is empty, either you are genuinely clear or nothing has been assigned a due date.
Leads
Everyone who has shown interest but is not yet a deal. Source, owner, status and when they were last touched. The filters across the top are the working views: follow-ups due, email engagement, and ownership. Most sales problems show up as a lead nobody has touched in two weeks.
Deals
Leads that became real opportunities, moving through your pipeline stages with a value and a close date. A deal only exists once someone converts a lead — that conversion is deliberate, so the pipeline never fills with speculative noise.
Companies
The organisations you sell to, with every lead, contact and deal attached to them. Selling to three people at one company is one relationship, not three. This is the screen that keeps it that way.
Contacts
The individual people — their role, their company, and the history of what has been said to them. Contacts are created by converting a lead, so nobody ends up in the database without a reason for being there.
Tasks
The concrete follow-ups — call back Tuesday, send the quote, chase the PO. Tabs split what is yours from what is overdue across the team. Overdue is the number a manager should watch.
Calls
Every call logged against a lead or contact, inbound and outbound, with its outcome. The unmatched tab is the useful one: calls that arrived from a number nobody recognises, which is usually a lead nobody created.
Sequences
Multi-step follow-up that runs itself — an email now, a reminder in three days, a call task after a week. It stops the follow-up depending on whether somebody remembered. Enrol a lead and the steps fire on schedule.
Sequence builder
Where a sequence is designed: the steps, the waits between them, and what each step does. Keep them short. A five-step sequence that gets finished beats a twelve-step one that gets abandoned halfway.
WhatsApp inbox
Conversations with leads over WhatsApp, in the CRM rather than on somebody's personal phone. This matters when a salesperson leaves: the conversation history belongs to the business, not to their handset.
Reassign queue
Leads waiting to be moved to a different owner — someone left, someone is overloaded, or the territory changed. Reassignment goes through a queue rather than a direct edit so the ownership history stays intact.
Analytics
What the pipeline is telling you, once there is enough in it to be worth reading.
Lead analytics
Where leads come from, how fast they convert, and where they stall. Source performance is the number that changes what you spend. If one source converts at half the rate of another, that is your marketing budget answering a question.
Forecast
What the pipeline says you will close, weighted by stage. A forecast is only as honest as the close dates in it — clean those up before trusting this number in a board meeting.
Weekly report
What the team actually did this week: calls made, leads worked, deals moved. Activity does not equal results, but a week with no activity always precedes a month with no revenue.
Settings
The structure your CRM runs on: stages, teams, fields and where leads come from.
General settings
The basics for your CRM — how it identifies your business and the defaults new records inherit. Worth setting before the team starts entering data, because defaults are hard to retrofit.
Pipeline stages
The stages a deal moves through, from first conversation to won or lost. Keep them few and make each one mean something a buyer does, not something you do — "demo booked" beats "in progress".
Lead fields
The fields your leads carry, including custom ones you add for how your business actually qualifies. Every extra required field is friction at the moment of capture. Add them sparingly.
Functional groups
Groupings that decide which part of the business a lead belongs to — product line, region, service. This is what stops a lead for one division landing in another division's queue.
Teams
Your sales teams and who manages them, which drives both assignment and what a manager can see. A team without a manager assigned is the usual reason approvals and escalations go nowhere.
CRM users
Who has access, and what they may do — a rep sees their own leads, a manager sees the team. Access here is about visibility as much as permission: it decides whose pipeline shows up in whose reports.
Integrations
Connections to where leads actually come from — web forms, Facebook lead ads, spreadsheets, telephony. A lead that arrives by email and gets typed in by hand is a lead that arrives late and sometimes not at all.
Mailboxes
The email accounts the CRM sends from and reads replies into. Once connected, replies attach themselves to the right lead automatically instead of sitting in one person's inbox.
Email templates
Reusable messages with merge fields, so the team sends something consistent and quick. The point is not speed alone — it is that everyone sends the version that works.
Automations
Rules that fire on their own: assign this source to that team, nudge a lead untouched for five days. Automate the routing and the reminders. Leave the judgement calls to people.
Campaigns
Groups of leads worked together — an exhibition list, a festival push, a re-engagement drive. Campaigns are what let you answer "did that spend work" months later, so tag leads at capture rather than in hindsight.
Lead sources
The list of where leads can come from, which everything in analytics is grouped by. Keep this list short and stable. Renaming sources later breaks the comparison you built it for.
Danger zone
A full reset of this workspace's CRM data, for demos and for handing a tenant back. It touches only your own workspace. Like the rest of the platform, the audit trail survives it.
A note on accuracy
These were recorded on a live workspace, so the figures on screen are real rather than mocked up. Screens change as the product improves — where a video and the app disagree, the app is right.