FORQA Command Centre

A mobile-friendly operating view from the overnight CTO + GTM review. It keeps the commercial story, beta readiness, technical risks, and next decisions in one place for Jack and Mark.

Core thesis

Sage-connected revenue forecasting for B2B SMEs whose forecast meetings are still powered by spreadsheets, CRM exports, and finance reconciliation.

FORQA should avoid enterprise RevOps positioning at first. The early wedge is trust, simplicity, and monthly/quarterly revenue clarity for MDs, FDs, and Sales Directors.

Forecast meeting replacementSME-firstSage/accounting actuals to validate

Readiness call

Guided beta

Good enough for curated design-partner demos if trust, admin guardrails, and deployment/auth proof are tightened. Not yet broad self-serve or multi-tenant beta.

What looks strong

Focused forecasting workflow already exists.
Architecture appears coherent for a small SaaS product.
HubSpot line-item sync design is specific, not generic.
Useful tests and docs are already present.

What needs proof

Production auth and deploy configuration.
Forecast number explainability and caveats.
Sage product/version and integration scope.
Single-tenant vs multi-tenant beta model.

Critical caution

Security/credential review produced an immediate incident-response item.
Do not expand production access until the owner verifies rotation, logs, config, and smoke tests.

Best first ICP

B2B SME using Sage/accounting with pipeline in HubSpot or spreadsheets.

MD/Founder or FD still owns forecast confidence.
Sales and finance disagree on the number.
Forecast meetings are manual and subjective.
Close dates slip and stale deals stay in pipeline.
Account managers hold too much knowledge in their heads.

Buyer map

Economic buyer: MD / Founder / Owner.
Finance co-buyer: FD / CFO / Controller.
Functional buyer: Sales Director / Head of Sales.
Daily users: reps and account managers.
Influencer: ops/admin, Sage partner, accountant.

Recommended pilot motion

Find Sage-heavy SMEs

Prioritise businesses where finance and sales reconcile manually.

Offer forecast audit

Ask how pipeline, Sage actuals, and cashflow decisions connect today.

Run guided pilot

Define success by forecast-call usage, time saved, and stale-deal visibility.

Package proof

Turn before/after workflow into case study, ROI, and demo narrative.

Next CTO actions

Owner-led credential incident response and log review.
Prove production config, JWT enforcement, and function coverage.
Fix/verify scheduled sync auth path.
Add unauthenticated smoke tests for all deployed functions.
Add data-quality/confidence panel: last sync, missing fields, stale records, caveats.

Next product/GTM actions

Choose product name for beta/demo and standardise copy.
Add trust microcopy for weighted/phased forecast and at-risk logic.
Prepare curated demo dataset and CRO/FP&A demo script.
Frame first call as a forecast visibility audit.
Build proof assets before scaling outreach.

Questions Jack + Mark should answer

Is this product called FORQA, Catalyst, or something else for beta?
Who is the first buyer: CRO, Finance, RevOps, or founder/operator?
Which Sage product/version is in scope, and is it actuals-only or read/write?
What is the source-of-truth metric: weighted forecast, won revenue, budget variance, issued invoices, recognised revenue, or cash collected?
Is the first beta single-tenant/design-partner only or multiple external tenants?
What is the go/no-go criterion for expanding beta?