Opting
/
How we work
Optingo Agile CRM

Implementation of CRM in an Agile Model —
no surprises

The project is divided into 3-week sprints with weekly reviews. You know what we're doing, 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 production starts — your team approves every stage
90 days of technical support after implementation
Arrange a demo
See the methodology →
Optingo Agile CRM — 3 fazy projektu
1
Prepare & Plan
Sprint 0 · Tygodnie 1–2
2
Construct
Serie 3-tygodniowych sprintów
3
Validate, Deploy & Support
UAT · Go-live · 90 dni wsparcia
✓ MVP w 6–8 tygodni
✓ Zarządzanie w ClickUp
Approach to the project

We implement projects in an agile model

An agile model means faster results, less risk and full transparency — instead of a long project with a surprise at the end.

⚠️
Traditional approach (Waterfall)
✗
Long time to the first effect
Full implementation after 6-18 months — no adjustment possible during
✗
Risk of non-compliance with needs
Requirements collected once, at the beginning — change and the system is already built
✗
Exceeding budget and deadline
Changes in progress cost a lot - each modification requires an annex
✗
Low adoption after launch
Users only see the system during training — too late for feedback
✅
Optingo Agile Model
✓
MVP in 6—8 weeks
Key processes are in production before they reach the full implementation stage
✓
Flexible sprint scope
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 go to training
Methodology

3 phases of each implementation

Each phase has clearly defined phase products, participants and outcome — you know exactly what you get and when.

1
Sprint 0
Prepare & Plan
Kick-off, Product Backlog, Project Plan
1
week
Phase Products
→
Kick-off — agreeing roles, tasks and risks
→
Product Backlog in ClickUp
→
Framework schedule with milestones
→
Data migration plan
→
Integration flows (ERP, email, others)
→
Agreed test plan
participants
👤 Product Owner (Customer)
👥 Process Owners (Client)
💻 IT (Client)
🔵 Optingo Team
The result of the phase
After phase 1, you have:
Agreed project scope, backlog priorities, sprint schedule, and full understanding of risks — before setup begins.
2
Sprint Series
Construct
Analysis, configuration, integrations, tests — sprint after sprint
3 weeks
per sprint
Each sprint includes
→
Analytical workshop with a prototype of the system
→
Configuration/customization of the sprint scope
→
Integrations with external systems
→
Testing the delivered scope
→
Sprint review with key users
→
Planning the next sprint
Tools and rules
ClickUp backlog Prototyp systemu Środowisko sandbox REST API / webhooks Time-boxing Min. kastomizacji
RULE: Product Owner can change backlog priorities before each sprint — flexibility without chaos.
The result of the phase
After phase 2, you have:
A working system in a test environment — your data, your processes, ready for acceptance tests.
3
UAT → Go-Live
Validate, Deploy & Support
Acceptance tests, training, production implementation, support
+90 days
support
Phase Products
→
UAT — e2e customer acceptance tests
→
Train-the-Trainer
→
Video training materials
→
Data migration to the production environment
→
Start-up and intensive support (first 2 weeks)
→
90 days technical support after commissioning
Training model
Train-the-Trainer
Optingo trains Youir Trainers (Key Users). Trainers conduct trainings for Teams. Your company is self-sufficient after the project.
The result of the phase
After phase 3, you have:
Signed acceptance protocol, working production system and team that uses the system independently from day one.
Structure of work

What does a sprint look like?

Every 3 weeks is a complete cycle: from analysis to configuration to testing and review.

One sprint = 3 weeks
Repetitive Rhythm — Predictable Progress
At the end of each sprint: working functionality + plan for the next sprint
Week 1
Analysis and Planning
Analytical workshops with key users
Presentation of the scope on the prototype of the system
Specification of requirements and use cases
Agreeing on the sprint scope for configuration
Week 2
Configuration & Integrations
Creatio System Configuration (no-code Studio
Integrations with external systems (ERP, email)
Building BPM processes and business rules
Documentation of changes in ClickUp
Week 3
Testing & Review
Testing the scope provided by Optingo
Sprint review with key customer users
Acceptance and corrections reported by the Product Owner
Planning the scope of the next sprint
🔵 Online meetings
📋 ClickUp — full transparency
✅ PO approves every sprint
⚡ Range changes before sprint
Project team

Who participates in the project?

The project requires commitment on both sides. Below — what we need from your company and what we bring.

Product Owner
On the customer's side — a key role
•
Manages Product Backlog
•
Approves the range of each sprint
•
Makes design decisions on the business side
•
Participates in sprint review and accepts phase products
•
Availability: ~4—6h per week
Process Owners/Key Users
On the Client's side — content
•
Participate in analytical workshops
•
Formulate and accept business requirements
•
They carry out functional tests in the sprint
•
Target: Trainers for other users
•
Availability: ~2—4h per week
IT/Administrador
On the Customer's side — technical
•
Provides access to integrated systems
•
Responsible for the work on the client's systems
•
Prepares the production environment
•
Target: CRM administrator after implementation
•
Accessibility: according to integration needs
Optingo Team
Project Manager + Consultant + Developer
•
Project Manager — coordination, backlog, communication
•
Creatio consultant — workshops, configuration, processes
•
Developer — integrations, customizations (if required)
•
Conducting Train-the-Trainer trainings
•
90 days of technical support after go-live
Project rules

6 Assumptions That Protect Your Project

Clear rules at the start prevent conflicts and overruns — you know where you stand.

01
Time-boxing
Each sprint has a fixed duration (3 weeks). The scope can be modified by the PO — time and cost remain predictable.
02
MVP Prima
We focus on key business processes first. The system works and is used before we implement the whole thing.
03
Minimum of Customization
We avoid costly programming — configuration instead of code. Customizations only when standard functions are insufficient.
04
Train-the-trainer
We train your coaches — they train the team. Your company is self-sufficient after the project, not dependent on Optingo.
05
Remote work
Most of the work is done online — meetings via Teams/Meet. Without wasting time commuting. Session recordings available in ClickUp.
06
Full transparency
All backlog, task statuses and sprint progress in ClickUp — access for your team 24/7. No hidden actions.

3 week

length of one sprint

6-8

Weeks to MVP

90 days

Support after launch

100%

projects with acceptance protocol

Ready to start Sprint 0?

Schedule a free 30-minute meeting. We will show you what the project looks like for your type of company — with specific stages and schedule.

BOOK A FREE DEMO
CONTACT US
No commitment
Demo tailored to your industry
We respond in 24h