One record per person
Forms, ad platforms and manual entry all land on the same contact, deduplicated by email and phone, with the original source preserved.
Built for real-estate teams of 3 to 25
NexaFlow catches leads from your forms and ad platforms, keeps the whole conversation on one record, and moves them through a pipeline the whole team can see — so nobody has to ask who is following up.
Launching soon — design-partner pilots are running now.
Lead
Claire Bennett
Timeline
Illustration, using made-up data.
Why teams switch
Leads arrive in six places — a form, an ad platform, a text, an agent's inbox. What breaks is not capture, it is the twenty minutes afterwards, and the week after that.
Forms, ad platforms and manual entry all land on the same contact, deduplicated by email and phone, with the original source preserved.
Every lead carries an owner and a due task. What needs doing today is a list, not a memory exercise.
A broker sees the pipeline; an agent sees their own work. Nothing lives only in somebody’s phone.
From first touch to closing
A lead arrives from a form, an ad, or a referral, and lands with its source and owner intact.
Work it through new, working and qualified — with the reason for every move recorded.
Convert to a deal, put it on the board, and keep the next action and the person owning it visible.
Won or lost, the history stays on the contact instead of leaving with whoever handled it.
What you get
Marked items are designed and scheduled but not yet running. We would rather you read that here than find it in week two of a trial.
Website forms and a webhook endpoint, plus Zapier for anything else. Duplicate leads merge instead of multiplying.
Convert a qualified lead into a deal, move it across a board, and keep the value, stage and owner on one screen.
Invite agents, assign leads by rule, and keep permissions matched to responsibility.
Connect Gmail or Outlook. The last 90 days sync in, every conversation lands on the contact it belongs to, and replies go out from your own address.
Meta, Google, LinkedIn and TikTok run through Zapier or a webhook today; native connectors are being built.
Drafting, summarising and prioritisation, with a person approving anything that reaches a client. Not yet switched on.
Our position on AI
AI is useful for the preparation around a client conversation and poor at deciding what to say to a person about the largest purchase of their life. NexaFlow is built on that line: the assistant prepares, a person approves, and the CRM records who decided what.
None of this is switched on yet. When it is, it will be optional, and every workflow will stay operable by hand.
An AI draft sits in the record until a person edits and sends it.
Roles decide what a person can see; the assistant does not widen them.
Suggestions are written to the record, not hidden inside a workflow engine.
Canadian by default
Database, storage and application servers all run in AWS ca-central-1. Mailbox credentials are encrypted with AES-256-GCM, and disconnecting a mailbox deletes them on the spot.
AWS ca-central-1
Montreal, Canada
Before you start
In Canada. The database, the file storage and the application servers all run in AWS ca-central-1, and data is not replicated outside the region.
Yes, through Zapier or a direct webhook today — both are live, and every lead keeps its source. Native one-click connectors for Meta, Google, LinkedIn and TikTok are in development.
No. Every workflow in NexaFlow is operable by hand. The AI layer is designed to prepare work — drafts, summaries, prioritisation — and to leave the decision with a person.
You can export it, and we delete it on request. Disconnecting a mailbox deletes the stored credentials immediately rather than at the end of a billing cycle.
Launching soon
We’re running design-partner pilots now. Join the waitlist and we’ll reach out as pilots and pricing open.