# Advisor Assessment — Engineering Management Suite (Product)

**Opportunity:** Commercialise the existing engineering-management toolkit (Leadership builder, Engineering standards, Capella Guru, PM Process, SBS generator, DTP publications, conversion tooling) as a productised offering for small engineering companies.
**Stage at writing:** Concept · **Assessor:** ZCode (acting investment advisor) · **Date:** 2026-09-12
**Review cadence:** fortnightly portfolio flip-through; full re-assessment at every stage gate.

---

## 1. Investment thesis

You already own the hardest part: a working, internally exercised engineering-management toolkit covering leadership role requirements, engineering standards, systems-engineering process (Capella/MBSE support), project-management process, system-breakdown generation, and technical publications. It has been used on real governed projects in this workspace.

The thesis is **asset repurposing with near-zero marginal cash cost**: package what exists, add AI-driven tailoring (generate drafts from the client's own past projects), and sell it to small engineering firms (≈10–100 staff) who cannot afford enterprise tooling or big-firm consultants but still lose money to inconsistent processes, slow proposal drafting, and unclear capability pathways.

You are not selling software. You are selling **an outcome**: a tailored engineering management operating system + the drafts it produces + the team capability it builds.

## 2. Target customer (hypothesis — validate, don't assume)

- **Who:** owner-managed engineering consultancies and delivery firms (civil, structural, rail, infrastructure, utilities), 10–100 staff, Australia-first.
- **Pain:** senior engineers spend nights drafting plans/standards/proposals; processes differ project-to-project; no systematic capability development; enterprise PPM/EMS tools are priced and sized out of reach.
- **Buyer:** managing director or delivery/operations manager (single decision-maker — short sales cycle possible).
- **Anti-customer (do not chase):** firms under ~10 staff (no management layer to sell to) and large firms (already served by enterprise vendors and internal PMOs).

## 3. Offering hypothesis (three tiers — see OFFERING_HYPOTHESIS.md for detail)

| Tier | What they get | Pricing hypothesis | Why it exists |
|---|---|---|---|
| **1. Foundation install** (fixed fee) | Suite deployed, templates tailored to their delivery history, capability assessment, management-system baseline | $8k–$15k | Entry point; funds itself; produces the case-study data |
| **2. Managed operating system** (monthly) | Ongoing tailoring, AI draft generation from their past projects, quarterly process audits, capability plans | $1k–$2.5k / month | Recurring revenue; the actual product |
| **3. Capability program** (per cohort) | Team training/coaching built on Leadership builder + standards | $ per cohort | Margin booster; deepens lock-in |

**Differentiator:** AI draft generation trained on *their own* previous projects — drafts come out in their voice, using their terminology, mapped to their real capabilities. Generic AI tools can't do this; enterprise vendors won't do this for SME prices.

## 4. Market & competition (honest view)

- **Enterprise PPM/governance platforms** (e.g. large PPM suites): too expensive, too big — not competing for the same buyer.
- **Generic AI document tools:** cheap but have no engineering-management governance depth and no tailoring to the firm's corpus. They commoditise *writing*, not *managing*.
- **Boutique consultants:** deliverable quality high, but $ per day is unaffordable and nothing repeatable is left behind.
- **Positioning gap you occupy:** engineering-specific governance content + AI tailoring + fixed-price packaging. Nobody in the SME band currently bundles all three.

The market risk is not competition — it is **willingness to pay** in the SME band. That is exactly what the concept-stage interviews must measure (see §7).

## 5. Investment & capital at risk

| Item | Estimate |
|---|---|
| Cash required to first revenue | Minimal (~$0–500: hosting, a demo environment, a one-pager) |
| Founder hours to first revenue | ≈ 100–140 h (packaging 40–60 h, discovery 15 h, pilot delivery 60–80 h) |
| Capital at risk | Primarily opportunity cost of time vs. NDIS / HAD Digital / Mario |
| Expected time to first revenue | 60–120 days if a pilot converts |

This is a **low-cash, high-time** bet. Its true cost is bandwidth — which is why the stage gates below are strict about earning the next tranche of hours.

## 6. Stage gates (entry → exit criteria)

| Gate | Entry criteria (leave previous stage) | Kill / pivot trigger |
|---|---|---|
| Concept → Validation | Offering hypothesis written (this doc); IP-clean asset inventory (ACT-001); 8+ discovery interviews; ≥3 credible "would pay" signals | <3 pay signals after 12 interviews → **park** |
| Validation → Build | 1 paid pilot (discount acceptable); pricing validated against tier hypotheses; delivery playbook drafted | No pilot at realistic price after 20 qualified conversations → **park** |
| Build → Market | 2 case studies with measured outcomes (hours saved, cycle time); packaged SKU; delivery effort within 2× of target | Delivery effort >3× target and not falling → **pivot to pure consulting** |
| Market → Revenue/Scale | Repeatable leads without founder-led outreach each time | CAC exceeds 12-month contract value → rethink channel |

## 7. Concept-stage KPIs (what we measure now)

| KPI | Target by day 60 |
|---|---|
| Discovery interviews completed | 13 (5 by day 30) |
| Problem-validation rate ("yes, this pain is top-3") | ≥ 40% |
| Willingness-to-pay signals (named price accepted as plausible) | ≥ 3 |
| IP-clean toolkit components packaged | 100% of demo surface |

## 8. Top risks (full register: 03_Registers/RSK.csv)

1. **SME willingness to pay** (HIGH) — mitigate by selling revenue-linked outcomes (proposal win rate, senior-engineer hours saved), not "tooling".
2. **Tailoring doesn't scale** (HIGH) — mitigate by building the template library + AI draft pipeline into the *first* pilot, not after.
3. **IP contamination** (HIGH) — the toolkit grew during paid engagements; audit before anything is shown externally (ACT-001).
4. **Founder bandwidth** (HIGH) — four active opportunities; this product only gets hours it earns through gates.
5. **Commoditisation by generic AI** (MEDIUM) — differentiate on governance depth + client-corpus tailoring.

## 9. Relationship to the other opportunities

- **AI Consultancy for SMB:** closest sibling — same buyer shape, same governance assets, horizontal (any AI project) vs vertical (engineering management). Decision ACT-004 decides whether they merge go-to-market. My advisor lean: **shared go-to-market, separate offerings** until interview data says otherwise.
- **Mario Software:** different domain and partner; shares only the AI-build capability.
- **NDIS / HAD Digital:** unrelated domains but compete for the same founder hours — see PORTFOLIO_STRATEGY.md.

## 10. Recommended next moves (30-60-90)

**Days 0–30**
- ACT-001: IP audit + clean-asset inventory of `C:\AI Projects\Engineering Management` (read-only; never modify that workspace).
- Package the offering one-pager + demo script from the clean inventory.
- ACT-002: build the 15-firm candidate list. ACT-003: run the first 5 interviews.

**Days 31–60**
- 8 further interviews; log every "would-pay" signal with name, price point, condition.
- Define a pilot scope you can deliver in ≤80 h; pitch it to the 2 warmest interviewees.

**Days 61–90**
- Deliver pilot start; instrument baseline metrics (drafting hours before/after, cycle time).
- Capture the first case study (even internal-quality); re-run the gate decision.

## 11. Decision framework summary

Proceed while: interviews keep validating pain ≥40% and pay signals keep arriving.
Pivot if: pain validates but pricing doesn't — collapse to pure consulting on the same assets (revenue now, productise later).
Park if: 12 interviews, <3 pay signals — the asset stays yours; the timing wasn't.