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 honest, day-by-day shape of the week between those files and a reporting surface people trust. Not a promise of outcomes, a map of the work.

Day 1

Drop your ugliest export on it.

Install the skills (one command, about a minute), open your agent, and hand it the file you trust least. It reads the bytes before the labels: finds the real header, names the traps, and hunts for the total the file asserts about itself. By the end of the session you have your first certified page, where every figure ties to the file's own totals, and a short list of what the file could not prove. That list is not a failure. It is the first honest thing a report has told you in a while.

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. Somewhere this week, a gate will refuse something: a stale export, a wrong period, a column that quietly changed. That refusal is the product working. 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 from the other system, the one nobody joins with the first. The agent declares the join explicitly, discloses the match rate, and keeps each side tied to its own file's totals. The gap between the two systems stops being a mystery and becomes a number on the page with an explanation: what shipped but has not sold, what was billed but has not landed. And when the Monday deck is due, it exports from this same build: charts land in PowerPoint with provenance on every slide, no screenshots.

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

The honest caveats. The week is work: you will answer definition questions, look at refusals, and make calls only you can make. The skills cannot make a vendor's file true, and anything they cannot prove ships labelled or not at all. What changes is where your time goes: from checking everything to ruling on the few things that genuinely need a human. One habit carries the whole week: when the agent asks a judgment question, answer it. Every ruling you record is a check that runs forever.