Pre-launch.
Already in production.
We’re holding off on customer logos until the people using Reline are ready to go on the record. Until then — here’s exactly who Reline is built for, and how the early teams using it are running it.
Patterns from the people already using Reline.
Roles, not names — until each customer signs off on a story we’ll publish. The patterns below describe how each kind of team configures Reline today.
Stand-ups, design reviews, and customer calls — one Lens per kind.
Three Lenses (Standup · Design review · Customer interview) are saved at the workspace level. Each meeting picks one. The summary is ready to push to Linear before the next meeting starts (Linear push rolling out).
Discovery calls auto-attach to the calendar event; recap is ready to push to Slack when you want.
Google Calendar webhook attaches the upcoming call to a fresh note. Recording starts on a click; on stop, the “Sales call” Lens drafts the recap, ready to push to #sales-calls (Slack push rolling out).
40 customer interviews in one folder, queried as one corpus.
A multi-note “Insights” Lens runs across the whole research folder once a week. RAG chat across the same folder answers ad-hoc questions during stakeholder reviews.
Free plan today; will pay the day the team grows past two.
One hour per note covers full meetings and lectures. Long-form webinars can split across pause/resume sessions until the upgrade. The audit log is already there for when the first hire lands.
Want your team’s name where these archetypes are?
Launch partners get hands-on onboarding, custom Lenses built with them, and a public story when they’re ready. We’re picky — six teams, six categories.