FS-DOC-01Operations
Launch Plan
Budget vs Actuals Reporting
[YourCompany.com] · Finance Department · Prepared by FullSpec · [Today's Date]
This Launch Plan covers everything you need to know about how your Budget vs Actuals Reporting automation moves from confirmed process map to a live, running system. It explains what is being built, how FullSpec will build it, what you need to provide, and what your role looks like once the automation is running. FullSpec handles all technical work end to end. Your involvement is limited to granting access to your existing tools and reviewing outputs at key checkpoints.
01What you're launching
Every month your bookkeeper exports actuals from QuickBooks, pastes them into a Google Sheets budget template, repairs broken formulas, and then the finance manager chases department heads for variance explanations before formatting and distributing the report. That sequence consumes roughly six hours of combined effort and regularly delivers the report four to seven days into the new period, by which point the numbers reflect a partially closed window. This automation replaces all of that assembly work with three coordinated agents that pull, compare, flag, and distribute the report on close day, leaving the finance manager a single commentary review rather than a data-assembly marathon.
Process
Budget vs Actuals Reporting
Trigger
Month-end period closes and actuals are finalised in QuickBooks
Final output
A date-stamped variance report published to Google Drive with a Slack notification sent to all stakeholders, same day as period close
Agents being built
3 agents: Actuals Sync Agent, Variance Analysis Agent, Report Distribution Agent
Tools involved
QuickBooks, Google Sheets, Google Drive, Slack
Volume
1 full report per month, covering 20 to 50 cost lines
Launch PlanPage 1 of 4
FS-DOC-01Operations
02How the build works
FullSpec follows a four-stage delivery process for every automation: Connect, Build, Test, and Launch. Each stage has a defined set of actions, a clear owner for each task, and a defined output before the next stage begins. You do not need any technical knowledge to participate. Your role in the build is to confirm access, review drafts, and approve outputs at each gate. FullSpec handles all configuration, logic, mapping, and testing.
Complexity level: Moderate. Estimated delivery window: 15 business days total. The delivery clock starts at the close of Connect, not payment. Connect must be completed, tool access confirmed, and mapping decisions signed off before the build clock begins.
1Connect
Estimated time: 2 to 3 business days
FullSpec
Reviews your existing Google Sheets budget template structure, documents the account-to-budget-line mapping rules, confirms the variance threshold configuration, and finalises the distribution list and Slack channel targets.
You
Share access to your QuickBooks account, Google Sheets budget template, Google Drive folder, and Slack workspace. Confirm the variance threshold percentage and the names of department heads who need to be prompted.
2Build
Estimated time: 6 to 9 business days
FullSpec
Builds the Actuals Sync Agent (QuickBooks API connection, account mapping logic, Google Sheets write operations), then the Variance Analysis Agent (variance calculation, threshold flagging, Slack prompts), then the Report Distribution Agent (Google Drive publish, version naming, stakeholder Slack notification). Each agent is unit-tested against a prior-period data set before the next begins.
You
Remain available to answer questions about edge cases in the budget template layout or unusual account codes. No action is required unless FullSpec flags a mapping question.
3Test
Estimated time: 3 to 4 business days
FullSpec
Runs a full parallel cycle alongside the existing manual process using the most recent closed period. Validates that actuals written to the sheet match the QuickBooks source, that variance calculations are correct, that Slack prompts reach the right department heads, and that the Google Drive file is published with correct naming and permissions.
You
Your finance manager reviews the automated output alongside the manually produced report for the same period and confirms the figures match. Signs off on the commentary draft quality and approves the report format before go-live is authorised.
4Launch
Estimated time: 1 business day
FullSpec
Switches the automation to live scheduling for the next period close, confirms the trigger is firing correctly, delivers the process runbook to your finance manager, and remains available for 30 days post-launch to monitor outputs and resolve any issues.
You
Notify your bookkeeper and finance manager that the automation is live. The manual process steps for data export, paste, and formula repair are retired from this point forward. The finance manager's only ongoing task is the commentary review and approval step.
Launch PlanPage 2 of 4
FS-DOC-01Operations
03What FullSpec needs from you
FullSpec needs only access to your existing tools. No technical knowledge is required from you or your team. All credential setup, API configuration, and permission scoping is handled by FullSpec. The table below lists exactly what is needed and when. Everything in this list should be ready before Connect closes so the build clock can start without delay.
QuickBooks
OAuth login credentials or an authorisation to connect a read-only API integration. FullSpec will walk you through the two-click authorisation screen.
Before Connect closes
Google Sheets
Editor access to the master budget template spreadsheet, shared with the FullSpec service account email that will be provided during Connect.
Before Connect closes
Google Drive
Editor access to the destination folder where published reports should be saved. FullSpec will confirm the folder path and sharing permissions at Connect.
Before Connect closes
Slack
Permission to install a Slack app in your workspace (admin approval may be required). FullSpec handles the app setup once permission is granted.
Before Connect closes
One decision you must confirm before Connect closes: the variance threshold percentage that triggers an alert and a Slack prompt to a department head. For example, any line where actuals exceed budget by more than 10% or $500, whichever is larger. This threshold drives all downstream flagging logic and cannot be finalised during the build without your confirmation. If you are unsure, FullSpec will recommend a starting point based on your cost-line count and historical variance patterns, but the final call is yours.
04Your role once live
Once the automation is live, the day-to-day effort for your team changes significantly. The table below sets out ongoing responsibilities for each party and the tasks that are fully retired from your team's workload.
Role
Ongoing responsibilities
What you no longer touch
You (business owner and finance team)
Finance manager reviews AI-drafted variance commentary in Google Sheets, edits any lines where the draft needs adjustment, and approves the report before it is published. This review takes under 20 minutes per cycle. Finance manager also maintains the account-to-budget-line mapping table when new account codes are added in QuickBooks.
Exporting P&L data from QuickBooks, pasting actuals into the budget spreadsheet, repairing broken formulas, manually calculating variances, chasing department heads individually for explanations, formatting and polishing the final report, and distributing the file to stakeholders.
FullSpec
Monitors the automation for the first 30 days post-launch. Responds to any support queries at support@gofullspec.com. Handles token refresh alerts if the QuickBooks OAuth connection expires. Provides a runbook covering all edge cases including unmapped accounts and missed Slack responses.
Not applicable. FullSpec manages all technical infrastructure, scheduling, and error handling throughout the subscription period.
Launch PlanPage 3 of 4
FS-DOC-01Operations
05What success looks like
The table below describes what you should expect to see at each milestone after go-live, and the specific signs that confirm the automation is performing as designed. If any of these signs are absent at the stated timeframe, contact FullSpec at support@gofullspec.com and the team will investigate.
Timeframe
What to expect
Sign of success
Week 1
The first live automated report cycle runs alongside the period close. The Actuals Sync Agent pulls figures from QuickBooks on schedule, writes them to Google Sheets without formula damage, and the Variance Analysis Agent posts Slack prompts to department heads. The finance manager receives a pre-populated commentary draft for review.
Report is available for finance manager review on the same day as period close. No broken formulas in the budget sheet. Slack prompts reach the correct department heads within minutes of the actuals write completing.
Month 1
The finance manager's monthly reporting workload is reduced to a single review session of under 20 minutes. The report reaches stakeholders on close day or the morning after, compared to the previous four to seven day lag. Department heads are responding to targeted Slack prompts rather than being chased by email.
Stakeholders receive the report within 24 hours of period close. Finance manager confirms the commentary draft quality is usable with minimal editing. Zero formula errors reported in the actuals columns.
Month 3
The automation has completed three full report cycles without manual intervention in the data assembly steps. The account-to-budget-line mapping table has been updated at least once for any new account codes, using the runbook process. Time savings of approximately 18 hours of combined bookkeeper and finance manager effort have been recovered over the quarter.
Three consecutive reports delivered on schedule with no pipeline failures. Finance team confirms the manual export, paste, and formula-repair steps have not been needed since go-live. FullSpec monitoring logs show no unhandled errors across all three cycles.
Next step: FullSpec will send you a Connect session invitation within one business day. That session is a short call where you share tool access, confirm the variance threshold, and review the account mapping table together. Once Connect closes, the build starts immediately and you will receive a progress update at the end of each build week. Questions before the Connect session? Reach the team at support@gofullspec.com.
Launch PlanPage 4 of 4