Skip to content
ParaplanAI

What's next, and what isn't.

The public face of our post-v1 backlog. Anything firms ask for during beta lands here before it lands in a sprint — so you can see what we are building, what is parked, and what we have politely declined.

Operator promise from the beta-onboarding script: feature requests are logged, not promised. This page is the log. If it isn't here, askhello@paraplanai.co.ukand we will add it.

In the product today.

A narrow practice-management layer in service of the calc and the compliance-annex PDF. Committed scope as of the 20 May 2026 operator review — these surfaces are built, in use, and not going anywhere.

  • Pension AA + Bond TSR calc engine. Pure-TypeScript deterministic maths against the HMRC PTM / IPTM corpus. Post-2021/22 PSA + SRB recalc per HMRC Brief 12/2021.
  • Compliance-annex PDF. Branded research pack with full step-by-step working, legislative references, source-document list, and disclaimer footer on every page.
  • Client records (encrypted PII). Optional clients layer with AES-256-GCM encryption + HMAC index. Calc engine never reads PII; audit trail stays on anonymised client_ref.
  • Cases. One case = one client situation; carries calc runs, uploaded source documents, and the issued PDF artefact.
  • Multi-firm RBAC. Owner / member roles with cross-firm isolation enforced at the Supabase RLS layer.
  • Adviser sign-off workflow. Paraplanner builds the case; adviser signs off via /calc-runs/[id]/sign before the PDF is treated as final.
  • Firm branding editor. Logo + accent colour applied to the compliance-annex PDF header from the firm settings page.
  • In-app feedback widget. Beta-cohort feedback collection without leaving the surface.

Scope note: this is a narrow CRM in service of the calc and PDF — not a Voyant-style cashflow platform, not a Plannr-style end-to-end practice manager. End-client portal access, marketing-list management, fact-find collection, and suitability-letter authoring stay out (see §04 Considering).

Shipping in the current cycle.

Closing the launch checklist before the public beta opens. These are in flight today.

  • Public roadmap, business-continuity note, and founder-credentials disclosure on the marketing surface.
  • Account-deletion + data-export telemetry events so the privacy commitments at /privacy §7 are observable end-to-end.
  • Two remaining baseline property invariants (pension configVersion round-trip and DC PIA ≤ earnings).
  • RLS policy rewrites for case_drafts and case_notes to collapse auth.uid() initplans.

Queued for the next cycle.

Items audited as Medium priority — close before general availability, not blocking beta entry.

  • Migrate rate-limiter to Vercel KV / Upstash Redis so per-route caps survive cold-starts.
  • Solicitor-reviewed Data Processing Agreement at /legal/dpa as a downloadable PDF.
  • Better Stack uptime probe + on-call alerting on the public status surface.
  • @next/bundle-analyzer wired in with a per-route bundle-size budget regression test.
  • Dynamic tier-card data source so marketing/PriceTier reads billing/tiers.ts directly and can never drift again.

Beyond v1 — parked for a planning cycle.

Bigger lifts that we want a paper trail on but are not committing to a date for. Each is in the backlog because at least one beta firm has asked.

  • CRM integrations. Read-only push of the signed PDF + audit hash into Intelliflo, Plannr, Iress Xplan. Status: shortlist.
  • Anthropic Files API migration. Cuts per-extraction token spend and removes the 30-day Anthropic abuse-window for repeat documents. Status: shortlist.
  • Scottish tax bands. Currently the UI notes rUK rates apply. Adding the SRIT bands is a v2 milestone. Status: parked.
  • Dependency upgrade phase 2+. Next 14 → 16, Stripe 16 → 22, Tailwind 3 → 4, Vitest 1 → 4, React 18 → 19, Zod 3 → 4. Status: each its own PR cycle.
  • Live Supabase PITR drill. Once the project is on the Pro plan; restores a corrupted client's tenant rows from a 24-hour-old snapshot. Status: shortlist.

Asked for — declined, for now.

The discipline of a narrow tool is what makes the calc engine defensible. These items would dilute that, so they are out of v1 scope by design. We will revisit each at the next planning cycle.

  • Lifetime cashflow modelling. Voyant's domain. ParaplanAI sits next to the cashflow tool, not on top of it. Declined for v1.
  • End-client portal, fact-find, suitability authoring. The shipped narrow CRM (see §00) holds adviser-side client records and case data; it is not a Plannr-style end-to-end practice manager. End-client login, marketing-list management, fact-find collection, and suitability-letter authoring stay outside the surface. Declined for v1.
  • Mobile-native app. Mobile-responsive web only. IFAs use laptops for client work. Declined for v1.
  • SDLT, IHT, CGT calculators. Stay narrow — two tools, done well. Declined for v1.
  • User-facing “AI assistant” surface. AI is internal infrastructure inside the extraction layer; never in the calc path. Declined for v1.

If one of these is a blocker for your firm, write in. We track every “declined” vote — three votes flips an item from declined to parked, ten flips it to shortlist.