What's next for Estimay: our roadmap

9 October 2026 · Updated 24 October 2026 · 4 min read

Estimay already covers the whole planning poker round: create a room, share the link, vote in secret and reveal together, and the voting result is saved as the estimate. Here is what we're working on next, and the principles every new feature follows.

Recently added

• Hosted in the EU. The app and its database now run in Amsterdam, the Netherlands, so what Estimay stores stays in the European Union.
• AI assistants, over MCP. Connect Claude, Claude Code, Cursor or ChatGPT, and it can set up a room with your sprint's stories and record the agreed estimates, signed in as you, with no account. The vote itself stays with the people in the room. Here's what MCP is and how it works.
• Linear. Connect a room to Linear, import a cycle's or the backlog's issues with their identifiers, and each final estimate goes back to the issue as a comment and its estimate. Like Jira and Trello, the connection belongs to the room. How it works.
• Google Meet. Start Estimay from Activities in a Meet call, and the room opens on the main stage for everyone in it, with no sign-up: each person types a name. People outside the call can still join through the invitation link. How it works.
• Jira. Connect a room to Jira Cloud, import a sprint's or the backlog's issues with their keys, and each final estimate goes back to its story points field. Like Trello, the connection belongs to the room. How it works.
• Trello. Connect a room to your Trello board, import a list's cards as stories, and each final estimate goes back to its card as a comment. The connection belongs to the room, so nobody needs an Estimay account. How it works.
• Slack app. Type /storyvote in a channel to start a room there, and open it right inside Slack, in its side panel, with your Slack name already filled in. People in a browser can still join through the invitation link. How it works.
• Discord Activity. Start Estimay from Activities in a Discord voice channel, and everyone who joins it lands in the same room with their Discord name already filled in. People in a browser can still join through the invitation link. How it works.
• Telegram Mini App. Open @storyvoteappbot or a room's Telegram link and plan inside Telegram, with your Telegram name already filled in. The Invite button shares a room straight to a chat, and rooms stay shared with people in a browser.
• Presenter view. A clean, read-only window for a shared screen, with a QR code to join and a full-screen button, while you keep the controls in your own tab.
• Floating scoreboard. In Chrome and Edge on desktop, a small always-on-top window with who has voted and your cards, which opens by itself when you leave the tab where the browser allows it.
• A compact phone layout. One row of seats and a smaller deck, so a round fits the screen.
• Async rooms. Choose Async when you create a room: every story opens for voting as it is added, and everyone votes in their own time, over hours or days. Cards turn over when the host or a facilitator reveals them, and the room shows what is waiting for you.
• Extra questions. Ask Risk, Clarity, Agent-ready or AI tokens next to the estimate, each with its own short row of cards, and keep the answers with the story.
• Auto-reveal. The cards turn over by themselves once everyone connected has voted.
• A story queue. Next takes the next story, drag to reorder, and open any estimated story to look back at its cards and results.
• AI tokens deck. Estimate how much model usage a story will take, from 10k to 10M+, next to its points. Here's how to choose a card.
• Custom decks. Type your own cards, or start from Fibonacci, T-shirt sizes or powers of two and change them.
• Discussion timer. The host or a facilitator starts a clock for the whole room from the top bar, and can add a minute, restart or cancel it. Here's how timeboxing sprint planning works.
• Facilitators. The host can let others run the game: add stories, start votes, reveal and change the settings.
• Reactions. Throw a 👍, a 🎾 or a 🎯 at a teammate's card, or send a ❤️ or a 🎉 that floats up everyone's screen, as on a live stream, without your name on it.
• Spectator mode. Product owners and observers can watch without voting, from the invitation or in Settings.
• Change your vote after the reveal. Anyone who voted can change their card from their seat, and the saved estimate follows.
• Hand the room over. A host who has to go can make someone else the host instead of ending and deleting the room, and can remove people from it.
• CSV import and export of stories and their estimates.

