An agency can offer several services and still need a very specific kind of project next. Maybe you have capacity for a migration, a design engagement, or a particular implementation. ‘Find businesses that need help’ is too broad to guide that search.
I'd start with the work you can deliver well right now. Name the project, the constraints, and the situation that would make a business look for outside help.
Describe a project you would actually take
Use a short service brief: the starting problem, the work included, supported platforms or requirements, and the conditions that would rule it out. Keep capacity and delivery constraints in mind when deciding what belongs in scope.
For a made-up example, a web agency might focus on migrating an existing site while preserving required integrations. That is a clearer discovery target than every conversation about websites. The exact brief should reflect work your agency can support.
Read whether they want advice, implementation, or hiring help
A question about a project doesn't always mean the author wants to hire someone. They may be learning the process or comparing approaches before deciding how to proceed. That affects the useful response.
Look for an explicit request for recommendations, outside assistance, or a provider. Check the requirements even when hiring intent seems clear. An urgent project can still be outside your expertise or available capacity.
| Hypothetical post | Useful first action |
|---|---|
| How do migrations work? | Explain the process or a key tradeoff. |
| Which approach fits these requirements? | Help clarify the decision. |
| Can anyone recommend an agency for this migration? | Check scope and disclose your connection when responding. |
Use the project brief in ICPSignal
Create an ideal customer profile around the customer and that specific project. Include exclusions for other agencies promoting themselves and work you cannot deliver. Review the profile, activate discovery, and inspect the posts behind the matches.
The fit explanation can help organize your review, but read the context yourself. If a required detail is missing, keep it as a question. Don't let a promising description turn unknown scope into an assumed commitment.
Help them understand the project before asking for a call
Offer one practical consideration tied to the request. Explain which requirement would affect the approach, or ask about the constraint that determines whether you can help. Say you represent the agency if you offer its services.
Track the conversation and record what you learn about scope. I'd rather begin with a clear, limited question than promise an entire project before understanding it. That makes the next discussion more useful for both sides.