Competitive Analysis Synthesis - AFPS Tracker
Stage 2 artifact review page for synthesizing four approved competitive-analysis frameworks. Canonical competitive-analysis files remain gated until final compiled YAML approval.
Status: review
Alignment date: 2026-06-16
Skill: competitive-analysis
Product path: research/afps-tracker
Canonical: gated
Scope
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.
The approved boundary excludes exec-loop-tracker, development execution tracking, generic PM replacement, active recommendation engines, and broad research repository workflows. Development-stage and AI-agent tools remain in scope only as adjacent alternatives because they can absorb context, handoff, planning, or workflow-state jobs.
Frameworks Synthesized
4 / 4
Porter, SWOT, Strategic Group Map, Feature/Pricing Matrix.
Canonical Status
Gated
No canonical synthesis or search log has been written.
Primary Risk
Substitutes
Native AFPS files and agent summaries may be good enough.
Executive Synthesis
Core finding: AFPS Tracker has no validated direct public competitor at the exact AFPS-native layer, but it sits in a high-substitution market where the user's current file bundle is the first competitor to beat.
The most important competitor is not a vendor; it is the current bundle of native AFPS artifacts, editor search, alignment pages, .progress.yaml, and ad hoc status files. That bundle is free, source-faithful, and already adopted, but it forces repeated reconstruction across YAML, markdown, generated HTML, and task history.
The strongest market gap is a passive, source-linked portfolio map that preserves AFPS artifact fidelity while making branch state, approval provenance, pipeline stage, and evidence references easier to scan. Generic workspaces and product tools are more navigable but require duplicated state. AI coding agents can reconstruct context on demand, but they do not provide a persistent, reviewable branch map and inherit broader trust issues around AI-generated summaries.
The main commercial risk is that direct AFPS user volume and willingness to pay remain unproven. Adjacent categories validate budget for product discovery, research repositories, generic workspaces, and AI developer tools, but none prove that AFPS operators will pay for passive workflow-state visibility.
Competitor Landscape
| Segment | Alternatives | Competitive Role | Synthesis |
|---|---|---|---|
| Source-native substitutes | Native AFPS repo artifacts; research/.progress.yaml; alignment/index.html; markdown; task files; ad hoc status files | Closest behavioral substitutes | Highest fidelity and zero price, but low navigability. This is the real baseline AFPS Tracker must beat. |
| Broad workspaces and PM systems | Notion, Trello, Linear | Places users can mirror workflow state | Strong for familiar surfaces, collaboration, boards, docs, and projects. Weak on AFPS-native parsing and evidence-linked pipeline semantics. |
| Product discovery and product intelligence | Jira Product Discovery, Productboard Spark | Adjacent product-decision budget competitors | Validate spend around product context, prioritization, and AI product workflows, but target broader product teams. |
| Research repositories and customer intelligence | Dovetail, Condens | Adjacent evidence/provenance competitors | Strong for research evidence centralization. They do not appear to model AFPS branch pipelines, approval YAML, or skill-stage state. |
| AI coding agents and spec/build systems | Claude Code, GitHub Copilot, Kiro | On-demand reconstruction and execution substitutes | Can summarize or act on repo context. They pressure AFPS Tracker to be faster, persistent, and more verifiable than asking an agent to reread files. |
| Agent-control planes | Runshift | Adjacent context/control-plane substitute | Validates shared context, trust gates, file locks, and auditability. More execution-control oriented than AFPS Tracker's research-state map. |
Company And Product Profiles
| Alternative | Profile | AFPS Tracker Relevance | Evidence Sources |
|---|---|---|---|
| Native AFPS artifacts | The current source of truth: progress YAML, product paths, alignment pages, framework outputs, markdown, and task docs. | Direct substitute and required input. | research/.progress.yaml; alignment/index.html; idea brief; ICP; framework outputs. |
| Ad hoc status files | Human-maintained summaries and next-step notes. | Lightweight continuity substitute but prone to drift. | Porter and Strategic Group Map artifacts. |
| Notion | Broad AI workspace with docs, knowledge base, projects, enterprise search, agents, collaboration, and pricing page. | Strong generic mirror surface; weak AFPS-native fidelity. | Product; Pricing |
| Trello | Board/card project management with templates, automation, Power-Ups, integrations, and pricing page. | Simple visual status mirror for light workflows. | Tour; Pricing |
| Linear | Product development system for teams and agents with issues, projects, docs, product planning, PRDs, and agent workflows. | Strong adjacent workflow system if research blends with execution. | Product; Pricing |
| Jira Product Discovery | Product-discovery tool for ideas, prioritization, discovery workflows, roadmaps, and Jira ecosystem connection. | Budget and category analog; not AFPS-native. | Product; Pricing |
| Productboard Spark | Product-agent and discovery workflow with product context, insights, prioritization, and pricing page. | Competes for AI-assisted product workflow attention. | Pricing |
| Dovetail | Customer insights and research repository platform. | Validates research evidence spend; not branch-state tracking. | Pricing |
| Condens | UX research repository for studies, analysis, tagging, insights, and collaboration. | Validates specialized evidence repository spend. | Pricing |
| Claude Code | Codebase-aware coding agent across terminal, IDE, web, and desktop workflows. | Strong on-demand repo-comprehension substitute. | Product; Pricing |
| GitHub Copilot | GitHub-native AI coding assistant with paid plans and agent/cloud-agent positioning. | Normalizes paid developer AI tooling. | Plans |
| Kiro | Spec-driven agentic development tool with specs, plans, tasks, steering/context, and hooks. | Adjacent spec/build workflow system; pricing not confirmed. | Product |
| Runshift | Agent-control plane for shared context, coordination, trust gates, and auditability. | Closest active-control-plane adjacency; pricing not confirmed. | Product |
Observable GTM And Pricing Patterns
- Native AFPS artifacts and ad hoc status files set a zero-price benchmark. Economic proof must come from repeated reconstruction time saved, lower context loss, and higher confidence in evidence-linked state.
- Broad workspaces, product discovery tools, research repositories, and AI developer tools validate adjacent budget categories. These are analogs only; they do not prove AFPS Tracker willingness to pay.
- AI developer tools create both budget normalization and bundle pressure. AFPS operators may already pay for Claude Code or GitHub Copilot and expect repo-state reconstruction from those tools.
- Enterprise product/research tooling is a weak first anchor because the canonical ICP starts with individual AFPS operators and dogfooding users.
- Missing pricing for Kiro and Runshift should remain a source gap; do not infer pricing model without current official evidence.
Market Gaps And White Space
- Passive, source-native AFPS branch map. Reviewed public tools do not appear to model
research/.progress.yaml,product_paths[], alignment approval state, framework working packets, or skill pipeline progression as first-class objects. - Portfolio view without duplicated state. Native files are faithful but scattered; generic workspaces are navigable but duplicate state.
- Evidence-linked state continuity. AI agents can summarize state, but users still need provenance.
- Trust-gated write-back as later expansion. Read-only or read-mostly first experience is lower-risk; write-back can expand value only when gated and auditable.
Competitive Positioning Lessons
- Compete against the user's current reconstruction workflow first, not against enterprise PM suites.
- Preserve AFPS-specific source fidelity as the product boundary.
- Treat "no direct public AFPS-native competitor found" as medium-confidence whitespace, not proof of demand.
- Avoid pricing confidence before direct AFPS operator interviews or dogfooding metrics.
- Make trust visible through source links, approval status, evidence refs, and non-destructive parsing.
Signals For Downstream Research
| Signal | Why It Matters | Suggested Validation Evidence |
|---|---|---|
| AFPS users repeatedly open three or more files/pages to answer status questions. | Confirms substitute pain and time-savings opportunity. | Dogfooding logs, screen recordings, or interviews. |
| Users trust read-only source parsing before write-back. | Reduces adoption risk and supports passive v1. | Prototype test with real progress YAML and alignment pages. |
| Multi-path projects feel harder than single-path projects. | Confirms branch-tree and portfolio-map value. | Compare user behavior across one-path and multi-path repositories. |
| Agent summaries are useful but not trusted as final state. | Supports persistent, source-linked map rather than pure AI summary. | Ask users to compare agent summary vs source-linked tracker. |
| Consultants or studios manage repeated AFPS-like workflows for clients. | Indicates commercial expansion beyond dogfooding operators. | Design-partner interviews. |
Evidence Matrix
| Claim | Source | Evidence Type | Inference | Confidence | Status | Decision Impact |
|---|---|---|---|---|---|---|
| AFPS Tracker is a research-stage source-state tracker, not a development execution tracker. | Idea brief, ICP, parent packet, all framework outputs | Repo artifact and approved synthesis | Approved scope consistently excludes execution tracking. | High | Evidence-backed | Keep canonical report scoped to AFPS research-state visibility. |
| Native AFPS artifacts are the strongest substitutes. | Porter, SWOT, Strategic Map, Feature/Pricing, progress YAML, index | Repo artifact and approved synthesis | Users already have source truth, but not a coherent portfolio map. | High | Evidence-backed | Compare AFPS Tracker first against manual repo reconstruction. |
| Direct public AFPS-native rivalry appears low. | All framework outputs | Approved web-sourced framework synthesis | Reviewed official pages found adjacent categories, not AFPS-native artifact trackers. | Medium | Provisional absence-of-evidence | State as whitespace, not proven demand. |
| Generic workspaces and PM systems are strong adjacent alternatives. | Notion, Trello, Linear official pages; framework outputs | Vendor evidence | They host mirrored state but do not natively parse AFPS artifacts. | High capability; medium AFPS behavior | Evidence plus inference | Keep them as adjacent competitors and substitute risks. |
| Product discovery and research repositories validate budget but not direct WTP. | Jira Product Discovery, Productboard, Dovetail, Condens pages; ICP | Vendor pricing/positioning and repo artifact | Adjacent spend exists, but AFPS-specific passive visibility is unpriced. | Medium-high | Inference | Avoid numeric pricing recommendations before WTP validation. |
| AI agents and control planes can substitute by reconstructing context on demand. | Claude Code, GitHub Copilot, Kiro, Runshift pages; frameworks | Vendor evidence and framework inference | Agent tools have code/repo context, specs, tasks, or control planes. | Medium-high | Inference | AFPS Tracker must be persistent, faster, and more verifiable than prompts. |
| Trust and provenance are central to the wedge. | Stack Overflow 2025 AI survey cited in Porter/SWOT; AFPS alignment workflow | Survey plus repo artifact | Heavy AI adoption coexists with trust concerns, and AFPS records evidence and approvals. | Medium-high | Evidence-backed trend plus AFPS inference | Preserve source links, evidence refs, and approval records. |
Required: Research Completeness
Is the evidence sufficient to use this synthesis as the basis for canonical competitive analysis?
Assumptions And Confidence Register
| Assumption | Status | Confidence | What Would Change It |
|---|---|---|---|
| AFPS Tracker should remain tightly scoped to AFPS research-stage artifacts. | Evidence-backed | High | User expands scope to generic PM, research repository, active recommendations, or execution tracking. |
| Direct public AFPS-native rivalry is low. | Provisional absence-of-evidence | Medium | Discovery of public AFPS-compatible trackers, templates, dashboards, or communities. |
| Passive source visibility is valuable enough for v1. | Provisional | Medium | Dogfooding shows users still prefer raw files or agent summaries. |
| Adjacent pricing pages are useful anchors but not direct pricing proof. | Inference | Medium-high | AFPS operators benchmark only against free files or bundled AI tools, or direct WTP tests reveal separate budget. |
| Write-back should be optional and gated after read-only value is proven. | Inference | Medium | Users demand write-back before value, or any write-back is rejected categorically. |
| Current framework source coverage is sufficient for synthesis review. | Evidence-backed for approved frameworks; provisional for final market confidence | Medium | Approval requests exact numeric pricing, hands-on trials, or direct interviews before canonicalization. |
Required: Assumptions And Confidence
How should these assumptions be handled in the canonical artifact?
Alternatives Considered
| Alternative Conclusion | Why It Was Not Selected | Residual Uncertainty |
|---|---|---|
| AFPS Tracker has low competitive pressure because no direct competitor was found. | Too optimistic: source-native substitutes, generic tools, and AI agents create high substitution pressure. | Exact AFPS power users may still feel a stronger gap than adjacent-market evidence can prove. |
| AFPS Tracker should compete as a product discovery or research repository tool. | That invites broader collaboration, feedback ingestion, research analysis, and roadmap expectations outside approved scope. | Later product paths might pursue a broader category after user evidence. |
| AI agents make a tracker unnecessary. | Agents can reconstruct state, but persistence, navigability, and source-linked proof remain gaps. | If agent summaries are reliable and fast enough in real AFPS repos, tracker demand weakens. |
| Write-back should be removed from the concept. | The approved idea brief includes a companion sync layer; evidence supports caution, not deletion. | Read-only prototype tests should determine whether write-back is needed. |
| Adjacent tool pricing can define AFPS Tracker pricing. | Adjacent pricing validates categories but not direct WTP for passive AFPS visibility. | Design-partner interviews could justify a specific package later. |
Source Coverage Gaps
- No direct AFPS user interviews, install telemetry, or usage analytics.
- No direct willingness-to-pay tests for passive AFPS Tracker.
- No hands-on competitor trials against a real AFPS repository.
- No exhaustive proof that no public AFPS-native tracker, plugin, or template exists.
- No technical validation of parser brittleness across historical AFPS artifact versions.
- Exact current numeric plan prices were intentionally not normalized in the Feature/Pricing Matrix because several pricing pages need recheck before numeric claims.
- Kiro and Runshift pricing remained not found or not public in the framework pass.
Proposed Canonical File Changes After Approval
| Path | Action | Notes |
|---|---|---|
docs/history/archive/YYYY-MM-DD/HHMMSS/research/afps-tracker/_working/preliminary-competitive-analysis-synthesis.md | Create archive copy | Preserve approved synthesis packet before canonicalization. |
research/afps-tracker/_working/preliminary-competitive-analysis-synthesis.md | Remove active working packet | Stage 3 cleanup after canonical artifact is written. |
docs/history/archive/YYYY-MM-DD/HHMMSS/research/afps-tracker/_working/competitive-analysis-run.yaml | Create archive copy | Preserve completed framework selection manifest. |
research/afps-tracker/_working/competitive-analysis-run.yaml | Remove active run manifest | Synthesis completion ends the framework loop. |
research/afps-tracker/competitive-analysis.md | Create canonical synthesis artifact | Use approved packet content with canonical header updates and final post-approval ## Next Steps. |
research/afps-tracker/competitive-analysis-search-log.md | Create canonical source log | Capture framework source URLs, repo-source inputs, source gaps, and reasoning trail. |
research/.progress.yaml | Update active path pipeline stage | Set AFPS Tracker active path pipeline_stage: competitive-analysis if final approval confirms canonicalization. |
alignment/competitive-analysis-afps-tracker.html | Convert from review to confirmed | Preserve approval decisions, caveats, evidence matrix, and final YAML. |
alignment/index.html | Update status metadata | Keep central index current. |
Required: Proposed File Changes
Are these the approved mutation boundaries for Stage 3 finalization?
Approval Gates
Required: Artifact Approval
Should this synthesis be canonicalized after any requested edits?
Required: Post-Approval Routing Timing
The current review page intentionally does not emit downstream skill routing. Should the Stage 3 canonical artifact generate the final Next Steps section only after approval?
Compile YAML
Use section feedback for revision requests. Use final compiled responses when the artifact review is ready for agent handling.
Answer at least one gate question or select section feedback to compile YAML.