CRM deployment the agile way — no surprises
The project is split into 3-week sprints with weekly reviews. You know what we do, you see the progress, you control the budget.
- Sprint 0 — kick-off and Product Backlog in 2 weeks
- 3-week sprints — analysis, configuration, testing
- MVP before go-live — your team approves every stage
- 90 days of technical support after deployment
OPTINGO AGILE CRM — 3 PROJECT PHASES
Prepare & Plan
Sprint 0 · Weeks 1–2
Construct
A series of 3-week sprints
Validate, Deploy & Support
UAT · Go-live · 90 days of support
PROJECT APPROACH
We deliver projects in an agile model
The agile model means faster results, lower risk and full transparency — instead of a long project with a surprise at the end.
⚠️ Traditional approach (Waterfall)
-
✗ Long time to first result
Full deployment after 6–18 months — with no chance to correct course along the way.
-
✗ Risk of mismatch with needs
Requirements are gathered once, at the start — they change, but the system is already built.
-
✗ Budget and deadline overruns
Mid-project changes are expensive — every modification requires an annex.
-
✗ Low adoption after launch
Users see the system only at training — too late for feedback.
✅ Optingo agile model
-
✓ MVP in 6–8 weeks
Key processes run in production before moving to the full deployment stage.
-
✓ Flexible sprint scope
The Product Owner can change backlog priorities before each sprint.
-
✓ Time-boxing = predictable budget
Every sprint has a fixed time and cost — no surprises on the invoice.
-
✓ High adoption from day one
Key users test the system at every sprint review — before they ever reach training.
METHODOLOGY
3 phases of every deployment
Each phase has clearly defined deliverables, participants and outcome — you know exactly what you get and when.
Prepare & Plan
Kick-off, Product Backlog, project plan
1
week
PHASE DELIVERABLES
- → Kick-off — align roles, tasks and risks
- → Product Backlog in ClickUp
- → High-level schedule with milestones
- → Data migration plan
- → Integration flows (ERP, email, other)
- → Agreed test plan
PARTICIPANTS
AFTER PHASE 1 YOU HAVE:
Agreed project scope, backlog priorities, sprint schedule and a full understanding of risks — before configuration begins.
Construct
Analysis, configuration, integrations, testing — sprint by sprint
3
weeks per sprint
EVERY SPRINT INCLUDES
- → Analytical workshops with a system prototype
- → Configuration / adjustment of the sprint scope
- → Integrations with external systems
- → Testing of the delivered scope
- → Sprint review with key users
- → Planning the next sprint
TOOLS & RULES
The Product Owner can change backlog priorities before each sprint — flexibility without chaos.
AFTER PHASE 2 YOU HAVE:
A working system in the test environment — your data, your processes, ready for acceptance testing.
Validate, Deploy & Support
Acceptance testing, training, production deployment, support
+90
days of support
PHASE DELIVERABLES
- → UAT — end-to-end acceptance testing by the client
- → Train-the-Trainer training
- → Video training materials
- → Data migration to the production environment
- → Go-live and intensive support (first 2 weeks)
- → 90 days of technical support after launch
TRAINING MODEL
Optingo trains your Trainers (key users). Trainers run training for the team. Your company is self-sufficient after the project.
AFTER PHASE 3 YOU HAVE:
A signed acceptance protocol, a working production system and a team that uses it independently from day one.
WAY OF WORKING
What does one sprint look like?
Every 3 weeks is a complete cycle: from analysis through configuration to testing and review.
Analysis & Planning
- Analytical workshops with key users
- Scope presented on a system prototype
- Detailing requirements and use cases
- Agreeing the sprint configuration scope
Configuration & Integrations
- Creatio configuration (no-code Studio)
- Integrations with external systems (ERP, email)
- Building BPM processes and business rules
- Documenting changes in ClickUp
Testing & Review
- Testing of the delivered scope by Optingo
- Sprint review with the client’s key users
- Acceptance and fixes reported by the Product Owner
- Planning the scope of the next sprint
PROJECT TEAM
Who takes part in the project?
The project requires engagement on both sides. Below — what we need from your company and what we bring.
Product Owner
On the client side — a key role
- • Manages the Product Backlog
- • Approves the scope of each sprint
- • Makes project decisions on the business side
- • Takes part in sprint reviews and accepts deliverables
- • Availability: ~4–6h per week
Process Owners / Key Users
On the client side — subject matter
- • Take part in analytical workshops
- • Formulate and accept business requirements
- • Run functional tests within the sprint
- • Ultimately: Trainers for the remaining users
- • Availability: ~2–4h per week
IT / Administrator
On the client side — the technical side
- • Provides access to integrated systems
- • Handles work on the client’s systems
- • Prepares the production environment
- • Ultimately: CRM Administrator after deployment
- • Availability: as integration needs require
Optingo team
Project Manager + Consultant + Developer
- • Project Manager — coordination, backlog, communication
- • Creatio Consultant — workshops, configuration, processes
- • Developer — integrations, customizations (if required)
- • Running Train-the-Trainer sessions
- • 90 days of technical support after go-live
PROJECT PRINCIPLES
6 principles that protect your project
Clear rules at the start prevent conflicts and overruns — you know where you stand.
01
Time-boxing
Every sprint has a fixed duration (3 weeks). Scope can be modified by the PO — time and cost stay predictable.
02
MVP First
We focus on the key business processes first. The system works and is used before we deploy everything.
03
Minimum customization
We avoid costly programming — configuration instead of code. Customizations only when standard features are insufficient.
04
Train-the-Trainer
We train your Trainers — they train the team. Your company is self-sufficient after the project, not dependent on Optingo.
05
Remote work
Most work is done online — meetings via Teams/Meet. No time wasted on commuting. Session recordings available in ClickUp.
06
Full transparency
The entire backlog, task statuses and sprint progress in ClickUp — access for your team 24/7. No hidden work.
3 wks
length of one sprint
6-8
weeks to MVP
90 days
support after launch
100%
projects with an acceptance protocol
Ready to start Sprint 0?
Book a free 30-minute meeting. We’ll show you what a project looks like for a company like yours — with concrete stages and a schedule.
- No commitment
- Demo tailored to your industry
- We respond in 24h