ICPSignalA request for migration help can sound like a good fit until you read the details. The source system may be outside your expertise. The deadline may be impossible. The person may want a tutorial rather than somebody to do the work.
I would define the projects I can serve before looking for more of them. That gives discovery a useful boundary and makes the first conversation more honest.
Name the work you can take responsibility for
Write down the systems or project types you support, what is included, and what would require additional investigation. Be clear about whether you advise, implement, or provide ongoing help. Those are different offers.
For a hypothetical example, a team might handle a particular website migration but exclude custom data transformations. That exclusion belongs in the brief if it determines whether the team can deliver. Use your actual capabilities in the live profile.
Separate stated requirements from unanswered questions
A useful post may name the source system, destination, integration needs, and reason for moving. It may also omit most of that information. Record what is known before deciding what you need to ask.
Don't treat an urgent deadline as evidence that the scope is manageable or that the project is funded. It is one condition to evaluate. I'd check whether the request fits before allowing urgency to determine the response.
| Detail | Why I would check it |
|---|---|
| Source and destination | Whether the work is within supported systems. |
| Data and integrations | Whether important requirements change the scope. |
| Deadline | Whether delivery is realistic. |
| Type of help | Whether the author wants advice, implementation, or a referral. |
Make the migration brief your discovery target
Use the audience, migration problem, and exclusions in an ICPSignal ideal customer profile. Review the profile before activation. Inspect matching posts and the potential-fit explanation, then check the surrounding conversation.
If results are mostly tutorials or providers advertising the same service, refine the brief using those patterns. If relevant requests are sparse, inspect customer language and available sources before making the profile broader than your actual offer.
Ask the question that changes whether you can help
Your first reply doesn't need a full project estimate. Offer one useful consideration and ask about the missing requirement that matters most. Disclose your connection if you introduce your service.
As the person answers, record the scope and promises made. Qualify the project before handing it off or discussing a firm commitment. I want the early conversation to reduce uncertainty for both sides, rather than create a promise the delivery team has to undo.