# BlueHill for SaaS implementation teams > How SaaS companies run customer implementation on BlueHill — relative-date onboarding templates, form-driven data collection, portal status visibility, time-to-value analytics. ## The implementation team job, in plain English The implementation team is the unsung hero of SaaS retention. Their job: get a new customer from "signed contract" to "in production using the product as intended" as fast as possible without burning the customer out on setup work. The metric that matters is **time-to-value (TTV)** — the days between contract signature and the customer hitting the value moment (first dashboard view, first integration synced, first invitation sent to their team — whatever your product defines as activation). Every day of TTV delay correlates with churn risk. The implementation team is the team that owns those days. BlueHill is built to compress them. ## The implementation flow on BlueHill ### Step 1: Template per product tier Build a [relative-date onboarding template](/features/onboarding) per product tier or per customer segment: ``` Template: "Enterprise customer onboarding" Day 0: Kickoff call (calendar invite) Day 1: Account provisioning form (admins, SSO config, user list) — Form Day 3: Integration setup (CRM connection, identity provider) — task + form Day 7: Pilot user training session Day 10: Production rollout to remaining users Day 14: First success milestone check-in Day 30: Hand-off to CSM ``` The template is built once per tier. Every new customer at that tier gets it cloned with dates auto-scheduled. ### Step 2: Forms collect data, not emails Each form ([Forms model](/features/forms)) captures structured data the implementation needs: - **Account details form** — company info, billing contact, primary admin - **Integration credentials form** — securely captured (BlueHill encrypts at rest) - **User provisioning form** — emails + roles for bulk-creation - **Brand assets form** — for branded portals Forms are portal-completable. The customer fills them on their own time. Submissions land as FormSubmissions linked to the customer + the relevant CustomerTask. The implementation specialist sees "form submitted at 14:32" rather than scrolling email for the third time. ### Step 3: Portal-driven status visibility The customer's [portal view](/features/customer-portal) shows their implementation plan — which tasks are done, which are in progress, which are blocked on their input. Three portal-specific fields drive the experience: - `portal_status` — what the customer sees as the current step - `portal_start` — when they last marked the task in-progress - `portal_complete` — when they marked it done The customer doesn't have to email "are we on track?" because they can see for themselves. ### Step 4: Internal coordination via team-collaboration layer Inside the implementation team: - [Internal notes](/features/team-collaboration) capture risks ("their IT team is dragging on SSO config — escalate by Friday") - `@mentions` notify the right person - The activity timeline records every state change The customer sees the portal. The team sees the internal layer. Two distinct realities, one customer record. ### Step 5: Time-to-value analytics The [analytics layer](/features/analytics) computes TTV from the activity log: - Mean TTV by template (which segment is slowest?) - TTV variance (which segments have unpredictable implementations?) - Stage-level cycle time (which step is the bottleneck?) - TTV by specialist (training opportunities) TTV becomes an operational metric — moved by changing the template, not by exhortation. ## A representative day for an implementation specialist **9am**: dashboard review. 18 active implementations. 3 have form submissions to review from overnight. 1 is approaching the 14-day TTV target and behind — needs a push. **9:30am**: review the 3 form submissions. Two are clean. One has a wrong SSO config — leave an internal note for the IT-coordination call, send a friendly portal message asking the customer to confirm a detail. **10am-12pm**: customer calls. Three kickoff-or-checkpoint calls. The customer record is open in each — full context, latest portal state, pending tasks all visible. **Lunch**: a new customer signs. Apply the "Enterprise onboarding" template, set kickoff date, send the first form invite. 90 seconds of work. **Afternoon**: the at-risk customer from this morning. Open their record, see the bottleneck (IT hasn't responded to the SSO config request in 5 days). Escalate via internal note + email to the customer's primary contact. **End of day**: 2 implementations cleared the "first success milestone" stage today. Time-block tomorrow for the hand-off prep call with the CSM team. ## Outcomes SaaS implementation teams report After 90 days on BlueHill (averaged across teams that switched from "PM tool + Google Forms + shared spreadsheet"): - **Mean time-to-value**: 12 days → 4 days - **Implementations per specialist per month**: 8 → 14 - **Stalled implementations >30 days**: 22% → 6% - **Customer-side "are we on track?" emails**: -75% - **Hand-off quality (CSM-rated, 1-5 scale)**: 3.2 → 4.6 ## Where BlueHill fits the SaaS journey | Stage | Tool | |---|---| | Sales / pre-contract | Your CRM (HubSpot, Salesforce, Pipedrive) | | Contract → activation (implementation) | **BlueHill** | | Activation → retention (CSM) | BlueHill, or BlueHill + Gainsight at scale | | Expansion / renewal | BlueHill + your CRM for opportunities | | Support | BlueHill ticketing | The clean fit is implementation + early-CSM + support. Past ~1000 customers, dedicated CSM platforms add value layered on top. ## Pricing for SaaS teams Most SaaS implementation teams land on **Professional** ($79/user/month) for the full feature set: forms, portal, analytics, time tracking. Enterprise tier kicks in around 30+ specialists for SSO and custom workflow needs. [See pricing](/pricing) · [Read customer stories](/customers) ## What this replaces SaaS implementation teams arriving at BlueHill typically replace: - A project management tool (Monday, ClickUp, Asana) - Google Forms / Typeform for data collection - A shared Google Sheet tracking implementation status - Notion for internal implementation notes - An ad-hoc email workflow for customer updates The consolidation matters, but the bigger win is the portal — customers stop stalling because they can see status without asking. ## See also - [BlueHill vs Monday.com](/compare/monday) — the most common switch for SaaS implementation