All 7 stages

Client guide Β· project stages

Your project, stage by stage

Every Zelix project moves through the same seven stages, from kickoff to complete. Each page here explains what is happening, what we need from you and how you know a stage is done, so you are never left guessing.

7 stages, 2 approval points Nothing reaches customers untested A WhatsApp update at every stage

The seven stages in about a minute.

The seven stages

Tap a stage for the full page: what happens, your checklist and common questions.

  1. Stage 1KickoffWe meet, collect access and agree who approves what.Usually 1 to 2 weeks ›
  2. Stage 2Requirements & designWe write the plan and sample conversations. You approve them.Draft in 2 to 4 working days ›
  3. Stage 3BuildWe build what you approved, in a safe test workspace.Dates set in your plan ›
  4. Stage 4TestingWe run hundreds of scenarios. You accept the results.Days, depending on scope ›
  5. Stage 5Go-liveCutover week, then the AI starts answering, step by step.Cutover week, then a few days of ramp-up ›
  6. Stage 6Hypercare30 days of close watch, fast fixes and weekly reports.30 days ›
  7. Stage 7CompleteHandover done. Your AI team is yours to run.Handover pack delivered ›
  8. Where am I?Your current stage shows on your client dashboard and in the WhatsApp message we send when it changes. Tap Learn about this stage in that message to land on the right page.

How you hear about a new stage

One WhatsApp and one email each time your project moves forward.

The WhatsApp you get when your stage changes

"What this stage means" opens the page for your new stage.

Two points where you decide

Your approval is required twice. Both protect you from paying for something you did not want.

You approve the plan

At the end of Requirements & design you read the plan and sample conversations, then reply "approved". Nothing is built before that. More ›

You accept the test results

At the end of Testing you see what was tested, what failed and got fixed, and three live scenarios. Nothing goes live before you accept. More ›

How we keep you updated

You should never have to ask where things stand.

  • Stage changes
    A WhatsApp message and an email, with a link to that stage's page.
  • Every Monday from Build to Hypercare
    A four-line update: done this week, next week, what we need from you, status.
  • After every meeting
    A written recap within 24 hours.
  • If a date moves
    A message within one business day, with the cause, your options and one new date.

The words we use, in plain English

Sign-off owner
The one person on your side who approves the plan and accepts the test results.
The plan
The written requirements and sample conversations you approve before we build. Also called the BRD or spec.
Not in this round
Items we agreed not to build now. They protect your timeline and can be added later.
Change request
A new idea after approval. We tell you the time and cost first, then update the plan.
UAT
User acceptance testing: hundreds of scenarios run against your AI before any customer sees it.
Cutover
The planned switch from your team answering every chat to the AI answering first.
Go-live
The day the AI starts answering real customers, starting with a small share of chats.
Hand-over
When the AI passes a chat to a person on your team, with the full conversation attached.
Off switch
Our ability to stop the AI in under a minute, sending every new chat back to your team.
Hypercare
The first 30 days live, when we review conversations closely and fix issues within 48 hours.
Handover
The end of the project: manual, training, day-30 report and a written support arrangement.

Questions about your stage?

Message us in your project WhatsApp group, or start a chat here. Your account owner replies.

Message us on WhatsApp