Shifter Order

extra-rebuild v1

SHIFTER ORDER: Website rebuild and migration (extra), bought with a Gear

Order number: the Gear Order's number, followed by "-R"
Order version: extra-rebuild v1
Shifter: Shifter Strategy FZ-LLC, UAE trade licence No. 17003064, hello@shifter.co
Client: the Client under the Gear Order bought at the same checkout

1. Agreement

1.1 This Order is made under the Shifter Terms and Conditions dated 25 October 2026 (§7, "Website rebuild"). It goes with the Gear Order (gear-no-call v1.4) bought at the same checkout, and takes effect with it (Gear Order 6.2). These parts of the Gear Order apply to this Order too:

As those rules and the Gear Order's 4.3 apply to this Order, "day 40" in them means the 10th business day after the item's date in clause 3, and the day-30 report means an email from Shifter by that day. A moved date never passes that day. If the input still hasn't arrived by then, the part that needs it counts as delivered on that day. The services in "When an item is outside either party's control" also include the Client's hosting, Vercel, Netlify, GitHub, GitLab and the domain registrar, and its sentence on written steps for the Client's developer doesn't apply to the staging site.

Decisions, answers and delays under this Order, including the go-live change in the Go-live row, don't count toward the Gear Order's 2.3 conditions (a) to (c). They affect the traffic guarantee only through the go-live day: the Go-live row, with its fallback, and 2.2.

If this Order ends under the Gear Order's 1.3 from the Gear's day 1, it ends on the day Shifter learns of it, and work not yet delivered stops. 2.1 doesn't apply to items due after that day. Before go-live, Shifter refunds this Order's fee in full within 2 business days after that day, unless it has already been refunded. After go-live, no refund is due, unless mandatory law requires more.

For what this Order covers, it controls over the Gear Order.

1.2 One rebuild at a time. Shifter runs one rebuild at a time. A rebuild is running from its payment until its go-live or until its Order ends. Queued rebuilds start in the order their payments succeeded. If a rebuild payment succeeds while another rebuild is running, Shifter says so within 1 business day after the payment. Within 5 business days of that email the Client chooses by email:

If the Client doesn't choose in time, Shifter refunds this Order's fee in full within 2 business days. Either way the Gear runs on. On a refund, this Order ends and the six-month minimum ends.

2. Fee, options, start and term

