# Audience Intelligence: Contact scanner that finds freelancers' first clients

New freelancer with skills but no pipeline is the first audience because the report already names a repeated pain, reachable channels, and a validation test that can be run before software is complete.

## Segments
- **New freelancer with skills but no pipeline**: First clients almost always come from existing contacts, but new freelancers stare at a decade of connections with no method for figuring out who might actually need their service or how to open the conversation. Trigger: Freelance-career research consistently shows first engagements come overwhelmingly from prior professional networks rather than marketplaces. Budget signal: One-time launch-package fee with a subscription for ongoing pipeline scanning.
- **Budget owner who feels the operational cost of the broken workflow.**: LinkedIn data-access restrictions constrain the import path. Trigger: AI-assisted product work and managed infrastructure reduce the first-version cost. Budget signal: $49-$499/month
- **Hands-on operator willing to pilot a narrow tool before a full rollout.**: One-shot usage pattern unless the ongoing-pipeline mode proves valuable. Trigger: One-time launch-package fee with a subscription for ongoing pipeline scanning. Budget signal: $99-$1,000/year add-on
- **New freelancer with skills but no pipeline who still run the workflow in spreadsheets, generic docs, email, or chat threads.**: First clients almost always come from existing contacts, but new freelancers stare at a decade of connections with no method for figuring out who might actually need their service or how to open the conversation. Trigger: The wedge is specific enough to test without claiming the whole market. Budget signal: Custom

## Channels
- **Reddit / forums**: Look for complaints, workarounds, and repeated questions. First move: Post a problem teardown for Freelancer go-to-market tools and ask how people solve it today.
- **Launch communities**: Launch traction shows whether the promise is legible. First move: Ship a narrow demo and watch which promise gets clicks.
- **Review and alternative pages**: Pricing and alternatives expose buyer objections. First move: Write an alternatives page that owns one narrow use case.
- **Community pain posts**: Use communities and forums where New freelancer with skills but no pipeline already describe the painful workflow. First move: Problem teardown, interview ask, and short demo clip
- **Direct outreach**: Direct conversations are the fastest way to verify budget ownership and switching cost. First move: Concierge pilot offer with a manually prepared sample

## Intent Keywords
`contact workflow`, `scanner validation`, `contact ai`, `scanner automation`, `sales`, `founder-tools`, `Freelancer go-to-market tools`

## Messaging Angles
- Contact scanner that finds freelancers' first clients should be tested as a narrow first-win workflow for one buyer: New freelancer with skills but no pipeline.
- Replace a narrow workflow that reaches value without configuration-heavy onboarding. with a focused first-win workflow.
- Promise proof around problem resonance: 5+ calls or 10+ detailed replies..
- De-risk adoption with concierge review or paid template.

## Objections
- LinkedIn data-access restrictions constrain the import path.
- One-shot usage pattern unless the ongoing-pipeline mode proves valuable.
- Needs real buyer access, not only desk research.
- Needs proof of budget or repeated urgency.
- Needs a crisp wedge before broad product work starts.
- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.