Six phases. Six weeks. A signed gate at the end of each.

This is the programme every StyleChain customer goes through, run by the 3 Clicks implementation team. It is published here so you can hold us to it.

Book a DemoRead the plan

Standard apparel PLM programme · 105 tracked tasks

The plan

Week numbers are the standard programme. Integrations and data migration, scoped in phase three, can extend it.

Phase 1Week 1

Project management and kickoff

Commercials, contacts and timeline are settled before anything is provisioned.

  • Service agreement countersigned, billing contacts and any custom SLA terms confirmed
  • Your project lead, IT contact, training coordinator and executive sponsor named
  • Start date, go-live date, UAT window, training dates and hypercare end date set
  • Draft Gantt published and approved in writing, kickoff call run, weekly check-in cadence set
Gate 1 Kickoff complete: signed agreement, contacts confirmed, Gantt approved
Phase 2Week 2

Infrastructure

Your instance exists, you can log in, and the API has answered a real call.

  • Subscription tier and feature set confirmed, production instance provisioned
  • UAT environment provisioned where the programme calls for one
  • Subdomain configured, credentials sent to your primary contact, login confirmed
  • Static IPs collected, IP allowlisting configured, API account created, documentation shared, test call verified
Gate 2 Infrastructure ready: instance provisioned, login confirmed, API verified
Phase 3Week 2

Integration scoping

What connects to what is decided in writing before configuration starts, so it cannot block it.

  • Discovery session, source systems and data flows documented
  • Integration owner named on your side
  • Native connection or custom integration decided for each system
  • In scope or out of scope documented, integration partner briefed if required
Gate 3 Integration scope confirmed in writing
Phase 4Weeks 3 to 4

Configuration and user acceptance testing

Four sub-phases, each signed off by you: company setup, company configuration, product and component configuration, then UAT.

  • Company details, customers, currencies, tax, roles, permissions and staff accounts
  • Barcode range, price types, terms, tags, component types and custom fields
  • Size scales, status workflow, season structure, spec templates, sample milestones, costing templates, supplier portal settings
  • You create a test style end to end, run the UAT script, critical defects are resolved, you sign the acceptance form
Gate 4 Configuration UAT sign-off with zero critical defects outstanding
Phase 5Week 5

Onboarding and training

Ten modules for your team, plus supplier portal training for the factories you invite.

  • Administration and application settings, component library, style development
  • Spec templates and sample reports, costing, supplier portal collaboration
  • Orders, range planner, shipping
  • Search, reporting and dashboards, then supplier portal training
Gate 5 Training sign-off: all required staff trained, supplier accounts active
Phase 6Week 6

Go-live and hypercare

A readiness check, a consultant on standby for the first production day, then weekly check-ins until close-out.

  • Configuration confirmed in production, all user and supplier accounts active, integrations tested in production
  • Go-live date confirmed, you create the first real live style, go-live confirmation sent
  • Weekly hypercare check-in calls and a review of system usage and adoption
  • Final review call, close-out report issued, transition to standard support
Gate 6 Go-live sign-off: readiness check passed, hypercare begins

Who does what

Named people on both sides from the first week.

Your team

  • Project lead: owns decisions, sign-offs and the weekly check-in
  • IT or technical contact: static IPs, API credentials, identity provider, integrations
  • Training coordinator: schedules the ten modules and the supplier sessions
  • Executive sponsor: approves the timeline and clears blockers

3 Clicks implementation team

  • Implementation lead: publishes the Gantt, runs kickoff and every gate
  • Configuration consultant: sets up the instance with you and provides the UAT script
  • Trainer: delivers the modules and supplier portal training
  • Go-live consultant: on standby for the first production day and through hypercare

Common questions

What product and IT teams ask about going live.

How long does it take?

Six phases over six weeks is the standard programme. Integrations and data migration are scoped in phase three and can extend the timeline.

What do we need to provide?

A project lead, an IT contact, a training coordinator and an executive sponsor, plus setup details, configuration decisions and sign-off at each gate.

Is there a test environment?

A production instance is always provisioned. A UAT environment is provisioned where the programme calls for one, with a UAT script before configuration sign-off.

What happens after go-live?

A consultant on standby for day one, weekly hypercare calls, a usage and adoption review, a close-out report and transition to standard support.

Do our suppliers get trained?

Yes. Supplier portal training is part of phase five, and supplier accounts must be active before the training gate is signed.

What about a second brand?

Each brand in a group is provisioned as its own instance and runs the same programme, usually shorter because the configuration decisions are already made. See Enterprise.

Walk through the plan with your own range

Give us 60 minutes and we will map the six phases to your team, your suppliers and your systems.

Book a Demo

60-minute walkthrough · no commitment