Features of The GTM Lead release enablement software

Release briefs

A release brief is one page that explains a product change to your revenue team. You set a title, a category (new feature, pricing, deprecation, policy or positioning), an effective date, a Markdown body and an optional source URL. Briefs start as drafts and go live when you publish them.

The Approved claims box lists what recipients may say. The Do not say box lists what they must avoid.

What it stores or shows: Title, category, status, effective date, body, approved claims, do-not-say claims, source URL and timestamps.

Example: A pricing brief with the approved line "Annual plans keep today's rate until renewal" and the do-not-say line "Prices are going up for everyone".

Recipient groups

Groups are lists of people such as SDRs, AEs or CSMs. You paste email addresses, one per line or as email,name, and the group is filled in one step.

Each unique email address counts as one recipient toward your plan limit, no matter how many groups it appears in.

What it stores or shows: Group names, email addresses and optional display names.

Example: Paste "jane@company.com,Jane Doe" and "john@company.com" into the AEs group to add two recipients.

Assignments and secure links

On a published brief you pick a group and create assignments. Each recipient gets a personal link that expires after 14 days. The app shows each link once so you can copy it, because only a hash of the token is stored.

The app does not send email. You paste the links into your own email or chat tool.

What it stores or shows: One assignment per recipient and brief, with status and timestamps, plus the hash and expiry of each link.

Example: Assign the pricing brief to the AEs group and copy four links into a Slack message from your own account.

Acknowledgement and readiness questions

Recipients open their link on any device, read the brief and answer your questions. You can add multiple choice questions with a correct answer, acknowledgement statements and open text questions. Multiple choice answers are graded automatically. Open text answers wait for review.

Three states result: viewed when the page was opened, acknowledged when the recipient confirmed, and ready when the check was answered correctly.

What it stores or shows: Question prompts, options, the correct answer, each recipient answer and its grading result.

Example: Ask "Do existing annual contracts change on November 3?" with the correct answer "No, they keep their rate until renewal".

Response review queue

The Responses page lists answers that wait for a human decision, such as open text answers. You mark each as correct or incorrect and can leave feedback.

What it stores or shows: The answer, its grade, reviewer feedback, reviewer and review time.

Example: An SDR writes a vague answer about discounts. You mark it incorrect and add the approved wording as feedback.

Readiness dashboard

Pick a brief on the Readiness page to see how many recipients are not invited, sent, viewed, acknowledged, ready or overdue, with a table of every recipient. The Overview page shows upcoming effective dates and counts across all briefs.

What it stores or shows: Nothing extra. It reads assignments and responses.

Example: Two days before an effective date you see 11 of 12 AEs ready and one still at viewed, so you message that person.

Activity log

Every important action writes an audit event: who did it, what changed and where it came from. The Activity page lists the latest events for your workspace.

What it stores or shows: Actor, action, target, previous and new value, provenance and time.

Example: An entry shows that a brief was published by a named teammate at a specific time.

Read-only MCP access

Create a token on the MCP access page and connect Claude or another MCP client. Agents can list briefs, read a brief, list recipients and read acknowledgements. They cannot create or change anything.

Tokens are shown once, stored as hashes and tied to one workspace. Revoke a token to cut access immediately.

What it stores or shows: Token hash, label, creation time and last use. Agents read existing data only.

Example: Ask your agent "Who has not acknowledged the pricing brief yet?" and it answers from the live data.