Most agencies send you a proposal, take your deposit, and then go quiet for two weeks. You are left wondering whether anyone has actually started working on your project, and the first sign of life is a vague email asking for your logo files.

We think that is a terrible way to start a relationship. The first week of any Shopify build sets the tone for everything that follows. It determines whether the project lands on time and on budget, or spirals into months of delays, misaligned expectations, and scope creep.

This article is a transparent walkthrough of exactly what happens during week 1 of a Shopify build with us. Every meeting, every deliverable, every decision point. We are publishing this because we believe transparency is the best way to demonstrate competence, and because we want you to know exactly what you are paying for before you sign anything.

Why week 1 matters more than any other

In twenty years of building ecommerce stores, I have learned one thing above all else: the quality of the first week determines the quality of the entire project. It is not hyperbole. The data supports it.

Projects that start with a thorough, structured first week are three times more likely to launch on time compared to those that start with a vague kickoff and no clear process. That statistic comes from our own project data across dozens of builds.

The first week is not about writing code. It is about understanding your business deeply enough that every line of code we write afterwards is the right one.

Here is why week 1 is so critical:

  • Misalignment costs money. Every assumption we get wrong in week 1 becomes a change request in week 6. Change requests cost 4-10 times more than getting it right from the start.
  • Speed comes from clarity. Teams that know exactly what they are building move faster than teams that are guessing. Week 1 gives us that clarity.
  • Trust is built early or not at all. If you feel confident and informed after week 1, that confidence carries through the entire project. If you feel confused and anxious, that anxiety compounds.
  • Technical risks surface early. The sooner we identify complex integrations, data migration challenges, or platform limitations, the sooner we can solve them — before they become deadline-killers.

This is why we invest so heavily in our first week. It is the highest-leverage time in any project. As we explain in our guide to choosing a Shopify agency, transparent process is one of the strongest signals of agency competence.

What happens before kickoff

Week 1 does not start cold. Before the kickoff call, we have already done significant work behind the scenes. This pre-work ensures we arrive at the first meeting prepared, not fumbling through introductions.

Pre-kickoff preparation (2-3 days before)

Here is what we do before the kickoff call:

  1. Review the proposal and scope document. We re-read every line of the agreed scope. If there are any ambiguities, we flag them for discussion during kickoff.
  2. Audit your existing store (if applicable). If you have a live store — whether on Shopify, WooCommerce, Magento, or any other platform — we run a full technical audit. Page speed, SEO health, app stack, theme code quality, and conversion funnel analysis.
  3. Research your competitors. We look at 5-8 direct competitors in your space. What are they doing well? What are they doing badly? Where is the opportunity?
  4. Set up project infrastructure. Slack channel or email thread, shared document folder, project timeline in our project management tool, and a development store on Shopify.
  5. Prepare the kickoff agenda. Not a generic template — a customised agenda based on your specific project, industry, and goals.

This pre-work typically takes 4-6 hours. It is included in the project cost. We do not charge extra for being prepared.

Day 1: The kickoff call

The kickoff call is the most important meeting of the entire project. It is where alignment happens. We schedule 90 minutes, and we use every minute.

Who attends

From our side: the project lead (usually me for builds under £30k) and the lead developer who will be writing the code. We do not send account managers who then have to relay information to developers. The people building your store are in the room from day one.

From your side: ideally the person making decisions and the person who will be providing content, product data, and brand assets. If those are the same person, even better.

What we cover

The kickoff is structured around five areas:

  1. Business context (20 minutes). We ask about your business beyond the website. Revenue targets, customer demographics, seasonal patterns, growth plans, marketing channels. This is not small talk — it directly shapes technical decisions. A fashion brand doing 40% of revenue in November needs different infrastructure than a subscription wellness brand with steady monthly revenue.
  2. Current pain points (15 minutes). What is broken? What frustrates your team daily? What are customers complaining about? These pain points become our priority list. If your current checkout has a 72% abandonment rate, that is problem number one.
  3. Feature requirements (25 minutes). We walk through the scope document line by line, asking clarifying questions. "Product filtering" might mean a simple colour dropdown to you and a multi-faceted, AJAX-powered filter system to us. We close every gap in understanding here.
  4. Technical requirements (15 minutes). Integrations (ERP, CRM, email platform, shipping), payment gateways, multi-currency, B2B functionality, subscription logic, or anything that touches a third-party system.
  5. Timeline and milestones (15 minutes). We set specific dates for key milestones: design approval, development complete, content migration, UAT, and launch. Every milestone has a clear owner — either us or you.

The kickoff document

Within two hours of the kickoff call, we send a kickoff summary document. It captures every decision, every requirement, and every assumption. You review it, flag anything we got wrong, and confirm. This document becomes the project bible. No "I thought you said..." conversations three weeks later.

Day 2: Technical discovery and audit

