Case study · Project delivery systems
A reusable ClickUp delivery system for projects, requests, QA, and client feedback
Excelerator AI needed a repeatable way to onboard each client, manage new projects and ongoing requests, enforce quality checks, capture feedback, surface blockers, and support delivered work. ClearKnot designed and implemented that operating system in ClickUp.
- Project or request intake
- Shared nine-stage pipeline
- Testing Passed gate
- Client Review and UAT
- Delivery
- 30-day hypercare
Project snapshot
- Client
- Excelerator AI
- Engagement
- ClickUp delivery system architecture and implementation
- Work covered
- Projects, requests, changes, bugs, data issues, client feedback, QA, UAT, deployment, and hypercare
- Delivered system
- Reusable client folder, 9 shared statuses, 5 task templates, 6 tested automations, structured fields, and client request form
- Status
- Complete, tested, and ready for client onboarding
The challenge
Two kinds of work, one pipeline that had to stay under control
Projects and requests required different internal phases but needed one controlled delivery pipeline.
The system had to keep scope, ownership, billing references, blockers, and client context on the work; prevent untested work from reaching the client; capture UAT feedback; alert the project manager to blockers; and track a 30-day hypercare period.
Requirements and constraints
What the system had to guarantee
Each requirement below became a structural rule rather than a habit the team had to remember.
- Scope, ownership, billing references, blockers, and client context stay on the work item.
- Untested work cannot reach the client.
- Client feedback and UAT findings are captured on a dedicated path.
- Blockers alert the project manager rather than waiting for a status meeting.
- Delivered work is supported for a tracked 30-day hypercare period.
Audit → Architect → Implement → Optimize
Mapped project, request, QA, review, deployment, blocker, and support paths.
Designed the reusable client folder, shared pipeline, fields, templates, UAT path, and control rules.
Configured 9 statuses, 5 templates, 6 automations, the request form, and the operating documentation.
Strengthened the two-way QA gate, made the client folder importable, corrected checklist persistence, removed test content, and retained deliberate manual controls where native ClickUp behavior was limited.
Completed projects
What ClearKnot built
The delivered system
- A reusable client workspace created through Create New → Choose Template.
- One nine-stage pipeline shared by projects and requests.
- Full, Light, Enhancement, Request, and UAT Finding templates.
- A two-way Testing Passed gate before and during Client Review.
- Structured request and feedback intake with a dedicated UAT findings path.
- Blocker controls that record the blocked date and notify the project manager.
- Automatic creation of a 30-day hypercare window at Delivery.
- Complete operating documentation and an end-to-end workflow diagram.
Problem-solving decisions
The QA gate works in both directions
Testing Passed is required before Client Review opens, and a new UAT finding clears it again — so work cannot quietly return to the client without being retested.
Manual controls were kept where automation would have been unreliable
Where native ClickUp behavior was limited, deliberate manual control points were retained instead of automations that would appear to work and then fail silently.
The client folder was made importable
The workspace is reproduced per client from a template rather than rebuilt, which is what makes the same delivery controls apply to every engagement.
Test content was removed before handoff
The delivered folder contains no test tasks, so the first real client project starts from a clean structure.
Verified outcome
Complete, tested, documented and ready to reproduce
At handoff, the delivery system was complete, tested, cleared of test content, documented, and ready to reproduce for each client.
It gives Excelerator AI one visible operating model for project and request delivery while retaining the different phases each type of work requires.
Measurement note: Time-saved, throughput, adoption, satisfaction and financial claims are not published for this project. They will be added only when approved evidence is available.
Project evidence
Client screenshots are not published without written approval. The diagrams below are reconstructed from the delivered architecture and contain no client data.
- Create New → Choose Template
- Nine-stage pipeline
- Structured fields
- Client request form
- Full
- Light
- Enhancement
- Request
- UAT Finding
- Work item ready
- Testing Passed set
- Client Review opens
- UAT finding clears Testing Passed
- Retest, then Client Review again
- Changes
- Bugs
- Data issues
- UAT Finding template
- Routed into the delivery pipeline
- Blocked date recorded
- Project manager notified
- 30-day window created at Delivery
Related services
The services behind this build.
Does your delivery process rely on people remembering the next step?
ClearKnot audits how work moves across clients, tools, approvals, delivery, and reporting—then shows you where ownership, handoffs, and controls need to change.