Start with the business problem
CRO should improve the percentage of suitable visitors who complete a meaningful action. It is not simply redesigning buttons or making a page look cleaner. The agency needs evidence about where users struggle and a method for deciding what to change first.
A low-traffic business may not have enough volume for statistically useful A/B testing. CRO can still mean fixing obvious friction, clarifying the offer, improving forms and strengthening trust based on behavioural evidence.
Compare proposals on the same questions
| Compare | Ask before signing |
|---|---|
| Research | Does the agency use analytics, recordings, heatmaps or user feedback? |
| Tracking | Are important conversions measured reliably before testing? |
| Prioritisation | How are hypotheses ranked by evidence, impact and effort? |
| Implementation | Who makes design or development changes? |
| Testing | When is A/B testing appropriate versus a direct fix? |
| Learning | How are wins, losses and inconclusive results documented? |
Ask who is responsible for implementation
Ask the provider to separate measurement fixes, usability issues and true experiments. Every proposed change should have a reason, an expected behavioural effect and a way to check whether it helped.
Do not assume a strategy, audit or setup line automatically includes every practical change needed to make it live. Put dependencies and internal responsibilities into the proposal.
Agree how success will be measured
The headline conversion rate should be interpreted alongside lead quality, revenue or booking value where possible. More submissions are not automatically a win if they are worse prospects.
Decide the reporting model before delivery so both sides know which numbers are useful and which are merely diagnostic.
Protect ownership and handover
Keep appropriate business ownership of platforms, data and core accounts. Document administrator access, exports and what happens if the supplier relationship ends.
Ask for proof that matches the work
Ask for an example hypothesis backlog showing the evidence, proposed change, priority and metric for each item.
Where client information is confidential, a supplier can still demonstrate process quality through redacted documents, owned properties or implementation evidence without inventing outcomes.
Watch for this red flag
How Kydos fits into the comparison
Kydos offers landing-page, analytics and heatmap-related services that can support conversion work. Heatmap setup is available as an add-on, while event tracking and dashboards are available through analytics.
Already comparing providers?
Use Kydos' published services as another benchmark before you sign.
View Kydos pricingFrequently asked questions
How should I compare conversion rate optimisation providers?
Use the same brief and compare deliverables, implementation responsibility, ownership, support, exclusions and the business outcome the work should improve.
Should I choose the cheapest provider?
Not automatically. Compare missing implementation, software, support and handover costs before deciding.
What should be agreed before work starts?
Agree the objective, responsibilities, access, approvals, deliverables, timeline, measurement and extra-charge triggers.
What is a warning sign?
The agency presents a long list of design opinions as a CRO audit without showing data, user evidence or a measurement plan.
What proof should I request?
Ask for an example hypothesis backlog showing the evidence, proposed change, priority and metric for each item.
How does Kydos fit?
Kydos offers landing-page, analytics and heatmap-related services that can support conversion work. Heatmap setup is available as an add-on, while event tracking and dashboards are available through analytics.