A community for training out loud.
Training out loud is also learned by seeing how another team does it. This page says who the community is for, what gets shared there, and which two direct channels lead to the team: LinkedIn and email.
A place to compare notes, not to sell.
This community is made of the people who use Frank with a team and have something to say about how it went: which scenario worked, which report was hard to read, what they changed in week two. It is not a product announcement channel or a support forum under another name.
Scenarios that worked
How a story was written, which document it came from, and what the person who approved it corrected by hand. No company name, unless the company wants one there.
How a report is read
What can be concluded from a session report and what cannot. The line between describing how a conversation sounded and diagnosing the person, discussed with anonymized examples.
What we decide in the product
Design decisions explained before they land, so whoever runs a program can object in time. The same things we write on the blog, but with a right of reply.
That conversation is also written on the team blog, where the team writes about practice, voice, and programs.
Two profiles, one problem.
The community is aimed at two specific people. Both have someone in their charge facing a hard conversation this week, and both need it to go well.
People development leads
They build the program, approve the scenarios Frank proposes, and read the team’s aggregated progress. It helps them to see how others organize practice, how much context they handed over, and what they left out.
Sales leaders who train hard conversations
They close, negotiate, retain. They train their team and often practice themselves. It helps them to know which scenario was hard for another team and how that team held it the second time.
If you are a consultant, a coach, or you research voice, there is room for you too. But the center is whoever uses Frank with a real team.
Where to find us.
Two channels, both handled by one of the four people on the team. Every message is read and answered by someone who builds Frank, not by a routing system.
It is where we announce first: team milestones, product changes, and whatever comes out of the daily work.
contact@tryfrank.app. Write with your concrete case and you get an equally concrete answer. Use it to book a demo, settle a product question, or suggest a topic for the blog.
If you want to know who is on the other side, meet the team. If your question is about a demo or a purchase, the contact page has the short route.
The front row is for the people practicing.
Whoever runs a pilot arrives with the raw material of this conversation: company context loaded, scenarios approved by a person, and the first reports read carefully.