Key points
- Use supported stored revenue criteria to define the target account segment.
- Check the recency and limits of revenue data alongside company fit.
- Review current CEO responsibility and contact fields before outreach.
Use company revenue to define an account-size hypothesis, then confirm whether the CEO is the right person for the proposed conversation. Revenue does not independently establish budget, founder status, procurement structure or the executive's preferred message.
Dievio supports stored company revenue bands. Combine them with relevant account and role criteria, and review the resulting records instead of assigning a fixed buyer profile to every revenue tier.
Choose a revenue band for a specific reason
Explain how account scale relates to the product or service. It may affect implementation needs, the economics of serving an account or the operating context. That relationship should come from evidence about the use case, not a claim that one band always buys faster.
The current Dievio filter offers bands from $0–$1M through $10B+, including $10M–$50M, $50M–$100M and $100M–$500M. Choose the available bands that suit the hypothesis and inspect the accounts returned.
| Question | Why it matters |
|---|---|
| Which company unit does the figure describe? | A parent group, subsidiary and operating business can differ |
| Is it an estimate, disclosed figure or stored range? | The precision and evidence are not interchangeable |
| Which period and currency are supported by the source? | A historical or differently defined figure may not answer today's question |
| Is the actual requirement revenue, ARR, valuation or budget? | Those measures describe different things |
When an exact threshold is essential, check suitable company disclosures or other appropriate evidence. A stored band is a search aid, not an audited current financial statement or a guarantee that a specific amount is available to spend.
Separate CEO identity from adjacent executive roles
Search relevant CEO variants and inspect the complete title. Founder, Owner, President and Managing Director may be relevant for some use cases, but they are not universally equivalent to CEO.
- Confirm the intended company, including subsidiary or parent scope.
- Check the person's current role evidence.
- Distinguish founder identity from executive responsibility.
- Identify whether the proposed task belongs to the CEO or another function.
- Include additional stakeholders only when their part in the evaluation is understood.
The CEO and founder search playbook develops that identity and role review.
Build a revenue-segmented search
- Define account fit. Record the activity, geography, scale requirement and exclusions.
- Select stored revenue bands. Use the supported options and retain the interpretation behind the choice.
- Add relevant role criteria. Start with CEO responsibility; keep adjacent titles distinguishable.
- Preview coverage. A free count preview shows matching contact records without full contact details.
- Retrieve a bounded set. Review actual companies, full titles and available contact fields.
- Research material uncertainties. Resolve exact financial thresholds, company-unit conflicts or unclear responsibilities before relying on them.
- Approve the handoff. Apply identity, ownership, preferences and campaign requirements.
Begin with CEO contact search. A preview does not count unique companies, confirm current revenue or establish email reachability.
Add other context without inventing native filters
Stored funding dates can support a separate hypothesis. They do not provide a native funding-stage, ownership-type, current hiring or intent filter. Research those facts externally when they are essential.
Employee size is another useful scale dimension, but it is not a substitute for revenue and does not have a universal mapping to it. Keep each criterion tied to the audience requirement.
If the result is unexpectedly narrow, inspect the effective query and title interpretation. Do not remove an essential condition solely to increase the total, or assume a different order of identical AND filters changes the final set.
Use the same evidence standard for contact review
The evidence required should follow the task and consequence of error, not an unsupported revenue-tier rule. A company domain's mail routing does not prove a named CEO's mailbox, and a naming pattern is not address-specific verification.
- Preserve the source and observation behind the person/company match.
- Separate available contact values from independent validation results.
- Keep uncertain or catch-all outcomes explicit.
- Check role or company conflicts instead of rejecting every new appointee automatically.
- Apply the campaign's exclusions and channel requirements before activation.
The data quality checklist covers those distinctions. Neither contact retrieval nor a separate validation result guarantees inbox placement.
Use segments to test a relevant business conversation
Different account scales may justify different implementation questions or buying-process research. Do not prescribe a message solely because a company falls above a particular revenue figure.
Track correct-account findings, relevant role matches, missing evidence and qualified conversations by cohort. Investigate audience and message differences before attributing an outcome to revenue segmentation itself.
For a repeated process, a custom API workflow can retrieve supported data. Your application owns the segment definition, review decisions and CRM handoff; repeated retrieval does not establish a fresh financial or mailbox verification.