Bring stories in, get estimates out

Stories already come in and go out as CSV files, and a Jira sprint, a Linear cycle or a Trello list comes in with its estimates going back to its issues or cards. Next:

• Copy to clipboard. Copy the session's results straight into a spreadsheet or a ticket, without a file.
• More trackers. Import stories from GitHub Issues, GitLab Issues and ClickUp and send the agreed estimates back, as Jira, Linear, Trello and Asana do today. Connecting a tracker will be optional: if you don't, Estimay never touches your backlog, just as today.

Estimate across time zones

Async rooms are here. Next:

• Reminders to tell teammates a story is waiting for their vote.

Keep and learn from your estimates

• Session summary. A one-page summary when the session ends: every story, its votes, the agreed estimate and the total.
• Optional sign-in. Joining will never need an account. Signing in, with your email, Google or GitHub, will keep your rooms on every device you use.
• Optional history. A signed-in host can save a room, so the team can come back to it. Rooms that aren't saved are still deleted when they end, or after 7 days (30 for an async room).
• Team insights. How often the team reaches consensus, which stories caused the biggest spread of votes, and how estimates add up across sessions.

Fit into your team's tools

Estimay is planning poker and the API around it, so the rest of your tools can start a room and use its results.

• More for AI assistants. More tools for the MCP server (revote, end a room, the deck, the timer, a results export, writing estimates to your tracker), ready-made prompts and a Claude Code plugin.
• Public API. Create rooms and read results from your own scripts and bots, with personal access tokens and an OpenAPI description.
• Webhooks. Get a call when an estimate is set or a room ends, to connect Estimay to Zapier, n8n, Make or your own service.
• Chat notifications. Post a session summary to a Slack or Microsoft Teams channel.

For every team, everywhere

• In your language. The whole site and the room in German, Spanish, French, Portuguese, Ukrainian, Turkish, Japanese and Polish.
• For larger organisations. Single sign-on, an audit log and admin controls, for teams whose company requires them.

Planning poker for AI-assisted teams

When an AI agent builds the story, the ticket is the prompt, and everything the team worked out during the vote has to end up in it. These features are about getting it there, without adding AI to the vote itself:

• Story notes. The goal, scope, constraints and open questions the team agreed on, kept next to the estimate and included in the CSV download, in the shape we describe in planning poker when AI agents write the code.
• Questions from the ? card. Whoever plays ? can type the question behind it. After the reveal it's listed under the story as an open question, instead of being forgotten by the next one.
• Copy as an agent-ready brief. Copy a story, its agreed estimate and its notes as Markdown, ready to paste into a ticket or an agent's prompt.
• Actuals and calibration. Import what each story really used (tokens, passes, review time) after the sprint and see it next to the estimate, so the retro starts with the stories that surprised you.

Exploring: AI assistance

We're looking at AI features, such as summarising a story's discussion, pointing out gaps in a story before it's estimated, or tidying the notes into a brief. Two rules will hold: the AI never votes, and it never shows a suggested estimate before the team's own cards are revealed, because an early number anchors everyone and hides the disagreement that makes planning poker work. These features would mean sending room content to an AI provider, so they would only ever be opt-in, and only after we've updated our Privacy Policy to say exactly what is sent and where.

What stays the same

• Joining stays instant. Teammates join with a link and a name, without creating an account.
• Data stays minimal. Anything that stores more, or shares data with another service, is opt-in, and the Privacy Policy is updated first.
• Ads stay out of the way. Ads pay for Estimay today (how that works). They appear on the site's pages, such as this blog, never in a room, and are personalised only if you agree. New features don't bring other third-party scripts.
• Simple first. Starting a session should always take under a minute. Features that get in the way of that won't ship.

Tell us what to build first

This roadmap has no dates, and the order isn't fixed: what gets built first depends on what teams ask for. Which of these would help your team most? Is something missing? Write to [email protected]. We read everything.

← All articles