Marketing agency / Project case study
2023Recorded work
Service intake.
A prepared workspace.
A tested approval handoff.
Marketing agency needed a repeatable way to turn service requests into prepared workspaces and reviewed work. A team-built delivery system connected intake, templates, client documents and approvals; Noah coordinated implementation, maintained templates and repaired task relationships.
- Client
- Marketing agency
- Contribution
- Team coordination, modifications & debugging
- Project status
- Team-built version under test
Tools & working context
Project scope and implementation.
- ClickUp
- Typeform
- Google Drive
- Google Docs
- Google Sheets
- Make
- JSON APIs
01 / Business context
The problem
to solve.
Repeatable agency services need more than a checklist. Intake must supply the right details, documents must reach the right folder and task relationships must survive the creation of client-specific work.
The new version combined service intake, reusable tasks, client files and approval steps. The recordings also show the testing and repair work around those handoffs.
Inside the workflow
A closer look
at the handoffs.
Start with the main path and its branches. Select a step for context, or switch to the technical map for implementation detail.
- Service intake form
Collect the client, requested work and responsible people. - Service-specific branches
Select the appropriate paid acquisition, retention, creative or internal workflow. - Reusable ClickUp templates
Service templates define parent tasks, nested subtasks and relative dates. - Create templated work
Apply the selected structure and carry task-specific assignee information. - Resolve client folder path
Walk the template’s folder-location path to the right client destination. - Copy supporting documents
Create task-specific copies of linked Google Docs and Sheets resources. - Connected client work
Retain parent, child and file references so generated work stays connected. - Subtask status changes
Completion and activation events drive the parent’s next-task context. - Update parent and next task
Keep the project state and next actionable subtask aligned. - Internal and external approval
A narrated test advances the task through distinct approval stages.
Read the workflow notes
- 01 / Prepare
Collect focused service intake
Forms and reusable task structures organized the information for the selected service. Copied client documents supplied a consistent working starting point.
- 02 / Link
Keep the work and files connected
Relative folder paths and templates located the supporting resources. Task relation and parent/child identifiers connected the generated work correctly.
- 03 / Review
Exercise the approval handoff
Debugging covered API payloads and ID mapping. A narrated test progressed through internal and external approval stages, with maintenance instructions for the template structure.
The client was still using its older system while this version was tested. A recurring-task design was separate proposed work, not an established production feature.
03 / Implementation detail
How it
was built.
The template-maintenance walkthrough explains why folder paths and names need to remain aligned with the automation. Changing a visible template is only part of maintaining its connected file structure.
Noah repaired the links between parent tasks, subtasks and supporting files, along with the information sent between systems. Those links let the team find the related work and move approvals through the correct project.
Teammates built several workflow branches and templates. Noah coordinated the work, maintained templates and investigated the problems shown in the recordings.
04 / Outcome & scope
Result
and scope.
The team built and tested a delivery-system version covering service requests, template maintenance and internal and external approval handoffs.
It does not establish migration to the new version, complete client acceptance or measured time savings.