Creatio implementation partner for Canada and the United States
Since 2001 we have designed, built and supported CRM from Vancouver for clients in Canada and the United States: process design, configuration, integration, custom applications and support.
- One system for records, processes and approvals — the process engine
- Your records can be stored in Canada: Creatio Cloud’s Ontario region, written into the contract — why Creatio
- AI agents work inside the roles and approvals you already have — the 10x release
The diagram is the process
A Creatio process as we would draw it in the BPMN 2.0 Process Designer. Every process model is executable, not just documented, so the map your operations team approves in Discovery is the one that runs.
- An opportunity enters the Proposal stage — a signal start fires.
- Creatio reads the opportunity and its account, and a Formula computes the discount from list price.
- A gateway asks: is the discount over 15 percent? If not, the quote continues on the default path.
- If so, an Approval task asks the sales director to approve the discount.
- Declined: the owner gets a Perform task to revise the quote, and the process ends there.
- Approved: a Call web service creates the quote in the ERP, and Modify data writes the ERP quote number back.
- Creatio emails the quote to the customer and waits three days on a timer.
- The owner gets a Perform task for the follow-up call, and the process ends.
When a step changes, the diagram changes where its owners can see it. An agent from Creatio AI Studio takes one step, and a person’s Approval follows it.
Why one system, and why this one
Four properties let day-to-day work consolidate in Creatio rather than fragment.
One place for the day’s work
The record, its process stage and the next task share one screen, so where a request stands is something anyone with the role can see rather than a question sent round by email.
Connected, not copied
Your finance system, your ERP and your website stay. They read and write the same Creatio records over secured, standard connections.
Canada, or the region you choose
Ontario, Canada is one of nine Creatio Cloud regions on AWS and Microsoft Azure, and on-site deployment is offered. Creatio publishes a SOC 2 Type II report and states ISO/IEC 27001 for its cloud services.
Configure first, code when needed
Most of what your people see is configured, not programmed. A changed page, field or rule is a configuration change your systems manager can review, not a development project.
Creatio partner (listed as Integrator) Implementation partnerWhere the product stops, you build on
Processes the standard product does not cover are where the spreadsheet comes back. In Creatio they become applications on the same users, data and permissions: an intake form, an approval that turns on contract type, an inspection checklist.
For your systems managerThe tooling, by name
The elements in the diagram above
- User actions (Approval, Perform task): a person acts, the approver on the Approvals tab or by email, the owner on a task
- System actions (Read data, Formula, Call web service, Modify data, Send email): the engine acts on records, arithmetic, a call to the ERP’s web service and mail
- Events (Signal start, Wait for timer, Terminate end): a stage change starts it, a timer holds it three days, an end closes it
- Gateways and flows (Exclusive (OR), conditional flow, default flow): the route branches on the discount and on the approval result
Integration
- OData 4 REST endpoints: your other systems read and write Creatio records
- The Call web service element: a process calls out to another system
- OAuth 2.0 on every external request, configured without code
Process engine
- BPMN 2.0 Process Designer: events, activities, gateways and lanes, drawn by drag and drop
- Approval as its own element: a named employee, their manager or anyone in a role approves, on the Approvals tab or by email, with delegation available
- Dynamic cases for work that does not follow one path: stages and their steps, with the route decided by the record
- Process versions: a change is saved as the current version or a new one, whatever instances are running
- A process log with the numbers an operations team asks for: how many completed, how long they took, how many tasks
- BPMN file import, so a map drawn in another tool is a starting point rather than a redraw
Custom applications
- Application Hub: build a new application beside the CRM, on the same users, roles and data
- Freedom UI Designer: pages assembled by drag and drop, so a screen changes without a developer
- Visual data model design: your objects, fields and relationships, defined where your systems manager can review them
- A library of no-code components, plus custom components we build once and your people reuse
- Creatio Marketplace: connectors and add-ons already built, checked before we build the same thing again
Mobile Creatio
- iOS and Android, with workplaces and sections set per role in the Mobile Application Wizard
- Freedom UI Mobile Designer: a visual drag-and-drop editor for the screens your field staff see
- Online, hybrid and offline modes, so a lost signal need not mean a lost record
- Business rules configured without code, and a barcode scanner component for stock, assets and site visits
The same process, on a phone
Mobile Creatio puts each role’s part of the process on a phone: a technician’s jobs, a rep’s calls, a manager’s queue. iOS and Android, online or offline; the screens per role are listed under custom applications.
Scale up, and back down
The licence you sign should not fix the size of your team. Creatio’s composable structure combines products, apps and user types and changes as needs change; when a reduction takes effect is a contract term we check.
Growth or Enterprise, per user; a per-organization plan also exists
Creatio Sales, Creatio Marketing, Creatio Service
Customer 360, Lead and Opportunity Management, Case Management
Mobile-Only, External, Restricted Data Input
No prices here: the structure is Creatio’s, and we model the options against your usage in Discovery.
New agents, the same approvals
The 10x release of 15 July 2026 matters because agents now run inside the same roles and approvals as everything else.
Creatio AI Studio
Prompt and workflow agent designers with policy enforcement, human-in-the-loop approvals, monitoring and audit. Our rules on top: a person releases anything a customer sees, and the model behind an agent stays your choice.
AI Twin
An employee describes a task and gets a personal agent for it. We deploy it like any other agent, inside your permission model.
CRM additions
Sales sequences, MEDDPICC and a Customer Communication Hub arrived with 10x: product features, not custom work. We check which ones your mapped process needs.
“10x” is Creatio’s figure, a ceiling rather than a promise: where it comes from and where it stops.
Three things to settle before the build
Map the process before the agent
An agent added to a broken process makes it fail faster. So the people who run the process draw and agree it first; an agent then takes named steps in that model.
The upgrade is its own project
Creatio AI Studio ships with 10x, so an earlier version means an upgrade before any agent: list what was customized, test it, stage the release, pick a quiet week.
Configuration or custom app, decided early
Most of what a program needs is configuration; some of it is a custom application. The line decides cost, upgrade risk and who maintains it, so we draw it in writing before the build.
Creatio, in practice
Mapping, validation and monitoring are built with the integration, not added when it fails. Every connection has a defined owner, a documented mapping, and a check that says when a record did not arrive — so a broken sync is a message to a person, not a discovery three months later in a report.
Where a system offers a supported API we use it; where it offers only a file drop, we tell you and design for the failure modes that brings.
Yes. Integrations, automation services and middleware are deployed directly into your own Google Cloud project or Microsoft Azure tenant, so data stays inside your security boundary. Canadian data residency is available — Creatio Cloud’s Ontario region, or your own Azure or Google Cloud Canadian region — and is written into the contract, along with the specific handling and retention terms, per engagement.
Yes, and it is usually better that way. The process maps and the baseline are about your work, not about a product, and a platform decision made after them is made against requirements rather than a demo.
Most of our work runs on Creatio. If your requirements point to another CRM, we will tell you, and tell you what to ask its partners: the recommendation follows the requirements.
Not answered here? Ask us directly — we reply by the end of the next business day.
Updated : we now write “United States” in full instead of “US”. Written against Creatio 10x — if a release since then has moved something on this page, tell us and we will fix it.
Platform facts on this page are Creatio’s own statements — sources. Kewl Consulting is a Creatio implementation partner; the judgments are ours.
- Creatio on BPMN and Process Designer basics (versions, flows)
- OAuth 2.0 authorization and OData basics, Creatio Academy
- SOC 2 Type II report announcement, 1 February 2024 — ask Creatio for the current report
- Creatio Cloud (data centres) and Creatio Studio (no-code tooling)
- Mobile Creatio and the Freedom UI Mobile Designer, Creatio Academy
- Composable pricing, 20 July 2023, and its May 2026 update
- The 10x announcement, 15 July 2026
The system your people open first is the one that lasts
Bring a process that lives in a spreadsheet. We will say what belongs in Creatio and what does not.