← Mayetik

Changelog

New features and improvements, in order of release.

July 2026

Knowledge structure, now with direction — connected to your workflow, and structured as a graph.

Categorize sessions, group them into recurring series, and watch trends emerge automatically. Intake records feed the knowledge base. Synthesis action plans go straight into Jira. And now every brief automatically extracts named people, decisions, risks, and commitments into a searchable knowledge graph — so nothing important gets buried in prose.

Organize your knowledge

Session categories

Classify any session as a Health Check, Win/Loss, Discovery, Alignment, Retrospective, Pre-Mortem, Stakeholder Feedback, or Other. The category appears as a badge in the session list and enables structural filtering across the knowledge base — find all health checks without relying on search terms.

BeforeFinding sessions of the same type required remembering the naming convention you used or scrolling through a long list.
AfterSelect a category in the session Details tab. The badge appears in the list instantly.

Recurring series

Group sessions that ask the same questions on a recurring schedule — monthly health checks, quarterly win-loss reviews — into a Series. The series page shows each instance with its synthesis status and response count.

BeforeRunning the same session monthly meant creating unrelated sessions with no structural link between them. Comparing findings required opening each one separately.
AfterCreate a series, assign sessions to it, and view all instances in one place — with cadence, synthesis status, and session counts side by side.

Series trend analysis

Once a series has at least two instances with completed syntheses, generate an AI trend analysis that compares the synthesis content across all instances. The result names specific themes with direction labels — Improving, Declining, Stable, Emerging, Resolved — and produces a single actionable recommendation.

BeforeSpotting trends across recurring sessions required manually reading each synthesis and comparing them side by side.
AfterClick Generate trend analysis on the series page. The AI compares all instance syntheses and returns a directional theme breakdown in seconds.

Unified category taxonomy

Sessions, recurring series, and campaigns now share one 11-value category vocabulary — including three new values (Futurespective, After-Action Review, Lessons Learned) merged in from what used to be a separate campaign-only list. Choosing a category for a campaign now automatically derives its campaign type.

BeforeSessions and campaigns each had their own separate category system, so the same concept — a retrospective, say — meant something slightly different depending on where you set it.
AfterOne category means the same thing everywhere — on a single session, a recurring series, or a multi-department campaign.

Synthesize with confidence

Synthesis readiness progress

Before org or project synthesis can run, Mayetik now shows exactly what is missing: a progress bar counting completed session syntheses toward the threshold, a per-session checklist with status indicators, and a direct link to trigger whichever session synthesis is still needed. No more guessing why the button is unavailable.

BeforeWhen synthesis could not run, a generic message appeared. Finding out which sessions still needed synthesis required opening each one and checking manually.
AfterA readiness panel shows how many of the required session syntheses are complete, which sessions are done, pending, or failed, and links directly to the ones still outstanding.

Synthesis DOCX export

Download any completed org or project synthesis as a Word document. The exported file preserves the full synthesis content with heading structure, ready to share, archive, or paste into a report.

BeforeSynthesis content was readable in the app only.
AfterClick Download DOCX on any completed synthesis and it arrives as a formatted Word file.

Synthesis table of contents

Long synthesis outputs now include a linked table of contents in the sidebar so you can jump directly to any section — themes, risks, action items, or whichever focus the synthesis was generated with.

BeforeNavigating a long synthesis meant scrolling to find the section you needed.
AfterA persistent table of contents on the right lets you jump to any section instantly.

Post-synthesis next actions

After a synthesis is generated, a contextual action bar appears below it suggesting what to do next: ask Mayetik a question about the findings, find follow-up interview questions, or review the previous synthesis for comparison.

BeforeAfter reading a synthesis, deciding what to do next — whether to ask a question, dig deeper, or compare — required navigating away manually.
AfterThree suggested actions appear directly below the synthesis: Ask Mayetik, Find follow-up questions, and Review previous.

Guided follow-up sessions

Completed org and project syntheses now suggest follow-up session ideas with a recommended audience and a one-click handoff into Session Studio. Studio opens with the synthesis context preloaded so admins can generate the next round of questions without starting from a blank prompt.

BeforeFinding the next session to run after a synthesis required manually translating the findings into a Studio prompt.
AfterClick Open in Studio from the synthesis output. Mayetik creates a draft follow-up session and preloads Studio with the right context.

Synthesis brief packs

Download a lightweight Markdown brief pack from any completed org or project synthesis. The pack bundles the synthesis, source list, Ask Mayetik prompt suggestions, generated follow-up questions, and suggested follow-up sessions for strategy reviews.

BeforeSharing a synthesis meant exporting the DOCX and separately collecting source context, follow-up questions, and next-session ideas.
AfterClick Brief pack to download one review artifact that combines the synthesis and the next steps.

Synthesis lineage and outcomes

Follow-up sessions created from a project or organization synthesis are now traced back to the synthesis that produced them. The synthesis page shows whether each follow-up is still a draft, collecting responses, has its first response, or is ready for a new synthesis pass.

