Implementation timeline
A typical implementation plan, from discovery and configuration to pilot, go-live and support.
These week ranges are typical. The plan depends on scope, integrations and data quality. Phases can overlap. Agree the actual schedule and acceptance steps during discovery.
Discovery
Typical weeks 1-2
What happens
Agree goals, scope, a process map, roles and a data inventory.
What you prepare
Bring process owners, sample requests and a list of data sources.
Outcome
A reviewed scope and a shared list of responsibilities.
Configuration
Typical weeks 2-4
What happens
Set up the tenant, users and roles, catalogs, approval rules, templates and criteria.
What you prepare
Prepare user lists, category owners, approval policy and catalog data.
Outcome
A configured workflow ready for integration and pilot checks.
Integrations
Typical weeks 3-6
What happens
Work on ERP or accounting export, KSeF test environment then production certificates, VAT White List, PunchOut and SSO if needed.
What you prepare
Provide integration owners, formats, test access and production access responsibilities.
Outcome
Reviewed connections and a documented handoff between systems.
Pilot
Typical weeks 5-8
What happens
Use one unit or category with real requests and a feedback loop.
What you prepare
Choose participants, real purchase examples and time for review.
Outcome
A tested workflow with issues assigned and configuration changes agreed.
Go-live
Typical weeks 8-10
What happens
Roll out access, train people by role and complete the cutover.
What you prepare
Confirm rollout owners, training attendance and the cutover plan.
Outcome
Users can request, approve, order and record receipt under the agreed rules.
Hypercare
Typical 2-4 weeks after go-live
What happens
Provide support, tune the configuration and hold the first review.
What you prepare
Collect questions, assign issue owners and bring examples to the review.
Outcome
A reviewed operating process and an agreed support handoff.
Confirm approval rules before the pilot. Treat KSeF production certificates and supplier data as named project tasks. Start with a scope the team can review, then use feedback to plan the wider rollout.