Roadmap

What we're building. And what we're not.

Most roadmaps tell you what a team wants to build. This one also tells you what we've explicitly decided against. Every “no” on this page is a yes to going deeper on the things we said yes to.

Shipping soon

Next in line.

  • Two-way PM tool sync

    Connect your PM tool with OAuth or a personal access token. A compatibility check runs against your actual workspace before anything imports; you get a green/yellow/red report up front. Once connected, edits flow both ways with visible sync state per task, last-write-wins on conflicts, and an undo window if you pick wrong. Asana first, other tools to follow.

  • AI task review

    Catches weak descriptions, ambiguous titles, and missing acceptance criteria before they land in a status meeting. Every AI feature has a template mode that runs without a model, so regulated teams can use Lumis without sending data to one. Per-org budget caps are hard, not a polite suggestion.

  • Push-to-testing and notifications

    Transactional email for invites and digests. A Slack bot with per-channel routing. Per-user notification preferences. AI-drafted test plans with department-specific templates. One message per day, per role, instead of thirty pings across three channels.

Evaluating

On the table. Not committed yet.

  • Jira integration

    For teams migrating off Jira, or running Jira alongside Asana during a transition. A reasonable API and a large footprint make this the natural next one to do.

  • Monday integration

    We get a lot of mid-market asks for Monday. We're still working through how much of their API we can cover at the depth we care about.

  • Linear integration

    Clean API, good fit for teams running Linear on engineering and something else on the rest of the business.

  • Notion integration

    Notion's webhook support isn't quite there yet, which makes real-time sync harder than it should be. We're waiting for their API to catch up.

  • ClickUp integration

    On our radar. We're still weighing depth versus breadth on this one. The waitlist has a lot to say about it.

  • Zendesk: tickets to tasks

    Ticket webhook ingestion, turning tickets into tasks with the Zendesk metadata preserved, optional comment sync back. Opt-in per customer. Never on by default.

  • Self-serve SSO/SAML

    Enterprise auth for customer organizations. Lands when the first enterprise contract does.

  • EU data residency

    Needs a multi-region setup we don't have yet. The international waitlist is the main signal for when to prioritize this.

Explicitly NOT on the roadmap

Decided against, with reasons.

  • Replacing your PM tool

    Lumis is a layer. It is not the PM tool. If you want to switch PM tools, pick the one that fits your team. Your current one stays the system of record.

  • Built-in time tracking

    Harvest, Toggl, and Clockify already do this well. Reinventing it would take effort we'd rather spend elsewhere.

  • Native mobile apps

    The web app is mobile-responsive. A native app would cost a lot and offer very little to a product that managers mostly use at a desk.

  • Tool-specific features that don't fit the sync model

    A few things in these PM tools, like Asana portfolios, goals, and forms, have data models that don't fit a two-way sync cleanly. Those land in the capability matrix per tool, not on the roadmap.

  • Generic workflow automation (Zapier-style)

    We are betting on integrations that go deep into one tool at a time, not on shallow integrations across hundreds.

  • Per-customer AI model training

    Per-org learning through prompt construction is already enough for this use case. Training a separate model per customer is expensive and doesn't pay off at our scale.

Want in on what's next?

Private beta is free. See what already shipped or drop us your tool of choice on the waitlist — it's the main signal we use for ordering.

Join the waitlist