BeforeAfter opening a follow-up session from synthesis, the original synthesis did not show what happened next.
AfterOpen any completed synthesis to see the follow-up sessions it created, their response progress, and the next best place to continue.

Know what to unlock next

Synthesis progress ladder

A three-rung status widget — Session, Project, Org — on the project dashboard, org dashboard, and series pages shows exactly what's blocking the next level of synthesis, with direct links to whichever specific sessions or projects still need to finish.

BeforeKnowing whether you had enough completed sessions to run a project synthesis, or enough project syntheses to run an org synthesis, meant checking each level manually.
AfterOne glance at the ladder shows what's done, what's partial, and exactly which session or project to finish next.

Intake forms in the knowledge base

Intake records indexed automatically

When a respondent completes an intake form, Mayetik now generates a prose summary of their responses and indexes it alongside session briefs. Completed intake records appear as sources in Ask Mayetik queries with a blue badge, attributed as 'Form: [form title]' to distinguish them from session briefs.

BeforeIntake form responses lived in the Records tab only. They were not searchable through Ask Mayetik and did not contribute to the organization's knowledge base.
AfterEvery completed intake record is indexed automatically. Ask Mayetik now searches across session briefs and intake responses in a single query.

Workflow integrations

Slack notifications

Connect a Slack incoming webhook to receive real-time alerts in any channel when briefs are ready, syntheses complete, upstream blockers are flagged by a campaign, or your weekly knowledge digest is ready. Configure which notifications to receive independently per organization.

BeforeKnowing when a brief or synthesis was ready required checking Mayetik manually or waiting for an email.
AfterConfigure a Slack webhook in org Settings. Notifications arrive in your channel automatically — brief ready, synthesis complete, and blocker detected.

Jira integration

Connect your Atlassian Jira instance and push any completed project or org synthesis action plan to Jira as a story with one click. The issue key links back to the source synthesis so work items stay traceable to the organizational knowledge that produced them. Creation is idempotent — clicking again returns the existing issue key.

BeforeSynthesis action plans lived in Mayetik only. Moving them into the team's backlog meant copying content into Jira manually.
AfterClick → Jira on any completed synthesis. A Jira story is created in your default project, labelled 'mayetik', and the issue key appears as a direct link.

Salesforce integration

Connect your Salesforce org in Settings using a Connected App (Client Credentials Flow — no user credentials stored). Once connected, any completed knowledge brief can be linked to a Salesforce Opportunity, Account, or Contact with one click. A search dialog lets you find the right record by name; Mayetik creates a Note on it with the full brief content, visible to everyone with access to that record. The linkage persists so the button becomes a direct link back to the Salesforce record.

BeforeKnowledge captured in Mayetik — win/loss debriefs, discovery notes, customer intelligence — had no path into Salesforce. Reps who needed it had to find the brief in Mayetik and copy relevant parts manually.
AfterClick Link to Salesforce on any completed brief, search for the Opportunity or Account, and confirm. The brief appears as a Note on the Salesforce record — visible to every rep with access, without leaving Mayetik.

Confluence integration

Connect your Confluence instance in org Settings using an Atlassian API token and a default space key. Once connected, any completed project or org synthesis shows a → Confluence button. Clicking creates a formatted page in your Confluence space — headings, lists, and emphasis preserved. The page URL is stored; subsequent clicks return the existing page link rather than creating a duplicate.

BeforeSynthesis findings lived in Mayetik only. Getting them into the team's Confluence wiki meant copying and reformatting by hand.
AfterClick → Confluence on any completed synthesis. A formatted page appears in your configured space — linked back to the synthesis, findable in Confluence search.

HubSpot integration

Connect HubSpot via a Private App token in org Settings — the portal ID is fetched automatically, no manual entry needed. Once connected, any completed knowledge brief can be linked to a HubSpot Deal, Contact, or Company. A search dialog with separate tabs lets you find the right record by name; Mayetik creates a note on the linked record and the brief content appears in the activity timeline.

BeforeKnowledge briefs captured in Mayetik had no path into HubSpot. Revenue teams who ran on HubSpot had to find the brief separately and update CRM records by hand.
AfterClick Link to HubSpot on any completed brief, choose Deal, Contact, or Company, search, and confirm. The brief appears as a note in the HubSpot record timeline — visible to everyone with access.

Outbound webhooks (Zapier / Make)

Configure an outbound webhook per organisation in Settings. Mayetik fires a signed HTTP POST to your endpoint when a brief completes or a synthesis completes — or both, configured independently. Payloads are signed with HMAC-SHA256 via an X-Mayetik-Signature header. The webhook secret is auto-generated if left blank. Last delivery status and timestamp are visible in the settings UI. Works with Zapier, Make, n8n, or any service that accepts inbound webhooks.

BeforeThere was no way to trigger automations when a brief or synthesis finished without polling Mayetik manually.
AfterConnect Zapier or Make once — then automations fire the moment knowledge is ready: notify a Slack channel, create a Notion entry, update a spreadsheet, or trigger any downstream workflow.

