Key points
- Identify a real recurring task and the client's capacity to use the output
- Compare total commitments and accepted deliverables over the same period
- Offer a documented scope without guaranteed savings, volume or results
Offer recurring lead-list work when the client has a repeatable task the agency can support. A second purchase or a question about freshness is a reason for a conversation, not proof that a retainer is the right next step.
Compare the proposed service with the client's actual needs, current spending and capacity to use the output. An upsell should solve an observed problem rather than create an unused monthly allocation.
Look for a recurring task, not a maturity label
Investigate whether the client repeatedly needs new contacts, company research, role checks, audience revisions or destination preparation. Those tasks can justify different service scopes.
- What work recurs, and how often is it actually needed?
- Has the client activated the prior accepted cohort?
- Which part of production or follow-up is constrained?
- Does the client need additional volume or better use of existing records?
- What evidence would establish that a recurring service helps?
- Who owns the budget and the decision?
Some clients are well served by occasional projects. Do not treat them as immature or require a fixed transactional-to-pilot-to-retainer progression.
Build a like-for-like comparison
Show current and proposed total commitments over the same period. Distinguish delivered contacts, accepted contacts, research scope, checking, support and destination work. State any required change in client operating capacity.
If comparing unit costs, use the same acceptance definition and realistic used output. A larger promised allocation can have a low nominal cost per record while leaving the client paying for unused work.
The pricing models guide separates the payment unit, cost scope and service responsibilities.
Offer components that match the problem
- New-contact cycles
- A bounded supply of previously undelivered relevant people under an agreed identity rule.
- Research or checking cycles
- Specific company, role or field investigations with documented evidence and limits.
- Audience maintenance
- Approved brief revisions and controlled source-coverage tests when the client's needs change.
- Destination support
- Mapping, versioning and exception handling for the client's actual workflow.
Do not promise native intent signals, technology-stack filtering or independently verified phone data as automatic Dievio upgrades. Confirm the separate source, work, rights and cost when a proposed component requires them.
Use evidence in the expansion conversation
Bring the purchase history, accepted output, actual operating work and unresolved problems. Ask whether a defined recurring scope would be useful.
A factual opening could be: “Your last two projects required the same role research and destination map. Would a scheduled version of that work help, or do you expect the need to remain occasional?”
Use this only when the history supports it. Do not claim the retainer eliminates all wasted representative time or that one campaign's pipeline will repeat every month.
Respond to objections as operating questions
- “We do not need that volume.” Check consumption and consider a smaller scope or continued project work.
- “The total cost is too high.” Review the proposed work and alternatives without disguising a larger annual commitment as savings.
- “We cannot commit yet.” Discuss a bounded test if useful and actually available; state its real cost and terms.
- “We already hold these contacts.” Identify whether the task is new discovery, review or retained-file reuse.
- “We need results, not files.” Clarify which outcomes the agency controls and how later campaign events would be measured.
A meaningful response may be to leave the current arrangement in place. Do not counter every objection with a larger allocation or a free pilot the agency has not approved.
Make the recurring commitment executable
- Approve the audience and purpose of each cycle.
- Define required fields, acceptance and correction treatment.
- Confirm source rights and the permitted client use.
- Model actual source, research, review and support costs.
- Set delivery frequency from both teams' capacity.
- Document the destination, review owner and release process.
- State change, renewal and cancellation terms exactly as agreed.
Do not invent a universal thirty-day cancellation right, annual discount, rollover allowance or “unlimited” entitlement. The written offer should match the service the agency can honor.
Keep Dievio operations and agency services distinct
Dievio's free preview counts matching contact records, not unique companies, net-new output after your private exclusions or verified quality. Search retrieval uses one credit per returned lead; empty results use none and repeated retrieval can charge again.
Saved-list downloads are free and do not refresh records. API credits are separate from workspace search credits. Your application owns schedules, CRM delivery, client reports and added research or checking.
The recurring workflow records these responsibilities. Repeated retrieval is not proof that an existing record's role or mailbox was newly checked.
Measure fit after the change
Track accepted delivery, client activation, unresolved exceptions, production effort and use of the agreed components. Keep campaign replies, meetings and opportunities under separate definitions and comparable observation windows.
A high satisfaction response is not automatically NPS. Bain's NPS method subtracts the percentage of detractors from the percentage of promoters; an individual nine-out-of-ten response is not that aggregate score. Use the actual method when reporting a named metric, or label ordinary feedback as feedback.
There is no universal retention or expansion target for every agency. Investigate unused output, delayed decisions and open issues before treating them as certain churn signals.
Use the client reporting guide to review the service. Propose expansion only when the next scoped task is useful, feasible and supported by the evidence.



