The subscription review

The subscription review turns the software you pay for each month into a plan: what a trainee could replace with an app of your own, what your own apps and agents should only connect to, and what to keep. Open it from "Review what you pay for each month" on the interview page.

List your tools

• Read the tools from my interview: lists the paid tools you named in your answers. Only figures you gave are kept; anything else shows "No price given". Pressing it again adds nothing new.
• Add a tool: the tool's name in your words, what it does, and optionally the seats and what you pay per month in total, in USD.

"Edit" and "Remove" change or delete a line. The list holds up to 40 tools.

When you stop paying for a tool (you cut it, or an app of your own replaced it), press "I stopped paying for it" on its line and enter the day. The line stays on the list as "Cut on" that day, is left out of the plan, and your monthly agent statement counts its monthly price from the next full month. "I still pay for it" undoes it.

How the plan sorts them

• Replace: internal team tools (team chat, tasks and job tracking, wiki and procedures, forms, a simple customer list, bookings, stock lists, dashboards) and the other everyday apps on the build-instead page. A trainee can build your own version, on a server you choose. Trainees learn to plan, deploy, run and extend these apps in the course's Business Suite module.
• Connect, never replace: accounting, invoicing, expenses, payments, payroll, banking and email delivery. They hold your money or send on your behalf, so they stay the record and your apps connect to them.
• Keep: regulated records (health, legal, tax filings, compliance) stay where they are; ask a professional before moving or copying them. Anything else we have no plan for is talked over at the scoping call.

Each line links to the workflow designs for that kind of tool.

The savings

For each tool to replace that you gave a price for, the plan shows what you pay in a year, the saving each year after the build, and, where we have an assumed build length, the saving in the first year (you keep paying the subscription while the trainee builds).

Your figures are tagged "your number". The running cost of your own app and the build length come from the build-instead page and are tagged "assumed"; they are not quotes, and nothing here is a promise of savings. There is no separate upkeep figure: changes after the build are work you agree with your intern or a retainer. A saving is never shown below zero: "No saving at these numbers" means the costs are higher.