Competitive Analysis Synthesis - AFPS Tracker

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.

Executive Synthesis

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.

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

Company And Product Profiles

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.
• Adjacent workspaces, product discovery tools, research repositories, and AI developer tools validate 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.
• Product and package pricing should be delegated to later monetization work. The current evidence supports a hypothesis, not a pricing decision: OSS core with managed SaaS for users who do not want to self-host, operate, or maintain the tracker.

Market Gaps And White Space

1. 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.
2. Portfolio view without duplicated state. Native files are faithful but scattered; generic workspaces are navigable but duplicate state.
3. Evidence-linked state continuity. AI agents can summarize state, but users still need provenance.
4. 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, dogfooding metrics, or explicit monetization research.
• Make trust visible through source links, approval status, evidence refs, and non-destructive parsing.

Signals For Downstream Research

Evidence Matrix

Assumptions And Confidence Register

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 because several pricing pages need recheck before numeric claims.
• Kiro and Runshift pricing remained not found or not public in the framework pass.
• OSS-core plus managed-SaaS packaging is not yet validated.

Confirmed File Changes

Approval Record

Final Compiled Response YAML

alignment_page: alignment/competitive-analysis-afps-tracker.html
response_status: complete
approval_status: ready-for-agent-review
required_gate_status: complete
unanswered_required_questions:
  []
gate_answers:
  - section: "Research Completeness"
    gate_type: "evidence coverage"
    status: answered
    answer: "Approve evidence coverage"
  - section: "Assumptions"
    gate_type: "assumptions/confidence"
    status: answered
    answer: "Canonicalize with stronger caveats"
    notes: "I think that pricing should be delegated to the monetization skill, however I think this tool will be OSS core with a managed SaaS available for users that don't want to self-host/manage."
  - section: "Proposed File Changes"
    gate_type: "proposed file changes"
    status: answered
    answer: "Approve proposed file changes"
  - section: "Artifact Approval"
    gate_type: "artifact destination"
    status: answered
    answer: "Approve synthesis for canonicalization"
  - section: "Post-Approval Route"
    gate_type: "post-approval route"
    status: answered
    answer: "Approve post-approval routing only"

This page is current for the completed alignment cycle. Later research can amend it only by archiving this confirmed page first and highlighting the amendment.