Roadmap

Meles is in development. This is what we're building, in the order we plan to build it. There are no dates: we'll add them when we can keep them.

The teams we're talking to can change the order, and when they do, this page changes too. If you'd want something sooner, say so when you join the waitlist.

Done so far

The groundwork, finished and running.

  • Foundations

    Hosting, deploys that check the service is healthy before they finish, error tracking, uptime monitoring and database backups.

    Done

  • A size budget for the widget

    The widget has a 20 KB budget, and the build fails if it goes over.

    Done

  • The waitlist

    It's open. Joining is how you'll hear first when there's something to try.

    Done

Now: the first release

What the first teams will use. Each item says whether work on it has started.

  • Talking to teams

    We're interviewing product and growth teams about how they ask and announce today. What we learn decides what comes first, and how Meles is priced.

    In progress

  • The widget

    One small script, or an npm package. It loads after your page is idle, works in single-page apps and on mobile web, and never throws errors into your page.

    Not started

  • Modals and banners

    Announce what's new, or nudge people towards something, with a call to action.

    Not started

  • Surveys

    NPS, CSAT, multiple-choice and open-text questions, inside your product.

    Not started

  • Targeting and a fatigue budget

    Show each campaign to the right people, by page, user traits and events. Frequency caps and a fatigue budget across every campaign mean nobody gets three popups in one visit.

    Not started

  • A builder with a live preview

    Set up a campaign in a form, and see exactly what your users will see before it goes out.

    Not started

  • Results

    Every response in one table, an NPS summary, and CSV export.

    Not started

  • Your whole team

    Invite teammates by email, with roles.

    Not started

  • AI agents, through MCP

    Run campaigns and read results from an AI agent, through an MCP server.

    Not started

  • Webhooks and Slack

    Send responses to your own systems with signed webhooks, and get notified in Slack.

    Not started

  • Deleting and exporting data

    Delete or export a person's data on request, through the API as well as the dashboard.

    Not started

Next

After the first release.

  • Integrations

    HubSpot, Segment and Zapier first, then cohort sync with PostHog, Mixpanel and Amplitude.

  • A public API, and campaigns as code

    A documented REST API, and a command-line tool that keeps campaign definitions in your repository.

  • AI insights

    Responses tagged and summarised by theme, with a weekly digest in Slack.

  • Link surveys

    Hosted survey pages you can share as a link.

  • A/B tests and multilingual surveys

    Test two versions of a campaign, and ask in your users' languages, with AI translation.

  • Bringing in past responses

    Load the survey responses you already have from a CSV file.

  • The dashboard as an app

    Install the dashboard on your phone or desktop, with push alerts for new responses.

Later

Guiding people through your product.

  • Product tours

    Multi-step tours, built with a visual element picker.

  • Checklists

    Onboarding checklists that tick themselves off as people use your product.

  • Tooltips and hotspots

    Point at a feature where it lives.

  • A “What's new” widget

    An in-product changelog, with a hosted page. Meles's own changelog will run on it.

  • React, Vue and Next.js wrappers

    Components for the frameworks you already use.

Considering

We'll build these only if enough customers ask for them.

  • A lightweight messenger

    A contact form or chat that hands off to the support tool you already have.

  • AI answers from your docs

    Answers drawn from your own documentation.

  • Native mobile SDKs

    React Native and Flutter, if the mobile-web route falls short.

  • SSO and audit logs

    For teams whose security reviews need them.

  • EU data residency

    A second hosting region, in the EU.

  • SOC 2

    For teams whose procurement requires it.

Ideas we're weighing

Things other survey and feedback tools do that aren't in our plan yet. None of them is promised. If one matters to you, tell us when you join the waitlist.

  • Surveys in your emails

    A survey's first question inside an email you already send, so answering takes one click.

  • Surveys inside a page

    Embed a survey in a page of your product or site, not only in a popup.

  • A feedback button that's always there

    A small tab people can open whenever they have something to tell you.

  • More question types

    A rating matrix, image choices, and file or screenshot uploads.

  • Personalised questions

    Use a person's name, plan or earlier answer in a question, and pass hidden fields along with each response.

  • Recurring surveys and response caps

    Ask the same person again on a schedule, and stop a survey once it has enough responses.

  • More ways to target

    By a person's earlier answers, their country and language, or their company's traits.

  • AI help writing surveys

    Draft a survey from a sentence, and let AI ask a follow-up when an answer is vague.

  • Dashboards and scheduled reports

    Build and share your own charts, and get them by email on a schedule.

  • Your data warehouse

    Send responses to BigQuery and other warehouses, to analyse them beside everything else.

  • More integrations

    Salesforce; marketing tools such as Customer.io and Braze; Google Sheets, Make and n8n; RudderStack; and Microsoft Teams.

  • Sequences

    Campaigns that follow on from each other, such as a series of onboarding messages.

  • Link surveys on your own domain

    Host survey pages at an address of your own.

Join the waitlist

The waitlist hears first when there's something to try. In the meantime you'll get a short build-in-public update every two weeks: what we built, what we learned from the teams we talked to, and what's next.

Two quick questions help us decide what to build first.

What do you want first?
NPS, CSAT, feedback and churn questions
Banners, popups and what's-new posts
Later: we'll build these after surveys and announcements