Building the small-business federal pursuit operating system

GovScout Pro's roadmap explains how the product is becoming more reliable, evidence-driven, collaborative, and capable across the pursuit lifecycle. Dates are planning windows, not contractual commitments. Last reviewed: July 13, 2026.

Horizon 1: Foundation and Trust (Q3-Q4 2026)

Shipped

Evidence-grounded Marcus case files

Guardrails and case-file structure for source-aware opportunity reviews.

  • Owner: Executive Technical Manager
  • Customer value: Faster, reviewable bid/no-bid decisions.
  • Dependency: Marcus evaluation suite and source trace rules.
  • Success signal: Users can explain each verdict from visible evidence.
Beta

Billing lifecycle hardening

Checkout, customer portal, webhook, failed-payment, recovery, and relock proof.

  • Owner: Release Management
  • Customer value: Clear access, invoices, upgrades, and cancellation.
  • Dependency: Stripe webhook and entitlement tests.
  • Success signal: Billing events lock and unlock the right plan automatically.
Beta

Accessibility and security baseline

Contrast, protected route, auth boundary, and CSP review work.

  • Owner: Security and QA
  • Customer value: Safer, easier product access across devices.
  • Dependency: Manual accessibility review and CSP staging.
  • Success signal: Priority pages pass contrast, keyboard, and auth checks.

Horizon 2: Complete Pursuit Workspace (2026-2027)

Planned

Persistent evidence library

Reusable company facts, certifications, past performance, and attachments.

  • Owner: Product Management
  • Customer value: Less repeated data entry across pursuits.
  • Dependency: Account storage, permissions, and privacy rules.
  • Success signal: Users can reuse approved facts in new case files.
Planned

Compliance matrices and capture plans

Structured proposal artifacts linked to the original solicitation package.

  • Owner: Engineering
  • Customer value: Clearer pursuit tasks and proposal evidence.
  • Dependency: Document parsing and case-file data model.
  • Success signal: Users can export a matrix tied to source requirements.
Planned

DOCX/XLSX/PDF exports

Downloadable work products for review and proposal operations.

  • Owner: Engineering and QA
  • Customer value: Work products can move into normal proposal review.
  • Dependency: Stable artifact templates and file-generation QA.
  • Success signal: Exports open cleanly and preserve source references.

Horizon 3: Market and Team Intelligence (2027-2028)

Planned

Award and incumbent context

Buyer and competitor context that supports lawful capture planning.

  • Owner: Product Management
  • Customer value: Better understanding of buyer history before pursuit.
  • Dependency: Reliable public award data and citation rules.
  • Success signal: Case files include current, sourced incumbent context.
Planned

Team and partner workflows

Collaboration support only where permissions and approvals protect users.

  • Owner: Security and Engineering
  • Customer value: Safer collaboration with partners and reviewers.
  • Dependency: Role permissions, audit trail, and sharing controls.
  • Success signal: Shared workspaces expose only approved pursuit data.
Exploring

Agency-specific playbooks

Reusable playbooks after federal workflows meet quality standards.

  • Owner: Editorial and Product
  • Customer value: More focused guidance for repeat agency targets.
  • Dependency: Primary-source maintenance and article review capacity.
  • Success signal: Playbooks stay current and link to official sources.

Horizon 4: Ecosystem and Post-Award (2028-2029)

Exploring

Post-award tracking

Obligations, deliverables, and performance evidence after award.

  • Owner: Product Management
  • Customer value: Preserve delivery evidence for future past performance.
  • Dependency: Pursuit workspace maturity and account controls.
  • Success signal: Users can track deliverables without mixing proposal data.
Exploring

Partner ecosystem

Consent-based relationships with providers and teaming partners.

  • Owner: Executive Technical Manager
  • Customer value: Users can find help without unclear referrals.
  • Dependency: Vetting policy, consent, and disclosure rules.
  • Success signal: Partner listings disclose role, limits, and relationship.
Exploring

Additional procurement modes

Commercial, state, or local workflows only after federal excellence.

  • Owner: Product Management
  • Customer value: Expand only after the core federal workflow is proven.
  • Dependency: Federal workflow quality, source coverage, and support capacity.
  • Success signal: New modes do not weaken federal-contracting accuracy.