- Planned
- Native
- Send and receive
Formwink + People Data Labs
Company context on a brief, from the work email they already gave you.
What it does at launch
Look up firmographic context — company size, industry, location — from the domain on a submitted work email, and attach it to the lead brief. Runs on submission, is rate-limited, and is skipped entirely for free-mail domains.
What comes back into Formwink
Company attributes attached to the brief, each labelled with its source and the date it was fetched.
Not implied
That enriched values are verified, or that they affect fit. Enrichment adds context a reviewer can read; it never sets a fit label, never disqualifies an inquiry, and is never treated as something the respondent told you.
A failed integration never becomes a lost submission. Every inquiry is saved first; delivery history shows receipt separately from any confirmed outcome.
Queued, not built. There is no date.
Delivery is not an outcome. An accepted webhook, a posted message or a created contact means the send succeeded — never that the inquiry became a customer. Receipt, human qualification and recorded outcome stay three separate facts.
How it connects
Native
Data moves
Send and receive
Available?
Planned
Keep exploring
Integrations
Clay
Run an inquiry through your Clay table, and read the result on the brief.
Integrations
HubSpot
Send inquiries to HubSpot. Bring their outcomes back.
Product
Lead qualification
Understand which inquiries deserve attention, and why.
Solutions · For your workflow
Client intake form
Structure the first conversation so the right clients get a fast, informed reply.
Formwink is in beta.
Connectors ship in the order beta users ask for them.