Executive · Weekly review

The weekly review, written before the meeting starts

A meeting that begins with everyone reading the same document is a different meeting.

What the worker does

A weekly business review in Polaris is a recurring task assigned to an AI worker connected to Stripe, HubSpot and Linear. Each Monday the worker assembles the same brief: revenue and its change, pipeline movement, what shipped, and what slipped, with each number sourced. It delivers the brief as a comment before the meeting. Leadership supplies the interpretation and the decisions.

Connections
Stripe · HubSpot · Linear
Cadence
Weekly, delivered before the meeting
Format
Identical structure every week

Same shape, every week, on purpose

The value of a weekly review comes from comparison, and comparison requires that the document does not change shape. When one week's brief has four sections and the next has seven, nobody can tell what moved.

This is precisely what a worker with a fixed skill file is good at and what a busy human is bad at. The person assembling the brief improvises depending on what they had time for. The worker produces the same sections in the same order whether the week was calm or terrible.

The sections worth fixing in the skill file

  • The number and its delta

    Revenue this week against last week and against the same week last month, each sourced from the connection it came from.

  • Pipeline movement

    Deals that changed stage in either direction, and what the movement does to the month.

  • Shipped

    What actually closed in Linear or GitHub, named, rather than a count of issues.

  • Slipped

    Commitments from last week's brief that did not land, carried forward with their age. This section is the one that makes the review honest.

  • Unowned

    Work in the leadership workstreams with no assignee, which is usually where next month's slip is already visible.

How Monday morning goes

  1. 1

    Sunday evening: the task fires

    A cloud machine claims the job. Nobody has to be online for this, which is the point of running workers on a machine rather than a laptop.

  2. 2

    It reads the sources

    Each connection you authorised, in the order set in the skill file, ticking acceptance criteria as sections complete.

  3. 3

    It delivers before the meeting

    One comment on the recurring task, with the document attached and anything it could not read stated plainly rather than left blank.

  4. 4

    Everyone reads first

    The brief is a comment on a shared task, so there is no distribution step and no version confusion.

  5. 5

    The meeting starts at the argument

    Decisions taken become tasks in the same workstream, owned and dated, and appear as slipped or delivered in next week's brief.

Questions people ask

+What if a data source is unavailable?

The delivery says so. A section marked as unread is more useful than a number the worker inferred, and stating what it could not verify is part of how deliveries are written.

+Can different teams get their own version?

Yes. Assign the worker one recurring task per team, each with its own acceptance criteria, and each delivery is a separate comment with its own history.

+Does this need us to move our data into Polaris?

No. The worker reads through connections you authorise once for the organisation, and Stripe, HubSpot and Linear stay where they are.

+How much does a weekly brief cost?

It is billed on human-equivalent hours at about $2 each, calculated from observable effort per session. A brief is a short session, and the line appears on the worker's work log where you can challenge it.

Your next hire takes 60 seconds.

The software is free — unlimited people, tasks, workstreams and docs. You pay only for work an AI worker actually delivers, itemised by the hour.

Get started free

Last checked .