Feature Roadmap
Living document. The product/feature plan, bucketed by capability area — what we build next and in what order. Companion to the two other roadmap pillars. Direction set with the owner on 2026-05-30.
How the roadmap is organized — three pillars
Hackorda's planning splits into three documents, each a distinct "bucket":
| Pillar | Doc | Answers |
|---|---|---|
| Infrastructure | Roadmap | How do we scale + harden? (Neon → queue → multi-tenant) |
| Core Features | this doc | What product capabilities do we build next? |
| Flows | Flows | How does each user journey work, step by step? (F-01→F-16) |
Current state of every shipped feature lives in Feature Matrix; this doc is the forward-looking view that turns its "Gaps" backlog into a prioritized plan.
Near-term lead: Tester Experience & Retention
The product is a two-sided marketplace (testers file bugs ↔ orgs pay for them). The near-term bet is the supply side: make testers want to stay and file more, better bugs. Everything else still progresses — this just front-loads the Tester Experience bucket in the Now lane.
Prioritization model
Each bucket is laid out as Now (this quarter) · Next (following) · Later (when triggered). The consolidated cross-bucket view is in §"Now/Next/Later at a glance" near the bottom — start there for the single prioritized list.
The buckets
A. Tester Experience & Retention ⭐ lead
Flows: F-07 (test run) · F-08 (file issue) · F-12 (balance) · F-16 (mobile) Shipped: run packs, draft autosave, file-issue + AI intake, balance dashboard (5 buckets), CSV export, mobile-friendly tester paths.
| When | Item | Why |
|---|---|---|
| Now | PWA manifest (installable) | Low effort, big ergonomics win — testers add to home screen, file on the go |
| Now | Mobile audit on issue detail | Same overlay/lightbox treatment as triage; filing on a phone should feel native |
| Now | File-issue speed + draft UX polish | Shorten the path from "found a bug" to "filed"; the core repeated action |
| Now | Earnings/balance clarity | Make "what am I owed / what's pending verification" unmistakable — trust = retention |
| Next | Tester onboarding/first-run guidance | Reduce time-to-first-bug for new testers |
| Next | Reputation / leaderboard surfacing | Tie the existing leaderboard into tester motivation loops |
| Later | In-app tester notifications richness (ties to bucket G) |
B. Triage & Evaluation
Flows: F-09 (triage) · F-10 (verification gate) Shipped: cross-cycle triage queue, single-card UX, mobile overlay, inline severity reclassify, lightbox, comments thread, group-by on All-Issues (#270).
| When | Item |
|---|---|
| Now | Cycle issues list polish — finish payout-status column, attachment count, severity filter chips (group-by-status shipped via #270) |
| Next | Bulk triage actions (approve/reject multiple) |
| Later | Smart triage ordering (AI-suggested priority) — pairs with bucket E |
C. Payouts & Finance
Flows: F-11 (payouts) Shipped: period batch run, per-tester batch, verification gate, per-issue payment, balance buckets.
| When | Item |
|---|---|
| Next | Past-batches view — drill into a payout_batches row, list issues paid, regenerate receipt, void |
| Next | Void/correct-payment UI (schema supports, no UI yet) |
| Later | Billing/usage metering per org (feeds Monetization + Analytics) |
D. Catalog & Cycle Setup
Flows: F-04 (catalog) · F-05 (cycle create) · F-06 (cycle docs) Shipped: orgs/products/versions CRUD, cycle CRUD + status machine, self-join toggle, per-cycle rate + verification-gate overrides, Notion-style cycle docs.
| When | Item |
|---|---|
| Later | Cycle templates (clone a cycle's config/docs) |
| Later | Cycle-close report as downloadable PDF |
E. AI & Automation
Flows: F-14 (Anthropic AI) Shipped: intake / run-summary / cycle-close agents, provenance log, vision via DO Spaces, key in admin UI.
| When | Item |
|---|---|
| Next | AI cost-cap enforcement (currently logged, not enforced) — pairs with infra durability (queue) |
| Later | Duplicate detection via pgvector embeddings |
| Later | AI-assisted triage prioritization (bucket B) |
F. Integrations
Flows: F-15 (Linear export) Shipped: Linear export (single + group), Linear admin UI.
| When | Item |
|---|---|
| Next | Linear → Hackorda webhook — pull external_status back (replaces manual sync) |
| Later | Jira / GitHub Issues export (schema supports, no UI) |
| Later | Multi-tenant Linear (per-org config) |
G. Notifications & Engagement
Flows: F-13 (notifications) Shipped: in-app bell + dropdown, 11 event types, mark-all-read, triage/payment pings.
| When | Item |
|---|---|
| Next | Email notifications (deferred today) |
| Next | Telegram bot fan-out — strong fit for the tester audience |
| Later | Digest/summary notifications |
H. Identity, Access & Admin
Flows: F-01 (sign-in) · F-02 (role mgmt) · F-03 (impersonation) Shipped: login, role management, admin impersonation, two-axis RBAC.
| When | Item |
|---|---|
| Next | Retire legacy student/admin role string; consolidate on numeric ROLES (code-health) |
| Later | Multi-tenancy (per-org isolation) — the big one; tracked as infra Phase 4 |
| Later | Encrypted credential store (creds currently plain in organization_integrations.config) |
I. Analytics & Telemetry
Cross-cutting (every bucket emits events). Shipped: the event taxonomy is named in feature-matrix §4 — nothing emits yet.
| When | Item |
|---|---|
| Next | Event sink — events table + emit helper, wire the documented event sites |
| Next | Per-feature usage dashboard ("which features are used heavily") |
| Later | Per-org usage analytics (feeds Monetization) |
Now / Next / Later at a glance
The single prioritized lane across all buckets.
🟢 Now (this quarter — Tester Experience leads)
- PWA manifest (installable) — A
- Mobile audit on issue detail — A
- File-issue speed + draft UX polish — A
- Earnings/balance clarity — A
- Cycle issues list polish (columns/filters) — B
🟡 Next
- Past-batches view + void/correct-payment UI — C
- AI cost-cap enforcement — E
- Linear webhook (status pull) — F
- Email + Telegram notifications — G
- Event sink + usage dashboard — I
- Legacy role consolidation — H
⚪ Later
- Cycle-close PDF, cycle templates — D
- pgvector dedup, AI-assisted triage — E
- Jira/GitHub export, multi-tenant Linear — F
- Multi-tenancy, encrypted creds — H (infra Phase 4)
- Per-org usage analytics, billing/metering — C/I
Open product decisions (owner's call, before the relevant item)
- Notification channels priority — email vs Telegram first? (Telegram fits the tester audience; email is more universal.)
- PWA scope — installable manifest only, or push notifications too (bigger lift)?
- Analytics build vs buy — self-hosted
eventstable vs PostHog (also an infra-roadmap open decision). - PDF reports — server-rendered (Puppeteer, like the proposal system) vs a service.
How we work this
- This doc is living — when a Now item ships, move it to "shipped" in the relevant bucket and pull the next item up.
- Feature work rides the same PR-per-change + green-CI flow as everything else.
- Re-confirm the near-term lead each quarter; it currently points at Tester Experience.
- The infra work that unblocks features (durable queue for AI cost caps + the event sink; multi-tenancy for per-org isolation) is tracked in Roadmap — the two roadmaps move together.