[ 01 — Compare · Luni vs Read.ai ]
Luni vs Read.ai.
↳ Read.ai
Read.ai pushes 'meeting copilot' real-time analytics — engagement scores, sentiment, talk-time stats during the call.
↳ Luni
Luni stays out of the meeting itself. Capture, summarise, leave. No live dashboards judging participants.
[ 02 — Side by side ]
The capability matrix.
↳ Capability
Luni
Read.ai
Zoom
Yes
Yes
Google Meet
Yes
Yes
Microsoft Teams
Yes
Yes
Real-time engagement scoring (in-meeting)
No (intentional)
Yes
Post-meeting talk-time analytics
Yes
Yes
Sentiment dashboards
No
Yes
Recap + action items
Yes
Yes
Continuous recordings (recurring meetings stitched)
Yes (Enterprise)
No
Free tier
10 meetings / month
5 meetings / month
Pro starting price
£10 / user / month (annual)
$19.75 / user / month
↳ Read.ai pricing as of public marketing site · Luni pricing in GBP, ex VAT
[ 03a — When Read.ai is right ]
Read.ai is the better fit when…
- · You actively want real-time engagement metrics shown to participants during the call
- · You run training / coaching sessions where sentiment scoring is the deliverable
- · Your team is comfortable with a more interventionist tool inside meetings
[ 03b — Why teams pick Luni ]
The case for Luni.
- · Post-meeting talk-time analytics, not real-time engagement theatre. Luni surfaces who spoke when AFTER the call — Read.ai surfaces it during. Participants don't see scores in the meeting
- · No engagement / sentiment scoring shown to anyone — we measure conversation, not personality
- · Recap reads as editorial summary, not as a behavioural report card
- · Reply-to-edit recap workflow Read.ai doesn't offer
[ 05 — Get in ]Try Luni when access opens.