Dievio
Key points
- Use founder and co-founder title variants, then confirm their current role.
- Narrow the audience with supported industry, location and domain filters.
- Validate counts before retrieving contacts and review records before outreach.
A founder prospect list needs three separate definitions: the companies you serve, the geography that makes them relevant and evidence that the person is actually a founder. A CEO, owner or managing partner can be a useful buyer without being interchangeable with Founder or Co-Founder.
Build the list around those distinctions, then add research only where it helps explain the next action. Industry and location provide context; they do not automatically establish buying intent, language or budget.
Decide whether founder identity is essential
If the use case specifically depends on the founder relationship, confirm it from suitable company or profile evidence. If the real requirement is executive responsibility for a problem, define that role instead of using founder status as a proxy.
| Title or status | Useful hypothesis | What needs confirmation |
|---|---|---|
| Founder or Co-Founder | The person helped establish the company | Current involvement and relevance to the task |
| CEO | The person holds an executive leadership role | Whether they are a founder and own the relevant decision |
| Owner or Principal | The person may have ownership or leadership responsibility | The actual business model and meaning of the title |
| Managing Partner | The person may lead a partnership or practice | Founder identity, organisational scope and the work they own |
The founder email search and founder audience are starting points for discovery. Review the full returned title and account context instead of accepting every adjacent executive title as a founder.
Specify the industry and business model
Name the activity your offer serves. “Technology” can include software vendors, consultancies and other different companies. A business serving healthcare clients is not automatically a healthcare provider, and a founder selling to banks is not necessarily running a bank.
- Record the target company's own activity.
- Separate its customer market when that affects the offer.
- Define essential product or service characteristics.
- Keep relevant company scale as context rather than proof of spending power.
- Write exclusions that prevent obvious account mismatches.
Use the ICP framework to make these choices explicit. A clear account definition helps the next operator interpret the list and the message.
Choose which geography the campaign actually needs
| Location concept | Useful when | Check |
|---|---|---|
| Company location | The account must be based in a market you serve | Whether the field represents the location relevant to your brief |
| Person location | The contact's working location matters | Whether it matches the campaign territory and current evidence |
| Operating market | The company serves customers in a particular region | External business evidence; headquarters may be elsewhere |
| Communication context | Language, time zone or channel requirements affect execution | Appropriate evidence rather than country-based assumptions |
DievioYour next customer starts here.
Find decision-makers by role, company and location. Build your next prospect list in Dievio.
Find my leadsFree audience preview · No credit card
Build the segment in a reviewable sequence
- Write the brief. State the activity, geography, founder requirement and problem being addressed.
- Select supported criteria. Use relevant industry, location, employee size and title variants. Company website/domain criteria can help when you already have accounts.
- Add necessary stored context. Revenue or funding dates can refine a justified hypothesis; they do not establish current budget or round stage.
- Preview coverage. Free Dievio previews count matching contact records, not distinct founder-led companies or total market size.
- Retrieve a bounded set. Confirm accounts, founder identity, current responsibility and required field availability.
- Record the accepted segment. Keep the definition, review date, source and unresolved cases together.
Start in contact search. Use the filter selection guide to choose useful criteria and the diagnostic workflow when a result is unexpectedly narrow.
Add dated research without turning it into intent
Funding announcements, hiring plans, product launches and installed technologies can help you investigate fit. Keep the actual source, date and relevant observation; do not automatically label the company “ready to buy”.
Dievio does not provide native funding-stage, technology-stack, hiring-growth or intent filters. Stored funding dates are a different capability. Company age and maturity should also be researched when needed rather than assumed from a title or funding label.
If you already have a founder's LinkedIn profile URL, profile lookup can return available matching contact fields. It does not supply a guaranteed current role, fresh mailbox verification or every research signal mentioned above.
Prepare a segmented, traceable handoff
- Preserve the person's identity, full title, company and relevant source URL.
- Keep industry and location interpretations explicit.
- Record the evidence supporting founder identity and current responsibility.
- Retain contact-field gaps and any separate validation provenance.
- Map columns to the CRM's actual schema; keep useful URLs rather than discarding them as unstructured text.
- Apply duplicates, ownership, preferences and campaign exclusions before activation.
- Assign an owner and a relevant next action for each approved cohort.
Keep messages differentiated where the business problem or communication requirements differ. A geography label alone is not a reason to stereotype a founder's budget, language or priorities.
Review account fit, correct founder identification, missing fields and qualified conversations by cohort. Avoid promising a fixed response lift from segmentation. For client delivery, the agency workflow adds the separate approval and handoff requirements.
