01Group
CRM
Customer records, lifecycle, ownership and revenue operations.
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.
85 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
Authenticated sending, lifecycle communication and delivery monitoring.
03Group
Web and publishing
Structured websites, content operations and commerce experiences.
04Group
Analytics and search
Measurement, search evidence, reporting and conversion research.
05Group
Automation
Connected workflows, monitored exceptions and responsible hand-offs.
06Group
AI and assisted workflows
Research, retrieval and application assistance with human control.
07Group
Advertising and acquisition
Regional campaigns connected to consent, CRM and business outcomes.
08Group
Account research and enrichment
Reviewable account intelligence, contact quality and prospecting operations.
09Group
Cloud and hosting
Application hosting, access controls, releases and recoverable operations.
10Group
Data and storage
Shared records, application databases, access policies and reconciliation.
11Group
Application engineering
Maintainable interfaces, services, code and deployment environments.
12Group
Messaging and distribution
Approved publishing, notifications and response workflows.
13Group
Creative operations
Reusable brand assets, localised creative and editorial review.
14Group
Payments and subscriptions
Payment journeys linked to customer state, service delivery and finance.
Cross-platform architecture and capabilities
Additional guides for connecting tools into a coherent operating system.
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.