Freelancer or agency: choose an owner for your store build

Choose a freelancer or agency by the ownership the project needs, not by assuming one category is inherently better. A capable individual may suit a focused build; a coordinated team may suit a broader project. Either can fail when scope and handover are unclear.

Compare named people, responsibilities and deliverables. The size of the supplier is not a substitute for an accountable plan.

Define the work before seeking quotes

List the pages, product-entry scope, integrations, content responsibilities and acceptance tests. Identify what already exists and what must be created.

Do not ask for “an ecommerce website” and expect comparable proposals. One supplier may include photography and copy while another includes only configuration.

Keep optional ideas separate. This lets both suppliers price the same essential project before discussing additional work.

Ask who does each part

For an agency, identify the person responsible for design, implementation and communication. For a freelancer, ask which tasks they perform directly and which depend on another specialist.

Subcontracting is not automatically a problem. Unclear responsibility is.

You should know who decides priorities, who answers technical questions and who fixes a defect discovered during acceptance.

Compare the communication model

Agree how questions, feedback and changes are recorded. A single shared decision log can prevent contradictory instructions, regardless of supplier size.

Ask what happens when the main contact is unavailable. An agency may have backup capacity; a freelancer may have a planned absence arrangement. Verify rather than assume.

Do not judge only by response speed during sales. Discuss the expected cadence during the build and after launch.

Review relevant work carefully

Look for examples resembling your catalogue and buying task. A visually impressive portfolio does not prove experience with your options, delivery rules or order handling.

Ask the supplier to explain their role in an example and the constraints they solved. Do not request private client data or credentials.

Use the discussion to understand their method, not to demand a free redesign of your entire store.

Make changes and defects distinct

A defect is a failure to meet the agreed requirement. A change introduces a new or revised requirement. Define the process for both.

This distinction protects the project from endless ambiguity. It also prevents an essential missing function from being dismissed as an optional enhancement.

Record how additional work is estimated and approved before it begins. Avoid relying on informal assurances that everything will be included.

Specify business-controlled ownership

The business should control the domain, relevant service accounts and final access. The supplier may need temporary permissions, but the handover should not depend on their private login.

List the files, configuration notes and training included. Ask which licences can be transferred and which subscriptions remain separate.

Do not interpret delivery of screenshots as delivery of an editable, maintainable store.

Check what acceptance releases

Ask which payment milestone follows the final check and what evidence marks completion. Keep unresolved defects in a written list with an owner and next action. Do not confuse a launched domain with acceptance of every contracted function, especially when a remaining issue affects orders.

Plan the period after launch

Ask who handles faults, updates and new requests once the build is accepted. Compare the scope and cost of any maintenance agreement.

A freelancer may offer a clear ongoing service; an agency may not include one. Evaluate the contract rather than the organisational label.

Keep a practical escalation route for urgent store problems, especially if custom code or integrations are part of the proposal.

Choose with the same acceptance case

Require both proposals to explain how they will prove the main buyer journey and merchant record. Include mobile use, an unavailable state and the agreed delivery behaviour.

Then compare total scope, accountable ownership and recurring responsibilities. The cheapest proposal may simply leave more work with you; the largest team may introduce coordination you do not need.

Select the arrangement that can deliver the defined result and leave the business able to operate it. A good supplier choice ends with clear ownership, not dependence on the supplier's size or sales confidence.