You send one Shopify Hydrogen brief to two agencies. Both propose a storefront, an editor for your marketers, app integrations, migration work, and launch support.
One quotes $24,000. The other quotes $32,000.
The gap looks like $8,000. Read line by line, the two proposals give your team different amounts of work. They also promise different things after launch.
This worked comparison follows one fictional merchant, Morrow Home, from the brief through both proposals, a reconciled scope, and a decision.
All businesses, proposals, fees, and timelines in this example are fictional. They are not actual agency quotes, Weaverse service prices, or market benchmarks. Shopify, Weaverse, and third-party subscriptions are excluded from both agency fees.
For the wider cost picture, see our Shopify headless pricing guide.
The brief both agencies received
Morrow Home is a fictional homeware brand on Shopify, with 180 products and 24 collections. Its team is an ecommerce manager, two marketers, and a freelance content coordinator for the migration. It has no developer of its own.
Campaign layouts currently wait on a developer. Morrow wants marketing to assemble pages in Weaverse, using sections built to its approved designs.
Both agencies receive the same designs, URL inventory, and app list. Morrow keeps its Shopify backend and checkout: US-only, English, USD, with no rebrand.
| Area | Requirement |
|---|---|
| Templates | Nine: homepage, collection, product, search, cart, campaign landing page, standard content page, blog index, and blog article |
| Shared elements | Header, footer, navigation, announcement bar, and 404 page |
| Custom sections | Shop by room, a material comparison table, and a product storytelling section |
| Content | Rebuild 12 landing pages currently assembled from Liquid sections; render 40 existing Shopify blog articles through the new template |
| Search | Product search with product type, price, and availability filters |
| Purchase journey | Product and variant selection, cart updates, existing discount behavior, and checkout handoff |
| Customer accounts | Configure and test access to Shopify-hosted customer account pages |
| Integrations | Klaviyo signup, the existing reviews provider, GA4, and consent handling |
| SEO migration | Review URLs, preserve agreed paths, map changed URLs, and check metadata and canonicals |
| Editing | Marketing edits content and layout in Weaverse within the agreed sections |
| Post-launch | A technical point of contact for the first 90 days |
Subscriptions, loyalty, B2B, additional languages, ERP work, and custom checkout development are excluded. Morrow supplies final copy and photography.
For this example, both agencies have confirmed the existing reviews provider supports the required Hydrogen display and submission flows.
“Weaverse included” leaves an important question open: which settings can marketing change? Developers define those controls through Weaverse’s custom component schemas.
Proposal A: $24,000, with merchant-led content migration
Agency A starts from a Hydrogen theme and adapts it to the approved designs. These themes are storefront codebases that developers customize and integrate.
A estimates eight weeks once the required designs, access, and content are ready.
| Proposal A wording | What it means for Morrow |
|---|---|
| “Implement nine templates and three custom sections using a Hydrogen theme with Weaverse integration.” | Matches the template and section counts, but does not specify which theme components are reused or which controls marketing gets. |
| “Build two sample landing pages and train the merchant team.” | Morrow assembles the other ten. |
| “Connect existing Shopify blog content to the article template.” | The content appendix assigns checks across all 40 articles to Morrow, including images, links, and layout. |
| “Integrate Klaviyo, reviews, and GA4.” | The integration appendix covers the signup form, review display, and selected storefront events. Review submission and purchase-event validation are excluded. |
| “Implement redirects from a merchant-supplied mapping file.” | Morrow audits the URLs and decides the redirects. The agency implements and tests the supplied rules. |
| “Complete storefront QA and launch support.” | The QA appendix covers core storefront functions and explicitly excludes migrated-content checks and end-to-end analytics validation. |
| “Hand over source code and provide training.” | Deployment instructions, environment configuration, and a rollback procedure are not specified. Morrow asks whether they are included. |
| “Provide a 30-day defect warranty.” | Covers defects against the accepted scope. The requested 90-day support arrangement is absent. |
The coordinator can assemble pages. Morrow still needs someone to approve content, check mobile layouts, and settle URL questions. That work belongs in the launch plan, even though it never appears on A's invoice. A's eight weeks also assume Morrow finishes its tasks on time.
Proposal B: $32,000, including migration and 90 days of support
Agency B also starts from a Hydrogen theme.
B splits its fee into $29,000 for implementation and $3,000 for 90 days of support. It estimates ten weeks. The same conditions on access, content, and approvals apply.
Both proposals cover the same templates, sections, search, purchase journey, account access, and consent implementation. B also takes on Morrow’s content and redirect work.
| Proposal B wording | What it means for Morrow |
|---|---|
| “Rebuild all 12 landing pages using merchant-supplied content.” | The agency assembles and checks the pages. Morrow supplies assets and approves the result. Copywriting is excluded. |
| “Retain 40 Shopify blog articles and validate their presentation.” | The articles remain in Shopify. The agency checks rendering, images, links, and URLs. |
| “Implement review display and the agreed review-submission flow.” | Includes loading, empty, and error states. |
| “Implement and validate the agreed GA4 event map.” | Testing runs through purchase, including consent behavior and duplicate events. The agency owns validation across the storefront and the agreed checkout tracking setup. |
| “Prepare the redirect map and run pre-launch and post-launch checks.” | Morrow approves URL decisions; the agency prepares, implements, and tests the mapping. |
| “Complete QA across functionality, content, redirects, and analytics.” | Includes the checks assigned to Morrow or excluded in A’s proposal. |
| “Hand over source code, training, and operating documentation.” | Explicitly covers deployment, environment configuration, and rollback. |
| “Provide 90 days of support, capped at ten hours per month.” | Includes an initial response to critical incidents within four business hours on weekdays, in an agreed time zone. Unused hours expire monthly. |
A four-hour response is not a four-hour fix. Work beyond the monthly allowance requires Morrow’s approval.
B’s 30-day defect warranty is separate: warranty fixes do not consume support hours.
The event map names sources, destinations, and validation methods. Shopify’s analytics and consent guidance covers storefront implementation; B must also document and test the agreed checkout tracking.
What Morrow’s marketers need to edit
Morrow asks both agencies to commit to these editing controls. They are project deliverables, not features assumed to exist in every Hydrogen theme.
| Component | Agency deliverable | Merchant editing controls |
|---|---|---|
| Campaign hero | Component configured for the approved design | Heading, desktop and mobile images, CTA text, link, and agreed alignment options |
| Shop-by-room section | Custom component with defined collection references and display rules | Room images, labels, linked collections, and item order |
| Material comparison table | Custom component supporting up to four columns | Column labels, cell content, and row order |
| Product storytelling section | Custom component with approved layout variants | Images, copy, CTA, and available layout choices |
| Campaign landing page | Template and supported section library | Add, remove, and reorder the configured sections |
Prices and inventory stay in Shopify. Replacing a room image is an editing task. Adding an interactive room planner requires new development.
The handover ends with a test. A marketer builds a campaign page alone: they replace the hero, add a material table, reorder sections, and check mobile layouts. If a promised edit still needs a developer, the agency fixes it.
Putting both proposals on the same scope
Morrow cannot absorb A’s assigned content and migration work. It asks both agencies to quote this scope:
| Workstream | Proposal A initially | Proposal B initially | Agreed comparison scope |
|---|---|---|---|
| Storefront | Nine templates, three custom sections | Same | Same approved designs and behavior, with documented editing controls |
| Landing pages | Agency builds two; merchant builds ten | Agency builds all 12 | Agency builds all 12 |
| Blog content | Merchant checks articles | Agency checks all 40 | Agency checks all 40 |
| Reviews | Display only | Display and submission | Display and the agreed submission flow |
| Analytics | Selected storefront events | Event map through purchase | One shared event map and validation checklist |
| SEO migration | Merchant supplies redirect map | Agency prepares and validates it | Agency performs the work; merchant approves decisions |
| QA | Core functionality | Functionality, content, redirects, and analytics | One acceptance checklist |
| Post-launch | 30-day warranty | Warranty plus 90-day support | 30-day warranty plus 90-day support, on equivalent terms |
| Handover | Code and training; operating documentation unspecified | Code, training, and operating documentation | One explicit handover inventory |
The acceptance checklist uses a shared browser and device matrix. Scenarios include an out-of-stock product, empty search results, failed review loading, cart updates, and a test purchase. The checklist also covers keyboard navigation and performance checks on the homepage, a collection page, and a product page, using an agreed device, network profile, and acceptance threshold.
The migration scope names which URLs to check, what each should do, and who approves exceptions. Our Shopify Hydrogen migration checklist covers these dependencies in more detail.
Morrow also requires the repository to sit in its GitHub organization and retains control of the service accounts. The agreement documents rights to project-specific code and assets, while the handover inventory lists the third-party theme and library licenses that continue to apply.
What happens to the $8,000 difference?
Morrow sends the reconciled scope to both agencies.
B confirms that its $32,000 covers the agreed scope. A confirms that operating documentation was not included in its original fee and submits a revision covering that work and the other additions.
| Addition to Proposal A | Illustrative fee |
|---|---|
| Assemble the remaining ten landing pages and check 40 blog articles | $2,000 |
| Audit URLs, prepare the redirect map, and validate redirects | $1,000 |
| Complete review submission and the agreed analytics scope | $1,500 |
| Add the remaining QA and handover documentation | $500 |
| Provide 90-day support on equivalent terms | $3,000 |
| Total additions | $8,000 |
A now totals $32,000: $29,000 for implementation and $3,000 for support. Its estimate moves from eight weeks to ten.
The totals happen to converge here. Real proposals can remain far apart after reconciliation.
Morrow could still take A’s original $24,000 scope, provided it assigns the remaining work internally and arranges technical coverage after launch. The lower agency fee would come with more responsibilities for its own team.
When does a request become extra work?
Morrow tests the agreement with two examples. Letting shoppers select products and generate a comparison adds interactions and data requirements to the manually populated table. Both agencies would quote it separately.
Uneditable column labels are different: editable labels were promised, so the agency must complete that work. Morrow records these distinctions alongside other cases:
| Situation | Treatment |
|---|---|
| One of the 12 landing pages is missing | Complete the contracted deliverable |
| Purchase events duplicate because of an implementation defect in the agreed tracking flow | Correct under the applicable delivery or warranty terms |
| Morrow asks the agency to populate a thirteenth landing page | Quote the additional content work |
| Morrow adds a French-language storefront | Scope a change covering implementation, content, and QA |
Neither agency starts additional work until Morrow’s designated approver accepts the price and any change to the launch date.
Everything this review found missing from A's proposal is now in its revised scope, with a price and an owner.
Which proposal does Morrow choose?
B keeps its build lead on the account for 90 days. A hands over to a separate support team. Morrow chooses B. It has no developer of its own, and its ecommerce manager wants someone who already knows the build.
A merchant with its own technical team and available content staff might reasonably choose A’s original scope and keep more of the work in-house.
The reconciled scope becomes part of the agreement. Marketing can change campaign images, copy, and section order using the tested controls. An interactive product comparison would need a separate estimate.
What should your team be able to edit after launch?
Start with a campaign page your team builds regularly. List the images, copy, collections, and section arrangements marketing needs to change. Identify which changes still need a developer.
Book a Weaverse demo to explore how those editing needs could work in a Hydrogen storefront. Bring your brief and a sample page to make the conversation specific.



