Key points
- Research stage evidence from reliable company and programme sources.
- Check founder identity and current responsibility at each account.
- Review contact details and adapt the message to the partnership purpose.
Finding pre-seed and seed founder contacts starts with identifying a real company, a relevant operating founder and a reason your offer fits. Research the stage where it matters, then use the company domain or known professional profile to discover available contact data.
Early-stage labels do not guarantee a budget, quick decisions or buying intent. A founder may be building the product, running another function, working part time or no longer operating the company. Your list should preserve what you know and leave the rest unresolved.
Write an early-stage account brief
Describe the customer problem, product category, market and operating conditions your offer requires. For example, a user-interview tool might fit a founder actively researching a product with potential customers. A complex infrastructure service may require a deployment environment that an early-stage project does not yet have.
Record stage information only with its source and date. An announcement can support the round it describes; employee count and revenue are context rather than reliable round labels. Missing funding data does not prove pre-seed or bootstrapped status. The company-stage segmentation guide explains how to keep these observations separate.
Use public sources to establish identity and relevance
| Source type | What to capture | What to check before acceptance |
|---|---|---|
| Company website or product page | Product, domain, named team and stated market | Whether the site is current and the person has an operating role |
| Public accelerator or portfolio listing | Company identity and the programme or investment relationship described | Listing date and whether the company still matches the use case |
| A public product launch | The product and person actually associated with the launch | Whether it represents a company, side project or different entity |
| A founder's own professional profile | Name, role, company and relevant description | Current responsibility and consistency with the company's identity |
| A public community contribution | The specific statement relevant to your product | Context, date, community rules and whether contact is appropriate |
Use only information you can access and process appropriately. A community membership, application, private cohort or event attendance list is not automatically public prospecting data. Do not assume hidden member directories can be collected or that a public post author has agreed to vendor outreach.
Investigate the founder's actual role
Founder, Co-Founder, CEO, CTO and product-related titles can describe different people at the same startup. Map the person to the workflow your offer changes. A technical founder may evaluate an integration; another founder may own customer acquisition. Neither assignment should be inferred solely from a title.
If founder experience matters to your offer, use a clear self-description or documented work history. An incomplete profile, small team, recent company or community membership does not establish that this is someone's first venture. Keep “experience unknown” as an acceptable outcome rather than creating a speculative personality segment.
Choose the discovery route that matches your inputs
You have reviewed company domains
Use company-website criteria and relevant founder or executive title variants in founder contact search. Add industry, company size or geography only where they support the account brief. Dievio has stored funding-date fields, not a native live pre-seed or seed-stage feed.
You have reviewed professional profiles
Use LinkedIn Lookup for known profile URLs. Check which fields are available for each returned record; some may have no email or phone. A profile match is not proof of current employment or a fresh mailbox check.
You have only a broad market definition
Start with supported company and role filters, then inspect a bounded sample. If the product requires a condition such as a specific technical environment or founder-owned acquisition, research that separately. A large contact count cannot validate those conditions.
Build an evidence-led working list
- Capture the account. Save company name, domain, use case and supporting source date.
- Resolve the person. Keep the full name, actual title, profile and relevant responsibility.
- Preview matching records. Free count previews hide contact details and do not measure the entire startup market.
- Retrieve a limited sample. New retrieval spends credits. Check identity, role fit and required fields before expanding.
- Review the channel. Keep email availability, separate validation outcomes and exclusions distinct. Do not fill missing addresses by guessing a company pattern.
- Assign the next action. Accept, research, exclude or hold; keep a reason and responsible owner.
Deduplicate people as well as companies: multiple founders can be valid contacts, but duplicate records for the same person do not add coverage. Keep the accepted list so repeated searches do not become an unnecessary recurring retrieval cost.
Example: turn a public product observation into a relevant question
Suppose a founder publicly explains that they are interviewing potential customers for a new collaboration product. If your tool supports that workflow, record the observation and verify the company identity. A possible opening asks whether interview organisation belongs to their current remit and offers a concrete explanation of your product's relevant capability.
Do not state that the company has raised money, needs a paid tool or is unhappy with its existing process unless you have evidence. Do not imply a mutual connection or customer result that does not exist. If community rules call for an on-platform answer, respect that context.
Review activation and refresh from actual changes
Public contact details and community participation do not grant blanket permission to market. Review the source, purpose, applicable jurisdiction and channel, and honour preferences and exclusions. The B2B data and outreach compliance guide separates personal-data processing from communication rules.
Revisit the record when the product, team, domain or contact outcome changes. Use the CEO and founder search playbook to connect these early-stage checks with a campaign-ready contact handoff.



