YOUR FIRST WEEK

Day one, raw exports.
Day seven, the report your team runs on.

You have exports out of your CRM, your ERP, your retailer portals, your billing system. Here is the week between those files and a reporting surface your team runs on: what the agent builds each day, and what it asks of you.

Hour one

The workspace, before the first chart.

Install the skills, point the agent at a folder, and let it build the ground floor: a landing zone your raw exports are archived into untouched, a naming convention that routes files without ever being trusted as evidence, and an intake loop that pulls fresh exports straight out of your Downloads folder so you never move or rename anything again. It ends by handing you a roadmap of the whole build, with every step that needs you personally marked and waiting.

Skills doing the work: workspace-architecture trust-the-upload

Day 1

Drop your ugliest export on it.

Hand it the file you trust least, or just download one and let the intake loop find it. It reads the bytes before the labels and hunts for the total the file asserts about itself. By the end of the session: your first certified page, every figure tied to the file's own totals.

Skills doing the work: anchor-discovery hostile-exports honest-dataviz

Day 2 to 3

The definitions fight, settled on the record.

The agent starts asking the questions your team has been arguing about by email: which churn, percent of what, gross or net. Answering once, on the record, is the most valuable thing you do all week. Each answer becomes a ruling the system holds forever, and the definition is printed beside the number, so the argument does not come back next month.

Skills doing the work: contested-metrics metric-store glance-test

Mid-week

The first refresh, and the first refusal.

Drop the next cut of the same file. The gates check it before anything publishes: the as-of date, the period it covers, the columns the report depends on. When a cut fails a check, the last good report stays live, the page says a newer cut is under review, and you get a triage list instead of a wrong number in a meeting.

Skills doing the work: trust-the-upload period-freshness verification-practice

Late week

A second system joins, and the gap becomes a finding.

Bring in the export nobody joins with the first. The agent declares the join, discloses the match rate, and keeps each side tied to its own file's totals. The gap between the two systems becomes a number on the page with an explanation. And the Monday deck exports from this same build: charts land in PowerPoint with provenance on every slide.

Skills doing the work: report-design provenance-reproducibility deck-export

When you are ready

The reports become a place.

One address for every report, behind a wall that denies by default, refreshed by dropping in a file, with a live layer your team works in: a task board, a notification hub, shared flags and rulings. The co-pilot walks the Cloudflare setup end to end and hands you the URL. This is the week you stop emailing screenshots. It can be day five or week three; the reports have to earn it first.

Skills doing the work: secure-intranet intranet-copilot delivery-and-alerts

How the week runs. The agent does the building and the checking. You answer the definition questions and make the calls only you can make: which churn, percent of what, gross or net, and what to do with a cut the gate held. Every figure on the page ties to its file's own totals, and anything a file does not prove ships labelled, with the reason on the page. Your time moves from checking every number to ruling on the few that need a human, and every ruling you record becomes a check that runs on every refresh after it.

Own the whole week → Start with the free skill See the end state, live