About
A CRM shaped by the work, not the category.
Zedata started because the tools built for agency lead-gen were either a general CRM with client separation bolted on, or an outreach engine with a contact list attached.
Why
The gap it was built for
An agency running outreach for a dozen businesses has a problem most CRMs never consider: the same team works across accounts that must never see each other. Bolting “teams” onto a single-tenant CRM produces a permissions model nobody trusts, and running one CRM per client produces twelve logins and no overview.
Zedata starts from the other end. An agency is the account; every client is a workspace inside it with its own contacts, pipelines and deals. You switch client the way you switch tabs, and a contractor invited into one workspace has no path to the rest.
The second problem is simpler and more stubborn: nobody enters data. A lead found on a profile page takes two minutes to type into a CRM, so it does not get typed. Capture had to be one click from the page you were already reading, or the rest of the product would sit empty.
Principles
What we will and will not build
These have already decided what the product does not contain — an inbox and an outreach engine were both built and then removed.
Nothing happens without a click
No background crawling, no scheduled scraping, no automated messages. Every record in Zedata exists because someone chose to capture it. This is a product decision as much as a safety one — tools that act on their own get their users’ accounts restricted.
Say what it does not do
Every page here lists absences as clearly as features. A CRM is a month of work to migrate into; finding out in week three that the thing you needed was a roadmap item is worse than never signing up.
Isolation is enforced, not implied
Workspace separation is checked on the server on every request, not hidden in the interface. An agency member cannot read another agency’s data even by calling the API directly.
Your data stays yours
Export a whole agency as a file at any time, and delete it permanently from the same screen. No retention games, no export fee, no support ticket required.
Built on
Boring infrastructure on purpose
A small team cannot also run a database. Everything here is managed, so the work goes into the product.
- Interface
- Next.js and React
- Backend
- Cloud Functions
- Database
- Firestore
- Auth
- Firebase Authentication
- Capture
- Chrome extension, Manifest V3
Where it stands
Still being built, and in use
Zedata is in active development and running for a small number of teams. Features can change and there is no uptime guarantee — so export anything you would hate to lose, which takes one click from Settings. If that is too early for you, it probably is; we would rather say so here than discover it together later.
Start capturing leads
Create an agency, add the browser extension, and your next profile visit becomes a record in your pipeline.