Freelancer or Agency? Compare Delivery Risk Before the Quote

Give every candidate the same brief: user journeys, required integrations, content responsibility, launch constraints and support expectations. Ask each to identify assumptions and exclusions. A cheaper proposal may omit migration, testing or content entry rather than reflect a more efficient delivery model.

Separate essential launch work from a later phase. For an illustrative booking website, the essentials might be service selection, availability, confirmation and staff access. Loyalty schemes and advanced reporting could be evaluated separately. Use your actual operating needs to decide the boundary.

An independent specialist can suit a tightly scoped technical job when your team can make prompt decisions. A staffed agency may suit simultaneous design, content and engineering work when those roles are genuinely included in the proposal. Neither business label guarantees quality or continuity.

Ask who will perform the work, who reviews it, and who can cover absence. If subcontractors are involved, establish their access and responsibilities. Request a relevant walkthrough in which the proposed developer explains a decision and a limitation, rather than relying only on attractive portfolio screenshots.

Use one row per deliverable and one column per supplier. Record included work, acceptance evidence, named owner, dependencies and extra charges. Add separate rows for hosting, recurring licenses, payment provider setup, accessibility checks, migration, training and support.

For each unclear item, write a question instead of guessing a price. For example: does product import include image cleanup and variant mapping, and who corrects bad source records? A quote cannot be compared fairly until those assumptions are aligned. Obtain current written proposals rather than treating an online rate range as a market fact.

A useful milestone describes something you can inspect: a reviewed prototype, a staging workflow using agreed sample data, or a release candidate passing the acceptance checklist. Specify what happens when feedback changes the original scope. Payment timing and amounts should follow the agreement with the supplier.

Keep domain, hosting and payment accounts under business ownership. Give role-based access, retain recovery methods and document how to revoke access at handover. Decide where source code lives and which licenses or third-party components restrict reuse.

Ask a staff member to perform a normal content update using the supplied instructions. Verify that deployment and backup recovery have an owner. Record support hours, response expectations, exclusions and the process for reporting a defect.

Use a short final decision note: why this supplier fits the work, which risks remain, and how those risks are covered. If neither proposal explains delivery or ownership clearly, clarify the brief before committing. A confident sales presentation is not evidence that the operating details have been resolved.