01Group
CRM
Selection, configuration, migration, lifecycle design and reporting.
Platforms
Choose tools by the work they have to support
Platforms are assessed against process, data, integration, governance and long-term ownership. Every listed platform now has a complete implementation guide.
36 platform guidesRequirements firstMigration plannedOwnership defined
01Capability map
Organised by operational purpose
A platform name is not a strategy. Each implementation needs a stated business problem, a scope, a data model, an integration plan and a named owner.
02Group
Authentication, consent, deliverability, templates and automation.
03Group
Web
Build, migration, performance, accessibility and content operations.
04Group
Analytics
Measurement planning, implementation, testing and reporting.
05Group
Automation
Orchestration, exception handling, monitoring and documentation.
06Group
Artificial intelligence and data
Assisted systems, retrieval, data movement and custom services.
02How a platform gets chosen
Four questions before a licence is bought
A recommendation that skips any of these tends to produce a system somebody else has to live with.
Process fit
Does the platform support the way the work has to run, or only the way it demonstrates?
Data ownership
Who owns each field, where the source of truth sits and how it leaves if you do.
Integration cost
What the connections cost to build, and more importantly to keep working.
Who maintains it
Whether the client team can realistically run it once the engagement ends.
Next step
Assess the platformin its operating context
Bring the process, the constraints and the systems already in play. The recommendation follows from those, not from a vendor preference.