Back to Journal
StrategyEngineering

From Brief to Live in 21 Days

A literal day-by-day breakdown of how we shipped a full e-commerce platform for Stryke in three weeks.

FTFivi Tech·February 5, 2026·2 min read·3,512 views

Stryke came to us with a brief, a deadline, and a deeply unrealistic timeline: a full e-commerce platform live in three weeks. We said yes because we had built the playbook for exactly this case. Here is the day-by-day.

Week 1, Discovery and architecture

Days 1 to 2

Brief workshop, scope lock, technical spike on the payment provider. Output: signed scope, one-page architecture diagram. Anything not on the diagram on day two is not in the launch.

Days 3 to 5

Design system tokens defined, three hero screens at high fidelity, repository scaffolded with CI green on day five. The CI being green on Friday of week one is the most important milestone of the project.

Days 6 to 7

Catalog model agreed with the merchant team. Importer script tested against a sample of 200 SKUs. The import script becomes the contract between us and the client's data.

Week 2, Build

Two engineers, one designer, one PM. Daily 15-minute standup, twice-weekly client demo, no other meetings on the team's calendar.

sprint/week-2.mdjavascript
Day 8:  Catalog import live in staging (1,800 SKUs)
Day 9:  Cart + checkout flow first pass
Day 10: Payment integration end-to-end (sandbox)
Day 11: Address book + order history
Day 12: Email transactional templates wired
Day 13: Admin order management screens
Day 14: Demo to stakeholders, sign-off on scope

Week 3, Polish and launch

Polish week is non-negotiable. We do not move launch into polish week to "save time." We move scope out instead. The client signs a one-line note that confirms what is being moved out, and that note ships with the launch announcement.

Days 15 to 17

Empty states, error states, loading skeletons, mobile passes, accessibility audit, performance pass to a 95+ Lighthouse score. Half the bugs we find this week were always there; the other half are introduced by polish itself, which is part of why we schedule the time.

Days 18 to 19

Soft launch to 10% of traffic via a feature flag. Monitor crash-free sessions, conversion funnel, and core web vitals hourly. If a number wobbles, we hold the ramp. Nothing about the launch is heroic; it's monitored.

Days 20 to 21

Full ramp. Stryke went live on day 21 with a 96 Lighthouse score, zero reported errors in the first 48 hours, and a conversion rate 38% above their previous platform.

Three-week launches are not heroic. They are systematic. Every shortcut you take in week one becomes a fire in week three.

The win wasn't the timeline. It was that nobody on the team worked a weekend. That's the only delivery metric that actually compounds.

Tags

#delivery#case-study#ecommerce#sprint#stryke

Share

FT

Fivi Tech

Fivi Tech is a marketing and software development agency in the Ajman Free Zone, built by founders with 35+ years of combined experience across the GCC. Posts here are written by whichever of us has the most to say on the topic, then reviewed by the rest before they ship. The byline is collective on purpose.

Stay in the Loop

Get a heads-up when we ship.

Drop your email — we'll let you know when we publish something worth reading. No cadence, no growth-hack newsletters.

Unsubscribe with one click. We don't share your email.