SharePoint / OneDrive integration

Connect a SharePoint document library in org Settings using an Azure AD app registration (tenant ID, client ID, client secret) and a site URL. An optional folder path scopes uploads within the library. Once connected, any completed project or org synthesis shows a → SharePoint button that uploads the content as a markdown file to the configured folder. The file URL is persisted and the button becomes a SharePoint ↗ link. Idempotent — pushing a second time returns the existing file URL.

BeforeSynthesis findings had no path into SharePoint. Teams using SharePoint as their knowledge base had to export and upload manually.
AfterClick → SharePoint on any completed synthesis. A markdown file appears in your document library — versioned, searchable, and accessible alongside the rest of the team's knowledge.

Google Drive integration

Connect a Google Drive folder in org Settings using a service account email, private key, and folder ID. No OAuth redirect required — share the target folder with the service account email once during setup. Once connected, completed project and org syntheses show a → Google Drive button that uploads synthesis content as a markdown file to the configured folder. Idempotent — the same synthesis always produces the same file.

BeforeSynthesis content stayed in Mayetik only. Teams who managed documents in Drive had to copy and paste findings by hand.
AfterClick → Google Drive on any completed synthesis. The file lands in your Drive folder — shareable, indexable by Google Search, and editable in Google Docs.

Dynamics 365 integration

Connect a Dynamics 365 instance in org Settings using Azure AD Client Credentials (tenant ID, client ID, client secret, instance URL). Once connected, any completed knowledge brief shows a Link to Dynamics 365 button. A search dialog with Account, Contact, and Opportunity tabs lets you find the right record by name using live OData queries. Mayetik creates an annotation note on the linked record with the full brief content, visible in the activity feed. The linkage persists; the button becomes a direct link to the Dynamics record.

BeforeKnowledge briefs had no path into Dynamics 365. Teams running deals and accounts in Dynamics had to locate briefs in Mayetik and update records by hand.
AfterClick Link to Dynamics 365 on any completed brief, search for the account or opportunity, and confirm. The brief appears as a note in the record activity feed — visible to everyone with access, without leaving Mayetik.

Notion integration

Connect Notion in org Settings using an internal integration token and a parent page ID. Share the target Notion page with the integration once via the page's Connect menu — no OAuth flow required. Once connected, any completed project or org synthesis shows a → Notion button. Clicking creates a structured page under your configured parent, with synthesis content converted to native Notion blocks: headings, lists, paragraphs, and dividers — with inline bold and italic preserved. The page URL is stored and the button becomes a Notion ↗ link. Idempotent — pushing a second time returns the existing page.

BeforeSynthesis findings had no path into Notion. Teams who managed their knowledge base or project wiki in Notion had to copy and reformat content by hand.
AfterClick → Notion on any completed synthesis. A structured page appears under your configured parent — properly formatted, searchable in Notion, and shareable with your team in seconds.

Knowledge graph

Automatic entity extraction

Every completed knowledge brief is now analyzed to extract named entities across four categories: people (named individuals referenced), decisions (explicit choices or conclusions), risks (specific blockers or concerns), and commitments (stated future intentions with a named actor). Entities are extracted with a confidence score; only high-confidence items are retained. The extraction runs in the background — briefs remain accessible immediately while entities are built.

BeforeKey people, decisions, risks, and commitments buried in knowledge brief prose could only be found by reading each brief individually.
AfterEvery brief automatically extracts and indexes named entities. They are searchable and filterable by type and project without opening individual briefs.

Entity browse page

The Knowledge Repository now includes an Entities page showing all named people, decisions, risks, and commitments extracted from completed briefs across the organization. Filter by entity type (People, Decisions, Risks, Commitments), project, or free-text search. Click any entity to expand the supporting excerpt from the original brief.

BeforeThere was no way to see all decisions or risks across an organization's briefs in one place.
AfterOpen Entities from the Knowledge Repository header. Filter by type or project to find what the organization has collectively decided, flagged, or committed to.

Commitment tracker

The Entities page includes a Commitment Tracker panel that highlights commitments captured in a brief that have not been referenced in any subsequent brief within 90 days. These are commitments with no follow-up signal — the people named in them may not have been heard from since.

BeforeCommitments made in sessions had no follow-up tracking. Finding which ones had stalled required searching manually.
AfterThe Commitment Tracker surfaces unresolved commitments automatically. Each entry shows the commitment text, the project it came from, and when it was captured.

Entity badges on Ask Mayetik sources

When Ask Mayetik returns sourced answers, each source card now shows up to three entity badges — decisions, risks, or commitments extracted from that brief. Badges provide instant structural context about the content of each source without opening it.

BeforeSource cards in Ask Mayetik showed session metadata (title, respondent, date) but no content signals.
AfterSource cards show entity badges for the top decisions, risks, and commitments in each brief, giving immediate context alongside the citation.

Entities tracked stat on Organizational Intelligence

