← Team Updates Hyvara AI
Product EnhancementsNext Sprint Brief
SDR Hive — Product Enhancement Backlog

Next Sprint Priorities

Design partner input from Colin Schap (Ensemble), David Maloof (PreSales Advisory), and Andrae Middleton (Hyvara) translated into a prioritized build backlog. Sequenced v0.5.x through v0.9.

Design Partner: Colin Schap — Ensemble
June 17, 2026
Confidential
v0.5.x — Quick Wins
Already in the build queue from Sessions 7–9. All shipped or confirmed this session.
Core tension surfaced by Colin Schap: SDR Hive currently feels like a report card. The SDR submits a transcript, AI produces a verdict, and the SDR reads their own exposure. Colin wants it to feel like a coach asking questions — where the SDR fills their own gaps and the output reflects their own thinking.
Persona Selector — Brand AE vs Partner / SI
Raised by Colin Schap — Ensemble
ShippedHigh
What & Why
Two fundamentally different qualification motions share the same UI. A brand AE at Adobe qualifies software budget and authority. A partner SDR at Ensemble qualifies SOW scope, MSA status, and co-sell alignment. Neither user had a way to declare which motion they were running.
Partner SDRs at Ensemble get coaching that understands SOW and co-sell context. Persona travels downstream through handoffs into DCN co-sell thread context.
Show details ↓
Transcript Validation Gate — Hard Block
Product quality — Session 9
ShippedHigh
What & Why
Free users hitting a hard block with no warning after pasting wrong content. Worse — it burned one of their 10 free analyses. A strict AI classifier now validates whether pasted content is a real sales conversation before the analysis runs. Non-sales content blocked with a polite amber pill. No count increment.
Free tier users don't lose one of their 10 analyses to an accidental paste. Protects analysis quality across the board.
Show details ↓
Granola API Key — Per-User Isolation
Security finding by David Maloof — PreSales Advisory
ShippedHigh
What & Why
The Granola integration was using a single shared API key stored as a Supabase environment variable. One key for all users — a key rotation or leak affects everyone simultaneously. Edge function rebuilt as per-user. Key stored in the user's own row under RLS, decrypted only within their session.
Each user's Granola connection is fully isolated. Pattern now applied to all future integrations — Fireflies, Fathom, Gong, Email.
Show details ↓
Simple / Advanced Toggle — Analysis Tuning
UX call by Andrae Middleton — Hyvara AI
ShippedMedium
What & Why
New SDRs hitting technique checkboxes, unlock rows, and sliders on day one — complexity kills adoption. Simple mode shows methodology name, percentage, and toggle only. Advanced mode shows everything. Preference saved to profile. Locked methods still visible in Simple mode as conversion prompts.
New SDR adoption improves. Locked methods still visible in Simple mode — free users see what they're missing without being overwhelmed.
Show details ↓
In-App Feedback → Linear
Product infrastructure — Session 9
ShippedHigh
What & Why
Design partners noticing bugs and features mid-session with no easy way to log them. Feedback button in sidebar — Bug/Feature toggle, mic dictation, AI polish (✨), Loom URL field. Submits directly to Linear HYV with submitter name and email. No Slack DMs, no lost feedback.
Colin's bugs land in Linear automatically. Every design partner session generates structured product feedback without interrupting the demo flow.
Show details ↓
Trial Nudge at 3 and 7 Analyses
Conversion — Session 9
ShippedHigh
What & Why
Free users hitting a hard wall at 10 analyses with no warning. Soft dismissible banner at 3 analyses. Strong modal at 7 — "You're almost out." Calendar invite for trial end. Upgrade moment arrives before the wall, not at it.
Free-to-paid conversion has a runway. Users see the upgrade moment with enough analyses remaining to feel the product's value before committing.
Show details ↓
v0.6 — Interactive Post-Call Dialogue
Colin's highest-impact feedback. Changes the core interaction model from passive output to active coaching dialogue. All three items are a workflow, not standalone features.
Post-Call Q&A Gap-Fill Dialogue
Raised by Colin Schap — Ensemble
v0.6High
What & Why
Current output feels like a report card handed to an SDR — AI-generated, passive, slightly accusatory. Colin wants the tool to ask clarifying questions so the SDR fills their own gaps. The SDR owns the output because they answered the questions. Trust goes up. Accuracy goes up. Adoption follows.
Shifts the experience from verdict to coaching dialogue. SDR owns the output. Reduces gaming and score manipulation.
Show details ↓
Multi-Call Transcript Blending + Re-Score
Raised by Colin Schap — Ensemble
v0.6High
What & Why
Call 1 produces a score and missing gates. SDR does follow-up call. Pastes Call 2 transcript. AI blends both calls, re-scores against the same framework, shows which gates moved from missing to confirmed. Score trajectory — Call 1 to handoff-ready — is the coaching story.
SDR and manager see progression arc, not just a single snapshot. Shows the tool is actually making reps better over time. Core retention argument for Team accounts.
Show details ↓
"Prep My Call" — AI Pre-Call Coaching Screen
Raised by Colin Schap — Ensemble
v0.6High
What & Why
When the follow-up call opens, it should already know the account, the open gates, and the script. AI writes the opener (callback to last call, show you listened), the middle (target questions per missing gate), and the close ask (what does a yes from this call look like). Tell-Show-Tell structure. SDR walks in prepared, not reconstructing context from scratch.
Reduces cognitive overhead before a follow-up call. SDR sees exactly what was unresolved and gets a call script — this is where the coaching metaphor becomes real.
Show details ↓
v0.7 — SDR to AE Connection Stream
The handoff workflow and the dirty laundry problem. Protects SDR trust by gating upward visibility behind SDR/AE agreement.
SDR to AE Messaging / Notification Gateway (The Volley)
Raised by Colin Schap — Ensemble
v0.7High
What & Why
SDR and AE need to agree on the handoff before it surfaces to the manager. The dirty laundry problem: a manager seeing a raw struggling rep analysis before the SDR/AE have agreed will use the tool to manage the tool, not the rep. Handoff only surfaces upward after both sides sign off.
Protects SDR trust. SDRs won't game or hide if they know the manager doesn't see it until they're ready. This is the architectural feature that makes Hyvara safe to use honestly.
Show details ↓
AE Accept / Reject / Kickback — Five SAL Outcomes
Raised by Colin Schap — Ensemble
v0.7High
What & Why
AE needs to be able to accept, push back for more gate coverage, or reject. Five outcomes: Accept, Kickback-for-gates, Reject-not-now, Reject-not-a-fit, Refer-to-partner. SDR gets notified on each outcome and sees exactly why. That is the coaching moment — SDR learns in real time whether their qualification was good enough.
Closes the feedback loop for the SDR. Handoffs don't disappear into a queue — the SDR learns what happened and why every time.
Show details ↓
Hyvara Lite Email Link for AEs Not on Platform
Raised by Colin Schap — Ensemble
v0.7Medium
What & Why
Not every AE will be on SDR Hive. Need a lightweight way to send a handoff briefing to an AE who just gets an email link — they see the qualification brief, can accept or push back, without needing a seat. Removes the "everyone has to be in the tool" barrier.
SDR can complete the handoff workflow even if the AE isn't a user yet. Every Lite touchpoint is a product demo — a potential seat conversion.
Show details ↓
v0.8 — Gamification Layer
Colin's basketball score metaphor. SDRs compete against their own score. Managers get a coaching view, not a surveillance view.
Persistent Score Display in SDR View
Raised by Colin Schap — Ensemble
v0.8High
What & Why
SDRs should be competing against their own score, not a rubric they don't understand. Score needs to be visible and persistent — not just appearing post-call. Makes progress visible at a glance. SDRs chase the number. Turns qualification into a game the SDR can win on their own terms.
Behavioral design — SDRs engage with the tool daily because the score is always visible. Drives repeat usage and metric improvement.
Show details ↓
Leaderboard for Team Leader + Leader Console Restructure
Raised by Colin Schap — Ensemble
v0.8Medium
What & Why
Team Leader needs to see how reps are trending — not just individual scores but comparative performance across the team. Leader Console currently collapses four distinct contexts into one: Team Dashboard (looking down), Managing Up (looking up), Team Ops (onboarding/PIPs), Platform Config (badges/branding).
Managers get a coaching tool that doesn't require sitting on calls. See which SDRs are improving, which are stuck, who needs a 1:1 intervention. Primary value prop for Team plan buyer.
Show details ↓
v0.9 — CRM Integration + Admin
One of these is a decision, not a feature. The background vs. primary UI question needs resolution before v0.9 scoping starts.
Background CRM Scanning Mode
Architecture question raised by Colin Schap — Ensemble
Decision needed
What & Why
Colin's most important product question: do you want Hyvara to be a primary UI that SDRs switch to, or a background tool that scans Sales Journal and surfaces insights without requiring a context switch? If switching to Hyvara is another step, small teams won't do it. This is an architecture decision — not a feature. The answer determines product positioning.
Determines the entire go-to-market motion and whether v0.9 CRM work is core or optional. Cannot scope v0.9 without this answer.
Show details ↓
Admin Impersonation / View As
Product infrastructure — Session 9
v0.9Medium
What & Why
Admin needs to see what any user sees without logging out and back in. Debugging, demo prep, and onboarding support all require this. Standard enterprise admin capability — partners will expect it.
Reduces support friction. Diagnose issues without asking a user to screen share. Required before enterprise accounts onboard.
Show details ↓
Google Sheets Connector — Call Sheet Pull
Raised by Colin Schap — Ensemble
v0.9Medium
What & Why
SDRs often maintain call lists in Google Sheets before CRM data is clean. Pulling from Sheets gives SDRs a way to bring account context into the tool without a full CRM integration. No CRM API key required. Meets SDRs where they actually work.
Lowers the barrier to getting account data into SDR Hive. Pre-CRM bridge that gets replaced by a native integration later.
Show details ↓
Open Decisions — Needed Before Next Phase
These are not features — they are architecture and strategy questions. Each one gates an entire phase of the roadmap. Resolve before scoping starts.
Interactive Q&A gap-fill vs. structured output with edit/confirm layer — which interaction model?
v0.6 cannot be scoped without this. The build is completely different depending on the answer.
Background CRM scanner vs. primary UI — which job is SDR Hive hired for?
Determines go-to-market motion, pricing model, and whether the v0.9 CRM work is core or optional.
Where does the score live in the SDR's daily view — sidebar persistent, top bar, or post-call only?
v0.8 gamification design depends on this. Wrong placement and the feature has no behavioral impact.
Who triggers the Volley to the AE — SDR manually at score threshold, or auto-trigger?
v0.7 architecture depends on this. Auto-trigger requires a threshold config UI. Manual is simpler but less sticky.
Does the persona field require migration on existing user accounts, or default to brand?
Affects all existing accounts including Kevin, David Maloof, Peter Webster, David Jones, and Lenke.