Outcome before tool
Start with the sales or operational change required. Select technology only after the job is clear.
About Poso
Poso builds the data and workflow layer behind B2B sales — CRM freshness, enrichment, research, routing and the handoffs between systems.

About the founder
I’m Abhishek Patra, the founder of Poso. I’ve spent ten years as a founder, combining hands-on engineering with a deep interest in how businesses actually operate.
Working across sales and recruitment has meant dealing with the details behind those functions: researching people and companies, keeping information current, coordinating follow-ups, and moving work between people and systems.
I’ve used systems and automation in that work for years. That experience shapes how I approach a project: understand the workflow, identify the constraint, and build something the team can use and maintain.
At Poso, my focus is sales data and workflow infrastructure for B2B teams—CRM freshness, enrichment, prospect research, routing, and the connections between them. I stay deeply involved in client projects, bringing engineering judgment and operational context to the work.
You work directly with me to understand the problem and shape the solution. I remain involved as the work moves into implementation, with attention to the data, workflow logic, exceptions, and handover.
Discuss your workflowRevenue teams rarely need another disconnected tool. They need the information they already have to become current, connected and useful.
That means treating CRM data, enrichment, automation and handoffs as one connected workflow. It means finding where context is lost, where decisions become manual and where ownership becomes unclear—then building the smallest reliable system that closes the gap.
The aim is not automation for its own sake. It is infrastructure that makes a serious sales motion easier to run.
How we think
Start with the sales or operational change required. Select technology only after the job is clear.
A workflow should survive real records, edge cases and ownership changes—not just look good in a demo.
Enrichment creates value when it reaches the system and person who can act on it.
Logic, exceptions and decisions should be understandable after the initial implementation is complete.
Poso is built to implement, not just advise. We work across CRM data, APIs, enrichment providers, automation platforms and the operational logic between them. Systems can be built inside the client’s existing environment, documented clearly and handed over when appropriate.
What Poso is not
Better foundations
Start with a specific data or workflow problem. Clear scope makes better infrastructure.
Book a workflow call