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.
Per-integration sync workers
Credentials round-trip end-to-end for all 17 integrations today, but only Asana and GitHub have their sync workers lit up. Jira, Slack, Linear, Zendesk, Figma, Notion, ClickUp, Trello, Salesforce, HubSpot, and Monday are next in sequence — each shipping at the same depth as Asana or not shipping. Admins will see each card flip from 'connected, inert' to full sync as the worker lands.
Stay in the loop
Going on vacation or stepping away from a project for a week? Stay in the loop is a bounded daily start-of-day + end-of-day thread covering just the projects + channels + repos you pick, plus a consolidated catch-up report on day N when you return. Different shape from the digest (recurring + scoped to 'what shipped'); this is 'what you missed while away.'
Cross-tool correlation engine
Schema is deployed; embeddings + hotspot detection workers are written and idle pending OpenAI + Anthropic keys on the worker service. Once flipped on, the dashboard's hotspot card fills in with detected clusters of related work across tools, and every task gets a 'similar items' drawer backed by pgvector similarity over every Signal in the org.
Subscription + billing (Stripe)
Self-serve signup + Stripe subscription layer to replace the invite-only beta once we have enough paying customer signal. Pricing SKUs map to the three tiers already published on /pricing. US-only through private beta, international rollout tied to the EU-residency item below.
Digest AI narrative + Slack delivery
The digest pipeline is live end-to-end on email today. Next additions: an AI-narrated preamble that summarizes the week's highlights before the structured sections (opt-in per subscription), and Slack delivery as a channel option alongside email.
Evaluating
On the table. Not committed yet.
Inbound comment ingestion
When a teammate comments in Asana, Lumis should pick that up and attach to the same task's thread. Outbound comments ship today (write in Lumis → push to Asana); inbound is the missing half.
Custom-field write-back
Today Lumis reads Asana's typed custom fields but only writes back the standard fields (title, description, status, assignee, tags, due date, followers). A mapping layer that lets admins declare how Lumis-native fields map onto Asana's enum/number/text/date customs is the next layer.
Real-time dashboard updates
Today the app shell auto-refreshes every 60 seconds while the tab is visible. A server-sent-events channel with Redis pub/sub would make sync state, dashboard counts, and the activity feed update instantly as worker jobs finish. Plumbing is clear; slice not yet scheduled.
Native mobile experience
The app shell is now mobile-responsive (the sidebar becomes an off-canvas drawer below tablet sizes). A native app is deeper commitment we'll revisit once paying customers tell us desktop isn't enough.
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.
Dark mode
Common ask. Honest answer: doing it right means a Tailwind theme rewrite + a visual QA pass across marketing, app shell, and staff portal. Deferred until we can spend a focused slice on it rather than shipping a half-inverted app.
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.