Porter's Five Forces Review - AFPS Tracker
Stage 2 preliminary Porter research for the active AFPS Tracker product path. The approved Stage 1 boundary has now been researched, but the canonical Porter artifact remains gated until artifact approval YAML is provided.
Statusreview
Stage2 artifact review
Date2026-06-15
Working packetresearch/afps-tracker/_working/preliminary-porter-five-forces-research.md
Canonical targetresearch/afps-tracker/competitive-analysis-porter-five-forces.md
Change Summary Updated
Section feedback:
This page replaces the Stage 1 scope page with a Stage 2 artifact-review page. It embeds the preliminary working packet, force scores, evidence matrix, confidence register, coverage gaps, and proposed canonicalization file set.
The prior Stage 1 page was archived at docs/history/archive/2026-06-15/104222/alignment/porter-five-forces-afps-tracker.html.
No canonical Porter artifact has been written. The active output is the non-canonical working packet at research/afps-tracker/_working/preliminary-porter-five-forces-research.md.
Market Boundary Updated
Section feedback:
AFPS Tracker is scoped as a research-stage workflow-state and branching-decision visualizer for AFPS power users and AI workflow operators. It reads workflow state already emitted by AFPS-style repositories, especially research/.progress.yaml, product_paths[], working packets, alignment pages, and task docs.
It is not a generic project manager, research repository, AI coding agent, or development execution tracker. exec-loop-tracker remains out of scope for this Porter lane.
| Alternative Category | Examples | Why Included | Boundary Caveat |
|---|---|---|---|
| Manual repo navigation and native AFPS artifacts | Editor file tree, rg, markdown previews, alignment/index.html, research/.progress.yaml | Direct current-state substitutes for reconstructing branch status and approval context. | Strongest substitute for exact AFPS users; not a commercial software competitor. |
| Generic workspaces and project tools | Notion, Trello, Jira, Linear | Users may bend task, project, wiki, issue, roadmap, or workflow surfaces into status tracking. | They do not natively model AFPS skill stages, product-path branch trees, or evidence refs. |
| Product discovery and product intelligence tools | Jira Product Discovery, Productboard Spark | They support idea, roadmap, feedback, product context, and competitive-analysis workflows with visible pricing. | They target broader PM teams and product workflows. |
| UX research repositories and customer intelligence platforms | Dovetail, Condens | They validate budget for centralized research evidence, search, feedback analysis, and insights repositories. | Their core object is research/feedback data, not workflow-state provenance. |
| AI coding agents and agent workflow surfaces | Claude Code, GitHub Copilot, Kiro, Linear agents | They make agentic work more mainstream and can absorb planning, docs, state, and codebase context. | Mostly build oriented; AFPS Tracker stops at research-to-build handoff. |
| Agent-control-plane tools | Runshift | They coordinate agents, context, file locks, approval gates, and audit trails. | More execution-control oriented than research portfolio mapping. |
| Ad hoc memory and status files | PROJECT_STATE.md, CURRENT_STATE.md, local summaries | They are easy to create and can preserve handoff context. | They add manual maintenance and can drift from canonical AFPS outputs. |
Force Assessment Updated
Section feedback:
| Force | Pressure | Evidence | Confidence | Implication |
|---|---|---|---|---|
| Rivalry | Moderate | No direct AFPS Tracker category was found in repo evidence or prior ICP research. Rivalry is indirect but broad across Notion, Linear, Trello, Jira Product Discovery, Productboard Spark, Dovetail, Condens, and Runshift. | Medium | AFPS Tracker does not face an obvious direct clone, but users have many adjacent places to park the same state. |
| New Entrants | High | The visible UI can be copied by users, workspace templates, or agent platforms. The harder layer is exact AFPS artifact knowledge, approval-state parsing, provenance, and safe write-back. | Medium | Defensibility depends on workflow coupling, trust, provenance, and keeping pace with AFPS artifact conventions. |
| Substitutes | High | Strong substitutes are free or already-owned: reading research/.progress.yaml, opening alignment pages, using alignment/index.html, searching with rg, asking an agent to summarize state, or maintaining a status file. | High | This is the largest structural constraint. AFPS Tracker must beat "just read the files" without creating duplicate state. |
| Buyer Power | High | The primary buyer is usually the individual AFPS operator. Direct willingness to pay is unproven. Adjacent transparent pricing creates benchmark expectations in the $10-$25 per creator/maker range and broader AI developer-tool subscriptions. | Medium-high | Pricing power is low until AFPS Tracker proves exact time savings, state fidelity, and trust around workflow files. |
| Supplier / Platform / Channel Power | Moderate-High | AFPS Tracker depends on AFPS artifact conventions, local Git/editor/agent environments, and browser-rendered alignment pages. Adjacent platforms also compete for user attention and context surfaces. | Medium | Risk rises if AFPS conventions drift or if agent/workspace platforms absorb the research-state job. |
Structural Opportunities Updated
Section feedback:
- Direct rivalry is weak at the exact AFPS layer. The market has many adjacent tools, but no observed direct competitor that reads AFPS
product_paths[], alignment pages, working packets, approval states, and task files as a coherent research portfolio. - Source-of-truth positioning can exploit substitute fatigue. Current substitutes force users to reconstruct state from YAML, markdown, HTML, and task docs.
- AI-agent growth makes the pain legible. Claude Code, GitHub Copilot, Kiro, Linear, and Runshift all validate broader movement toward agent-assisted work, multi-agent coordination, context, and control.
- Trust and provenance are a wedge against generic AI summaries. Stack Overflow's 2025 survey reports high AI usage alongside accuracy distrust, supporting a human-verifiable tracker that links back to source files.
- Adjacent categories validate spend without defining the product. Product discovery, product intelligence, research repositories, and AI developer tools all publish paid plans or enterprise motions.
Structural Risks Updated
Section feedback:
- Substitutes may be good enough. If AFPS users have only one active path or use the workflow lightly, direct file reading or one-off agent summaries may be sufficient.
- AFPS market size is unproven. The canonical ICP says public evidence does not prove AFPS user volume or direct WTP.
- Generic platforms can absorb the surface. Notion, Linear, Productboard Spark, GitHub Copilot, Claude Code, Kiro, and Runshift all have plausible paths to adjacent state-map features.
- Two-way write-back raises trust cost. Buyer power and supplier pressure rise if users fear corruption of canonical YAML or generated artifacts.
- Workflow-coupling creates maintenance burden. Schema drift, skill-output changes, or alignment-page contract changes can break the tracker unless compatibility is maintained.
Evidence Matrix Updated
Section feedback:
| Claim | Evidence | Inference | Confidence | Decision Impact |
|---|---|---|---|---|
| AFPS Tracker is scoped to research-stage branch and pipeline state. | research/afps-tracker/idea-brief.md, research/.progress.yaml, parent packet. | Approved repo artifacts keep execution tracking out of scope. | High | Preserve boundary unless artifact approval expands it. |
| Primary ICP is AFPS power users and AI workflow operators; direct WTP is unproven. | research/afps-tracker/icp.md. | Buyer power remains high until paid intent is tested. | High | Do not overstate pricing power. |
| Generic workspaces and project tools are adjacent rivals/substitutes. | Notion, Trello, Linear. | These tools cover projects, docs, issues, AI, and team workflow surfaces users may already own. | High for capabilities; medium for AFPS switching behavior. | Artifact should rate rivalry and substitutes above low. |
| Product discovery tools validate adjacent paid workflows. | Jira Product Discovery pricing; Productboard Spark pricing. | Budget exists for product discovery and product-intelligence workflows, but not necessarily for AFPS-specific state maps. | High | Use as adjacent spend evidence only. |
| Research repositories validate adjacent evidence-centralization budgets. | Dovetail pricing; Condens pricing. | Research evidence systems have paid motions, but their object is research data rather than workflow state. | High | Keep category distinction clear. |
| AI agents and control planes increase platform pressure. | Claude Code, GitHub Copilot plans, Kiro, Runshift, Linear. | These tools expand planning, context, agent delegation, and coordination surfaces that can absorb adjacent state-tracking jobs. | Medium-high | Rate supplier/platform power as moderate-high. |
| Human-verifiable state remains important despite AI adoption. | Stack Overflow Developer Survey 2025 AI section. | High AI use combined with accuracy distrust supports provenance-backed state over autonomous summaries alone. | High for developer sentiment; medium for AFPS-specific inference. | Preserve source links and approval provenance as core structural advantage. |
Assumptions And Confidence Updated
Section feedback:
| Assumption | Status | Confidence | What Would Change It |
|---|---|---|---|
| AFPS Tracker should remain tightly scoped to AFPS research-stage artifacts. | Evidence-backed by approved artifacts | High | Artifact approval expands scope to execution tracking or broad PM workflows. |
| Direct public AFPS-category rivalry is low. | Provisional | Medium | Discovery of public AFPS-compatible tracker tools, templates, or communities. |
| Substitution pressure is high. | Evidence-backed | High | User interviews show current substitutes fail even for light one-path workflows. |
| New entrant pressure is high for shallow UI, lower for safe AFPS-aware sync. | Inference | Medium | Technical validation shows AFPS parsing/write-back is trivial or much harder than expected. |
| Buyer power is high in the first ICP. | Evidence-backed | Medium-high | Direct paid-intent evidence from multiple AFPS operators or studios. |
| Supplier/platform power is moderate-high. | Inference | Medium | AFPS contracts stabilize, or a dominant platform absorbs the exact state layer. |
Alternatives Considered Updated
Section feedback:
| Alternative Finding | Why It Was Not Selected | Residual Uncertainty |
|---|---|---|
| Rivalry is low because no direct AFPS Tracker competitor exists. | Indirect rivals and substitutes can still capture attention, budget, and workflow state. | Direct rivalry could be low inside a known AFPS user group. |
| Buyer power is moderate because adjacent product tools have paid plans. | Adjacent WTP does not prove AFPS-specific WTP. | Studios or consultants may have higher WTP if they adopt AFPS across clients. |
| Supplier power is low because the product can run locally over files. | Local execution reduces vendor dependency, but AFPS schema drift and platform ecosystems still create pressure. | A read-only v1 would reduce write-back risk. |
| Threat of entrants is moderate because workflow knowledge is niche. | UI and summaries are easy for users or agents to copy; workflow knowledge only helps if encoded reliably. | If AFPS remains private/niche, commercial entrants may ignore it. |
Source Coverage Gaps Updated
Section feedback:
- No direct AFPS user interviews, install telemetry, or usage analytics.
- No current public evidence that AFPS is a recognized external workflow category.
- No direct pricing or willingness-to-pay tests for AFPS Tracker.
- No hands-on testing of competitor products against an AFPS repo.
- Limited evidence on whether AI-native studios or fractional consultants would adopt AFPS before needing a tracker.
- No technical validation yet of how brittle AFPS parsing/write-back would be across skill-output versions.
Proposed File Changes Updated
Section feedback:
| Path | Action After Artifact Approval | Notes |
|---|---|---|
docs/history/archive/YYYY-MM-DD/HHMMSS/research/afps-tracker/_working/preliminary-porter-five-forces-research.md | Create archive copy | Preserve the approved Stage 2 packet before canonicalization. |
research/afps-tracker/_working/preliminary-porter-five-forces-research.md | Remove active working packet | Stage 3 cleanup after canonical artifact is written. |
research/afps-tracker/competitive-analysis-porter-five-forces.md | Create canonical Porter artifact | Use the approved packet content plus any requested edits. |
alignment/porter-five-forces-afps-tracker.html | Convert from review to confirmed | Preserve approval decisions and caveats. |
alignment/index.html | Update status metadata if needed | Keep the central index current. |
Artifact Approval Gates Updated
Section feedback:
Compile Review YAML
Use feedback-only YAML for revisions, or answer every required gate and compile final approval YAML for agent review.
Required answers remaining: 5