Echometer
5.3Psychology-backed retros and team health checks for engineering teams
Echometer is a German retrospective, health-check and 1:1 meeting platform built around recurring pulse surveys, structured retros and longitudinal team development tracking. It pitches itself to busy team leads — engineering managers, scrum masters and agile coaches — who want research-grounded question libraries rather than a blank whiteboard.
Full review →
LetRetro
6.0The retro tool that thinks with your team
LetRetro is a fast-shipping, AI-forward retrospective platform aimed at engineering teams rather than Scrum Masters. AI clusters the cards, writes the board summary and drafts action items that open as Jira, GitHub or GitLab issues; Voice Mode lets anyone speak a card straight into the right column; and an official MCP server lets Claude, Cursor and VS Code read and drive boards. Excalidraw-style Canvas boards, sentiment trend analyses and a team health checker sit on flat pooled-seat pricing — $15/mo for up to 200 seats — rather than per user.
Full review →Summary
Echometer scores 5.3 overall and is best for engineering managers and agile coaches who want recurring health-check pulses tied to retros, with EU data residency and a research-flavoured question library. It offers a free tier.
LetRetro scores 6.0 overall and is best for developer-leaning agile teams and startups that want AI-assisted retros wired into Jira, GitHub and GitLab, an official MCP server their AI clients can drive, and flat pricing that doesn't grow with headcount — and that don't need a timer, recurring retros or a procurement-grade security story. It offers a free tier.
Echometer leads on retro toolkit, fun factor and enterprise-grade. LetRetro leads on ease of use, value, AI & insights, integrations and open platform.
Across our eight scoring dimensions, LetRetro edges ahead with an overall score of 6.0. That said, the right pick depends on your team — see the dimension-by-dimension breakdown below.
Scores compared
| Detail | Echometer | LetRetro |
|---|---|---|
| Category | Retrospectives | Retrospectives |
| Team size | Mid-market | Small |
| Free tier | Yes | Yes |
| Free limit | Starter: 1 team, 25 workspace members, unlimited retro guests, 1 retro/month after trial, 2-retro archive per team | 3 boards, 1 team, 20 pooled seats, 1 canvas, 2 AI docs/mo, 5 exports/mo, 10 voice cards/mo; no integrations and no MCP requests; community support |
| Starting price | €29/team/mo | $15/mo (Pro, flat) |
| Est. 3 teams × 8 people | €87/mo billed annually (3 teams × €29 Pro) | $15/mo (Pro — flat plan covers unlimited teams within its 200 pooled-seat cap; 24 users fits) |
| Enterprise | Yes | Yes |
| Founded | 2019 | 2025 |
| HQ | Münster, Germany | Bengaluru, India |
| Data residency | Germany | — |
| Languages | 2 (English, German) | English only |
| Export formats | PDF · Markdown · Email | PDF · Markdown |
| Features | 44 | 27 |
| Integrations | 1 | 5 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | Echometer | LetRetro |
|---|---|---|
| Features | ||
| Custom templates | ✓ | ✓note |
| Anonymous input | ✓ | ✓ |
| Health Checks | ✓ | ✓note |
| Action tracking | ✓ | ✓ |
| Async mode | ✓ | — |
| Whiteboard | ✓ | ✓note |
| Independent voting | ✓ | ✓ |
| Polling | ✓ | ✓note |
| Icebreaker games | — | — |
| Agile Estimations | — | — |
| Team Kudos | — | — |
| AI grouping/clustering | — | ✓ |
| AI action items | ✓note | ✓note |
| AI Summaries | — | ✓ |
| Team Insights | — | ✓note |
| In-meeting AI assistant | — | — |
| Action dashboard | ✓ | ✓note |
| Integrations | ||
| Asana | — | — |
| Azure DevOps | — | — |
| Basecamp | — | — |
| ClickUp | — | — |
| Confluence | — | — |
| GitHub | — | ✓ |
| GitLab | — | ✓ |
| Jira | ✓ | ✓ |
| Linear | — | — |
| Microsoft Teams | — | — |
| Monday.com | — | — |
| Notion | — | ✓ |
| Shortcut | — | — |
| Slack | — | ✓ |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | — |
| GDPR | ✓ | ✓note |
| SSO / SAML | ✓note | ✓note |
| SCIM provisioning | — | — |
| ISO 27001 | — | — |
| On-premises | — | ✓note |
| Public API | — | — |
| Webhooks | — | — |
| MCP server | — | ✓note |
Echometer — pros
- + 200+ research-grounded health-check items, custom models and auto-scheduled pulse surveys
- + Longitudinal team radars, heatmaps and a cross-team workspace dashboard tied to retros
- + German-only hosting (Open Telekom Cloud, Magdeburg/Biere) with a GDPR data processing agreement
- + Open actions resurface automatically in the next retro, with owner email reminders and one-click push to Jira
- + Per-team, not per-seat, pricing — €87/mo covers three teams of eight, billed annually
Echometer — cons
- − Integrations stop at Jira — no Slack, Teams, Confluence or Linear
- − No public API or webhooks; export is PDF, Markdown and an emailed recap
- − No SOC 2 — the ISO 27001 certificate covers the datacenter, not Echometer itself
- − Retro-side AI is one function: suggested measures. No clustering, no AI session summary
- − No scheduled or recurring retros — you copy a past format and start each session manually
LetRetro — pros
- + Flat pricing — $15/mo Pro covers unlimited boards and teams within a 200 pooled-seat cap, so 24 users costs exactly what 4 do
- + AI is the product, not a bolt-on: card clustering, board summaries, action items organised by owner, a sentiment snapshot, 50 trend analyses a month, and <strong>Voice Mode</strong> — hold Shift+Space, say a sentence, and it lands as a card in the right column with a priority and due date
- + An <strong>official, MIT-licensed MCP server</strong> — one-command install, 17 tools, 11 clients, and its own component on the public status page — so Claude, Cursor or VS Code can read boards and file cards without a bespoke script
- + Dev-stack card linking is real and deep: Jira, GitHub and GitLab with inline issue editing, comments, MR/PR status, and one card linked across all three at once
- + Ships genuinely fast — AI summaries, MCP, GitLab, Canvas boards, 2FA and Voice Mode all landed between June and August 2026, each documented in a changelog that has matched the product every pass
LetRetro — cons
- − The integrations and comparison pages sell Linear, Asana, Confluence and Snowflake. The shipped app has setup pages for six connectors only — Jira, GitHub, GitLab, Slack, Notion and Google Docs. Verify anything you're depending on
- − Thin enterprise story: Google and Microsoft sign-in but no SAML, SCIM still 'working on', no customer-facing audit log despite the homepage's <em>immutable audit trails</em> claim, and no LetRetro-held SOC 2 or ISO 27001; on-premise and SLA sit behind a quote-only Enterprise tier
- − Solo-founder micro-SaaS — the team page still lists one person (Dhanush Kandhan, Bengaluru) — and independent coverage is negligible. A durability risk for procurement whatever the shipping cadence
- − Facilitation staples are missing: no timer, no recurring or scheduled retros, no async-first mode, no parking lot and no team agreements. It's built around live sessions
- − No public REST API and no webhooks; MCP is the only programmatic route in, and it — like every integration — is Pro-only. Documented exports are PDF and Markdown, metered at 5/mo on the free tier
Keep comparing
Other Echometer comparisons
Other LetRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.