GLOBALAI
Home About
Services▾
How it works Use cases Courses Blog
→ Back to the blog
Discovery
November 2026 · 8 min read

Eight weeks to launch: what actually happens each week

A real project broken down by week — what got built, what was delayed, where the client had to decide, and what we'd do differently.
When we say the first phase goes live within four to eight weeks, the first question we hear is how that's possible. Here is the breakdown of one project — a retail chain with nine branches — week by week.
The first two weeks are interviews and mapping. We sat with the chain manager, two branch managers, the finance manager and the person who runs the warehouse. We didn't ask them to describe the procedure but to open their screens and show us what they actually do. That's where it emerged that special orders were handled in a WhatsApp group, which didn't appear in any document.
Week three is planning and decisions. We presented the current picture and a phased plan, and the client had to decide three questions: who owns customer data, what counts as a closed order, and what happens when a branch sells an item that's out of stock in the warehouse. Every delay in these decisions is a direct delay to the timeline — and it's the only part of the project outside our control.
Weeks four to six are the build. We set up the system, matched the screens to the names the team actually uses, and migrated the data from the spreadsheets with duplicates cleaned up. At the same time we ran the new system alongside the old method, so any gap would surface in time and not after the switchover.
Week seven is testing and training. We tested edge cases — what happens when an order is cancelled after inventory has already been deducted, and what happens when a branch works without internet. Branch managers got a one-hour training session and a short document covering the five processes that change in their day-to-day work.
Week eight is go-live and support. We didn't switch off the old method on the same day; we kept it open read-only for another two weeks. What we'd do differently: bring the three decisions forward to week one instead of week three. They didn't need the full mapping, and they were what held everything up.
The bottom line
A project's timeline depends less on development speed and more on how fast the organization makes three or four hard decisions.
More articles
Discovery
Why projects stall in month six
Customer service
When an AI agent should hand over to a person
Data
Why every department has a different number for the same question
Relevant to you?
We'd love to hear what this looks like in your organization
An introductory call of about 20 minutes, at no cost and no commitment.
Book a discovery call
GLOBALAI
End-to-end AI services for companies and organizations — from discovery to ongoing support.
Services
Discovery & architecture Multichannel communication Core systems: CRM & ERP Enterprise AI Dashboards, reports & BI Automation & integrations Custom development Product & project management
Company
About How we work Use cases Careers Contact Terms of use
Contact
CS@GlobalAI.co.il
04 6959909 | 03 9599705
94 Yigal Alon St., Alon Tower 2, Tel Aviv
35 Menachem Begin St., Link Complex, Tirat Carmel
© 2026 GlobalAI Ltd. All rights reserved.
GLOBALAI.CO.IL