Echometer
5.5Psychology-backed retros and team health checks for engineering teams
Echometer is a German retrospective and 1:1 meeting platform built around recurring health-check pulses, structured retros, and longitudinal team development tracking. It pitches itself to engineering managers, scrum masters and agile coaches who want research-grounded surveys rather than a blank whiteboard.
Full review →
LetRetro
5.4The retro tool that thinks with your team
LetRetro is a young, AI-forward retrospective platform that pitches itself as MCP-native and CLI-first, connecting to sprint data to surface what's slowing a team down. It centres on real-time collaborative boards, AI-generated retro documentation, sentiment/trend analysis and a team health checker, on a flat (pooled-seat) pricing model rather than per-user.
Full review →Summary
Echometer scores 5.5 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 5.4 overall and is best for developer-leaning agile teams and startups that want AI-assisted retros wired into their sprint data and dev stack (GitHub, GitLab, Linear), plus health and sentiment tracking, without enterprise overhead. It offers a free tier.
Echometer leads on retro toolkit, open platform and enterprise-grade. LetRetro leads on ease of use, fun factor, AI & insights and integrations.
Across our eight scoring dimensions, Echometer edges ahead with an overall score of 5.5. 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, 1 retro/month after trial, 2-retro archive per team | 3 boards, 1 team, 20 pooled seats, 2 AI docs/mo, 5 exports/mo, 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 | — |
| HQ | Münster, Germany | Bengaluru, India |
| Data residency | Germany | — |
| Languages | 2 (English, German) | English only |
| Export formats | PDF · Markdown · Email | — |
| Features | 44 | 19 |
| Integrations | 1 | 6 |
Feature & integration comparison
Side-by-side checklist across features, integrations and security. Hover a note for details.
| Capability | Echometer | LetRetro |
|---|---|---|
| Features | ||
| AI Summaries | ✓note | ✓ |
| AI grouping/clustering | ✓note | — |
| AI action items | ✓note | ✓note |
| Action tracking | ✓ | ✓ |
| Team Insights | — | ✓note |
| Polling | ✓ | ✓note |
| Action dashboard | ✓ | ✓note |
| Custom templates | ✓ | ✓note |
| Anonymous input | ✓ | ✓ |
| Independent voting | ✓ | ✓ |
| Async mode | ✓ | — |
| Agile Estimations | — | — |
| Health Checks | ✓ | ✓note |
| Team Kudos | — | — |
| Whiteboard | ✓ | — |
| Integrations | ||
| Asana | — | — |
| Azure DevOps | — | — |
| Basecamp | — | — |
| ClickUp | — | — |
| Confluence | — | — |
| GitHub | — | ✓ |
| GitLab | — | ✓ |
| Jira | ✓ | ✓note |
| Linear | — | ✓ |
| Microsoft Teams | — | — |
| Monday.com | — | — |
| Notion | — | ✓ |
| Shortcut | — | — |
| Slack | — | ✓note |
| Trello | — | — |
| Security & Privacy | ||
| SOC 2 | — | — |
| GDPR | ✓ | ✓note |
| SSO / SAML | ✓note | — |
| SCIM provisioning | — | — |
| ISO 27001 | — | — |
| On-premises | — | ✓note |
| Public API | — | — |
| Webhooks | — | — |
| MCP server | — | — |
Echometer — pros
- + Health-check question library grounded in University of Münster psychology research
- + Strong longitudinal pulse and team-radar reporting tied to retros
- + EU-only data residency (Open Telekom Cloud, Germany) with GDPR DPA
- + AI Co-Pilot clusters ideas and proposes SMART action items
Echometer — cons
- − Thin chatops integrations — no native Slack, Teams or Confluence
- − No SOC 2; relies on ISO 27001 datacenters and EU residency
- − 1:1 meetings and the deepest AI live in a separate paid product
- − No native scheduling or recurring retros — sessions start manually
LetRetro — pros
- + Flat pricing — $15/mo Pro covers unlimited boards and teams within a 200 pooled-seat cap, so a growing org isn't billed per head
- + AI is a genuine focus, not a bolt-on: retro-doc generation, sentiment/trend analysis, key takeaways and improvement suggestions that cut the post-retro write-up burden
- + Developer-stack integrations up front — GitHub, GitLab and Linear are live, unusual for a retro tool this young, alongside an <strong>MCP-native, CLI-first</strong> pitch
- + Built-in team health checker and sentiment-over-time trend dashboards — longitudinal signal many cheap retro tools skip
- + Real-time collaborative boards with anonymous input, live polls and one-click retro-to-task conversion, spun up with minimal setup
LetRetro — cons
- − Thin enterprise story: SSO isn't listed on any published tier, no SCIM or audit logs, no LetRetro-held SOC 2 or ISO 27001; the on-premise option and SLA sit behind a quote-only Enterprise tier
- − Founder-led micro-SaaS (built and run by Dhanush Kandhan in Bengaluru; self-described as an unfunded two-person weekend project) with a very thin public track record — a real durability risk for enterprise procurement
- − Integration list is aspirational — Jira, Confluence, Trello, Asana and ClickUp are all flagged 'coming soon', and the vendor's own copy is inconsistent about which connectors are actually live
- − Retro toolkit lacks facilitator staples: no confirmed timer, recurring/scheduled retros, parking lot, team agreements or async-first mode — it's built around live, real-time sessions
- − Free tier is tight — 3 boards, 1 team, 2 AI docs and 5 exports per month — so any regular use pushes teams onto Pro quickly
Keep comparing
Other Echometer comparisons
Other LetRetro comparisons
Not sure which to pick? Read our guide on how to choose a retrospective tool.