Design partner feedback from Colin Schap at Ensemble translated into shipped product — same day. Here's what changed, what it unlocks, and what's coming next.
"Right now the tool feels like a report card. The SDR submits a transcript, AI produces a verdict, and the SDR reads their own exposure. I want it to feel like a coach asking questions — where the SDR fills their own gaps and the output reflects their own thinking."
— Colin Schap, Account Executive / Team Leader — Ensemble"If you're storing API keys in a shared environment variable, one compromised integration exposes every user on the platform. Each key needs to live in the user's own row — isolated, protected by RLS, decrypted only within their session."
— David Maloof, Advisor — PreSales Advisory — Security & Integration Architecture"Not every SDR needs to see technique checkboxes and unlock rows on day one. There should be a simple view that shows the methodology and the blend without the complexity — and an advanced view for those who want to go deeper. Let the user choose."
— Andrae Middleton, Co-Founder — Hyvara AI — Analysis Tuning UX| What Colin said | What we built | Status |
|---|---|---|
| SDR needs to see what gates are open before the follow-up call, not after | Follow-ups redesign with progress rings, missing gate tags, and "Prep my call" CTA | Shipped |
| After the follow-up call, blend both transcripts and show me where I moved | Multi-call qualification architecture — v0.6 scoped and Coming Soon preview live | v0.6 |
| I'm a Team Leader at Ensemble — I need to see both the SDR view and the manager view | Role switcher with SDR / AE / Team Leader toggle. colin.ensemble pre-configured with all three roles | Shipped |
| Partner SDRs at Ensemble are qualifying SOWs and co-sell motions — not just software | Persona selector: Brand AE vs Partner / SI. Rides the analysis payload into v0.6 prompt injection | Shipped |
| SDRs should compete against their own score, not a rubric they don't understand | Progress rings in Follow-ups. Score gamification and persistent score display queued for v0.8 | v0.8 |
| If switching to Hyvara is another step, small teams won't do it | Background CRM scanner vs primary UI — architecture decision queued for v0.9 scoping | Decision needed |
| The manager shouldn't see a struggling SDR's analysis before the SDR and AE agree on the handoff | Volley / SDR-to-AE messaging gateway — v0.7 architecture with five SAL outcomes | v0.7 |
| Shared Granola API key is an architectural risk — one key for all users is not acceptable at scale | Edge function rebuilt as per-user. granola_api_key stored per user row under RLS. Pattern applied to all future integrations. | Shipped |
| New SDRs don't need technique checkboxes and unlock rows on day one — complexity kills adoption | Simple / Advanced toggle added to Analysis Tuning and qualifier landing page. Preference saved to profile. Simple mode hides techniques, shows locked methods as conversion prompts. | Shipped |
"The earpiece in the anchor's ear. Hyvara is the AI voice coaching in real time — without getting in the way. Every build item today moves the product closer to that metaphor and further from a report card."
— Hyvara product positioning, Session 9"Think of it as LEGO. Each brick is complete. You can use a single brick. But the moment you connect two bricks, the structure becomes something more than the sum of its parts. The connection between an SDR Hive and an AE Hive is not a feature — it is a revenue relay. And the relay is the platform."
— Hyvara Platform Architecture, June 17, 2026"If you're storing API keys in a shared environment variable, one compromised integration exposes every user on the platform. The fix is per-user isolation — each key lives in the user's own row, decrypted only when their session calls it."
— Security principle applied to Granola integration, Session 9