Customer implementation template
Manage customer implementation from dependent delivery work through scope decisions, revision-specific acceptance, go-live and support handover.
What is this implementation delivery template?
Launchpath connects delivery projects to customer contacts and sponsors. A project starts with dependent milestones and can record linked risks or blockers. Scope requests preserve the proposed target, scope and impact for a manual decision. Approved changes and material plan edits create a new plan revision; prior customer acceptance becomes historical. Go-live requires completed delivery, resolved risks, no pending scope requests and acceptance for the current revision. Support handover then records the receiving owner, runbook and training evidence, either completing the project or reopening it for follow-up. The built pilot uses ToolJet Database and fictional records; installation and release validation remain pending.
- Screens
- 5 connected pages
- Data source
- ToolJet Database
- Language
- English
- Appearance
- Light + dark
Built for Implementation managers and customer success teams coordinating midmarket customer launches.
Which customer launch needs attention and what is preventing it?
A customer implementation app for delivery projects, dependent milestones, blockers and go-live decisions. Keep the customer contact and delivery evidence connected to the work.
- Delivery portfolio
Find the next customer delivery decision
Search by customer, project or lead and filter project state. Open the matching project from its milestone, acceptance and launch context.
- Projects
Create a customer delivery plan
Create a customer-linked project with a delivery lead, target and scope, then work through the initial milestone plan.
- Delivery workspace
Deliver and resolve risks
Complete prerequisites, record evidence and resolve linked risks or blockers. Material edits create a new plan revision.
- Scope & launch
Decide scope and record acceptance
Review scope requests, record customer acceptance for the exact revision and complete support handover after go-live.
- Customers
Keep delivery contacts connected
Maintain implementation contacts and executive sponsors without removing existing project history.
What does the template cover?
Customer delivery readiness portfolio
Four searchable customer project cards show matching projects ordered by target date, with milestone progress, unresolved risks and acceptance state.
Milestone dependencies and delivery risks
Milestone prerequisites and linked risks block completion. Evidence and material edits are retained; changing reviewed work makes prior acceptance historical.
Scope decisions and fresh acceptance
Scope changes retain their proposed scope, target, requester and impact. Approved requests apply a new revision; stale requests cannot overwrite newer work.
Go-live, handover and remediation
Go-live requires current acceptance and readiness. Support handover captures ownership and evidence, with Accepted or Follow-up required outcomes; reopening requires fresh acceptance.
ToolJet Database with sample data
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Customers | 4 sample customers | Fictional customer organizations with implementation contacts, email addresses and executive sponsors. |
| Projects | 9 sample projects | Five original pilot projects plus four varied enterprise scenarios, including a pending scope change, accepted delivery, live handover and a completed handover. Synthetic QA records are additional. |
English desktop pilot. No external notifications, customer portal, file upload, integrations or enforced independent approval. Customer representative and reviewer names are manual attestations. Evidence is text/reference metadata. Legacy project decisions are preserved without manufacturing current acceptance. Reads are bounded to 1,000 rows per table and writes stop at 1,000 rows per table. Export, installation and enterprise acceptance remain separate gates.
Make it yours with AI.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
How to use this template.
Add it to your workspace
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance once the template is released.
Start with the included database
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Make it work your way
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.
Template FAQs
What does this customer implementation app include?
It includes customer-linked projects, dependent milestones, risks and blockers, scope decisions, customer acceptance, go-live and support handover evidence.
How do scope changes affect acceptance?
Approving a scope request or making a material plan edit creates a new plan revision. Prior acceptance stays in history but cannot authorize launch of the revised plan.
What blocks go-live?
Incomplete milestones, open risks or blockers, pending scope requests and missing current-revision customer acceptance block go-live. The launch owner must also confirm readiness.
Is support handover separate from go-live?
Yes. After go-live, record the receiving owner, runbook and training/access evidence. Accepted completes handover; Follow-up required reopens delivery on a new revision.
Can I change branding and features with AI?
Yes. Prompt AI to change the design, add fields or adapt delivery rules, then test the resulting dependencies, acceptance invalidation and handover behavior before use.
Expense reimbursement
Receive individual expense claims, review receipt references against saved per-expense limits, and record approval or reimbursement.
Security exception management
Track time-limited security exceptions with a risk owner, compensating controls, recorded assessment and remediation evidence.
Employee probation reviews
Coordinate employee probation reviews using role-specific periods, manager feedback, competency scores and documented confirmation or extension decisions.