The superpower · the intranet co-pilot
The other half of the superpower. Where the intranet skill is the architecture, the co-pilot is the guide: it holds the whole end state in view, always knows the next most valuable step, and walks you from your first export to a working intranet on Cloudflare, provisioning and all.
For the operator who owns the numbers, no data team required.
A complete internal platform has a known shape: the pipeline, the certified reports, the team layer, delivery, access and governance. The co-pilot holds that map and sequences it so each phase ships something that works, with data and reconciliation before pretty pages, never the reverse.
It guides the human-only steps, creating the account and an API token that can touch only what the build needs, then does the mechanical work itself: the Pages project, the database, the workers and the default-deny wall, and it hand-delivers the live URL. The token lives in the environment, never in the chat.
The engine is reusable and the per-instance work is config: source specs and anchors, the roster and zones, branding and rules. Nothing company-specific is hardcoded, so the second intranet is a new configuration, not a fork.
After each phase the co-pilot walks the whole menu and names what an audience will need but has not got, dashboards with no delivery, client zones with no per-viewer slice, without over-building. That is the difference between a folder of reports and a platform. And buying in once buys the road ahead: every paid tier includes lifetime updates, so deeper libraries, more templates, and the self-serve hosted tool ship to you free when they land.