Method
We don’t copy the base.We rethink the system.
Most products in a category start from the same template and compete on the details. We start from the work itself: who carries it, where it happens, and what it has to prove. Here is what that changed in Hyves.
01 · The Hyves ledger
The base everyone copies, and what we built instead.
Every category has a default that new products inherit without asking. These are the ones Hyves refused, and what took their place.
01
No campaign object
Sales software is built around the campaign: a list, a sequence and a send date, with the research and the deal kept somewhere else.
Hyves has no campaign object. Research, outreach and the deal all hang off one account record: the dossier.
A rep works from one record, so a signal found in research changes the message and the pipeline view at the same time.
02
No brief, no list
Sales tools begin with a setup project: a brief to write, a market to describe and a list to upload.
Hyves starts at sign-in, and a work email is the only input. It researches your own company first (21 stages in 7 chapters), then launches the first market search on its own.
About fifteen minutes after signing in, the first job is reviewing research on your own company, not filling in a form.
03
Every score quotes its evidence
Lead scoring returns one number without its reasons, and a missing data point quietly counts against the account.
The rubric has 12 dimensions written for your product, each scored 0, 1 or 2 with the evidence quoted; missing evidence counts as unknown, never zero. Before the search spends anything, the rubric is checked against your existing customers, and the run pauses if they would not pass.
A rep can check any score against its source, and a rubric that would reject your own customers is caught before it costs anything.
04
Bottom-up, in waves
Outreach goes straight to the most senior title on the account, and everyone gets the same sequence.
Hyves maps each account’s people into seven roles and contacts them in waves: users first, then champions and everyone else, then the economic buyer. Blockers are never contacted, and each wave opens after a reply from the one below or after five days.
The buyer hears from you last, after the people who feel the problem first have been asked.
05
Autonomy set per account
Automation is governed by one setting for the whole tool, decided once for every account.
Each account has its own send mode: approve every message, approve the first, or let it run inside the plan. One agent per account decides each next step and logs it.
How far the system acts on its own stays the person’s decision, one account at a time, with every step written down.
06
Proposals, not a to-do list
Automation writes tasks straight onto the list, and every tool keeps its own reminders somewhere else.
What the agents and SYNC want done arrives in Hyves as a draft, in one queue, grouped by kind. It joins the task list only when a person confirms it.
A person sees in one place everything the machine wants done, and decides what actually happens.
07
The call files itself
Call notes are typed up afterwards, if at all, and the CRM learns what was said only when someone logs it.
A call in Hyves is transcribed as it happens, never recorded. On an open deal, the summary and the next step land on the deal by themselves, and the tasks from the call wait for the rep to confirm.
The account knows what was said without anyone typing it up, and nothing acts on the rep’s behalf without a click.
02 · Practice
How a rethink starts.
Find the real unit of work
Ask what the work actually revolves around before building anything. In sales it was the account, not the campaign, so Hyves has no campaign object.
Delete the step before automating it
An automated setup form is still a setup form. Hyves has no brief and no list; it starts from a work email.
Design for where the work happens
Sales work happens in the CRM, the inbox and the calendar a team already runs, so Hyves sits on top of them instead of replacing them. A call started from a deal opens with its brief, on the account it belongs to.
Make the machine show its evidence
A claim that cannot point at its source does not ship. Every Hyves score quotes its evidence, and what was not found stays unknown.
Let the person set how far it acts
People decide how far a system may act on its own. In Hyves that is set per account, and every step the agent takes is logged.
Copying the base gives you the same system with a new interface. We start from the person who carries the work and the place it happens, and rebuild from there. Hyves is that method, shipped for B2B go-to-market teams.