For finance teams and owner-led businesses

Most month-end hours go to carrying files.

Download, paste, attach, send. Somebody on your team is the cable between the accounting system, Excel and the inbox. Pick a recurring process, mark which steps move information and which need judgment, and see what the moving costs you. Then the order to automate it in, and where a person still signs.

  • 8 recurring processes
  • Your numbers, not a benchmark
  • Approval gates built in
  • Companion workbook

Pick a process   Map the steps

The processes

Where the carrying happens.

Each one is a job your team already runs every week or month. Pick the ones that sound like your shop. The first one is the classic: one report per cost centre, sent to the right budget owner.

    Nothing picked yet.

    Map the steps

    Find the work between the work

    Mark every step for what it really is.

    Move means information going from one place to another. Process means fixed rules. Judge means a person deciding what the numbers mean. Approve means someone signs. Change any tag or minute count.

    StepTypeMinutes per run

      Is it worth it?

      What the carrying costs you.

      The moving minutes come from the map above. Change anything. These are your assumptions, not an industry figure.

      One report per cost centre counts as one run. A team with 148 cost centres enters 148.

      Filled from the map. Overwrite it if your team is faster or slower.

      Per cent. Someone still reviews the dry run and handles exceptions, so 100 is not an option.

      Moving hours a month today0
      Hours back per year0
      Value of those hours, first year$0
      Net after the build$0
      Payback—

      Choose the connection

      No API is no longer the end of the conversation.

      There are three ways to get information out of a system without a person in the middle. Use the simplest one that is reliable. Answer three questions about the system you are stuck on.

      Does it have an approved connector or API your IT team will allow?

      Can it email or drop a scheduled export on its own?

      Does every login ask for a code from a phone (MFA)?

      • 1. Connect directlyAn approved connector, API or MCP connection reads the data where it lives. Start read-only. Give write access only to the step that needs it.
      • 2. Automate the exportThe system schedules its own export to a fixed folder. A workflow tool picks it up, so the AI always works on the latest file without anyone uploading it.
      • 3. Let an agent use the screenFor portals with no API, a browser agent logs in, picks the period and downloads the report the way a person would. It stops and asks when it hits a code or an error.

      Build order

      Map first. Connect second. Send last.

      Teams that start with the tool usually automate the wrong step. This order holds for every process above.

      1. Map the whole journeyFrom the source system to the person who uses the result. Tag every step. The waste is rarely the analysis; it is collecting files from five places every Monday.
      2. Pick the simplest reliable connectionConnector if one exists, scheduled export if it does not, screen agent for the portals with neither. Write down what happens when a file is missing or a login fails.
      3. Give the recurring run to a scheduled agentNot a prompt someone remembers to paste. It checks the source is ready, collects the files, confirms the period, logs what it did, and stops with a clear message when something is off.
      4. Connect the next action, with a gateDistribution, a draft journal, a forecast update. Run it dry first: the proposed send list goes to a reviewer, and nothing leaves until they approve it.

      Where a person signs

      Faster is only useful if you trust it.

      These rules are the reason the output can be used on real numbers.

      • Dry run before any sendThe agent proposes who gets which file. A reviewer checks for missing files, duplicate recipients and anyone receiving another department's numbers, then approves.
      • Formulas calculate, AI does notVariances, totals and forecasts are Excel formulas tied to the source, with a control tab. AI drafts structure and commentary. It never types a number.
      • Read-only by defaultAccess to bank, payroll and the ledger starts read-only. Nothing moves money, posts an entry or changes source data.
      • Every run is loggedWhat was collected, from where, for which period, what was sent to whom, and who approved it. If you cannot answer that, do not run it on real numbers.

      The companion workbook

      Eight sheets, live formulas.

      The step map and the cost above as a spreadsheet you can argue with, a cost-centre report pack with an owner table, a dry-run check that catches missing files and wrong recipients before anything sends, a delivery log, the connection chooser and the build order.

      One email with the workbook. No sequence.

      The offer

      One report, mapped, on me.

      Write down the steps your team takes to produce and send one recurring report, with the systems involved. I will send back the handoff map: which steps only move information, the connection route for each system, and where the approval gates belong.

      If it turns out the process is already lean, you have it in writing. If it is not, you will know which hours to take back first.

      Set up 30 minutes