The Organizational Intelligence dashboard now shows a fifth stat card — Entities tracked — displaying the total number of knowledge entities extracted across all org briefs all time. Clicking the card navigates directly to the Entities page.

BeforeThe Organizational Intelligence dashboard showed brief volume, sessions, and contributors, but no signal about structural knowledge density.
AfterA single number on the dashboard shows how much structured knowledge — decisions, risks, commitments, people — has been captured from the organization's sessions.

Explore what you already know

Analysis Workbench

Generate source-backed themes from your organization's completed knowledge briefs — then inspect, organize, and act on what the evidence actually says. Themes are grouped by signal strength (Strong, Moderate, Weak) with a source count derived from how many briefs ground each one. Click any theme to expand an inline evidence panel showing the excerpt from each contributing brief, with a direct link to the original session. Analyst controls let you pin a theme for visibility, dismiss one that is not relevant, rename it to match your language, and add a private note with context or caveats. Copy an evidence pack to share a theme and its supporting evidence as formatted Markdown. Jump from any theme into Ask Mayetik with a prefilled query that surfaces deeper evidence from the indexed archive.

BeforeUnderstanding what the organization had collectively learned required reading each synthesis individually, cross-referencing findings manually, and hoping nothing was missed.
AfterOpen Analysis Workbench from the org workspace. Filter by project or date range, click Generate themes, and within 60 seconds the AI returns 5–8 source-backed themes grounded in your completed briefs — with evidence you can inspect, accept, rename, and act on.

Reach respondents where they are

Voice Call Intake

A phone-style respondent experience for intake forms. Respondents open a shareable call link that looks and feels like an incoming phone call — an animated ring screen, a spoken greeting, and questions read aloud one at a time. Each answer is captured by voice, displayed on screen as a transcript, and confirmed with a tap or by saying "yes." Answers save field by field so a dropped call loses no progress. The call link shares the same form and record as the existing chat interface — admins choose which to share.

BeforeIntake forms required respondents to type answers in a chat interface, which felt unfamiliar on mobile or in hands-free contexts.
AfterShare the call link. Respondents tap to answer, speak their responses, confirm each one, and hang up when done — no typing required.

Learn and get oriented

Getting Started Guide

A four-step tutorial at /guide that walks new users through their first session, invitation, and knowledge brief. The page resolves your first project automatically so every step links directly to the right place in your workspace — no navigating required.

BeforeNew users had to explore the product to discover the sequence: find a session, send an invitation, wait for a brief. Each step was one more thing to work out.
AfterOpen /guide and follow four steps: view your session, invite someone, read the brief, and open the learning guide. Direct links, right workspace, no guesswork.

Project setup checklist

When you have a project with sessions but no briefs yet, the project dashboard shows a four-step Getting Started checklist: session published, invitation sent, response received, first brief generated. Each step links directly to the relevant page. The checklist hides automatically once you receive your first brief.

BeforeThe project dashboard showed stats and navigation links, but did not indicate whether a project had been fully set up or what still needed to happen.
AfterThe checklist surfaces on the dashboard until you hit your first brief — then steps aside.

Learning Guide

A single scrollable reference page at /learn covering the concepts behind Mayetik: what sessions are, how knowledge briefs work, why structured conversations outperform surveys, the full knowledge flow pipeline, the role hierarchy, invitation types, synthesis, and Ask Mayetik. Sections are labelled by audience — basics, admin, and advanced — so readers can stop when they have what they need.

BeforeUnderstanding the concepts behind Mayetik required using the product and working things out from context.
AfterRead /learn before or alongside using Mayetik. The learning guide explains the why behind every major feature — without requiring a demo or onboarding call.

Glossary

A public glossary at /glossary with 37 defined terms across four categories — Product, Technical, Business, and Methodology. Each term has a definition, a usage example, and links to related terms. Filterable by category. Each term has a dedicated page for direct sharing.

BeforeMayetik terminology — briefs, sessions, synthesis, intake — was not explained in one place. New users and stakeholders encountered terms without a reference.
AfterOpen /glossary and browse or search any term. Link directly to a specific definition when sharing context with a colleague or documenting a workflow.

Help hub articles

The Help hub is now organized into three topic groups — Getting started, Building sessions, and Collecting & analyzing — each linking to a focused article instead of one long page. Ten articles cover the most common questions.

BeforeThe help hub was a single long page; finding the answer to one specific question meant scanning past everything else.
AfterOpen Help, pick a topic group, and go straight to the article that answers your question.

Get to value faster

Template deep-link activation

Any template — on a public audience page, the template library, or in-app — now has a direct activation link. Clicking it resolves your primary project, handles sign-in with a redirect back if needed, and opens the session creation wizard with that template pre-selected. No manual navigation required.

BeforeFinding a template on a landing page or library page and then starting it in the product required signing in, navigating to a project, finding the sessions list, and opening the Browse Templates panel.
AfterClick Start with this template. Mayetik handles the rest — sign-in, project resolution, and wizard pre-fill included.

Contextual help panels

