FS-DOC-01Operations
Launch Plan
Campaign Performance Reporting
[YourCompany.com] · Marketing Department · Prepared by FullSpec · [Today's Date]
This Launch Plan gives you a clear picture of what is being built, how the build unfolds, and what your team needs to do at each stage. FullSpec handles all technical construction, configuration, and testing end to end. Your role is to provide tool access, confirm one configuration decision before build begins, and review the first live report output before sign-off. Nothing in this document requires technical knowledge.
01What you're launching
Right now, your Marketing Manager spends roughly two and a half hours every reporting cycle logging into Meta Ads Manager, Google Analytics, and HubSpot separately, downloading CSVs, fixing mismatched date ranges and column names, rebuilding charts by hand, writing a summary under time pressure, and finally posting the result to Slack. The actual analysis gets whatever time is left over, which is rarely enough. This automation replaces every mechanical step in that cycle with three purpose-built agents that collect, normalise, and distribute the report on a fixed schedule. The only task that remains for a human is reviewing the draft commentary before it goes out, keeping judgement in the loop where it matters and removing it from everywhere it does not.
Process
Campaign Performance Reporting
Trigger
Reporting period ends on schedule (weekly for performance report, monthly for executive summary)
Final output
A Slack message with top-line metrics, underperformance flags, and a link to the live Looker Studio dashboard, delivered within 15 minutes of period close
Agents being built
3 agents: Data Collection Agent, Normalisation and Insight Agent, Distribution Agent
Tools involved
Meta Ads Manager, Google Analytics, HubSpot, Google Sheets, Google Looker Studio, Slack
Volume
~4 reports/month across weekly and monthly cadences
Launch PlanPage 1 of 4
FS-DOC-01Operations
02How the build works
FullSpec follows a four-stage delivery process for every automation build: Connect, Build, Test, and Launch. Each stage has a defined output before the next one begins, so nothing gets built on an unstable foundation. The Build stage itself is broken into three sequential agent builds, one per agent, so each piece is tested independently before it is connected to the next. You will receive progress updates at the close of each stage and have a single review point before go-live.
Complexity level: Moderate. Estimated delivery window: 15 to 20 business days. The delivery clock starts at the close of Connect, not payment. Connect cannot close until all tool credentials and the one configuration decision in Section 03 have been confirmed.
1Connect
Business days 1 to 3
FullSpec
Sends you a credential checklist and a short onboarding form. Reviews your existing Google Sheet structure and Looker Studio data source connections. Confirms API access is available for Meta, Google Analytics, and HubSpot. Raises any blockers before the build clock starts.
You
Complete the credential checklist (see Section 03). Confirm the one configuration decision around commentary review. Reply to any clarifying questions from the FullSpec team within one business day.
2Build
Business days 4 to 14
FullSpec
Builds and tests the Data Collection Agent (API connections to Meta, Google Analytics, HubSpot). Builds the Normalisation and Insight Agent (column standardisation, KPI calculation, AI commentary draft). Builds the Distribution Agent (Looker Studio refresh trigger and Slack post). Tests each agent against two previous reporting periods before connecting them in sequence.
You
No action required during this stage. You may be asked to approve a minor Google Sheets structural change if the existing layout needs adjusting to support automated writes.
3Test
Business days 15 to 17
FullSpec
Runs the full end-to-end flow against live data. Validates metric alignment across all three platforms, checks date range accuracy, confirms Slack message formatting, and verifies the Looker Studio dashboard refreshes correctly. Shares test outputs with you for review.
You
Review the test report output and the Slack message. Confirm the numbers look correct against what you would expect from a manual run. Flag any discrepancies to the FullSpec team. Sign off once satisfied.
4Launch
Business days 18 to 20
FullSpec
Moves the automation to the live schedule. Monitors the first two live report runs to confirm outputs are clean. Delivers the full documentation suite including the SOP, Test and QA Plan, and Developer Handover Pack. Hands over ongoing monitoring.
You
Confirm the Slack channel and recipients are correct before the first live run. Review the first automated report as it arrives. Contact support@gofullspec.com if anything looks unexpected in the first live outputs.
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 on your side. The table below lists every credential item needed and when it must be in place. All items are needed before Connect closes so the build clock can start without delay.
Meta Ads Manager
Admin access to the Business Manager account so FullSpec can configure API app permissions and retrieve campaign data. If the account has not used the API before, Meta app review may take 1 to 3 extra days.
Before Connect closes
Google Analytics
Editor or Administrator role on the GA4 property so FullSpec can configure the Data API connection and confirm goal and event tracking is set up correctly.
Before Connect closes
HubSpot
Super Admin or Private App creation access so FullSpec can generate a private app token scoped to contacts, deals, and campaign attribution data.
Before Connect closes
Google Sheets
Editor access to the master reporting spreadsheet. If no master sheet exists yet, FullSpec will create one and share it with you for confirmation.
Before Connect closes
Google Looker Studio
Editor access to the existing Looker Studio report, or confirmation that FullSpec should create a new one. The dashboard must be connected to the Google Sheet before go-live.
Before Connect closes
Slack
The name of the Slack channel where reports should be posted, and Workspace Admin approval to add an incoming webhook or Slack app integration.
Before Connect closes
One decision you must confirm before Connect closes: Should the automation hold the Slack post until a team member has reviewed and approved the draft commentary, or should it post automatically once the commentary is generated? The Standard build defaults to a human review step (approximately 10 minutes per report) before distribution. If you prefer fully automatic posting, confirm this in writing to the FullSpec team and the review gate will be removed. This is the only configuration choice that cannot be changed after the build begins without rework.
04Your role once live
Role
Ongoing responsibilities
What you no longer touch
You (business owner / Marketing Manager)
Review the draft commentary produced by the Normalisation and Insight Agent each reporting cycle (approximately 10 minutes). Edit or approve the summary, then confirm distribution. Flag any unexpected metric results to support@gofullspec.com. Notify FullSpec if you add a new ad platform or change your HubSpot pipeline structure.
Logging into Meta, Google Analytics, or HubSpot to export data. Copying and pasting CSVs into a spreadsheet. Fixing mismatched column names or date formats. Rebuilding charts or refreshing data ranges. Manually formatting and posting the Slack report summary.
FullSpec
Monitors the scheduled runs and alerts you if any agent fails to collect data or post within its expected window. Maintains API credential health and handles token refresh when platform authentication expires. Applies fixes for any platform API changes that break the data collection flow. Responds to support queries at support@gofullspec.com within one business day.
Not applicable. FullSpec does not touch your campaign strategy, ad creative, or budget decisions.
Launch PlanPage 3 of 4
FS-DOC-01Operations
05What success looks like
Timeframe
What to expect
Sign of success
Week 1
The first two or three automated reports arrive in Slack on schedule. The Marketing Manager reviews the draft commentary and approves or edits it before distribution. Minor formatting preferences may surface that the FullSpec team will adjust quickly.
The report lands in Slack within 15 minutes of the reporting period closing, and the numbers match what you would expect from a manual check. No CSV downloads or spreadsheet work required.
Month 1
The schedule is running reliably across both weekly and monthly cadences. The commentary quality from the Normalisation and Insight Agent improves as the team refines the language and threshold settings. Stakeholders begin engaging with the Looker Studio dashboard directly rather than waiting for the Slack summary.
Approximately 3.5 hours per week returned to the Marketing Manager. Reporting is no longer dependent on one person being available. The first monthly executive summary runs automatically without any manual preparation.
Month 3
The process is fully embedded in the team's rhythm. The $2,400 build cost has been recovered through time savings. The Marketing Manager is spending reclaimed hours on analysis and strategy rather than data wrangling. The automation has handled at least 12 weekly reports and 3 monthly summaries without requiring manual intervention.
Annualised time saving of 175 hours is on track. Annual staff cost for reporting has dropped from $9,100 to approximately $1,820. The team has visibility into whether any campaign thresholds or distribution settings should be adjusted for the next quarter.
Next step: Share tool access for all six platforms listed in Section 03, and reply to the FullSpec onboarding form with your commentary review preference. Once both are confirmed, the Connect stage closes and the build clock starts. Questions before then: contact support@gofullspec.com.
Launch PlanPage 4 of 4