Two website proposals can promise the same launch and still describe very different projects. One may include content migration, test evidence, and a documented handover. Another may cover only theme setup. Comparing totals without comparing responsibilities can make the lower number look clearer than it really is.
This guide is for businesses evaluating WordPress or Shopify work. It does not assume that one platform is universally better. It helps identify what each proposal includes, which risks remain with the business, and what evidence should exist before the work is accepted.
Start with the business outcome
Before comparing platforms, restate the outcome the project should support. Is the priority publishing flexibility, faster merchandising, a catalogue migration, improved checkout reliability, multilingual content, lead generation, or easier day-to-day administration?
A proposal should connect its technical approach to that outcome. A long feature list is not a substitute for explaining how the proposed work changes the current situation.
Normalize the scope before comparing price
Put every proposal into the same comparison structure. If an item is missing, label it not stated instead of assuming it is included.
- Discovery and requirements
- Information architecture and page templates
- Theme design or customization
- Content and product migration
- Forms, search, filters, checkout, and integrations
- Analytics and consent configuration
- Accessibility, responsive, browser, and performance checks
- Redirects, metadata, canonicals, and launch SEO controls
- Training, documentation, deployment, and post-launch support
This makes exclusions visible. A proposal that omits migration, copy preparation, product-data cleanup, paid extensions, or launch support may still be valid, but its price should not be compared as though those responsibilities disappeared.
For WordPress, examine the maintenance model
WordPress gives teams broad control over hosting, themes, plugins, content structures, and custom development. That flexibility also means the proposal should explain who owns ongoing updates, backups, compatibility checks, security monitoring, and recovery.
WordPress documentation recommends keeping WordPress, plugins, themes, and the server environment current. It also advises creating a current backup before plugin or platform updates. A credible proposal should describe the maintenance boundary rather than treating launch as the end of technical responsibility.
- Which hosting environment is assumed, and who administers it?
- Which plugins are required, who licenses them, and what renews annually?
- Is custom functionality isolated from theme updates?
- What backup and restore process will be tested?
- Who checks compatibility before production updates?
For Shopify, examine access and ownership
Shopify projects have a different operating model. The platform manages much of the underlying commerce infrastructure, while the project may involve theme customization, product and collection setup, app configuration, data migration, and integrations.
Shopify recommends collaborator access for professionals working on an existing merchant store, allowing the merchant to control which areas are available. Shopify also provides client transfer stores for new builds. A proposal should use an appropriate access path and should never require the merchant to share a personal password.
- Will the work happen through collaborator access or a client transfer store?
- Who owns the store, domain, theme license, apps, and third-party accounts?
- Which apps are essential, and what are their recurring charges?
- How will products, customers, redirects, and tracking data be migrated or preserved?
- What must the merchant configure directly, such as payments, tax, shipping, or policies?
Separate build cost from operating cost
Ask for a simple first-year and ongoing-cost view. It should identify the professional fee separately from hosting or platform plans, premium themes, plugins or apps, transaction-related services, email tools, monitoring, maintenance, and support.
Do not assume every recurring tool is unnecessary, but require a reason for each one. The proposal should explain what business capability it provides, what happens if it is removed, and who controls the subscription.
Look for a safe access plan
Access should be role-based, limited to the work, and revocable. The business should retain ownership of its domain, hosting or store, analytics, payment accounts, repositories, and primary administrative identity.
Ask how credentials and sensitive exports will be handled, when temporary access will be removed, and which accounts will remain after handover. Avoid arrangements in which a site depends permanently on a professional's personal account.
Require a migration and redirect inventory
If an existing site or store is being replaced, “migration included” is too broad. The proposal should specify the content types, product fields, media, customer or order data, URLs, metadata, and integrations in scope.
It should also identify what cannot be migrated automatically, how exceptions will be reviewed, and how old URLs will map to the new structure. A redirect list, representative data checks, and post-launch crawl are clearer acceptance evidence than a general promise to preserve SEO.
Compare testing as evidence, not adjectives
Words such as robust, optimized, responsive, and secure are difficult to accept without defined checks. Ask each proposer to name the environments, journeys, devices, and evidence included.
- Representative mobile and desktop journeys
- Forms, search, account, cart, checkout, and notification behavior
- Empty, error, loading, and recovery states
- Content and product samples after migration
- Analytics and conversion-event validation
- Canonical, robots, sitemap, and redirect checks
- Backup or rollback readiness for launch
No responsible proposal can guarantee that software will contain no defects. It can define what will be tested, how issues will be prioritized, and what support applies after release.
Clarify change control before work begins
Good proposals explain how new requests are assessed. They distinguish a correction from a scope change, show who may approve extra work, and state how timing or price changes will be documented.
This protects both parties. The business can make informed trade-offs, while the professional is not expected to absorb unlimited additions inside a fixed estimate.
Define a usable handover
A handover should leave the business able to operate the result. Depending on the project, it may include administrator access, source files, repository access, theme or plugin documentation, an extension inventory, license ownership, deployment notes, training, analytics verification, and a list of known limitations.
Ask what access will be removed after acceptance and what support remains available. If maintenance is a separate service, it should have its own scope, response expectations, and price.
A practical proposal scorecard
- Outcome fit: Does the approach address the stated business need?
- Scope clarity: Are deliverables, exclusions, and responsibilities explicit?
- Platform fit: Does the operating model suit the team?
- Ownership: Will the business control its accounts, data, licenses, and assets?
- Risk handling: Are migration, access, dependencies, and unknowns visible?
- Acceptance evidence: Are testing and completion checks observable?
- Total responsibility: Are recurring costs and maintenance duties clear?
- Handover: Can the business operate the result after launch?
Useful primary references
- WordPress.org: Site Health and ongoing maintenance
- WordPress.org: managing and updating plugins
- Shopify Help Center: working on client stores
- Shopify Help Center: building stores for clients
Make the final comparison explicit
Before approving a proposal, write a one-page decision note: the chosen outcome, included scope, business responsibilities, recurring costs, major assumptions, acceptance checks, and handover owner. If those items cannot be stated clearly, the proposal probably needs clarification before work starts.
Businesses can use NerdVine's guidance for working with independent professionals when preparing a project for review.