Seven key pages — Ask Mayetik (project and org), Campaigns, Intelligence, Intake Forms, Session wizard, and Synthesis — now include an expandable help panel. Each panel explains what the feature does, when it works best, and the single best next step for a first-time user. Panels collapse after reading and never block the page.

BeforeLanding on an unfamiliar feature page — Campaigns, Synthesis, Ask Mayetik — gave no in-context explanation of when to use it or how to start.
AfterOpen the Help panel on any of the seven pages. Best used when, next step, and a learn-more link are one click away without leaving the page.

Guided empty states

Campaigns, Intake Forms, and Synthesis now show a numbered Try this first guide when the page has no content yet. Each step links to the action that makes progress possible — creating a campaign, building a form, or triggering a synthesis — so admins know exactly what to do without hunting for the right button.

BeforeEmpty state pages showed a generic message and a single action button, with no indication of what sequence of steps was needed to get from zero to something useful.
AfterThe empty state walks you through the setup sequence step by step. Follow the guide and the page fills itself in.

Session creation decision prompt

A highlighted Studio-first card sits above the session list at all times — type a title and go straight into Studio — alongside shortcuts to start blank, use a template, or import from JSON.

BeforeThe empty-state prompt for creating a first session only appeared once, so returning admins starting a second or third session had no consistent entry point.
AfterThe same creation prompt is always there. Pick Studio, a template, blank, or JSON import — every time.

Sales templates

Six new curated templates — Win/Loss Debrief, Competitive Intelligence, Discovery Call Capture, Buyer Committee Mapping, Rep Knowledge Transfer, and Quota Review Debrief — under a new Sales category.

BeforeSales teams browsing templates found nothing built for their use cases — win/loss debriefs, competitive intel, discovery calls.
AfterA Sales category with six ready-made templates matches exactly what a revenue team runs — debrief, competitive intel, discovery, buyer mapping, handoff, and quota review.

Make value visible

Outcome Dashboard

An org-level outcome tracker that shows whether captured conversations are becoming structured evidence, syntheses, action plans, and operational work. The Outcome Loop visualization moves through five stages — Capture, Evidence, Synthesis, Action, Integration — with live counts at each stage. A metric grid shows sessions, completed briefs, syntheses, action plans, Jira issues, and knowledge entities side by side. A per-project breakdown shows which projects are contributing to the outcome pipeline and which are stalled.

BeforeThere was no way to see what all the sessions, briefs, and syntheses had actually produced at an org level — whether the captured knowledge had turned into anything.
AfterOpen the Outcome Dashboard from the org workspace. The pipeline from conversations to tracked work is visible in one view — with counts at every stage.

Pilot Success Report

A sponsor-ready outcome summary page that packages the org's pilot proof into a shareable format, with a Markdown download. The report shows the Outcome Loop with live data, per-project status, and a curated next-steps section generated from the org's actual state — not a template. Download it as a formatted Markdown file for a business review, board deck, or procurement conversation.

BeforeDemonstrating pilot value to a sponsor or budget holder required manually gathering stats from multiple pages and assembling a summary by hand.
AfterOpen Pilot Success Report from the Outcome Dashboard. Download a Markdown file that summarizes what was captured, structured, and turned into follow-up action — ready to share without writing a single word.

Guided Proof Workspace

A step-by-step workspace that helps org admins establish first pilot evidence. Five pre-configured proof paths — Organizational pulse, Win/loss intelligence, Program impact, Sprint retro, and Knowledge transfer — each link directly into Session Studio with the right template pre-loaded. Live progress metrics at the top of the page show sessions created, responses collected, briefs generated, and syntheses run from the org's own data.

BeforeNew org admins starting a pilot had to figure out which session type to run first, how to involve the right people, and how to show early progress — all without a structured path.
AfterOpen the Proof Workspace, pick a proof path that matches your pilot goal, and click through to start the session. Your progress metrics update as sessions complete.

Governance and portability

Governance & Data Portability Center

A control panel for org admins who need to verify data access, plan portability, or satisfy a security or procurement review. The page shows a four-item readiness grid — Access, Portable data, Auditability, Destinations — with live counts drawn from the org's actual state. A portable inventory lists every exportable record type with counts and direct export links. A portability manifest download generates a dated Markdown summary of the org's data inventory, access controls, and export capabilities.

BeforeAnswering 'where is our data, who can access it, and how do we get it out?' required contacting support or navigating multiple pages to assemble the answer.
AfterOpen the Governance Center. The readiness check, portable inventory, and manifest download are on one page — ready to share with IT, security, or procurement in minutes.

Your integration hub

Integration Center

A unified hub that shows the connection status of all 10 Mayetik integrations — Slack, Zapier/Make, Jira, Confluence, SharePoint, Google Drive, Notion, Salesforce, HubSpot, and Dynamics 365 — in a single view, grouped by category. Each card shows the integration description, primary use case, and a Configure or Review settings button that links directly to the right settings section. A header stat shows how many of the 10 integrations are currently connected. Three setup-sequence tips guide new admins through a recommended activation order.

