Your search surface. With no client selected, browse the whole company or contact database. Pick a client to build their universe: filter by keyword, geography, size or tags, run an extended search for more companies, then select rows to approve, exclude, or push into a campaign.
Run an extended search straight from your filters, no brief required. Free; companies land in this client's universe. Then select rows → push to a campaign → find people. Prefill from brief →
Everything held back for . Suppressed domains & emails are blocked from all future searches; excluded companies were pulled out of the active list. Nothing here is deleted - you can put any of it back.
Filters are supportive: comma-separated terms match any (not all), words inside one term match together, and rows missing sector, size, revenue or location data stay included.
Company
Industry
Geography
Size
Tags
Name
Title
Email
Company
Location
LinkedIn
Tags
No matches in the database.
1
Credits & cost
Two ledgers, deliberately separate. Cost is what the vendors charge us, in
their units. Credits are what clients hold, in ours - 1 credit = 1 delivered
lead (verified valid/ok), charged once per company. A bounce refunds it.
The difference between the two columns is the margin on that client, and it is not guaranteed positive.
House account - spend with no client attached
Operator-direct enrichment, builder exports, the FHRS/Google universe work, the orphan-job reaper. Real money, nobody's invoice. This is the half of the question a client-only ledger can never answer.
Each client and their targeting brief (the firmographics + titles that define who to reach). Add a client, review or edit a brief, then confirm it to build that client's universe. A confirmed brief is optional - you can also build lists directly on the Universe page.
Set up a new client
Creates the client as a prospect and assigns their portal login - the email below is their username and the password appears once, right here. Add a first campaign now if you already know its name - or do it later from the Universe push flow.
Paste domains (or emails - the domain part is used), or load a CSV/TXT. These are held back from all future targeting for this client: companies already in their universe are pulled out, and every domain is suppressed from future searches.
Nothing pending. The next brief draft will appear here.
Bulk Import
Bring your own spreadsheets into the database. Drop a CSV or Excel of companies (or companies + contacts) - columns are matched automatically and rows are deduped against what's already here, so you confirm before anything lands. You can tag or relate every company a batch adds.
Drop a spreadsheet here.
.csv, .xlsx, .tsv - or click to browse. Column mapping is AI-inferred on upload (~$0.05–0.10).
Parsing + inferring columns
Recent imports
Label this import -
Applies to every company the batch landed. Tag and relationship are each optional - use either or both. Relationships are revertible in one click afterwards.
Anchor review - confirm before anything is written
Chain name variants
Chain grouping links premises by exact name, so different spellings of the
same chain - Costa Coffee / Costa,
Tesco Express / Tesco,
Co-operative Food / Co-op - stay split.
Detecting them flags the longer variant against its shortest-name root for you to
confirm or dismiss in the merge-review queue below. Nothing is merged automatically.
Merge review - likely duplicate companies
Mapping changed - re-map to re-project the rows and refresh dedup before committing.
Mailing responses replies for this campaign, inline; the system never auto-replies (§5.7)
Sender warmup
Sending capacity
Targeting - company types & job titles
Live activity
Agent run - campaign timeline
Food Service Map
—
608,649 UK food-service premises mapped. Pan and zoom: dense areas cluster, zoom in to see individual premises - click any one to inspect it. Search categories and types - each pick lands as a pill, and the map narrows to premises matching all of them - or filter by region. Draw a boundary (the polygon tool, top-right of the map) to list the premises inside it and push them to a client campaign.
Classify food-service premises into the foodservice map
Pick a business-type bucket, optionally narrow by name keyword or region, preview the match count, then assign a category. Only touches premises not already classified, and is reversible - re-run any time.
These premises were auto-filed by a name-keyword rule the system was not confident about - e.g. home bakeries filed as Restaurants at confidence 0.65. Re-file moves one to the right category and marks it manually reviewed - no automatic pass ever changes it again. Low confidence is the queue, not a failure.
Pre-send check
The pre-send checker now opens as a popout on the campaign page - it just opened above this note. Reopen the checker →
Reply Monitor
The Reply Monitor now opens as a popout from the dashboard's Mailing responses panel - it just opened above this note. Reopen the monitor →
When a contact bounces, unsubscribes, or goes 7+ days without a reply, this queue surfaces the company so you can promote the next backup contact into the active slot - keeping every company covered without manual chasing. Mostly quiet until live email sending is connected.
Scanning all clients
Queue clear.
No advance-eligible contacts right now. The next contact to hit the 7-day boundary will appear here.
Pick a client and campaign.
The people side of a campaign - every contact found for it, with email-verification status. Pick a client and campaign to see them and export the ready ones.
Campaign Contacts -
Every contact found for this campaign, with email-verification status. Export the ready ones - “pending” means the email hasn't been verified yet.
GDPR / data-subject requests - deletions, suppressions, and access requests. Add a request, match it to contacts in the database, then action or reject it. Reviewed weekly; records are soft-deleted so the audit trail survives.
Loading the queue
All caught up.
Nothing pending. The next request will appear here.
Recently actioned
Market Signals
Events in the world become ready-to-launch campaigns. Record a trigger (listing win, raise, reg deadline - manual entry only; automated watchers each need their own scoped admission), confirm it against a real signal, then launch a play - the segment resolves through the same filters as everywhere else and stages a draft campaign. Nothing spends here: enrich, verify and Instantly keep their own confirm gates, and activation stays human-only.
The playbook's loop: Watch → Infer → Confirm → Act. Chains ≥2 need a real confirming signal before launch.
Signal feed
No signals recorded yet.
Spot a listing win or a raise? Record it above - the matching play is one click away.
Play library
Launch a play
Stage a scheduled play
Staging records the calendar window as a confirmed signal and stages a draft campaign. Nothing sends - enrich, verify and Instantly keep their own gates; activation stays human-only.
Retailer calendar
Built to be corrected, not perfect on day one. Windows are hand-curated at month precision - correct any you know better; an edit stamps today as the last-verified date.
Map relationships
Directional, typed company-to-company links - wholesale_supplier · distributor · partner · parent · subsidiary. Pick a hub to bulk-tag its customers, or to review its existing graph.
Tags are free-text labels you put on companies or contacts - e.g. bidfood_customer · qsr · vip - so you can slice the database any way you need later. Relationships are typed company-to-company links (who supplies or distributes to whom). Build by hand, by uploading a list, or by mapping a hub's customers in Map relationships; everything here powers search, filtering, and the graph.
Tags applied from uploads or premises promotions where the match was less than certain. Keep the right ones, remove the wrong ones - either way they leave this queue.
Filter search results based on keywords associated with companies*
Suggestions:
Filter search results to include a specific company name*
The location of the company headquarters for a person's current employer*
Suggestions:
The number range of employees working for the company*
Suggestions:
Job titles held by the people you want to find*
Suggestions:
A word or phrase that appears in the person's name, job title, or company name*
The location of the company headquarters for a person's current employer*
Suggestions:
The location of the company headquarters for a person's current employer*
Suggestions:
The number range of employees working for the company*
Suggestions:
Pre-send check
Every email exactly as Instantly will send it - resolved names, subject, body. Sign off, edit, or personalise each one before launch. Keyboard: j/k next/prev · a approve & advance · e edit · r reject · A approve all pending · esc close.
Copy bank
Campaign-level sequence copy, generated from evidence on file - the play's angle, the trigger event, and relationship hooks from your own graph. Nothing is invented: no hooks on record means no hooks in the copy. Generated copy lands here first, never straight on a draft.
Reply Monitor - 0 replies
Classified replies for triage-mode clients. The system classifies and routes - it never auto-replies, and replies stay visible to the client in both modes (forward is the default). Low-confidence classifications wait here for your review.
Loading replies
No replies here yet.
Pick a client above. Replies appear when a triage-mode campaign receives them - this sprint they arrive via the synthetic feed.
Find companies
Set filters to find target companies - searching is free.
1 · Companies2 · People3 · Name & run
Enter or comma commits a pill. Keywords are supportive - each one widens the match (any, not all).
Its own free search (title × territory) - lands companies + ranked contacts into the campaign. It is NOT scoped to step 1's companies; Stage B scoping stays on the approve → find-people flow.