Pipeline CRM
Deal stages, forecasting and activity history for a sales team that has outgrown a spreadsheet.
Next.js · TypeScript · PostgreSQL · Tailwind
Explore
From $549
PortfolioCSM1 / 8
CRM & Sales
RetentionLive
Customer Success Hub
Everything a CSM needs to answer one question before the renewal call: is this account getting value, and can I prove it?
- From
- $649
- Function
- 23
- Roles
- 3
- Users
- Unlimited
Next.js · TypeScript · PostgreSQL · Recharts
Inside the app
What it does out of the box
23 connected functions on one schema, spanning three permission levels. Everything below is in the template before a line of customisation.
Portfolio
Opens on contract value, healthy accounts and revenue at risk, with a twelve-week usage trend beside them. Usage moves weeks before a renewal conversation does.
Book of business
Every account filtered by health, stage and segment, sorted worst-health first by default because that is the order the work actually arrives in.
Renewals
Upcoming, negotiating and committed, each with a probability and a countdown. The weighted number is the one you defend in a forecast meeting.
Automation
Rules written as trigger, condition and actions, with a log of what each one did. A rule that fires with no record is a rule nobody trusts.
Reports
Health mix, churn trend, renewal forecast, adoption by segment, task completion, lifecycle funnel and workload by CSM. All the monthly questions in one place.
Notifications
What the rules raised and what was emailed on your behalf, in one centre. Turning a rule off stops the noise at source rather than hiding it.
Integrations
Which sources are connected, and plainly what the health model loses without each one. It keeps working on fewer signals rather than breaking.
Health model
The weights behind every score, with a live preview of how many accounts would change band before you apply it. Nobody is told until you do.
Permissions
Three roles, one build
A CSM sees their own book. A team lead sees the whole team and the risk pipeline. An administrator owns the scoring model. Every level is included, and the boundaries are enforced on the server rather than by hiding buttons.
CSM11 functions
Their own book of accounts
- Work an assigned book of accounts
- See health scores and what drives them
- Track renewals by notice date
- Run risk and expansion playbooks
- Assemble a QBR pack without rebuilding it
Team Lead17 functions
The whole team, plus their own book
- Everything a CSM can do
- Coverage and load across every CSM
- Risk pipeline ordered by revenue at stake
- Reassign accounts between owners
- Join or escalate a save conversation
Administrator23 functions
The scoring model behind every number
- Everything a team lead can do
- Set the health scoring weights and bands
- Publish and version the playbook library
- Read and export the audit log
- Control who can change the model
The build
Every function in the box
23 functions, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.
Access
- Sign in
Workspace
- Dashboard
- My accounts
- Health scores
- Renewals
Programme
- Playbooks
- QBR builder
Management
- Team book
- Risk pipeline
Administration
- Scoring model
- Audit log
What you get
Delivered as a repository, not a login.
Post-sale teams managing 50–2,000 accounts who track renewals in a spreadsheet and hope.
- 11 production functions spanning three permission levels
- Full source code and PostgreSQL schema in your repository
- Role-based access control, enforced server-side
- Immutable audit log written on every change
- Responsive layouts, usable on a phone, not just resized
- CSV import and export on every core record
- Deployment configuration for your cloud account
- Twelve months of updates, and no per-seat charge ever
Access and evidence
Built to survive a revenue review
When a renewal is lost, the first question is always what changed and who knew. Both are answered by the data model rather than by a report someone assembles after the fact.
- Row-level permissions, enforced server-side on every query
- Immutable audit entry on every score, owner and playbook change
- Score history retained, so a drop can always be explained
- Seven-year retention with a one-click export
- Account notes scoped to the owning team
- SSO, two-factor and CRM sync available in a fitted build
- Self-hosted, so customer data never leaves infrastructure you control
Related
Apps that pair with this one
Partner Portal
A whole partner programme in one app: deal registration, a gated resource library, training, funding requests and tier performance.
Next.js · TypeScript · PostgreSQL · Auth.js
Explore
From $549
Operations ERP Suite
The full ERP spine: orders, CRM, production, stock, purchasing, projects, finance, approvals, reporting, people and automation.
Next.js · TypeScript · PostgreSQL · Recharts
Explore
From $899
Questions
Customer Success Hub, in practical terms
Do I get the source code for Customer Success Hub?
Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery. There is no licence key and nothing that calls home.
How many people can use it?
As many as you like, across all three roles. Pricing is per application, not per user, so putting the whole customer success org on it costs the same as putting one pod on it.
Can we change how the health score is calculated?
Yes, and without a developer. The weights, the data sources behind each factor and the band thresholds are all editable by an administrator, versioned, and applied on the next nightly run. The contributing factors stay visible to every CSM so nobody argues with a black box.
Does it replace our CRM?
No, and it should not try to. It is the post-sale workspace that sits alongside the CRM. A fitted build syncs accounts, contacts and contract values both ways, so the CRM stays the system of record for the commercial relationship.
Can Customer Success Hub be changed to match our process?
That is the usual route. A fitted build adjusts segments, health factors, playbook steps, renewal notice rules, branding and up to two integrations, and typically takes one to three weeks from a signed scope.
What does it cost to run?
Hosting only, paid to your own cloud provider, roughly $50 to $200 a month depending on account volume and telemetry. There is no recurring fee to us unless you choose managed hosting.
Want Customer Success Hub shaped around your process?
A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.
