Every hive in the Hyvara platform is a standalone product. It works alone. It generates value alone. It prices and sells alone. But every hive has a connection port — a lightweight thread layer that docks to the adjacent hive when the customer is ready to link them together.
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.
The complete B2B revenue motion runs through seven distinct handoffs. Hyvara owns the intelligence layer at every one of them.
| Hive | Status | Users | Core Action | Connection Port |
|---|---|---|---|---|
| SDR Hive | ● Live — v0.5.0 | SDR (paid) AE (Lite) | Qualify call, score framework, volley to AE | → AE Lite receives handoff briefing |
| AE Hive | Roadmap — v1.0 | AE (paid) SE (Lite) | Accept handoff, manage deal, volley to SE | → SE Lite receives technical brief |
| SE / Presales Hive | Roadmap — v1.1 | SE (paid) SE Lite | Technical discovery, POC, confirm win | → Win signal to DCN and CSM |
| DCN | ● Live — v0.4 | Brand AE (paid) Partner AE (paid) | Co-sell intelligence, partner overlap, deal threads | ↔ Brand AE ↔ Partner AE thread |
| CSM Hive | Roadmap — v1.2 | CSM (paid) Implementation (Lite) | Implementation handoff, renewal, expansion signals | → Expansion loops back to SDR/AE |
The Connections module is the thread layer that enables communication between roles across hive boundaries. It was built first inside DCN — the co-sell intelligence product — because that is where partner-to-partner communication was most urgent. But it was never a DCN-only feature. It is platform infrastructure.
- Creates a persistent thread between two roles across a handoff boundary
- Tracks thread status: active, awaiting reply, stale, expired
- Pins cross-partner or cross-role accounts at the top for priority visibility
- Allows accept, reject, kickback, and refer actions on both sides
- Generates Lite access tokens — time-limited links for non-seated users to participate
- Notification hooks via Resend — new threads, replies, status changes
The Lite version is the growth mechanism built into the platform architecture. Every hive can send a connection request to someone who does not have a paid seat. The receiver gets just enough access to participate in the thread — see the handoff, respond, accept or push back — without requiring a full seat purchase.
- SDR → AE Lite: AE receives briefing, no seat required. Sees value, requests full AE Hive access.
- AE → SE Lite: SE receives technical brief. Joins SE Hive or stays Lite if volume is low.
- Brand AE → Partner AE DCN Lite: Partner org buys DCN Team as co-sell volume grows.
- CSM → SDR/AE expansion: Expansion brief received with no additional seat required.
Every user in the Hyvara platform has two identity attributes that travel with them across all hives and all handoffs. These are independent fields — set once, used everywhere downstream.
- Brand persona: AI coaches against direct software sale gates. Economic Buyer is the end customer budget holder. Timeline is the software deployment window.
- Partner persona: AI coaches against co-sell and professional services gates. MSA status is a prerequisite gate. SOW scope and co-sell motion with the brand AE are primary qualifiers.
The Connection Spine builds incrementally. Each phase adds one new hive and one new connection port. Nothing breaks existing hives when a new one is added.