BeforeSeeing which integrations were active required scrolling through the full settings page and inferring connection status from whether credentials had been saved.
AfterOpen Integration Center from the org workspace. Connected integrations show a green badge; unconfigured ones show a Configure button. The full stack is visible at a glance.

Manage who sees what

Bulk Ask Mayetik access

Grant or revoke Ask Mayetik access for multiple project participants at once from the Members page, with a live count showing how many participants can currently query the knowledge base.

BeforeTurning on knowledge-base access for a whole team meant clicking Grant once per person.
AfterSelect everyone who needs access, click Grant once, and see exactly how many participants can query the knowledge base at a glance.

Clearer upgrade path

Trial Conversion Panel

A contextual upgrade panel on the org dashboard that adapts its headline, recommendation, and call-to-action to the org's actual state. Urgency is shown as Healthy, Ending soon, or Blocked. The recommended package — Project Intelligence or Organizational Intelligence — is derived from whether the org has multiple projects or active campaigns. The nudge escalates through four stages based on completed briefs: no briefs prompt 'create proof first'; a few prompt 'build more evidence'; enough briefs surface the specific upgrade recommendation with a direct link to pricing.

BeforeThe trial banner showed days and responses remaining, but gave no guidance on which plan to upgrade to or whether the org had built enough value to justify it.
AfterThe conversion panel reads your usage and tells you what to do next — build more evidence, or upgrade to the package that fits your scope. The recommendation matches your actual pattern.

Updated pricing packages

Paid tiers are now named Project Intelligence and Organizational Intelligence — replacing the previous Team and Pro labels. Project Intelligence covers up to 10 projects with 300 responses per month and project-level synthesis and search. Organizational Intelligence covers unlimited projects with 1,500 responses per month, org synthesis, integrations, governance, and the Outcome Dashboard. An Enterprise tier is available for custom volumes, dedicated onboarding, and security review.

BeforePlan names ('Team', 'Pro') described a company size rather than what intelligence capability the plan unlocked.
AfterPlan names describe scope: Project Intelligence for one team, Organizational Intelligence for the whole organization.

June 2026

Campaigns is here.

Run coordinated sessions across every team in your organization — with progress tracking, per-department synthesis, and org-level action plans, all from one place.

Campaigns

Multi-department campaigns

Create a campaign, attach a session to each department, and invite everyone at once. Progress, synthesis, and action plans for every department roll up into a single campaign view.

BeforeRunning the same session across multiple teams meant duplicating sessions, managing separate invitation lists, and assembling findings by hand.
AfterOne campaign covers every department — tracking, synthesis, and action plans included.

8 campaign types

Choose a type and Mayetik pre-loads the right question sets, synthesis guidance, and action plan framing. Types span retrospectives, vision alignment, engagement pulse, performance review, risk assessment, go-to-market readiness, and policy review.

BeforeEvery campaign started from scratch — question structure, synthesis framing, and action plan format all had to be worked out each time.
AfterChoose a type and the right scaffolding loads automatically.

Per-department action plans

Once a department's responses are synthesised, Mayetik generates a concrete action plan: what to do, who owns it, and why it matters.

BeforeSynthesis told you what people said, but translating that into concrete steps was left to you.
AfterA prioritised action plan comes out of synthesis automatically, drawn directly from the findings.

Cross-department synthesis

After all departments complete, Mayetik synthesises across them: where teams agree, where they diverge, and what the organisation should prioritise next.

BeforeComparing findings across teams meant reading multiple synthesis documents and drawing your own conclusions.
AfterMayetik surfaces the patterns and divergences across every department in a single report.

Auto-synthesis

When every invited participant in a department submits, synthesis runs automatically. Org admins receive an email when it's ready.

BeforeYou had to remember to trigger synthesis for each department once responses were in.
AfterIt runs on its own — you get an email when it's done.

Campaign progress tracking

See how far each department has come — completed vs. invited — from both the campaign list and the campaign detail page.

BeforeChecking participation required opening each session and counting responses.
AfterA progress bar per department, visible at a glance from the list.

Release cycle retrospectives

A dedicated campaign type for engineering teams running multi-team retrospectives after each release. Supports linked cycles so you can track how commitments carry forward over time.

BeforeRetrospective findings lived in isolation — no easy way to see whether last cycle's actions were followed through.
AfterEach cycle links to the next, with commitment tracking built in.

Know what your organization is learning

Organizational Intelligence Dashboard

A live snapshot of knowledge capture across your organization. Headline stats (all-time and 30-day brief counts, sessions, and contributors), a 12-week brief volume chart, top projects, top contributors, and the 6 most recently generated knowledge briefs — all on one page.

BeforeUnderstanding how much knowledge your organization was actually capturing meant checking each project individually.
AfterA single page shows the full picture: brief volume over time, which projects are most active, and who is contributing.

Theme Pulse

On-demand AI analysis of the 15 most recent knowledge briefs in your organization. Extracts 5–8 recurring themes — topics, concerns, and insights that surface across multiple contributors — with a summary of each and an overall observation.

