[ LIVE SERVICE · AUTO-BUILT FROM YOUR REPO ]

Your team help page

A living help site for your team that rebuilds itself from your own workflows every time the system changes. Role-grouped tasks, copy-paste briefs, SOPs, and a changelog, always current.

This portal is our documentation for you. The team help page is your documentation for your team, and the difference that matters is that it maintains itself. Every time you change a workflow, the help page rebuilds from your own files. It can't drift out of date, because nobody writes it by hand.

A live service that deploys from your repo. It's generated from your workflows' own descriptions, so it's always an exact mirror of what your system actually does today.

What it is

A private, fast help site for the people who run your system day to day. It is not this portal (that's ours, about the install). This is theirs, about the doing:

• Common tasks grouped by role. Your media buyer sees media-buyer tasks, your ops person sees ops tasks. Each task has a "say this" example, the exact phrasing to hand the terminal.
• Copy-paste briefs. The ten most common jobs, pre-written with every field the workflow needs, so a colleague gets it right the first time instead of digging through chat history.
• SOPs for the flows that matter. Step-by-step, with the preflight checklist and the known gotchas baked in.
• A "what's new" changelog. Every workflow improvement and new capability lands here automatically, so the team sees what changed without reading commit logs.
• An optional login wall. Gate it behind a company email if you want it private to your team.

The part that makes it different

It rebuilds itself. When we (or later, your own team) add or change a workflow, the help page regenerates from that workflow's own description on the next push and redeploys on its own. There's no separate "update the docs" step to forget. The single most common reason internal wikis rot, that updating them is a manual chore nobody owns, simply doesn't apply.

Proven, and you're looking at its sibling

Our own agency runs one of these. It's the overview our whole team works from: every skill, every agent, the role-grouped tasks and SOPs, rebuilt automatically on every change. This client portal is built with the same generator, reskinned. So you've already seen the engine, you're reading a page it produced right now.

How it's delivered

It's generated from your repo and deployed to a URL you control (help.youragency.com if you want the custom domain). During the Install phase we stand up your version, pointed at your workflows and reskinned to your brand. After that it's automatic: your system changes, your help page updates, no one lifts a finger.

Where it fits in your rollout

Your help page goes live during the install, carrying only the workflows you've actually installed (not all fifty, per the anti-overwhelm rule). It grows exactly as your system grows. By the training phase, every person has a page that speaks their role, and their own Claude can answer "how do I do X" from the same source of truth.