Resolve the company record
Move from a target list, company name, or domain into one durable operating record with registry and LinkedIn context aligned.
ProspX helps sales and research operators resolve target companies, reconstruct the org chart, and activate validated account intelligence without flattening everything into a generic CRM.
3
Core workspaces
1
Resolved company graph
4
Operator actions after review
Launch view
Leadership layers
Executive leadership
Revenue and GTM leadership
Functional directors
Regional and team managers
Activation gates
Problem
ProspX exists to correct that order of operations. The product starts with company resolution and org-chart review so downstream outreach can be based on a real buying committee.
Move from a target list, company name, or domain into one durable operating record with registry and LinkedIn context aligned.
Turn employee discovery into a manager-usable company map with reporting lines, leadership layers, and confidence markers.
Push approved intelligence into leads, campaigns, deals, or exports through explicit operator actions.
Workflow
The launch site should describe the actual retained workflow: company intake, account resolution, hierarchy review, then explicit activation.
01
Operators start from a company, website, or target list and queue LinkedIn-aware resolution.
02
The system resolves the account, normalizes identity, and groups overlapping source records into one company spine.
03
Researchers review titles, reporting lines, hidden contacts, and manual edits inside the hierarchy workspace.
04
Approved outputs feed leads, campaigns, deals, and exports only when an operator chooses to trigger them.
Launch modules
The public IA stays narrow and credible. It shows product truth, a realistic platform preview, and a clear handoff into launch conversations.
Hero
Explain ProspX as company resolution plus hierarchy intelligence, not a generic CRM.
Problem framing
Show the cost of running outreach before the account and reporting structure are understood.
Workflow
Walk through intake, entity resolution, hierarchy curation, and operator-triggered activation.
Role model
Frame the product for admins, managers, operators, and viewers with clear workspace boundaries.
Platform preview
Expose a high-fidelity static shell that mirrors the retained internal product surfaces.
Proof and CTA
Reinforce product truth, then end with a launch review call to action.
Roles
Admins, managers, operators, and viewers all work inside the same product boundary, but they should see different capabilities and responsibilities.
Workspace governance
Pipeline oversight
Core production
Read-only consumption
Proof
These are the non-negotiable truths the public site and the internal app shell now share.
The UI treats the company as the anchor object and keeps downstream sales entities secondary until the account is understood.
Operators can inspect reporting lines, titles, and edge cases before they push records into campaigns or CRM workflows.
Viewing account intelligence stays observational. Sync, export, and campaign actions remain explicit workflow events.
Platform
It shows the future shell shape using realistic operational, intelligence, and administration modules without pretending the milestone-one website is a live authenticated product.
Review a static shell that mirrors the retained app surfaces: companies, opportunities, leads, deals, campaigns, hierarchy canvas, hierarchy detail, and administration.