Four builds, one entry point, and a retainer that keeps it all true.
Every engagement is fixed fee with a written scope, a working agreement on change control in production, and a documented handover your team can maintain. If you do not know which one you need, start with the audit.
Planhat implementation
New instance or rescue. Operating model first, data model and integrations second, scoring and automation third, dashboards last.
02 · Estate workAutomation and data architecture
Automation audit and catalogue, property data dictionary, consolidation with written rollback, multi-level hierarchy rollups that reconcile.
03 · PredictionHealth scoring that is backtested
Designed from your renewal and churn history, weighted by what predicted the outcome, validated on a holdout set, surfaced where the CSM plans the week.
04 · Revenue visibilityTeam cockpits and NRR reporting
Targets in, gap and week-over-week movement at every level, forecast against actual, and a prioritisation layer with an action log.
Planhat estate audit
Two weeks inside your instance. A written map of every automation, property and integration, a ranked fix list, and a fixed-fee proposal for the fixes.
See the audit After the buildEstate stewardship retainer
A monthly block of senior hours that keeps the estate and its documentation true as the platform, the data and the team change.
How retainers workWhere the work happens.
Planhat is the platform we know from the inside. The data layer around it is where most of the value gets made or lost.
Not sure which one you need?
That is what the strategy call is for. Thirty minutes, a specific read on your instance, and a recommended order of operations whether or not we work together.