---
title: How to Choose an Ecommerce Agency Before Signing the Contract
description: Evaluate an ecommerce agency through proof scenarios, delivery team, QA, security, incidents, access ownership, support, transparent cost, references, and exit.
source: https://pingvera.com/blog/choose-ecommerce-agency.html
---
# How to Choose an Ecommerce Agency Before Signing the Contract

Choose an agency by how its delivery team understands critical workflows, manages uncertainty and releases, and supports production after launch—not by portfolio polish. A capable partner can explain boundaries, assumptions, risks, acceptance, incident handling, and handover.

Give shortlisted teams the same concise brief and representative scenarios. Meet the people expected to deliver the work, not only the sales lead and a hand-picked reference.

## At a glance

- map workflows and risk before issuing a request;
- give every candidate the same proof scenarios;
- reward clear assumptions and unknowns;
- meet delivery and operational leads;
- review release, QA, security, and incident practices;
- retain control of domain, accounts, code, and data;
- separate project acceptance from continuing support;
- agree export, documentation, and transition assistance.

## Prepare an evidence-based brief

Include:

- business and product model;
- critical customer and staff journeys;
- systems and sources of truth;
- catalogue, order, and peak profile;
- markets, payment, tax, and fulfilment;
- staff roles;
- known constraints and legacy defects;
- security and privacy obligations;
- intended outcome and budget boundaries;
- fixed dates and dependent campaigns.

Do not hide difficult legacy behaviour. It will return later as delay and change cost.

## Score before presentations

Approve weights before meeting vendors, so persuasive delivery does not rewrite the criteria.

## Interview the operating model

Ask:

- How would you investigate a payment/order mismatch?
- What happens when ERP or fulfilment is unavailable?
- Who can authorise an emergency fix?
- Which checkout tests are mandatory?
- How is production access governed?
- How do you communicate an incident?
- What appears in a maintenance report?
- How is restore tested?
- What exactly do we receive at termination?
- Which risk in our brief appears underestimated?

Look for evidence-driven reasoning: verification, containment, named decision ownership, reconciliation, and follow-up—not memorised perfection.

## Check references properly

Speak to at least two comparable customers where possible. Ask who actually delivered, why cost and dates changed, how the team behaved during incidents, what post-launch support is like, whether reports and invoices are understandable, how accessible documentation is, and whether the client would choose them again.

One public logo is not proof of a current or representative relationship.

## Contract the operating realities

With legal and technical review, cover:

- deliverables and acceptance evidence;
- customer dependencies and roles;
- change and estimation process;
- severity, support hours, and escalation;
- security, data, and subcontractors;
- intellectual property and licences;
- domains, repositories, and cloud ownership;
- backup and restore responsibility;
- reporting and audit evidence;
- termination, export, and transition period.

## Warning signs

- fixed certainty before discovery;
- promises of “no downtime”;
- refusal to introduce the delivery team;
- production accounts owned solely by the agency;
- no release evidence or change log;
- support defined as “message your account manager”;
- no vulnerability process;
- handover dependent on goodwill;
- a rewrite proposed without a measurable reason.

## FAQ

### Should the lowest bid win?

Only if scope, assumptions, operating support, risk, and ownership are genuinely comparable. A lower number often represents a different proposition, not greater efficiency.

### Is paid discovery useful?

Often, for complex commerce, when it creates client-owned artefacts: workflow and dependency maps, risks, options, estimates, and a decision-ready plan.

### Can one agency build and maintain the store?

Yes. Define operations before launch, and ensure access, documentation, and transition remain under business control.

## Sources

- [UK NCSC: supply chain security guidance](https://www.ncsc.gov.uk/collection/supply-chain-security)
- [OWASP Software Assurance Maturity Model](https://owaspsamm.org/)
- [Google SRE: Managing Incidents](https://sre.google/sre-book/managing-incidents/)

Reviewed: **3 September 2026**.

Continue with [platform selection](https://pingvera.com/blog/choose-ecommerce-platform.html), the [maintenance onboarding checklist](https://pingvera.com/blog/website-maintenance-onboarding-checklist.html), and [agency handover](https://pingvera.com/blog/website-handover-between-agencies.html).

Pingvera can form part of independent monitoring and reporting requirements; partner quality still rests on people, operating process, and evidence.
