Vague Data
A pipeline that fills itself.
A lead lands, a rule fires, a person owns it. Duplicates are caught at the door, and every deal carries its own documents and payments.
The record everything else writes to. Calls, threads and conversations land here, on the lead they belong to, owned by the right person from the first minute.
- Round-robin routing by country, city, source or campaign
- Duplicates caught across typed, imported and form intake
- Deals carry stage, documents and payment schedule
- Overdue payments flag themselves
Round-robin routing by country, city, source or campaign
Duplicates caught across typed, imported and form intake
Deals carry stage, documents and payment schedule
Overdue payments flag themselves
In detail
What Data does.
Capabilities that exist today.
Routing
The lead never waits.
A form is filled at two in the morning. In most pipelines it sits unowned until someone opens a spreadsheet after breakfast, and by then the customer has filled in your competitor's form too. Here a rule fires on arrival: Dubai leads to the Dubai desk, Instagram leads to whoever is next in the rotation. Preview a rule against real leads before switching it on, and re-run it when the team changes.
- Round-robin by country, city, source or campaign
- Preview the rule's outcome before you commit it
- Re-run a rule across existing leads
- Bulk assign, reassign and archive
City is Dubai → Dubai desk. Otherwise → next in rotation.
Dubai · Instagram · 2:01 am
Riyadh · Webflow form · 2:14 am
Intake
One customer. One record.
The same person will fill your form twice, and appear in a CSV a month later with their name spelled differently. Duplicate detection runs at every door, typed, imported or submitted, so they land on the record you already have with the history intact, instead of becoming three leads assigned to three people.
- Detection across manual, form and CSV intake
- Saved filters for the views your team lives in
- CSV import in, filtered exports back out
- A response taxonomy you define, not one we impose
Existing record
Kristin Watson
3 calls · 2 threads · 1 deal
Incoming row
K. Watson
csv_march.xlsx · row 118
Deals and money
The deal carries its own paperwork.
Stage, documents and payment schedule travel with the deal, on the customer record. When an instalment slips past its date it flags itself, so the overdue payment surfaces in the pipeline where someone owns it, not in a finance review three weeks later.
- Multi-step deal creation with document upload
- Payment schedules with overdue alerts
- Channel partners and clients alongside leads
- Tasks and notes on the record
signed · 4 Mar
paid · 12 Mar
due 9 days ago
Better together
Data works with the rest.
Everything writes to the same customer record, so adding a second product does not mean a second migration.
Calls that log themselves.
See PhoneThe 24-hour window, handled.
See WhatsAppThe whole suite
One login, one record, one bill.
Questions
Data, specifically.
No. Deals are table-first, built for volume and filtering rather than dragging cards. If a board is essential for you, say so on the demo.
Yes, by CSV, and duplicate detection runs on import so a migration does not double your database.
Access is role-based and enforced on the route, not just hidden in the interface.
Yes. The response taxonomy is editable, so the stages match how your team actually sells.
See Data on your own data.
Thirty minutes, your records, no slides.