Back to Financial Reporting

Launch Plan

What FullSpec will build for you, what happens at each stage, and what your automation looks like once live.

4 pagesPDF · Operations
FS-DOC-01Operations

Launch Plan

Financial Reporting Automation

[YourCompany.com] · Finance Department · Prepared by FullSpec · [Today's Date]

This Launch Plan is your single reference point for everything that happens between now and go-live. It covers what is being built, how the build is structured, what FullSpec needs from you and when, what your ongoing role looks like once the automation is live, and how you will know it is working. FullSpec handles all configuration, testing, and deployment. Your involvement is limited to providing access credentials and approving the report draft during the review gate, exactly as you do today.

01What you're launching

Right now, every reporting cycle starts with your bookkeeper and finance manager manually exporting data from Xero and HubSpot, pasting figures into a master Google Sheet, rechecking formulas, writing variance notes, and then distributing the finished PDF via Slack. The whole sequence takes roughly 3.5 hours per cycle, runs four times a month, and is one of the most error-prone tasks in the business. The automation being built replaces nine of the ten manual steps with three coordinated agents that run on a schedule, populate the report automatically, draft variance commentary for the finance manager to review, and deliver the finished PDF to the right people without anyone touching a spreadsheet.

Process
Financial Reporting: scheduled data fetch, variance analysis, and PDF distribution
Trigger
Scheduled date for each report type, for example the first working day after month-end or every Monday morning for the weekly flash report
Final output
A PDF report saved to Google Drive and delivered to the configured Slack channel with headline variance figures
Agents being built
3 agents: Data Fetch Agent, Variance Analysis Agent, Distribution Agent
Tools involved
Xero, HubSpot, Google Sheets, Google Drive, Slack
Volume
Approximately 4 reports per month across weekly flash, monthly P&L, and cash-flow views
Launch PlanPage 1 of 4
FS-DOC-01Operations

02How the build works

The build follows four sequential stages: Connect, Build, Test, and Launch. Each stage has a clear owner and a defined set of actions. FullSpec leads the technical work at every stage. Your involvement is focused and short: you provide access during Connect, give feedback during Test, and approve the go-live during Launch. The four stages are designed to move quickly while making sure nothing reaches your stakeholders until the output has been verified against your existing manual reports.

Complexity level: Moderate. Estimated delivery: 4 weeks (approximately 20 business days) from the close of Connect. The delivery clock starts at the close of Connect, not payment. Providing tool access promptly at the start of Connect is the single biggest factor in keeping the timeline on track.
1
Connect
Business days 1 to 3
Who
Actions
FullSpec
Sends a short credential request listing exactly what access is needed for Xero, HubSpot, Google Sheets, Google Drive, and Slack. Reviews your existing Google Sheets report template to identify the cell references the agents will write to. Confirms the variance threshold and the scheduled report dates with you. Audits the template structure and flags any layout changes needed before build begins.
You
Grant OAuth access or share API credentials for Xero and HubSpot. Share the current Google Sheets report template. Confirm the variance threshold percentage you want the system to flag. Confirm the Slack channel and recipient list for distribution. Answer any clarifying questions from the FullSpec team within 24 hours to avoid delaying the build start.
2
Build
Business days 4 to 14
Who
Actions
FullSpec
Configures Xero and HubSpot API connections with authenticated credentials. Builds the Data Fetch Agent with the scheduled trigger and writes the cell-reference mapping to the Google Sheets template. Tests the fetch logic against two historical reporting periods. Builds the Variance Analysis Agent with the confirmed threshold, connects commentary output to the report summary section. Builds the Distribution Agent including the Google Drive PDF export, the Slack notification, and the finance manager approval gate. Keeps you informed of progress at each agent milestone.
You
No action required during the build phase. If FullSpec surfaces a question about your report template layout or a specific field mapping, a same-day response keeps the timeline intact.
3
Test
Business days 15 to 18
Who
Actions
FullSpec
Runs the full automation against at least two historical reporting periods and compares outputs against the figures produced manually for the same periods. Tests the variance threshold logic, the approval gate behaviour, the PDF export, and the Slack delivery. Documents any discrepancies and resolves them before handing over for your review. Provides you with a side-by-side comparison of the automated output and the equivalent manual report.
You
Review the test report output and confirm that figures, formatting, and commentary match your expectations. Flag any layout preferences or naming conventions that need adjustment. Your sign-off on the test output is the trigger for moving to Launch.
4
Launch
Business days 19 to 20
Who
Actions
FullSpec
Runs the automation in parallel with your manual process for one full reporting cycle so outputs can be compared in real time. Resolves any final discrepancies identified during the parallel run. Activates the live schedule and confirms the first automated run completes cleanly. Delivers the process runbook and monitoring setup. Keeps monitoring active for the first two weeks post-launch and is available at support@gofullspec.com for any issues.
You
Complete the manual report as normal during the parallel-run cycle, then compare it against the automated output FullSpec provides. Confirm the automated version is accurate. Once confirmed, the manual process can be retired. From this point your only ongoing step is reviewing the variance flags and approving distribution, which takes approximately 20 to 25 minutes per cycle.
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 API configuration, credential management, and connection setup is handled by FullSpec. The table below lists what is needed for each tool and when it must be provided. Everything in this list should be ready before Connect closes so the build phase can start without delay.

Tool
What we need
When
Xero
OAuth authorisation via the Xero app connection flow. FullSpec will send a link. You approve the connection in your Xero account. No password sharing required.
Before Connect closes
HubSpot
A private app API key with read access to Deals and Pipelines. This can be created in HubSpot Settings under Integrations in under five minutes.
Before Connect closes
Google Sheets
Editor access to the master report template file. Share the file with the FullSpec service account email provided during Connect.
Before Connect closes
Google Drive
Editor access to the reporting folder where completed PDFs are saved. Share the folder with the same FullSpec service account.
Before Connect closes
Slack
Confirmation of the target channel name and permission for a Slack app to post to that channel. FullSpec handles the app installation; you approve it in Slack.
Before Connect closes
The one configuration decision you must confirm before Connect closes is the variance threshold: the percentage by which an actual figure must differ from its budget line before the Variance Analysis Agent flags it and drafts commentary. A starting point of 10% is recommended based on your process mapping, but this number is yours to set. If you are unsure, FullSpec will recommend a value based on your historical data and it can be adjusted at any time after go-live without rebuilding the automation.

04Your role once live

Role
Ongoing responsibilities
What you no longer touch
You (business owner / finance team)
Review the variance flags and commentary drafted by the Variance Analysis Agent each cycle, approximately 20 to 25 minutes. Approve or reject the report before distribution fires. Adjust the variance threshold or the Slack recipient list if business needs change. Contact FullSpec at support@gofullspec.com if a run fails or a figure looks unexpected.
Manual exports from Xero and HubSpot. Copy-paste data entry into Google Sheets. Formula checks and total verification. Formatting charts and the summary page. Exporting the PDF and posting it to Slack manually.
FullSpec
Monitors the automation for failed runs and connectivity issues. Provides support for any configuration changes, such as updating the variance threshold, adding a new report type, or adjusting the Slack channel. Handles any API changes from Xero, HubSpot, or Google that could affect the data fetch. Available at support@gofullspec.com.
Not applicable. FullSpec does not review your financial figures or approve report content. The finance manager retains full control of what is approved for distribution.
Launch PlanPage 3 of 4
FS-DOC-01Operations

05What success looks like

Timeframe
What to expect
Sign of success
Week 1
The first automated report run completes on schedule. Figures are checked against the manual parallel run and confirmed to match. The finance manager completes the review step and approves distribution. The Slack notification lands in the finance channel with the correct PDF link and headline figures.
Automated output matches the manual report for the same period. Distribution fires only after finance manager approval. No manual data entry was required.
Month 1
All four scheduled report cycles complete without manual intervention. The finance manager spends around 25 minutes per cycle on review rather than 3.5 hours on the full process. Variance commentary appears in every report, consistently, rather than being skipped under time pressure. Any early configuration adjustments, such as refining the variance threshold, are made by FullSpec based on your feedback.
Time per cycle is down to approximately 25 minutes for the finance manager. Zero copy-paste errors. Variance commentary present in every report. Report delivery same day as period close.
Month 3
The automation is fully embedded in the reporting rhythm. Approximately 75 hours of finance team time have been recovered relative to the manual process. The variance threshold has been tuned to the right sensitivity level. The finance manager is using the review step as a genuine quality check rather than a time-consuming production step. Stakeholders are receiving reports faster and with more consistent commentary than before.
Approximately 75 hours saved versus the manual baseline over 90 days. Report turnaround consistently same-day after period close. No stakeholder complaints about delayed or incorrect reports. Finance manager review gate functioning as a lightweight sign-off, not a bottleneck.

Next step: the FullSpec team will send you the credential request and the Connect session invite within one business day. All you need to do is gather the tool access items listed in section 03 and confirm your preferred variance threshold. From there, FullSpec handles everything through to go-live. Questions before then can be sent to support@gofullspec.com.

Launch PlanPage 4 of 4

More documents for this process

Every document generated for Financial Reporting.

ROI and Business Case
Finance · Owner
View
Process Runbook / SOP
Operations · Owner
View
Developer Handover Pack
Technical · Developer
View
Integration and API Spec
Technical · Developer
View
Test and QA Plan
Quality · Developer
View