How to scope a Creatio implementation in 5 working sessions

Most CRM projects don't fail during build. They fail during scoping, when nobody writes down what 'done' means and every stakeholder leaves the room with a different picture in their head. The fix isn't a longer discovery phase — it's five focused working sessions with the right people and a written artifact at the end of each one.

Here is the sequence we run with clients before we quote a Creatio implementation. Each session is 90 minutes, has a named decision-maker in the room, and produces one document. Five sessions, roughly three weeks of calendar time, and you have a statement of work someone can actually sign.

Session 1 — Outcomes, not features

Start with the business result, not the software. Ask each leader in the room to finish this sentence: 'Twelve months after go-live, this project was worth it because ___.' You will get answers like shorter sales cycles, fewer manual handoffs between sales and delivery, or accurate forecasting for the first time.

Write down three to five outcomes and, for each, the number you would look at to know it happened. If nobody can name the number, the outcome is aspiration, not scope. Park it.

Output

A one-page outcome list with an owner and a measure per line. Everything you build later gets traced back to a line on this page.

Session 2 — The process walk

Walk the end-to-end process the way work actually flows today: lead arrives, gets qualified, becomes an opportunity, gets quoted, gets won, gets handed to delivery, gets invoiced. Draw it on a whiteboard with the practitioners who do the work, not the managers who describe it.

Two things to hunt for: places where information is re-keyed into another system, and places where work sits waiting on a person. Those are your automation candidates, and they are usually where the return on the project lives.

Output

A current-state process map with re-keying points and wait states marked, plus a first-pass future-state map showing which steps Creatio absorbs.

Session 3 — Data reality check

This is the session teams want to skip and later wish they hadn't. Pull the actual records out of the current system — CRM, spreadsheets, the shared inbox, the finance system — and look at them together.

• How many duplicate accounts exist, and what rule identifies a duplicate?
• Which fields are required today, and which are actually populated?
• Where does the system of record change hands (marketing to sales, sales to delivery, delivery to finance)?
• What history genuinely needs to migrate, and what only needs to be archived and readable?

Migration scope is usually the single largest variance in an implementation estimate. An honest hour here is worth a week of change orders later.

Output

A migration inventory: objects, record counts, cleanup rules, and an explicit list of what will not be migrated.

Session 4 — Integrations and identity

Creatio rarely lives alone. List every system it must exchange data with and, for each one, answer four questions: which direction does data flow, how often, who owns the field mapping, and what happens when the integration fails at 2am?

Do the same for identity. Single sign-on, user provisioning, and role structure are small decisions that become expensive if they surface after build has started. Agree on the role model now — sales rep, sales manager, delivery, finance, admin — and what each role can see.

Output

An integration register with direction, frequency, owner, and failure behavior per interface, plus a role and permissions matrix.

Session 5 — Phasing and the go-live bar

The final session is a prioritization exercise. Take everything from sessions two through four and sort it into three buckets: needed at go-live, needed within 90 days, and genuinely later. Be ruthless. A tight first release that people adopt beats a complete one they resent.

Then define the go-live bar in plain language — the specific things that must be true for you to switch off the old system. For example: every open opportunity is in Creatio, quotes generate from templates, and the weekly pipeline report runs from the dashboard rather than a spreadsheet.

Output

A phased scope with a written go-live definition. This becomes the backbone of the statement of work.

What to watch for

• No decision-maker in the room. If approvals happen afterwards by email, you will re-run the session.
• Feature lists instead of outcomes. 'We need a custom dashboard' is a solution; ask what decision the dashboard supports.
• Skipping the data session. Data quality is the most common cause of estimate overrun.
• Treating the process map as final. It is a working draft; expect it to change once users touch a configured system.

The point

Five sessions won't give you a perfect plan. They will give you a shared, written understanding of what you are buying and what you are deferring — which is what makes the estimate defensible and the project governable.

If a scope document can't be traced back to a business outcome and a number, it's a wish list with a budget attached.