PRODUCT DELIVERY ROADMAPBaseline verified 3 November 2026 · v0.3.0
Build the real campaign engine first.
Simulate media until integrations are ready.
This roadmap turns the Growth Desk reference into a delivery plan. The research, campaign strategy, writing, image creation, manager review, client workspace and client approval are intended to be real product capabilities. Advertising-platform execution and analytics will be clearly simulated first, then connected to live providers in a later milestone.
Real product workResearch, create, review, approve
Gather company and campaign information; understand the market; produce strategy, copy and generated images; keep versions and evidence; give BuxUp managers and each client a real, private review-and-approval workflow.
Simulated at firstConnect, publish, measure
Build the complete channel and reporting experience with a mock platform adapter and labelled fictional data. No real Meta or Google account, ad, spend, traffic, lead or analytics result is touched during this phase.
CURRENT VERIFIED BASELINE
What is already implemented
Status refers to the working MVP Space, not to screens shown in the Growth Desk design reference.
Owner-led UK pilot · release v0.3.0
Implemented · verified 3 Nov 2026
- Campaign foundation: an owner dashboard, UK/English domain workspaces and document intake.
- Real research and creative pipeline: configured Hermes/Gemini research, a shared campaign brief, separate director/writer/image-prompt steps, and three platform treatments with generated images and copy.
- Review and handoff: source-linked UK review, versioned edits, whole-pack internal approval, editable client-review email draft, seven-file export and ZIP.
- Quality evidence: 63 tests and the production frontend build passed in the verified release.
Current boundary: the verified pilot is single-owner. It does not yet provide teammate roles, client logins or a private client approval workspace. Email is prepared, not sent; campaigns are not published; ad-platform analytics are not live.
TARGET END-TO-END FLOW
The intended customer journey
Only the media-provider responses are mocked in the initial integration-shaped build. The work and approvals around them are real.
Understand the companyGather its site, offering, audience, documents, goals and constraints.
Research and createUse real research and generation to prepare the strategy, platform copy and images.
BuxUp manager reviewReview evidence and approve or request changes to a specific campaign version.
Client's private viewThat client reviews its own campaign and approves, rejects or comments on the exact version.
Simulate, then connectShow a complete mock launch/reporting flow now; replace the mock connector with live APIs later.
DELIVERY SEQUENCE · NO DATES PROMISED
Milestones to build and verify
Statuses describe the verified pilot and planned expansion. Dates, owners and estimates should be agreed before committing to delivery windows.
M0
Owner-led pilot foundation
ImplementedKeep the proven single-owner flow as the baseline: domain and document intake, real research/creative work, versioned campaign pack, internal review and manual client handoff.
AcceptanceThe released workflow remains reproducible, its evidence and versions are preserved, and its boundary is explicit: no email is sent and no ad is published automatically.
M1
Complete real company intelligence and campaign production
Core implemented · expandExtend the existing real research and creative pipeline into the full Growth Desk workflow. Gather the client's company information and source documents; understand its offering, audience and market; record cited evidence and uncertainty; plan the campaign; write platform-specific material; and create original campaign images. Managers must be able to inspect, edit and revise a version without losing the research or unaffected platform work.
AcceptanceA campaign can be traced from client inputs to dated sources, strategy, copy and generated image files. Facts and assumptions are distinguishable; revisions create a new version; sample fixtures are not presented as client research.
M2
Real BuxUp manager review and client approval workspace
PendingAdd authenticated roles and a private workspace for each client. A BuxUp manager reviews the campaign first. The client then sees its own campaign, research summary, assets and status, and can comment, approve or reject the exact version. A material edit supersedes the previous approval and returns the campaign for review.
AcceptanceManager and client actions are real, version-specific and auditable. A client cannot access another client's campaign, evidence, files or decisions. Approval does not itself publish an advertisement.
M3
Complete the media workflow using simulated providers
Planned · mock dataBuild the channel setup, campaign status, launch-preview and analytics/reporting experience around a mock adapter shaped like future Meta Ads, Google Ads and Google Analytics 4 connections. Use clearly labelled fictional accounts, campaign IDs, spend, impressions, clicks, conversions and leads so the full workflow can be exercised before API access is ready.
AcceptanceThe interface and approval lifecycle work end to end; every simulated result is visibly labelled; test fixtures are repeatable; the mock adapter makes no live platform requests and cannot spend money or publish ads.
M4
Production readiness and client-data safeguards
Required before wider rolloutComplete and test role permissions, client-data isolation, audit history, secure credential handling, operational monitoring, recovery, cost/usage controls, accessibility and support procedures. Recheck these controls across the manager and client approval journey.
AcceptanceSecurity and access tests prove each role can see and do only what it should; sensitive tokens stay server-side; approval, rollback and failure states are reviewable.
M5
Replace simulated connectors with live platform integrations
Later · separately approvedOnly after the mock workflow and readiness gates pass, connect real provider accounts: Meta Ads, Google Ads and Google Analytics 4 first, with any additional channels agreed separately. Implement least-privilege authorization, secure token storage, real campaign/report reads, error and rate-limit handling, and platform-specific publishing controls.
AcceptanceEach real connection is tested in a safe environment, its data is identified as live and traceable to the provider, and creating or changing an ad requires the agreed human approval before any spend or publication.
NON-NEGOTIABLE BOUNDARIES
How we keep the roadmap honest
Real means real
- Company context, research, campaign writing, generated assets and approval decisions use the actual application workflow.
- Source, version, reviewer and approval status remain visible.
Simulated means labelled
- Fake accounts, campaigns, metrics and outcomes carry a persistent “SIMULATED” or “DEMO” label.
- Mock metrics are never described as client results or performance evidence.
No accidental live activity
- The mock stage has no live ad-platform credentials or API calls.
- No email, ad, budget, or external campaign is sent or changed without the required approval.
Live integrations are a separate release
- Provider authorization, API scopes, security review and live-data validation are explicit go-live gates.
- Mock and live environments remain clearly separated and independently testable.