# Roadmap

What Liftwire has decided not to build, what is still undecided, and what it is committed to. There are no dates on this page; an item gets one when it is scheduled, and the [changelog](/docs/changelog) records it when it ships.

## Decided against

- **A dashboard, gallery or browse interface.** Liftwire is used through your coding agent. The tactic pages exist so agents and search engines can read them, not as a gallery to browse.
- **A/B test or variant detection.** Telling which variant of a page a visitor saw is not in this phase, and has no date.
- **An e-commerce vertical.** The corpus is B2B SaaS marketing sites. E-commerce is not in this phase, and has no date.

## Undecided, and said so

- **Multi-step flows.** Today `audit_site` audits a site's key pages one at a time, and the `optimise_signup_flow` prompt walks an agent through a signup flow page by page. Nothing joins the steps into a funnel or measures where visitors drop out between them. Whether to build that is not decided.

## Committed

- **The library thresholds.** The launch bar and the six-month bar the tactic library must clear, with live values, are on [Library status](/docs/library-status).
- **An evaluation of whether Liftwire is worth paying for.** The same coding agent does the same conversion task with no tools, with web search only, and with Liftwire, and the results are judged blind. Its report will be published with raw transcripts whatever the result.
- **Self-serve billing**, once online payment is wired. Until then: Paid plans are set up by hand while online billing is being finished: email support@liftwire.io and your key is issued with the plan's limits. See [Limits and pricing](/docs/limits).
- **A changelog entry for every release that changes a tool, a grade rule, a threshold or a data policy**, in the [changelog](/docs/changelog).