Owner: Andrew Herbert + Head of Delivery (joint)
Contributors: Marketing Manager (D1) · BA (D4/D6)
Entity: REMAP.ai (GTM strategy & sign-off) · PrivateAI (delivery)
Status: v0.9 · In Progress · Pending Andrew Herbert review
Version: 0.9 | Last updated: 2026-07-01
⚠️ Andrew Involved — Andrew gates the product-fit decision (Step 2) and signs
off the GTM plan before launch (Step 6). No secondary product launches without his
explicit approval at both checkpoints.
What this workflow does: Turns a secondary product — an off-the-shelf, repeatable
solution — from an idea into something the delivery team can sell and deliver
consistently, without Andrew or a senior developer in the room for every build.
What triggers it: Two entry doors:
What it produces: A launched secondary product that is priced, documented, and
delivery-ready — plus a trained team and a complete per-product document pack
(service definition, Developer Playbook, processes, training material, and
landing-page brief).
Why it matters: Secondary products create repeatable revenue that does not consume
senior time per build. Productising and delegating delivery directly reduces Andrew's
bottleneck — a standing business priority.
| Role | Department | Responsibility | Andrew? |
|---|---|---|---|
| Andrew Herbert — CEO | D1 Marketing | Gates the product-fit decision (Step 2). Signs off GTM plan before launch (Step 6). | Yes |
| Head of Delivery | D4 Delivery | Owns requirements, feasibility, Developer Playbook, delivery readiness, and live escalation | No |
| Marketing Manager (Shahzaib) | D1 Marketing | Builds go-to-market artifacts and landing-page brief within the document pack | No |
| BA | D4 → D6 | Prices the product using the pricing framework (OPS-O01) | No |
Primary owner: Andrew Herbert + Head of Delivery — jointly accountable
Review authority: Andrew Herbert — must sign off on any changes to this document
Step 1 — Spot the signal
Step 2 — Product-fit check ⚠️ Andrew gate
Step 3 — Assess requirements
Step 4 — Feasibility check
Step 5 — Price the product
Step 6 — Andrew sign-off on GTM plan ⚠️ Andrew gate
🤖 Step 7 — Build the product document pack
Step 8 — Train the team
🤖 Step 9 — Launch / go live
⚠️ Tool gaps: Landing-page tool and knowledge management platform are both
unconfirmed — flagged as TBD pending OPS-O02 assessment. Neither blocks building
the document pack — build the pack first, publish once tooling is confirmed.
| Tool | How it's used | Agent-ready |
|---|---|---|
| Google Workspace | GTM plan, requirements, service document, Developer Playbook, training material | Yes — API + MCP |
| n8n | Artifact generation and publishing pipeline for document pack and landing page | Yes — native |
| Xero | Profitability tracking against the primary KPI | Yes — API |
| Pricing framework (OPS-O01) | Sets product pricing and delivery approach | N/A — internal process |
| Landing-page tool | Publishing the product landing page | TBD — pending OPS-O02 |
| Knowledge management | Storing and retrieving the document pack and training material | TBD — pending OPS-O02 |
Decision: Is it a product? (Step 2) ⚠️ Andrew gate
| Option | Condition | Action | Owner |
|---|---|---|---|
| A | Genuinely repeatable | Continue to requirements (Step 3) | Andrew + Head of Delivery |
| B | One-off engagement | Route to AI Project delivery (DEL-03) | Andrew + Head of Delivery |
Decision: Is it feasible? (Step 4)
| Option | Condition | Action | Owner |
|---|---|---|---|
| A | Feasible at repeatable quality | Price it (Step 5) | Head of Delivery |
| B | Not feasible now | Park with documented gap list | Head of Delivery |
Decision: GTM sign-off (Step 6) ⚠️ Andrew gate
| Option | Condition | Action | Owner |
|---|---|---|---|
| A | Approved | Build document pack (Step 7) | Andrew |
| B | Not approved | Revise and re-submit or stop | Andrew |
| Scenario | How to handle | Escalation |
|---|---|---|
| Client interest fades before launch | Pause; retain the requirements note for future reactivation | Head of Delivery — decides whether to pause or continue |
| Feasible but no one can deliver it yet | Hold launch until placement (DEL-05) covers the capability; document the skills gap | Head of Delivery |
| Landing-page / KM tool undecided | Build the document pack anyway; publish once tooling confirmed — do not block internal readiness | OPS-O02 decision required |
| Live product runs into build trouble the trained team can't resolve | Team escalates to single accountable point | Head of Delivery — owns all escalations post-launch |
| Pricing changes after product has launched | BA reassesses pricing. Andrew approves any change. Update document pack and sales briefing immediately. | Andrew — final pricing authority |
| Metric | Type | Target |
|---|---|---|
| Launch success signal | Lagging | ≥ 2 satisfied clients AND overall profitable within first month |
| Deliveries without senior-dev involvement | Leading | High % of builds delivered by trained team independently |
| Time from signal → launch | Lagging | TBD — set at first launch |
| Secondary product revenue | Lagging | TBD — set at first launch |
| Document pack completeness at launch | Process | All sections present — Playbook, processes, training, landing-page brief |
| Step | Current state | Suggested automation | Tool | Effort |
|---|---|---|---|---|
| Step 7 — Build document pack | Manual | Template-driven generation of service doc and Developer Playbook from a product brief | n8n | Medium |
| Step 9 — Launch / go live | Manual | Auto-publish landing page + notify Sales and Delivery on go-live | n8n + landing-page tool (TBD) | Medium |
Upstream:
Downstream:
| Version | Date | Description | Author |
|---|---|---|---|
| 0.9 | 2026-07-01 | Initial draft — product-fit decision gate, feasibility check, BA pricing, document pack structure, team training, and launch process documented. Two Andrew gates marked. Tool gaps (landing page, KM) flagged pending OPS-O02. | REMAP Workflow Builder |
← Back to Marketing Hub · ← Back to Company Operating System