BeforeFinding patterns across briefs meant reading them manually and forming your own synthesis.
AfterClick Generate and see the recurring themes across your most recent knowledge, extracted automatically.

Ask Mayetik — org level

Ask a plain-language question across every project in your organization and get a synthesized answer with citations. Optionally narrow the search to a single project. Each source shows the project name so you know where the answer came from.

BeforeAsk Mayetik was scoped to one project at a time — org-wide search required checking each project separately.
AfterOne question, searched across every indexed brief in the organization.

Reusable Ask questions

Save high-value org-level Ask prompts and rerun them in one click. Saved questions appear directly in Ask Mayetik, can be deleted when they are no longer useful, and are audit logged for traceability.

BeforeTeams had to remember or retype the questions they wanted to ask repeatedly.
AfterRecurring intelligence questions become shared, reusable prompts.

Answer follow-up questions

After Mayetik answers an org-level question, it now suggests next-best follow-up questions with Run and Save controls, plus quick paths back to the repository and org synthesis.

BeforeAfter reading an answer, deciding what to ask or synthesize next was left to the user.
AfterMayetik keeps the intelligence loop moving with contextual next steps.

Knowledge brief detail pages

Open any completed brief from the organization repository to read the full markdown brief, review source context, download it, jump back to the source session, or ask Mayetik about it.

BeforeThe repository showed recent briefs, but reviewing a full brief required finding it through another workflow.
AfterEach brief has a dedicated detail page that connects reading, asking, downloading, and synthesis.

Org Synthesis

Generate a cross-project synthesis across all project syntheses in your organization. Choose one of 6 focus types — Top Themes, Risks & Blockers, Lessons Learned, Decisions & Rationale, Stakeholder Alignment, or Action Items — and Mayetik synthesizes through that lens.

BeforeProject syntheses existed in isolation. Rolling up findings across all projects was a manual exercise.
AfterOne synthesis across every project, shaped by the focus that matters right now.

6 focus types for project synthesis

When generating a project synthesis, choose a focus: Top Themes, Risks & Blockers, Lessons Learned, Decisions & Rationale, Stakeholder Alignment, or Action Items. Each produces a different lens on the same session data.

BeforeProject synthesis always produced the same five-section report regardless of what you actually needed to know.
AfterChoose a focus and get an analysis shaped by the question you're trying to answer.

Project briefs export

Export all completed knowledge briefs for a project as JSON (full content) or CSV (metadata and 2,000-character preview). Available from the responses page header when at least one brief exists.

BeforeIndividual briefs could be downloaded one at a time as Markdown files.
AfterAll briefs for a project in one file — JSON for downstream processing, CSV for review.

Build sessions worth taking

Session Studio

Describe your research goal in plain language and the AI generates a complete session design: questions, answer types, hints, and branching logic. Refine through conversation, apply in one click. Available on any draft session.

BeforeA blank question list.
AfterA full design, shaped by conversation, ready to publish.

Readiness Review

Before publishing, run an AI quality check across eight design criteria. Get a scored report with flagged issues and suggested questions you might have missed.

BeforePublishing meant hoping the session design was sound.
AfterA scored quality report with specific issues flagged — before anyone sees it.

Curated templates

Browse a library of ready-to-use session templates, each scored for readiness. Clone any template into your project and customise from there.

BeforeFinding a good starting point meant searching externally or building from memory.
AfterA scored library, one click to clone.

Get started and stay informed

Welcome session for new accounts

Every new account starts with a Team Health Check session already built — four questions covering wellbeing, what's working, current challenges, and what leadership should know. A welcome email arrives at sign-up explaining the three-step path to a first brief.

BeforeNew accounts landed on an empty project with no guidance on where to start or what a session should look like.
AfterSign up and find a ready-to-publish session waiting. Review the questions, publish, and you're collecting responses within minutes.

First-run guidance on the project dashboard

When a new account has a draft session with questions but hasn't published yet, the project dashboard shows a context-aware Getting Started card with the session name, question count, and a direct link to review and publish. The card disappears automatically once the first session is published.

BeforeNew users had to find the Sessions section, open the draft, and figure out the publish flow without any prompting.
AfterThe dashboard tells you exactly what to do first — and confirms you're ready with a question count before you go.

Response notification emails for admins

Project admins and owners receive an email as soon as a participant completes a session and a knowledge brief is generated. The email names the participant, the session, and links directly to the responses page. Anonymous respondents from public questionnaires are included.

BeforeAdmins had no way to know a response had come in without checking the dashboard manually.
AfterA notification arrives the moment the brief is ready — participant name, session title, and a direct link to review.

May 2026

Know what participants actually said

Responses overview

Every response across all sessions in a project, filterable by session, status, respondent, and date range, from a single page.

BeforeReviewing responses meant opening each session one at a time.
AfterThe full project picture, filtered however you need it, in one place.

CSV export

Download any session's responses as a spreadsheet-ready file: one row per respondent, one column per question.