ItemSelection
FeeEither USD 8,000 once (rebuild USD 5,000 plus migration USD 3,000), or USD 5,000 once with the six-month option, which waives the migration fee. It's charged at checkout as one-time lines on the Gear subscription's first invoice. Any tax is shown at checkout, and a refund under this Order includes the tax charged on what it refunds. Platform, hosting, theme, plugin and domain fees are the Client's own third-party charges.
Six-month optionIf chosen at checkout, the Gear's minimum term is its first 6 billing periods: from the first charge to the day before the 7th monthly charge date under the Gear Order's Payment row. A billing period whose base fee isn't charged, or is refunded or credited, under the Gear Order's 2.2 or 2.3 still counts, and doesn't extend the minimum. Shifter's confirmation email records the minimum's end date. A stop email during the minimum ends the Gear subscription when the minimum ends (Terms §7; Gear Order 6.2 and Stopping row). If this Order's fee is refunded in full for any reason (1.1, 1.2, Before rebuild day 1, Long-stop, 2.1, "Parts that stay on the current platform" in clause 3, or the Gear Order's 6.2), or this Order ends before go-live, the six-month minimum ends that day. Shifter ends it in Stripe within 2 business days, and the Gear runs month to month from then.
PlatformOne of these, chosen by the Client in the access steps: WordPress, on the Client's own hosting; or a code site Shifter builds and deploys to the Client's own Vercel or Netlify account. Webflow and Framer aren't offered under this Order. A code site's repository is in the Client's own GitHub or GitLab account, with Shifter as a collaborator, and its forms send through a service in the Client's own account. Shifter's role on the host excludes domains, DNS and billing. From the day the rebuilt site serves the domain (Go-live row), Shifter's repository access is the CMS user under the Gear Order's 4.1, limited as in its 4.2.
Rebuild day 1The latest of the Gear's day 1, the business day after Shifter confirms by email that the rebuild access in clause 4 is all in, and, for a queued rebuild, its queue start under 1.2. Shifter sends that email within 2 business days after the last item in clause 4 arrives. The page-changes item is in once the Client sends its changes or says it has none. A website-only CMS user the Client gave under the Gear Order's 4.1 counts as the CMS user in clause 4. No item here is due before rebuild day 1.
Before rebuild day 1The Client may cancel this Order alone by email at any time before the later of rebuild day 1 and the third business day after the payment. Shifter then refunds this Order's fee in full within 2 business days, this Order ends, and the six-month minimum ends. If the Gear Order doesn't take effect, ends before the Gear's day 1, or ends by a cancel or refund under its Before day 1 row, its Places row or its 2.3 eligibility check, this Order ends with it, and its fee is refunded with the Gear (Gear Order 6.2).
Long-stopIf the rebuild access isn't all in within 20 business days after the Gear's day 1, Shifter emails to ask for it within 1 business day after that 20th business day. If it still isn't in 10 business days after that email, the Client may choose by email, within the next 5 business days, a refund of this Order's fee or 20 more business days. If the access is all in before the Client chooses, rebuild day 1 follows the Rebuild day 1 row and no refund is due under this row. Otherwise, if the Client chooses the refund, or doesn't choose within those 5 business days, or the access still isn't in at the end of the extra time, Shifter refunds this Order's fee in full within 2 business days after that choice, that 5th business day or the end of the extra time, this Order ends, and the six-month minimum ends.
If the Gear stopsIf the Gear subscription stops after the Gear's day 1, this Order still runs to the end of the fixes window. For this Order, "the service ends" in the Gear Order's 4.4 means the end of the fixes window, and Shifter keeps the access and material the rebuild needs until then. After the Gear's service ends, "the update" and "the next update" in the Gear Order rules this Order uses mean an email from Shifter to the approver within 2 business days after the move or event.

2.1 Agreed work, or the fee back

2.2 The traffic guarantee and the rebuild

This rebuild keeps the Client's domain and its GA4 property, and each hostname listed in the Gear's start email stays in scope. Under the Gear Order's 2.3, the rebuild counts as one of Shifter's own changes. If the traffic guarantee applies, its 90-day window then runs from the go-live day (clause 3), not from the Gear's day 1, and the baseline period doesn't change (Gear Order 2.3, "A rebuild bought from Shifter"). If the page list (clause 3) moves a hostname in scope to another hostname on the same domain with a 301, the page list names both. From go-live, both count as hostnames in scope for the window, and the baseline is recounted with both over the same 90 days. The go-live report, or, under the Go-live row's fallback, an email from Shifter within 1 business day after the go-live day, gives the recounted baseline with a GA4 export. If this Order ends, or its fee is refunded, before go-live, no hostname is added and the baseline isn't recounted. That recount, under this Order, is the only baseline change the rebuild makes. If this Order ends, or its fee is refunded, before go-live, or go-live hasn't happened by the Gear's day 90, the window stays days 1 to 90 and the other 2.3 dates stand. If the Client asks for a different domain or GA4 property, that's a change under the Gear Order's 2.1, and the traffic guarantee no longer applies.

2.3 No results promise

This Order doesn't promise rankings, traffic, leads, AI mentions or citations, or any change in AI answers. Page speed and accessibility scores depend on the platform, theme, plugins and content, and aren't promised.

3. Agreed work (the delivery check)

ItemDue and completion check
Page listBy rebuild day 10: the sitemap and page list, for the approver to agree within 2 business days. It has up to 15 pages, plus the Client's existing blog posts and articles, and the legal pages as they are. It names the hostnames the rebuilt site will serve. Across platforms with more than 150 posts, not counting the Gear's own articles and pages, it names the 150 that move: those with the most qualified sessions in the Gear's 2.3 baseline or, without one, the most recent. Each other existing page or post not on the list gets a 301 to the closest migrated page in the redirect map. The Gear's own articles and pages all move ("The Gear's own work while the rebuild runs"). If the approver asks for changes in that time, Shifter sends the changed list within 2 business days, and it stands. If the approver hasn't replied in that time, Shifter's list stands.
DesignBy the later of rebuild day 17 and 3 business days after the page list stands: one homepage design and one inner-page design, in the Client's existing brand, for the approver to approve within 3 business days. One round of changes: Shifter sends the changed designs within 3 business days, and they stand. If the approver hasn't replied in time, the designs stand.
Staging siteBy the later of rebuild day 30 and 8 business days after the designs stand: a staging site on the Client's chosen platform, with every page in the agreed list built to the agreed designs. Existing posts are migrated: at any count on the same platform (WordPress to WordPress), or up to 150 across platforms, with more by quote. Posts above 150 that the Client doesn't buy by quote are redirected under the page list. A redirect map goes with it, and the site is sent to the approver for acceptance.
AcceptanceThe approver accepts the staging site, or sends one written list of defects, within 5 business days after it's sent. A defect is a page that doesn't match the agreed list or designs, or doesn't work. Shifter fixes the listed defects within 5 business days and sends the fixes with a note of each. The site then stands as accepted on the day the fixes are sent. If they aren't sent within those 5 business days, the Client may claim under 2.1 within 5 business days after that day, or accept the site by email with the listed defects carried into the fixes window. If it does neither in that time, the site stands as accepted on the last of those 5 business days, with those defects carried into the fixes window. If the approver hasn't replied in time, the staging site stands as accepted.
Go-liveWithin 5 business days after acceptance, Shifter sends the go-live steps in writing for the Client or its developer: for a code site, adding the domain to the project in the Client's Vercel or Netlify account and changing only the web records (A or CNAME) for the hostnames the page list names for the rebuilt site to serve; for WordPress, the same DNS change or, on the same hosting, the switch from staging to live. Nameservers, MX and the existing TXT records stay as they are. If the platform asks for a TXT record to verify the domain for the new site's team, the go-live steps say so, and the Client or its developer adds only that record. The Client, or its developer, makes the change and tells Shifter by email within 10 business days after the go-live steps are sent. If Shifter sees the rebuilt site live before that email, the day it sees it counts as that email. Within 1 business day after that email, Shifter checks and reports in writing on: the 301 redirects for every changed or dropped address, schema, llms.txt, robots.txt and the sitemap, the GA4 tag or Tag Manager container (same IDs), the other site-wide scripts and the consent banner's categories and defaults carried over, Search Console verification kept, the Gear articles and pages added since the staging site was sent, and any baseline recount under 2.2. Go-live is the day that report is sent or, if it isn't sent within that 1 business day, the business day after the Client's email. For this Order and the Gear Order, the rebuilt site serves the domain from the day Shifter's report after the Client's email is sent or, if that report is late or isn't owed, the business day after that email. The 10th-business-day fallback below doesn't make it serve the domain. If the Client's email hasn't arrived within those 10 business days, the 10th business day counts as go-live for this Order (including 1.1, 1.2, the Six-month option row and the fixes window) and for the Gear Order's 1.3, its 2.3 dates and its 6.2. Until the Client's email arrives, the Gear's articles and site changes still go on the site the domain serves, with the CMS user or developer route given under the Gear Order's 4.1, and Shifter adds each to the rebuilt site and lists it in the go-live report. A later switch to the rebuilt site is then the Client's own change under the Gear Order's 2.3, and Shifter's report follows within 1 business day after the Client's email. Shifter adds Gear work to the rebuilt site, and owes the report after a later switch, only until the fixes window ends. If no switch has come by then, Shifter lists the Gear work it added by email within 2 business days after the fixes window ends. After that, Shifter's work for a switch, and carrying over Gear work published since, is a change under the Gear Order's 2.1.
Fixes windowFor 30 days after go-live, Shifter fixes, within 5 business days each, defects in its own build that the approver reports in writing.

What's out of scope: new copy beyond moving the existing words, new photography or illustration, logins, shops or payments, memberships, multi-language sites, custom apps or new integrations (existing forms, embeds and site-wide scripts, such as a Tag Manager container, pixels and chat or booking widgets, are carried over as they are), and any page beyond the agreed list. Each is a change under the Gear Order's 2.1.

Parts that stay on the current platform: if the current site has a shop, logins, memberships, payments or other-language pages, the page list says so. Those parts stay on the Client's current platform at a hostname the Client keeps, linked from the rebuilt site. If they can't, the Client may cancel this Order by email within 5 business days after the page list is sent. Shifter then refunds this Order's fee in full within 2 business days, this Order ends, and the six-month minimum ends. Comments, users and form entries on the current site aren't carried over.

Forms: they're rebuilt to send to the same destinations as today, through a service in the Client's own account on a code site (Platform row). Shifter never imports form submissions, customer records or payments (Gear Order 4.2).

The Gear's own work while the rebuild runs: it's unchanged. The Gear's site changes go on the live site until the rebuilt site serves the domain (Go-live row), and the rebuild carries them over. Articles and pages Shifter made under the Gear Order, including the media-room page, are migrated at any count and don't count toward the 15 pages or the 150 posts. Any published after the staging site is sent are added to the rebuilt site and listed in the go-live report.

4. What the Client provides (the rebuild access)

Through the rebuild steps linked in the Gear Order's confirmation email, by email:

Shifter never asks for registrar, DNS or billing logins on any account. Domain, DNS, hosting and platform accounts stay the Client's. The Client, or its developer, makes the go-live change from Shifter's written steps (Go-live row). The approver's decisions in clause 3 are made by email.

5. Acceptance

5.1 No signature is needed. This Order takes effect with the Gear Order when the payment succeeds, but only if the checkout showed it beside the Gear Order's checkbox (Gear Order 6.2, "Shown"). Choosing the six-month option at checkout accepts it.

5.2 This Order, the Gear Order and the documents in the Gear Order's 1.1 are the whole agreement for this extra. Nothing said on a call or in a chat adds to them.