How we work
Your Sprint or Rebuild follows a written plan. You approve the design before we build in Shopify, then approve the finished preview before launch.
Your project, step by step
Review the service scope and price before booking. The required payment reserves your place in the production schedule, including upcoming work while another build is active.
Your confirmation links to your private project page. It holds your onboarding checklist and current production estimate, followed by your project plan and payment history.
Open your confirmation email and complete onboarding through your private project link.
Send your store URL and Shopify collaborator code, along with the materials for the agreed work. We request collaborator access for you to approve, then verify the required permissions and files.
At the kickoff Zoom, we confirm the deliverables and project objective. Your written scope records the production window, payment milestones and revision allowance. We save the starting pages and relevant reports for comparison after launch.
Approve the Shopify access request and written scope. Choose one person to consolidate feedback.
We create an HTML demo showing the proposed design on mobile and desktop. You receive a preview and an explanation of the changes before Shopify implementation begins.
We handle feedback within the agreed revision allowance and record approval of the current version. A Rebuild's 25% design payment is due at this point, before implementation.
Review the demo, send one consolidated response and approve the version you want us to build.
We implement the approved design in a duplicate Shopify theme. Your storefront stays live while we build. A midpoint update shows completed work, outstanding decisions and the next preview date.
After our internal checks, you receive the Shopify preview for final review. Send one consolidated revision list through your project page. Additional work receives a separate price and schedule before it starts.
Review the Shopify preview and submit your consolidated feedback. Approve the finished version before launch.
After final approval and the remaining payment, we publish at the agreed time. We check the affected shopping paths on mobile and desktop before and after launch.
Your handoff includes a recorded walkthrough and before-and-after document. We explain routine updates on the handoff Zoom and record your support dates on the project page. An agreed non-publishing handoff follows the written scope.
Pay the remaining milestone and confirm launch timing. Review the handoff and bring your questions to the walkthrough.
Around day 14, we check how the work is holding up and review any issues. Around day 30, we review the available store reports against the starting period, accounting for changes in traffic and promotions.
We ask for honest feedback after delivery. Public testimonials and case studies require your separate permission. We share the proposed case study for approval before publishing it.
Share any issues and the relevant store reports. Tell us how the experience went and whether you want to discuss further work.
The practical details
A Sprint is planned for 7–10 business days. A core Rebuild takes 4–6 weeks. Production starts in the agreed window after access and materials are verified. Delayed materials or approvals move the forecast, with the current dates shown on your project page.
A Sprint includes up to two consolidated revision rounds across the project. Your Rebuild scope states its allowance. Send feedback through your project page so decisions stay attached to the version being reviewed.
A Sprint includes 14 days of support for bugs caused by the agreed implementation. A Rebuild includes 30 days. The 30-day results check-in is separate from the implementation support period. Further build work receives its own agreed scope.
Contact supportReview the service scope and current availability. Send your store link if you need help choosing.