Day 2 is the most technically intensive day of the week. This is where our developers dig into the details that most agencies skip entirely.

Existing store audit

If you have an existing store, we run a comprehensive audit covering:

  • Performance. Core Web Vitals on mobile and desktop. We test every template: homepage, collection pages, product pages, cart, and checkout. We are looking for LCP under 2.5 seconds, TBT under 200ms, and CLS under 0.1.
  • SEO health. Crawl the entire site. Check indexation status, canonical tags, structured data, internal linking, redirect chains, broken links, and meta data. We document every SEO issue that needs to be fixed or preserved during the migration.
  • App stack. List every installed app, its purpose, its performance impact, and whether we need to replicate its functionality in the new build. Most stores have 15-25 apps. We typically recommend keeping 6-8 and replacing the rest with native functionality or custom code.
  • Data export feasibility. Products, customers, orders, reviews, blog posts, URL redirects. We test export from the existing platform to confirm data quality and identify any fields that will not map cleanly to Shopify.
  • Theme code quality. If staying on Shopify, we review the existing theme code. Is it worth iterating on, or is a rebuild more efficient? We are honest about this — sometimes a few targeted fixes deliver more ROI than a full rebuild.

Third-party integration mapping

We document every system that needs to connect to Shopify:

Integration What we check Common issues
ERP / accounting API availability, sync frequency, field mapping Legacy systems with no API, manual CSV exports
Email / SMS (Klaviyo, etc.) Event tracking, customer sync, flow migration Historical data migration, segment rebuild
Shipping / fulfilment Rate calculation, label generation, tracking Custom shipping rules, multiple warehouses
Reviews Export format, review count, image reviews Proprietary formats, no export option
Payment gateways Shopify Payments compatibility, subscription billing Gateway-specific features, PCI compliance

This mapping prevents the nightmare scenario of discovering a critical integration is impossible in week 6. We have seen projects derail because nobody checked whether the client's ERP had an API until development was already underway. We solve that on day 2.

Day 3: Design direction and sitemap

Day 3 bridges strategy and execution. This is where the project starts to become visual and tangible.

Sitemap and information architecture

We build a complete sitemap covering every page and template. For a typical ecommerce store, this includes:

  • Homepage
  • Collection pages (with hierarchy — parent and child collections)
  • Product page template(s) — some stores need 2-3 different product page layouts
  • Cart and checkout
  • Content pages (about, contact, FAQ, delivery, returns)
  • Blog and article templates
  • Account pages (login, register, order history)
  • Search results
  • 404 page

The sitemap is not just a list — it includes the navigation structure, internal linking strategy, and URL hierarchy. Getting this right is fundamental to both SEO and user experience.

Design direction session

We hold a 60-minute design direction session. This is not about showing you mockups — it is about aligning on visual direction before we start designing. We cover:

  • Brand audit. We review your existing brand assets — logo, colour palette, typography, photography style, tone of voice. We identify what works and what needs refinement.
  • Competitive positioning. Using the competitor research from pre-kickoff, we discuss where you want to sit visually relative to your market. Premium and minimal? Bold and disruptive? Clean and accessible?
  • Reference gathering. We share 8-12 reference sites (not necessarily competitors) that illustrate different design approaches. You tell us what resonates and what does not. This saves weeks of back-and-forth on mockups.
  • Component inventory. We identify every unique component the design will need: product cards, collection grids, hero sections, promotional banners, trust badges, review displays, and so on.

By the end of day 3, we have a clear design brief that our design team can execute against without guesswork.

Day 4: Development environment and early build

While most agencies are still circulating meeting notes, we are already building. Day 4 is when code starts being written.

Development environment setup

We configure the Shopify development store with:

  • Store settings. Currency, tax configuration, shipping zones, checkout settings, payment gateways (in test mode), and notification templates.
  • Theme scaffold. We start with a clean Dawn-based foundation (never a bloated premium theme) and begin structuring the section architecture. Every section is built to be modular, reusable, and manageable by your team after launch.
  • Essential apps. Only the apps that are genuinely needed. Typically: Klaviyo (email), a reviews app, our own filtering and cart apps where appropriate. Every app must justify its existence with a clear revenue or operational benefit.
  • Version control. The theme is connected to a Git repository from day one. Every change is tracked, reversible, and documented. This is not optional — it is how professional development works.

Structural development begins

By the afternoon of day 4, our developer is building the foundational elements:

// Week 1 development priorities
const week1Build = {
  navigation:    'Header, mobile menu, mega nav structure',
  footer:        'Links, newsletter, trust signals',
  typography:    'Font loading, scale, responsive sizing',
  colourSystem:  'CSS custom properties, dark/light modes',
  gridSystem:    'Collection grid, product cards, responsive',
  cartDrawer:    'Slide-out cart with upsell placeholder',
};

