Roadmap
Feature Classification
Core-Now
| Feature |
Why |
| Proposal drafting, revision, review, approval, share, export |
This is the product |
| Multi-tenant auth, roles, workspace access |
Everything else depends on correct tenant/role boundaries |
| Public share portal |
Externally visible, tied directly to proposal delivery |
| Proposal exports and export history |
Export is part of the core outcome |
Later
| Feature |
Why |
| CRM: accounts and contacts |
Useful and supportive — not the primary reason the product exists |
| Templates, assignees, SLA reminders |
Improve throughput around core workflow; secondary to draft-review-share-export loop |
| Architecture canvas and BOM/cost estimator |
Helpful enrichment; should not keep driving workbench complexity up |
| AI quality and readiness workflows |
Keep parts that materially improve approval quality; don't expand casually |
Drop
| Feature |
Why |
| Broad AI experimentation surfaces |
Scope creep; if a new AI surface doesn't directly strengthen a core workflow, don't build it now |
| Additional admin/ops/analytics expansion |
Only justified when tied to reliability, security, or revenue |
60-Day Priorities
Priority 1: Proposal Lifecycle Reliability
- Tighten remaining lifecycle route/service boundaries
- Add targeted regression coverage for review and export edge cases
- Remove remaining brittle behaviour around approval/share/export transitions
- Success: core lifecycle changes easy to ship; regressions caught before merge; no recurring production bugs in share/export/approval
Priority 2: Workbench Maintainability
- Keep simplifying parent orchestration and panel boundaries
- Improve highest-friction workbench interactions only where they affect core workflow
- Continue adding helper-level tests for extracted decision logic
- Success: no new wide flat prop surfaces; no new large monolithic workbench files; user-facing regressions trend down
Priority 3: Delivery Confidence
- Keep CI runtime reasonable while preserving meaningful gates
- Add missing high-value workflow coverage only where a real blind spot remains
- Review flake risk in app-backed and browser tests
- Success: CI remains understandable and green; app-backed tests stay stable; new tests added selectively
Deferred (60-day window)
Out of scope unless directly tied to reliability, security, or revenue:
- New AI analysis surfaces
- More workbench tabs or side panels
- Broader CRM expansion
- Additional admin or ops UI expansion
- Nice-to-have analytics widgets
- New demo/public experiences
- Broad billing/settings surface growth
- AI experimentation not tied to proposal quality, approval discipline, share, or export
Reassessment Triggers
Revisit the roadmap only if:
1. A customer or revenue-critical need clearly changes product priority
2. Production reliability issues shift the risk profile
3. The current three priorities are materially complete