Sales software
ICPSignal: from public conversations to reviewed leads
Turning public buying signals into leads a person can understand, review, and move into a sales workflow.
By Curtis Tech Solutions3 min read
A public post asking for help can be the start of a useful sales conversation. Finding that post is only one part of the job. A team still needs to understand the request, judge whether it can help, and decide how to respond.
ICPSignal brings those steps into a lead discovery and review workflow. Curtis Tech Solutions developed the product’s discovery tools, reply drafts for human approval, and CRM integrations. The design centers on keeping the original conversation and the reason for a match close to the person making the decision.
Start with the customer you can help
The workflow starts with an ideal customer profile: a plain-language description of the people a business wants to serve. ICPSignal uses that context to look for relevant public conversations and surface potential leads with an explanation of the fit.
For example, a software consultancy might be interested in someone asking for help replacing an internal tool. A passing mention of software would provide much less useful context. This example shows why discovery needs to consider what a person is asking for, as well as the words in the post.
The explanation gives the reviewer something to evaluate. They can compare the suggested match with the source conversation and decide whether the business has a relevant service to offer.
Make review part of the workflow
A discovery system produces candidates. The product still needs a place to review them, keep useful context, and choose the next action. ICPSignal’s lead feed brings those decisions into the application instead of leaving a team to piece them together from disconnected links.
That distinction matters when building AI-assisted software. A matching score is an input to a decision. The underlying request, its context, and the reviewer’s judgment remain important. Showing why a lead was suggested makes the software’s output easier to inspect and challenge.
Keep a person in the reply loop
ICPSignal can prepare a reply draft around a relevant conversation. A person reviews and approves the message before it is sent. This keeps the business responsible for whether its response is useful, accurate, and appropriate to the discussion.
For the interface, drafting and sending are distinct actions. A suggested response needs to be editable, and the reviewer needs enough context to make a choice. The practical goal is to reduce the work of preparing a thoughtful reply while keeping the final decision visible.
Carry context into the CRM
Once a team chooses to pursue a lead, it can work in ICPSignal or use a CRM integration. The project includes connections for HubSpot, Salesforce, and Pipedrive. Carrying the source and conversation context into that next stage helps explain why the lead is there.
The engineering spans a Go backend and a React and TypeScript interface, connecting discovery, review, outreach, and handoff. It is a product development project whose value depends on how well those steps fit together. The central lesson is to design around the person deciding what happens next, from the first signal through follow-up.