Case study — 01/05

Delivery governance across 14 months of continuous scope evolution

A small fixed-scope website that grew into a long-term partnership at more than four times the initial contract value.

ClientAI SaaS platform — US, founder-led
RoleProject Manager / Delivery Lead
Team2 UI/UX designers, Webflow developer

Context

A US-based AI startup came to us for a small fixed-scope marketing website. Fourteen months later, the engagement had grown into a long-term partnership covering web design, Webflow development, content systems and ongoing marketing support, at more than four times the initial contract value.

That growth was not an accident. It was the result of deliberately redesigning how the engagement worked.

The stakes

The biggest delivery risk on this project was never design or development. It was content.

The founder knew his product deeply but struggled to turn that knowledge into finished copy. Pages sat blocked for weeks. The original completion target slipped. At the same time, the client was budget-sensitive, new requests kept arriving as if they were already included, and a rigid fixed-scope model was creating friction with a product that evolved every month.

Left unmanaged, this becomes the classic agency death spiral: scope creep, timeline drift, margin erosion, and a frustrated client who blames the agency for all three.

What I did

Restructured the engagement model. I moved the project from pure fixed-scope to a hybrid: fixed-scope phases for defined deliverables, plus Time & Materials workstreams for the evolving requests, with fully transparent hour tracking. When the project exceeded its originally allocated resources, I negotiated an additional budget allocation, structured so delivery never had to stop.

Built content collection systems. Instead of asking the founder to write from a blank page, I introduced structured content templates and page frameworks. His job changed from creating content to refining it. When the client hired a marketing manager, I routed feedback and content collection through her, which shortened every cycle.

Held the scope line. When a major new page was requested mid-delivery, I did not absorb it. I separated it from the existing agreement, documented the full effort across design, development, CMS and motion, and had it approved as its own initiative with its own budget and timeline.

Set content deadlines with teeth. I made it explicit that production could not proceed on placeholders, and stopped building major pages without approved copy.

Outcome

  • Engagement grew to 4×+ the initial contract value over 14 months
  • Three Time & Materials cycles renewed by the client
  • New initiatives approved outside the original scope instead of eroding it
  • Delivery margin protected throughout
  • A client relationship strong enough that the partnership kept expanding

What I’d do differently

I would transition the engagement model earlier. The first months were spent trying to fit a fast-moving startup into a delivery structure built for stable requirements. Naming that mismatch sooner would have saved administrative overhead on both sides.

Available for contract