What needs you, your meetings and your deals.
Six things that make the CRM run the way your company sells.
What the team and the autopilot need a person to decide.
Loading…
Loading…
Loading…
Loading…
Prospects book real free times with you, and meetings land on your calendar with the brief an hour before.
Paste a target list and press the button. Roughly 90 seconds per organisation, one at a time.
Each video opens by naming what research found on that company. Rows with no signal have nothing to open with, so they are unticked — tick one anyway if you know better. About two minutes a video.
The ticked rows go in as cold prospects — no consent travels with them. Their CRM decides each one: new, added to an organisation it already has, parked for a person to review, or rejected as a duplicate.
A topic plan drawn from a playbook — what is changing in that niche's world, not what we would like to say about ourselves.
Before filming anything, check where the subject is actually searched. Compliance topics are read, not watched — the tool will say so rather than letting you make videos nobody looks for.
Sorted by what each reply is actually saying. The two that matter are otherwise buried among the automatic ones.
Loading…
What Leads › Find leads › Find warm leads wrote for each organisation, grouped by the city it ran for. Read and correct a message here before any of it goes.
Pipeline messages are not here. A message to an account in the pipeline is written inside its deal (Pipeline › Accounts › Work this deal), and waits for approval in Messages › Sending — or is recorded there if you sent it yourself.
Choose a city.
No email is connected for sending. Approved messages can be downloaded and sent from the team's own email, dated within that address's daily allowance.
Every drafted message waits here — whether it came from a campaign or from a step of a deal. Nothing leaves until you approve it, and approving records your name against it.
Loading…
Where each one actually reached — counted from what has left, not from what was planned. Nothing goes without your approval.
Sending re-checks five things at the last moment: the account may send, a person approved it, the date has arrived, the address has not asked to stop, and the sender is under its daily cap.
Loading…
One sentence. The rest — what to search for, which columns to record, what counts as a buying signal, which rivals to look for, how to grade a fit — gets written for you, and you can change any of it before it runs.
Written once. The one-line summary goes into every message, the proof points are the only claims the sequence writer may make, and the rivals become names research looks for on a prospect's own site.
Add a product on the Demos tab by uploading a spec — then describe it here.
Your site, product pages, case studies, demo videos, LinkedIn. The system reads them and writes down what they actually claim — you approve it before anything is kept.
Pick a scenario and I'll set the options and list the steps for it.
Nothing running. Submit a job to see live progress.
Loading…
Everyone who can sign in to this account. An operator runs campaigns; an administrator can also add people and manage keys.
They sign in with this email and password. Ask them to change it — you will both know it until they do.
CSV or Excel, in your own column names. Nothing is imported until you have checked how the columns match.
Pulled from the company's own systems with read-only credentials. Every lead goes through intake: duplicates are caught and anything uncertain waits for review.
Leads that may duplicate something already here, or research the CRM cannot vouch for. Nothing is merged without a person.
Questions the research engine could not settle alone: two records that may be one organisation, sources that disagree, a contact whose identity is unclear. Decide each one; nothing is merged or deleted from here.
Found by research, a partner referral without consent, or a cold list. No consent is held for them. When a reply qualifies one, it becomes an account and joins the pipeline.
Research these reads each organisation's own website and keeps one dated fact about them, with the page it came from — the line that makes the first email theirs. Only their own site: an address on a shared domain, like a certifier's or a ministry's, is never read as if it were theirs. Move to pipeline opens each at Untouched as a researched account — cold, so nothing can be sent until somebody agrees to hear from us.
What the autopilot prepared and is waiting on a person for: messages to approve, leads to move, deals to advance, replies and escalations. Approve runs exactly what you see, including your edits.
Loading…
The autopilot follows these in every draft and every choice. A Director's instruction for a territory or a deal is added on top of the company's.
Every decision the autopilot took or did not take, with the reason and the evidence.
In sandbox mode every message is captured here instead of being sent. "Blocked live" shows what the consent rules would stop for real. Simulate a reply to see how the autopilot handles it.
How good the autopilot's work is, measured by people and by outcomes, and what your own results suggest changing. Nothing here changes on its own: an administrator applies each suggestion, and every applied change can be undone.
Built from your won and lost reasons, reply rates, experiments and how much people edit the AI's drafts. Each one shows its evidence and exactly what applying it changes.
Loading…
A share of last week's messages, picked at random, for a person to score. The scores show on the dashboard, so quality is measured rather than assumed.
By template and by person, for messages and documents. A template people keep rewriting is a template to improve.
Test two to four subject lines, opening paragraphs or follow-up timings. Each deal always gets the same variant. A winner is chosen on interested replies and meetings, never opens, and only once the difference is more than chance; it is then offered as a suggestion.
Placeholders: {org_name}, {contact_name}, {country}, {sender_name}. For timing, write the days after the first message, for example "4, 10" on one line and "3, 7" on the next.
The points each fact about a lead is worth, and what your finished deals say they should be. New points are offered as a suggestion once there are enough outcomes.
Each mailbox's allowance today, its warm-up, this week's bounces and opt-outs, and its domain's SPF, DKIM and DMARC. A mailbox slows down by itself before a problem.
Won deals after the sale: onboarding progress, the latest satisfaction score and when each renews. Late milestones and renewals coming up also appear in Needs you for the person who owns them.
Loading…
Open pipeline by expected yearly revenue, the way the operating model reads it: by tier and forecast category, direct and partner revenue apart, and the strategic opportunities that need executive support.
How every lead is routed by scoring: the Control Room's priority where it has one, the CRM's model where it does not. Only ready routes enter the pipeline on their own; high-value leads with thin data go to research first.
Earned when a deal is won, by plan and the credit on the deal team. Someone other than the earner approves; a payout records its reference. If a won deal unwinds, unpaid commission is voided and recent payouts flagged for recovery.
Tiers by expected yearly revenue decide who owns a deal; strategic triggers ask for executive support. A deal that changes tier asks for a transfer and keeps its original credit.
Milestones opened when a deal is won, each due a number of days after winning and owned by a role on the deal team.
Who on the deal team earns, on which figure and at what rate. Members of the same role split by their credit, equally when none is set.
Terms on a deal that need a yes before it can be won. The person who asks never approves; changing an approved term asks again.
Commercial value, data confidence and contactability kept apart. Change weights or thresholds as a new draft; an administrator approves it and every lead is rescored.
Your research and scoring engine. Every 30 minutes the CRM reads its current scores and its outreach routing queue, and returns what happened: routes taken, deals won or lost, opt-outs and outcomes.
The partners who refer organisations to you, what their referrals became, and whether they get updates. Referrals are credited automatically from the partner named on each lead.
Loading…
Each introduction a partner makes. With acceptance on, new ones wait for the territory's Director or Growth Lead; an accepted introduction is protected for the set number of days, and the partner is told the decision, never the client's details.
Connect the tools your team already uses. Keys are encrypted on the server and never shown again, only a masked hint. Every feature that uses one still works without it.
Loading…
WhatsApp delivers only templates Meta has approved. Write one, submit it, and read back the decision.
Every 30 minutes: stage changes people make there come here, and deals, contacts and activity from here go there. When both changed, nothing is overwritten and the owner decides.
Set once. Proposals, prices, discounts, contracts and the Proposal, Contract, Won and Lost stages always stay with people, whatever is chosen here.
Tick nothing to work every territory. Start with one to try it.
New email address? Set SPF, DKIM and DMARC first, then let it warm up: it starts at the number above and climbs to the daily maximum over the warm-up length. Use a separate domain for cold outreach. Until an address is connected, approved email can be downloaded from Messages › Sending with the same limits.
Which steps your deals have at each stage, and whether they must be done before a deal moves on. Some companies sell simply and want a stage to be a status; some want every answer on record. Changes apply to every deal straight away, and work already recorded against a step you switch off stays in the deal's history.
Required must be done before the deal moves on. Core can be passed over with a one-line reason. Optional never stops anything. Off hides the step.
Loading…
The name, colour and logo on every document this company exports, and the logo in the header here. Only administrators can change them.
PNG, JPEG or WebP, up to 512 KB. A wide logo on a transparent background works best.
The only proof sentences the CRM puts in a first message, one per line, as
when | sentence. when is a crop (coffee), a focus (eudr, cooperative)
or default. Leave empty and no proof point is used.
What every draft is written under and checked against. The model is told these rules before it writes; anything that still breaks one is listed under the draft.
Written the way a contract writes them, for example two (2) years. Every document that names a term (the proposal, the order form, Schedule 1 and the service agreements) uses these, and a single deal can change any of them on its own Documents panel. Leave a field empty and the document keeps its template's own wording.
The bands a new deal is valued from, by edition and size. A deal already open keeps its value. Leave Up to empty for the top band. Bands in one edition cannot overlap.
Sales roles are separate from sign-in roles, and anyone can hold several — a Growth Lead in one territory and a Director in another.
The stages, territories and prices this company starts with. Safe to run again: nothing already changed is overwritten.
What a proposal, brief or intro starts from. Keep one per product where they differ; the shared version is the fallback.
Every client company on this platform. Each one's playbooks, registers and contacts are separate — nobody sees another's.
Creating a company does not create anyone who can sign in to it. Add its first administrator from the People tab once it exists.
Stopping the local engine cancels running jobs and shuts down the local model server, returning its memory to the system. The control API stays up so you can start it again from here.
Loading…
A saved product keeps its spec and every linked asset together, so future demos need only the client research.
Loading…
You create the OAuth client in your own Google Cloud project, and you approve it on Google's own screen. We never see a password, and the upload permission is the only one requested — not the one that can also delete videos.
Uploads are always private. Making a video public is something you do on YouTube, having watched it.
Per client, per provider, over the last 30 days. What an invoice for the local-model tier is made from.
Loading…
Loading…
Finished drafts are written straight into this mailbox's Drafts folder, where you review and send them yourself. Nothing here can send mail — it only appends.
Adding a new address? Set SPF, DKIM and DMARC on its domain first, and leave "sending for weeks" unticked: it warms up from a few a day to the daily maximum (Autopilot settings › Deliverability). Keep cold outreach on its own domain.
Keep the two apart. Cold outreach goes from a domain bought for it, so a complaint or a block never reaches the domain your company's real mail goes out on — and someone who opted in hears from your own name, which is what they agreed to.
Check replies reads the inbox and cancels the remaining touches for anyone who answered — and suppresses them everywhere if they asked to stop. Run it before each new batch. It only reads: nothing is moved, deleted or marked read.
On Plesk the host is usually
imap.yourdomain.com or mail.yourdomain.com on
port 993. The password is encrypted before storage and never returned
to this page, not even masked.
Loading…
Each row is one kind of AI work, and lists the CRM stages and steps it writes for. Pick a provider, then one of its best models — free ones are listed first. Leave a row on Default to use the first provider you have a key for.
Loading…
Keys are encrypted on the Mac and never sent back to this page — only a masked hint. With none configured, decks are still produced by the deterministic composer.