These foundational elements need to be rock-solid because every other component builds on top of them. Getting the typography, colour system, and grid right in week 1 means design consistency throughout the entire build.

Day 5: Week 1 review and roadmap lock

Friday is review day. We bring everything together and align on the path forward.

Internal review

Before speaking to you, we run an internal review. The project lead and developer walk through everything from the week:

  • Are there any scope items we are unsure about?
  • Have we identified any technical risks?
  • Is the timeline realistic given what we have learned?
  • Do we need any additional information or assets from the client?

Week 1 review call

We schedule a 30-45 minute call with you to present our findings and align on next steps. This call covers:

  1. Discovery summary. Key findings from the technical audit, competitive analysis, and integration mapping. No 80-page document — a clear, prioritised summary of what matters.
  2. Development store walkthrough. We show you the development store with the structural elements in place. You can see the navigation, footer, basic layout, and colour system. It is not pretty yet, but it demonstrates momentum.
  3. Risk register. Any technical risks or dependencies we have identified. For example: "Your ERP integration will require a custom middleware layer, which adds 5 days to the timeline" or "Your product data needs cleaning before import — 200 SKUs have missing descriptions."
  4. Updated timeline. Based on everything we have learned, we confirm or adjust the project timeline. If anything has changed, we explain exactly why and get your sign-off.
  5. Action items for week 2. Clear tasks for both sides. What we will deliver, what we need from you, and when.

What you receive at the end of week 1

By Friday evening, you have the following deliverables in hand:

  1. Kickoff summary document — every requirement, decision, and assumption documented and confirmed.
  2. Technical audit report — performance, SEO, app stack, and data migration analysis (if migrating from an existing platform).
  3. Sitemap and information architecture — complete page structure with URL hierarchy.
  4. Design direction brief — visual direction, references, and component inventory.
  5. Integration specification — every third-party system mapped with connection method and timeline impact.
  6. Development store access — you can log in and see the structural foundation being built.
  7. Updated project timeline — milestone dates confirmed or adjusted based on discovery findings.
  8. Risk register — known risks with mitigation plans.
  9. Action items list — clear tasks for both sides with deadlines.

That is nine deliverables in five days. Compare that to the industry average of "we will be in touch" and you start to see why choosing the right agency matters so much.

Common mistakes that derail week 1

We have run enough projects to know what goes wrong. Here are the common mistakes — from both sides — and how to avoid them.

Mistakes brands make

  • Not having a decision-maker available. If every question needs to go through three layers of approval, week 1 stalls. The person with authority to approve scope, design direction, and timeline must be reachable.
  • Holding back information. Some brands do not mention their ERP, their existing agency contract, or their plan to add 500 SKUs next quarter until week 4. Tell us everything upfront. There are no embarrassing questions.
  • Expecting mockups on day 1. Design comes after discovery, not before. If an agency shows you pixel-perfect mockups before understanding your business, they are designing for aesthetics, not for revenue.
  • Not preparing brand assets. Logo files, brand guidelines, product photography, and copy. If these are not ready by kickoff, the project timeline extends. Simple as that.

Mistakes agencies make

  • Sending account managers instead of builders. The people in the kickoff meeting should be the people building the store. Information loss through intermediaries causes errors.
  • Skipping the technical audit. Jumping straight into design without understanding the technical landscape is like designing a house without checking the foundation.
  • No documentation. If the kickoff decisions are not documented, they do not exist. Human memory is unreliable. Documents are not.
  • Generic process. Every project is different. A fashion brand migration from Magento needs a different week 1 than a food brand launching their first DTC store. Templates are fine for structure, but the content must be customised.

These mistakes are exactly the warning signs we discuss in our guide to evaluating a Shopify agency. If your current agency is making them, it might be time for a conversation with us.

What comes next: weeks 2-4

Week 1 is the foundation. Here is a brief overview of what follows:

Week 2: Design. Homepage and key template designs based on the direction agreed in week 1. We present designs for review and refinement. Most projects need 1-2 rounds of revisions.

Week 3: Core development. Approved designs are built into functional Shopify templates. Product pages, collection pages, and the homepage come to life. You can interact with the development store and provide feedback in real time.

Week 4: Content and integration. Product data migration, content population, third-party integrations, and SEO implementation. The store starts looking and feeling like the final product.

Each week has the same discipline as week 1: clear deliverables, documented decisions, and a review call. We maintain momentum because we maintain structure.

For a deeper look at our full Shopify development process, visit our service page or read our complete build timeline guide.

Transparency is not a marketing strategy for us. It is how we operate. Every client we work with gets this same level of structure, documentation, and communication from day one. The result is projects that launch on time, on budget, and with no surprises.

If you are about to start a Shopify project and you want to know exactly what you are getting into before you commit, start a conversation with us. We will walk you through our process in detail, answer every question, and give you an honest assessment of whether we are the right fit.