Handoff Atlas

• 

  Fictional Larkfield Repairs journey baseline

• 

  Compare customer waiting with staff work

• 

  Choose and edit a handoff in the journey

Why I built it

A slow customer journey is often called “too much admin”, even when most of the elapsed time is waiting between people and systems. Handoff Atlas makes those two quantities visible before anyone claims an automation will save labour.

What it does

The app maps a fictional five-step enquiry journey for Larkfield Repairs. Its quote step, for example, takes 20 minutes of hands-on work but includes 20 hours of customer waiting. Select and edit a handoff, propose a smaller wait or workload, and see the before-and-after totals immediately. Download a Markdown brief with the chosen change, inputs, calculations and assumptions.

How it was built

This new, dependency-free JavaScript browser app was scoped with the official Devpost Learn Skill Pack. The public repository includes source, run instructions, and draft scope.md, prd.md and spec.md. Codex assisted with implementation and tests. Those planning documents are agent-proposed drafts, not personally reviewed learner notes.

Challenge and learning

Reducing customer waiting is not automatically the same as reducing staff labour. The calculation and copy preserve that distinction. Scoping one complete journey made the idea testable; using fictional figures and browser-only calculations made assumptions visible without implying a measured business outcome.

What is next

Try the method with consented, real enquiry timestamps, validate where waits occur, and only then decide whether a CRM or automation change is justified. This is a proof of concept, not a client deployment.

Run locally with Node.js 20+: clone the repository, run node server.mjs, then open http://localhost:4173. No packages, account or API key are needed. Built by ImpactLayer.

Built With

• javascript
• node.js