One conversation, from a live count to a running feed.
The chat that counts and builds
Know in seconds how many of the people you want exist and what they cost, before you spend anything.
You describe the audience in plain English. The chat picks the filters, runs the count against our identity graph of hundreds of millions of people with phones, emails, addresses, property, in-market signals, form fills and callers, and shows the number live. Then it asks the one question that matters: once, on a schedule, or as an audience?
“Homeowners in ZIPs 75034, 75035 and 75071, homes built before 2010, owner-occupied, with a cell phone”
About 38,000 homeowners match, and 31,000 of them have a cell phone that rings.
Do you want them once, on a schedule, or as an audience in your ad account?
Hail-path homeowners
Fills in as you go. The checklist below says what is left.
- What
- Homeowners in ZIPs 75034, 75035 and 75071, homes built before 2010, owner-occupied, with a cell phone31,000 in the pool right now
- Supply
- About 90 a dayNew matches, measured over 30 days. First send clears the 31,000 standing now.
- You get
- Every Monday, up to 700
- Goes to
- Posts to your dialer webhookOne test record goes first, nothing is live until it lands.
- Headroom
- About 2,700 a month, inside 250,000Past that it stops sending rather than billing more.
- Cost
- Feed 1 of 1 includedNo extra charge for this one.
The deal card beside the chat. Every line is written by a live count, never by the assistant. Figures shown are illustrative.
Most data vendors make you wait for a sales rep to come back with a count. Here the count is the first thing you see, and the card beside it shows the cost at your volume, so the decision is yours to make in the same minute.
Book a demoSeven things people ask for, and what happens next.
Each one is a real situation, the ask in the buyer's own words, what the chat sends back, and what it costs on the plan that carries it. Platform, Scale and Growth each carry a monthly fee, and Enterprise is on its own terms. Counts are free on all of them.
Counts and exports in chat
A roofing company gets a hail storm on Tuesday and wants to be knocking on doors by Thursday. They know the ZIP codes. They do not know how many homes are there or what a list would cost.
- They ask
- “Homeowners in 75034, 75035 and 75071, homes built before 2010, owner-occupied, with a cell phone”
- What comes back
- The chat counts them against our identity graph while you watch and writes the number and the price on the card beside it. Say the word and it exports the file: name, address, phone, email where we have it, with Do Not Call flagged on every cell number.
- What it costs
- Counts are free. Each record you keep counts against your plan: Platform is $99 a month with 1,000 records included, then $0.10 each. All plans
Website visitor identification
A solar installer spends real money sending people to a quote page, and most of them leave without filling it in. The ad platform says they visited. Nobody can say who they were.
- They ask
- “Who is on my website right now?”
- What comes back
- The chat gives you one snippet, or emails it to your developer. From the first real visit on, visitors who leave without a form come back as people, with a phone, an email and a mailing address where we have them, listed on Overview as they arrive and ready to call, mail or push to an ad audience.
- What it costs
- Counts are free. Each record you keep counts against your plan: Platform is $99 a month with 1,000 records included, then $0.10 each. All plans
Data feeds
A call center has forty seats and a floor that runs out of numbers by Wednesday. Someone downloads a list every week, uploads it to the dialer, and forgets which rows were already called.
- They ask
- “Homeowners aged 45 to 70 in Florida and Texas with a cell phone, 20,000 a week, into our dialer”
- What comes back
- The chat sets the schedule, posts one test record to your webhook, S3 bucket or inbox, and waits for you to say it landed. From then on every run arrives on time with the records you already have taken out, and the row on Overview says when it last sent and when it sends next.
- What it costs
- A recurring feed is a slot on the plan. Scale is $1,000 a month with 20,000 records included, then $0.05 each and 1 recurring feed included; each additional feed is $500 a month. One feed carries up to 250,000 records a month, then it stops sending rather than billing more. All plans
Ad audiences on Meta, Roku and streaming TV
A Medicare agency runs Meta and streaming TV in three states and rebuilds the audience by hand every month from a spreadsheet. By the time it uploads, a third of the people in it have already turned 65.
- They ask
- “Put the people turning 65 in Florida, Texas and Arizona on Meta and streaming TV”
- What comes back
- The chat builds the audience, you share your ad account once, and we push it into Meta, Roku or Vibe and refresh it every day as new people qualify. Nothing to download and nothing to upload, and Overview shows how many people are in it today.
- What it costs
- An audience is a feed slot on the plan. Scale is $1,000 a month with 20,000 records included, then $0.05 each and 1 recurring feed included; each additional audience or feed is $500 a month. One audience holds up to 2,000,000 people. All plans
Database activation
An auto dealer group has 300,000 past customers in a CRM and no way to know which of them is shopping again this month. The file has names and addresses. Half the phone numbers are old.
- They ask
- “Here is our customer file. Tell me who in it just went in market for a car.”
- What comes back
- Drop the file on the chat. We match it against our identity graph, show the match rate, fill in current phones and emails, and watch it. When one of your customers goes in market, moves, or changes phone, that record is sent to the feed you picked, on the schedule you set.
- What it costs
- Your own database is on Growth: $5,000 a month with 250,000 records included, then $0.02 each, and 5 recurring feeds included to send the matches out on. All plans
The identity API
An insurance agency gets inbound calls all day and the agent answering sees a phone number and nothing else. The CRM has a field for everything, and no time to fill it in while the call is ringing.
- They ask
- “Check this phone number”
- What comes back
- Your software sends the phone number to one endpoint and gets the person back: name, address, email where we have it, and the signals we hold, fast enough to use before the agent says hello. The chat shows you the exact call for what you just built, and batch appends run the same way over a file.
- What it costs
- Counts are free. Each record you keep counts against your plan: Platform is $99 a month with 1,000 records included, then $0.10 each. All plans
The assistant connector
A marketing lead already spends the day in Claude or Cursor and does not want one more tab. They want to size an audience in the same window they write the brief in.
- They ask
- “Count homeowners in Phoenix with a pool and a home over $600,000, and set up a weekly feed to our CRM”
- What comes back
- Paste one URL into the assistant you already use and sign in when it asks. From then on that assistant counts, prices, orders and sets up feeds with the same tools as the chat here, spends the same records, and asks you before it spends anything.
- What it costs
- No charge on any plan. Counts are free there too, and records cost what they cost on your plan. All plans
Where it goes
Records land where your team already works, on the schedule you set, and nothing goes live until a test proves the connection.
The same audience can go out five ways. A one-off file. A recurring feed that posts to your webhook, writes to your S3 bucket, emails a CSV, or waits for your code to pull it. An audience kept fresh in Meta, Vibe or Roku. A pixel that names the people visiting your website. An identity API your own app calls, phone in and identity out. You can also upload your own customer file and ask to be told when anyone in it moves, changes phone or goes in market.
“Homeowners aged 45 to 70 in Florida and Texas with a cell phone, 20,000 records, delivered weekly”
A list you have to download and upload is a list that goes stale. A feed with a passed test send runs on its own, dedupes against what you already have, and stops at its ceiling instead of billing you more.
Book a demoFive real records went to your webhook
POST https://crm.example.com/hooks/tdtm200 OK- Dana Whitfield · Plano, TX(555) 010-4471
- Marcus Oyelaran · Frisco, TX(555) 010-2208
- Priya Natarajan · McKinney, TX(555) 010-9135
- Tom Albrecht · Allen, TX(555) 010-6624
- Renee Castellanos · Prosper, TX(555) 010-3390
No charge for a test. The same five records will not be sent again.
Did they land where you expected?
Then it runs on its own
The test send before any feed goes live. Names and numbers shown are invented.
- Webhook. Each batch posted as JSON to a URL you give us.
- Your CRM. Most CRMs accept a webhook.
- S3 bucket. A CSV in your bucket on every run.
- Email CSV. A file to the inbox you choose.
- API pull. Your code asks for the next batch when it is ready.
- Ad audience. Kept fresh in Vibe, Meta and Roku.
- Pixel. Your website visitors, identified as they arrive.
- Your database. Upload your file, be told when anyone in it changes.
Overview, everything you own on one roster
One screen answers the four questions an owner has about every feed: what is it, how often does it run, did it deliver, and what does it cost.
Every feed, audience, pixel and API key on the account is a row. Each row carries its cadence, when it last ran and when it runs next, a thirty-day sparkline of volume, the cost, and a plain sentence if anything needs attention. Product tabs are for setup. Status lives here.
“People aged 64 to 65 in Florida, Texas and Arizona with a cell phone and a mailing address”
When a feed stops you find out from the roster, in words, the same morning, instead of from a quiet month and a surprised sales team.
Book a demoTexas homeowners over $400K
LiveWebhook1,400 in the last 24 hours. 42,000 this month, inside 250,000.
Every day at 06:00
Last 2h ago, next in 22h
Feed 1 of 1 included
Records count against your plan
Turning 65 in FL, TX and AZ
LiveMeta audience48,000 people in the audience. Refreshed this morning.
Refreshes daily
Last 6h ago, next in 18h
$500 a month
Second feed on the plan
Website visitors
LivePixel · example.com310 visitors identified this week. 2,900 since install.
As they arrive
Last visitor 4 minutes ago
2,900 records
Metered against your plan
Customer file, in market for auto
Test sendYour database · S3Waiting on you to confirm the test file landed in your bucket.
Five test rows were written to s3://example-bucket/tdtm/ 20 minutes ago.
Every Monday
Not run yet
$500 a month
Charged when you switch it on
Identity API
API keyProduction key12,400 lookups in the last 7 days, 9,800 matched.
When your app calls
Last call 1 minute ago
12,400 records
Metered against your plan
The Overview roster. One row per feed, audience, pixel and API key, with cadence, thirty days of volume and cost. Figures shown are illustrative.
Bring the audience. We count it live.
Thirty minutes. Tell us who you are trying to reach and we run it against the real data while you watch. You leave knowing your count and your cost before you spend anything.
Book a 30-minute demoNo deck and no trial. If we are not a fit we say so on the call.
What the demo covers
- The audience you are trying to reach, counted live against the real data.
- What it costs for your volume, against prices you already saw on the pricing page.
- How it gets delivered: a recurring feed, the pixel, the API, or your ad platform.
- Compliance for your specific use case, including DNC and consent.
Prices are published. Read them first so you arrive knowing the numbers.