BeforeResponses lived in Mayetik and nowhere else.
AfterOne click and they're in your spreadsheet.

Ask Mayetik

Ask a question in plain language and get a synthesised answer drawn from every knowledge brief in the project, with citations to the sessions it came from.

BeforeUnderstanding what participants said across a project meant reading every brief yourself.
AfterAsk a question, get a synthesised answer with sources.

Project synthesis

Once two or more sessions have been individually synthesised, Mayetik generates a cross-session view: convergent themes, divergent findings, gaps and blind spots, and an organisation-level action plan.

BeforeCross-session analysis was a manual exercise.
AfterMayetik synthesises across every session in the project — themes, divergences, gaps, and next steps.

Brief download

Download any participant's knowledge brief as a Markdown file from the responses page.

BeforeKnowledge briefs were readable in the app only.
AfterDownload and share them anywhere.

Reach anyone, without the friction

Public questionnaire

Share any session via a unique link — no account required. Respondents complete the session anonymously and receive a knowledge brief when they finish.

BeforeCollecting responses from people outside your organisation required creating accounts for them.
AfterShare a link — anyone can respond, no setup needed.

Intake forms

Build AI-driven data collection forms for external respondents. Define the fields you need; the AI gathers them through natural conversation. Completed records export as CSV or JSON and can trigger a webhook.

BeforeCollecting structured data from external respondents required a separate tool.
AfterBuild a form in Mayetik, let the AI collect it conversationally, and export the results.

Hands-free voice mode

When text-to-speech is enabled, sessions flow automatically: the AI reads the question aloud, the microphone activates, and silence detection stops the recording when the participant finishes speaking.

BeforeVoice input still required participants to click Record after hearing each question.
AfterThe AI reads, the mic starts, silence stops it — no clicks required.

Voice selector

Choose the voice participants hear from six options: Nova, Alloy, Echo, Fable, Onyx, and Shimmer. Set it per session.

BeforeAll sessions used the same AI voice.
AfterChoose the one that fits the tone of your research.

Personalized completion message

Add a custom message participants see after they submit — to thank them, set expectations, or point them to next steps.

BeforeParticipants saw a generic confirmation screen.
AfterA message written by you, specific to this session.

Feedback pipeline

Users can submit feedback from any page in the product. Submissions land in an admin inbox where they can be triaged, assigned a status, converted into GitHub issues with AI-written specs, and tracked through to resolution.

BeforeProduct feedback had no structured home — it arrived by email or not at all.
AfterA full pipeline from in-app submission to GitHub issue to resolution.

April 2026

Mayetik is live.

The complete session lifecycle is here: design a session, invite participants, capture answers, and deliver a knowledge brief to everyone who takes part.

From question to knowledge, end to end

Session Flow

Participants move through a session one question at a time. When they finish, a personalized knowledge brief is generated automatically — a structured summary of everything they shared.

BeforeKnowledge collection happened in scattered documents, meeting notes, and email threads with no consistent format.
AfterEvery participant gets a structured brief the moment they finish — no follow-up, no manual synthesis.

Voice Input

Participants can speak their answers rather than type them. Audio is transcribed in real time; only the text is stored.

BeforeCapturing spoken knowledge required a separate recording tool, manual transcription, and hours of editing.
AfterSpeak an answer and it's captured as text, automatically.

Build and manage sessions

Session Builder

Create sessions with text, multiple choice, and rating scale questions. Reorder questions, add hints to guide responses, and soft-delete without losing historical answers.

BeforeDesigning a structured question set meant a third-party survey tool, disconnected from where you stored and analyzed results.
AfterBuild, publish, and manage sessions in the same place you review responses.

Publish and Close Workflow

Sessions move through draft → published → closed. Participants can only join published sessions; closing locks new responses without deleting existing ones.

BeforeKnowing when a session was open or under construction required manual coordination with your team.
AfterA clear status workflow keeps every session in the right state at every stage.

Bring in your team

Invitation Flow

Send email invitations to participants. Each invitation creates the right membership automatically on acceptance — no manual account setup required.

BeforeGetting participants into a tool meant creating accounts for them or sharing a generic link with no tracking.
AfterSend an invitation; Mayetik handles membership when it's accepted.

Google Sign-In

Sign in with a Google account alongside magic link email. No password required either way.

BeforeMost knowledge tools required a password, creating friction for occasional participants.
AfterSign in with Google or a magic link — no password, no account setup.

Organizations and Roles

Group projects under an organization with owner and admin roles. Org admins can create projects, manage members, and invite new people without needing system admin access.

BeforeManaging access across multiple projects meant touching every project individually.
AfterSet roles at the org level and they apply across every project within it.

Know what happened and when

Audit Trail

Every significant action — invitations sent and accepted, sessions published, members added and removed, roles changed — is logged with a timestamp and the user who triggered it. Viewable at system, organization, and project level.

BeforeWhen something changed, there was no way to know who did it or when.
AfterA full, immutable log of every action across the platform, scoped to whatever level you need.