Blog Working with Locomotive

How long does a website project with Locomotive take?

A website project with Locomotive typically takes 5 to 7 months from kickoff to launch, and up to a year for larger or more complex projects. Here's how we move through it, phase by phase, and what keeps the calendar honest.

Guide 4 min read

Populous website, designed and built by Locomotive
A good website has a rhythm, and so does the project that builds it. Ours typically runs 5 to 7 months from kickoff to launch, and up to a year when several markets, many integrations or a large content migration enter the picture. A focused site with content ready to go can move faster.

Below, we walk through how we actually run a project, phase by phase, and what your team does at each step. It's our own process, shaped by our team and our clients. If you need a week-by-week planning model you can adapt to any agency, our separate guide to the enterprise website redesign timeline has one.

5–7 months
Typical time from kickoff to launch
Up to 1 year
For larger or more complex projects
CA$125,000
Where most of our website projects start

Our process, phase by phase

Our phases overlap on purpose. Development starts on approved components while the rest of the design is being finalized, and content work runs alongside development. That overlap is what keeps most projects within 5 to 7 months. The vast majority of the time, our in-house team handles design and development, with trusted partners for specialized needs.

1. Discovery and strategy

We sit down with you to define goals, audiences, success measures and constraints. We meet the people who will use and update the site, and audit your current content, analytics, URLs and systems. We also confirm the CMS that fits your team: Craft CMS, Sanity, Strapi, Contentful, DatoCMS, WordPress or another platform. Your role: name a decision-maker and give us access to data and systems. Milestone: an approved brief.

2. User experience and architecture

We design the sitemap, navigation, page types and content model, then prototype the key journeys with real content wherever we can. Lorem ipsum hides a lot of problems. Your role: review the structure with the people who own the content. Milestone: an approved structure and key journeys.

3. Art direction and design system

We set the art direction and build a system of typography, colour, components, responsive behaviour and motion. If the concept includes 3D or WebGL, this is where we decide what it's for and how fast it has to run. When the project includes branding, the identity work comes first and feeds this phase. Your role: focused feedback from the decision-maker, within agreed review windows. Milestone: an approved design system.

4. Development and CMS

We build the templates and components, set up the CMS, roles and workflows, and connect forms, analytics, search, CRM or e-commerce. Your role: confirm integrations and third-party access early. Milestone: a working site in a staging environment.

5. Content and migration

While development moves ahead, new content is written, translated and entered, and existing content is migrated. We test a sample batch first, then scale up, and prepare a redirect for every URL that changes. Your role: own the content and approve it on time. Milestone: a site filled with real content.

6. QA and accessibility

We test key journeys across browsers, devices and input methods, check keyboard access, contrast and motion preferences, and put integrations through their paces with realistic data. Milestone: a go/no-go decision based on test results.

7. Launch, and what comes after

We deploy through a rehearsed process and verify forms, redirects, analytics and indexing in production. Then the site stays with us: we host, support and evolve the sites we build, so the improvements keep coming after launch. Milestone: the site is live, and the next improvements have an owner.

Populous website on mobile
Project listing on the Populous website

What makes a project with us shorter or longer

Design and code rarely derail a schedule. Decisions, content and dependencies outside the project team usually do.

What keeps a project on schedule

  • One decision-maker per approval, with review windows agreed at kickoff.
  • Content owners named early, with time set aside to write and approve.
  • A clear brief that separates must-haves from nice-to-haves.
  • Access to systems and data (CMS, CRM, analytics, hosting) from the first weeks.

When to plan for up to a year

  • The site serves several markets, languages or brands, each with its own approvals.
  • A large content library is being replaced.
  • The site connects to many internal systems.
  • Custom 3D or WebGL scenes need assets produced and tested on real devices.

A new brand identity alongside the website also adds time, since the identity work comes first. Larger organizations, like the global design firm behind the Populous website, often plan for a longer runway: more voices, more content and more systems to bring into line.

Projects rarely slip because of design or code. They slip when decisions and content arrive late. A clear decision-maker and content ready on time are worth weeks.
Production Director, Locomotive

Planning your launch date with us

Start from the date that matters, like a product launch, an event or the end of a contract, and count back to see whether 5 to 7 months fit. If they don't, we'll suggest trimming the first release before we squeeze any phase: launch the priority journeys, then add the rest in planned phases.

At kickoff, we agree on who approves what, how long reviews take and how scope changes are handled. SEO, accessibility and performance sit in the plan from day one, where they're cheapest to get right.

We work with clients worldwide, in English and French. When your teams are spread across time zones or languages, we build that into the review calendar from the start, so approvals keep moving.

Time and budget travel together. Most website projects with us start around CA$125,000, and our guide to what a website with Locomotive costs explains what moves that number. For the bigger picture, read what Locomotive offers. Got a date in mind? Tell us, and we'll help you work back from it.

Frequently asked questions

How long does a website project with Locomotive take?

Typically 5 to 7 months from kickoff to launch. Larger or more complex projects, with several markets, many integrations or a large content migration, can take up to a year, while a focused site with content ready to go can move faster.

What are the phases of a Locomotive website project?

We run it in seven phases: discovery and strategy, user experience and architecture, art direction and design system, development and CMS, content and migration, QA and accessibility, then launch. Several of them overlap on purpose. After launch, we host, support and evolve the site.

Can Locomotive deliver a website in less than 5 months?

Sometimes. A focused site with few templates, ready content and a small decision team can launch sooner, or you can launch a first version with the priority journeys and add the rest in planned phases. Squeezing every phase of a large project usually costs quality or adds risk, so we'd rather trim the first release.

Why do some Locomotive projects take up to a year?

Projects stretch when the site serves several markets, languages or brands, replaces a large content library, connects to many internal systems, or needs sign-off from several departments. A new brand identity alongside the website adds time too, since the identity work comes first.

What does Locomotive need from my team to stay on schedule?

One decision-maker per approval, review windows agreed at kickoff, content owners named early, and access to your systems and data from the first weeks. Design and code rarely cause the delays; late decisions and late content usually do.

Let's work together

Ready to take your brand to the next level? Tell us about your project.

Start a project