Owner: Andrew Herbert (CEO) + BA (Hammad Akram)
Contributors: Head of Delivery (HoD — technical feasibility) ·
Finance Lead (commercial viability) · Marketing Manager (market signals)
Department: D1 — Marketing (upstream gate for MKT-03)
Entity: REMAP.ai + PrivateAI (both)
Status: Recommended draft · Pending Andrew Herbert + BA review
Version: 0.1 | Last updated: 2026-07-18
Classification: Internal
⚠️ This is a recommended draft prepared by the BA for review. It has not
been validated by the workflow owner. Review and approve before treating as
operational.
What this workflow does: Acts as the validation gate between a product or
service idea and a go-to-market launch. Every new product or service at REMAP.ai
and PrivateAI passes through MKT-02 before MKT-03 (GTM) is triggered. It ensures
decisions to build, launch, or retire a product are made deliberately — with
market evidence, technical feasibility, commercial viability, and strategic
alignment all confirmed before resources are committed.
What triggers it: Two entry points:
What it produces: A binary go/no-go decision on the product or service —
with a documented Validation Assessment (MKT-02-DOC-01) signed off by Andrew.
If go → triggers MKT-03 (GTM). If no-go → decision and rationale archived for
future reference.
Why it matters: Every GTM launch (MKT-03) consumes significant time from
Andrew, Shahzaib, Muskan, and the delivery team. A product that reaches GTM
without a validation gate risks wasting that effort on something the market
does not want, the team cannot deliver, or the business cannot price correctly.
MKT-02 is the investment protection step.
| Role | Department | Responsibility | Andrew? |
|---|---|---|---|
| BA (Hammad Akram) | D6 | Runs the validation process end-to-end — market research, feasibility coordination, commercial analysis, validation report | No |
| Andrew Herbert — CEO | D1/D6 | Primary decision maker — initiates validation, provides strategic context, makes the final go/no-go call, signs off MKT-02-DOC-01 | Yes |
| HoD (Hamza Tasneem) | D4 | Technical feasibility input — can the team build and deliver this? What is the effort estimate? | No |
| Finance Lead | D6 | Commercial viability input — does the pricing model work? What is the margin? | No |
| Marketing Manager (Shahzaib) | D1 | Market signal input — is there evidence of demand? What are competitors doing? | No |
Every product or service is assessed across four dimensions. All four must pass
for a go decision.
| Dimension | Key question | Evidence needed | Owner |
|---|---|---|---|
| Market fit | Is there a real, recurring demand for this? | Client requests, outbound reply signals, competitor analysis, ICP interviews | BA + Shahzaib |
| Technical feasibility | Can the team build and deliver this at consistent quality? | HoD effort estimate, tooling assessment, DEL-05 bench capability check | HoD |
| Commercial viability | Can it be priced to cover cost and generate margin? | BA pricing model using OPS-O01 framework, Finance Lead cost estimate | BA + Finance Lead |
| Strategic alignment | Does this fit where REMAP.ai is going? Does it distract or reinforce? | Andrew's strategic context from OPS-O04 (EOS V/TO) | Andrew |
Step 1 — Validation brief
Step 2 — Market fit assessment
Step 3 — Technical feasibility assessment
Step 4 — Commercial viability assessment
Step 5 — Strategic alignment check
Step 6 — Go — complete MKT-02-DOC-01 and trigger MKT-03
/Marketing/ProductValidation/.Step 7 — No-go — archive decision
/Marketing/ProductValidation/.| Section | Required | Notes |
|---|---|---|
| Product / service name | Yes | What it is called |
| Description | Yes | What it does and who it is for |
| Source of idea | Yes | Andrew's initiative / market signal / client request / ops pattern |
| Date of assessment | Yes | |
| Market fit findings | Yes | Evidence for/against demand · competitor analysis |
| Technical feasibility findings | Yes | HoD rating · effort estimate · conditions |
| Commercial viability findings | Yes | Proposed price · cost · margin · upsell path |
| Strategic alignment notes | Yes | Andrew's assessment |
| Go / No-go decision | Yes | Single clear decision |
| Conditions (if go) | If applicable | Any conditions attached to the approval |
| Rationale (if no-go) | If go = no | Which dimension(s) failed and why |
| Andrew sign-off | Yes | Date and confirmation |
| Next step | Yes | MKT-03 triggered (go) · archived (no-go) |
| Tool | How it's used | Agent-ready |
|---|---|---|
| Google Workspace | MKT-02-DOC-01 Validation Assessment · research docs · commercial model | Yes — API + MCP |
| Google Drive | Filing validated and no-go assessments at /Marketing/ProductValidation/ |
Yes — API + MCP |
| ClickUp | Pipeline data — client request frequency signals | Yes — API |
| Instantly / Dripify | Outbound reply signals — demand evidence from cold outreach | Yes — API |
| OPS-O01-DOC-01 | Pricing Framework — commercial model foundation | Internal reference |
| OPS-F01c-DOC-01 | Financial Forecast — cost structure reference | Internal reference |
| DEL-05-DOC-02 | Placement record — bench skills for feasibility check | Internal reference |
| Google Meet | Step 5 strategic alignment session with Andrew | Yes |
Market fit signals (Step 2)
| Signal strength | Action | Owner |
|---|---|---|
| Strong — multiple client requests + competitor activity | Proceed to Step 3 | BA |
| Weak — limited evidence | Flag to Andrew · his call to continue or stop | BA → Andrew |
| None — no evidence of demand | Recommend no-go · present to Andrew | BA → Andrew |
Technical feasibility (Step 3)
| Rating | Action | Owner |
|---|---|---|
| Feasible | Proceed to Step 4 | HoD confirms |
| Feasible with conditions | Document conditions and cost implications · proceed | HoD + BA |
| Not feasible | Stop · flag to Andrew with reason | HoD → Andrew |
Commercial viability (Step 4)
| Margin outcome | Action | Owner |
|---|---|---|
| Meets threshold | Proceed to Step 5 | BA + Finance Lead |
| Below threshold | Alternative model presented to Andrew · his call | BA → Andrew |
Go / No-go (Step 5)
| Decision | Action | Owner |
|---|---|---|
| Go | Complete MKT-02-DOC-01 · trigger MKT-03 | BA |
| No-go | Archive decision with rationale | BA |
| Scenario | How to handle | Escalation |
|---|---|---|
| Andrew wants to skip validation and go straight to GTM | BA documents the decision and rationale. Andrew signs off on a fast-track validation note. MKT-03 proceeds with that note as the briefing doc. | Andrew's decision — BA documents |
| HoD identifies feasibility risk after GTM has begun | BA and Andrew notified immediately. GTM paused pending re-assessment. | HoD → BA → Andrew |
| Competitor launches the same product during validation | Accelerate validation. Prioritise market fit and pricing assessment. Present to Andrew within 48 hours. | BA → Andrew |
| Product fails in GTM after validation approved | Capture in DEL-10 retrospective equivalent. Update MKT-02-DOC-01 with post-launch outcome. Improve validation criteria. | BA + Andrew |
| Finance Lead unavailable for commercial viability | BA prepares commercial model using available data. Notes Finance Lead input as pending. Does not block go/no-go if other three dimensions are clear. | BA flags to Andrew |
| Metric | Type | Target |
|---|---|---|
| Validation assessment completed before GTM begins (%) | Process | 100% — no GTM without MKT-02-DOC-01 |
| Go decisions that result in successful product launch (%) | Lagging | Baseline needed — track from first validation |
| No-go decisions with documented rationale (%) | Process | 100% |
| Time from validation brief to go/no-go decision (days) | Leading | ≤ 10 business days |
| Andrew sign-off obtained before MKT-03 triggered (%) | Process | 100% |
Upstream (feeds MKT-02):
Downstream (MKT-02 feeds into):
| Version | Date | Description | Author |
|---|---|---|---|
| 0.1 | 2026-07-18 | Recommended draft prepared by BA from operational context. Pending Andrew Herbert and BA formal review and approval before v0.9 designation. | BA (Hammad Akram) |
← Back to Marketing Hub · ← Back to Company Operating System