Projects · Mini Hostpapa
Customer Lifecycle & Journey
From first visit to churn: every touchpoint where HostKid wins or loses trust.
Customer Lifecycle & Journey
Forget the tech stack for a minute. A hosting company lives or dies on moments: the five minutes after signup, the first failed invoice, the DNS typo that takes someone's shop offline.
This doc maps the customer lifecycle at executive level. Volume 19 turns the provisioning slice into engineering reality. Here we stay in the customer's shoes.
This page is the main headlines: stages, trust moments, and failure modes. As we research and build, we will add sequence diagrams, portal flows, API contracts, and architecture views (frontend, global system, provisioning). Those land in later volumes when we engineer for real. Read this for orientation, not implementation detail.
Lifecycle stages
Each stage has expectations. Miss them and churn isn't a mystery. It's a receipt.
Stage-by-stage
1. Awareness & evaluation
Customer compares plans, reads docs, checks status page reputation.
We owe them: clear pricing, honest limits, working marketing site, trust signals (security posture doc, uptime story later).
Failure mode: hidden fees, vague “unlimited” claims.
2. Signup & identity
Account created, email verified, maybe payment method captured.
Touchpoints: portal, identity (Volume 9), ERPNext account (Volume 11, Corporate).
Failure mode: signup works but account isn't billable; MFA missing for admin.
3. Purchase & provision
Customer clicks Buy VPS (or shared plan). Money authorized. Provisioning engine fires.
This is the Volume 19 flagship flow. Executive requirement: predictable time-to-service. We'll measure it in Executive metrics.
Nothing destroys trust faster than “payment succeeded” followed by silence for 45 minutes. Status comms matter even in the lab.
4. Onboarding
Customer gets credentials, DNS instructions, first login docs.
We owe: welcome email, getting-started guide, default security nudge (SSH keys, not password-only).
Failure mode: provision succeeded but customer can't find the IP or panel login.
5. Steady use & expand
Site runs, mail flows, maybe they add domains or upgrade SKU.
Touchpoints: portal dashboard, DNS (Vol 12), email (Vol 13), subscription upgrades in ERPNext (Vol 11, Corporate).
Failure mode: upgrade billing works but platform quota doesn't. Classic desync bug.
6. Support & incidents
Something breaks. Ticket opened. Ops engaged.
Executive rule: support is not “free debugging for misconfiguration” forever (boundaries in ToS), but platform faults are always on us.
Volume 23 owns runbooks. Here we only define when the journey breaks trust.
7. Renewal & retention
Subscription renews or customer actively re-commits.
Signals: payment failure (dunning), usage drop, support anger, competitor migration talk.
8. Migration away (churn)
Customer exports, cancels, DNS moves. Offboarding should be dignified. Angry ex-customers talk.
Volume 24 covers migration mechanics. Executive rule: export paths exist (backups, DNS records, docs).
Journey map (executive view)
| Stage | Customer goal | HostKid must deliver |
|---|---|---|
| Signup | Start quickly | Fast, clear account creation |
| First provision | Service exists & reachable | Automated, measured, communicated |
| First week | Site/email works | DNS, SSL, docs, responsive support |
| Growth | More resources / sites | Self-service upgrade, fair limits |
| Incident | Transparency + fix | Status, ETA, postmortem culture |
| Exit | Leave without hostage data | Export, cancel clarity, no dark patterns |
What this doc does not cover
- Portal UI wireframes → Volume 10
- Provisioning queue design → Volume 19
- Ticket system setup → Volume 23
Next: Product portfolio & service catalog. What they're buying at each stage.