The engineer's whole job is revenue operations and the tools behind it. They score your team against the Tenbound Standard, and they work on video calls or in your office.
They watch your team work and open the tools, instead of asking people to describe it.
Asks people to describe the work, and stops there. What comes back is the version your team can put into words, which is the version that already made sense to them.
Asks the same questions, then stays and watches. Sees the list a rep actually built, the reply nobody routed, and the step everybody works around without mentioning it.
It can be done in a couple of days. How long it takes depends on how quickly the sessions can be booked with each role.
Nothing is installed and nothing is connected. The sessions happen on a screen share.
45 minutes from one person in each role. Nobody prepares anything.
The engineer spends 45 minutes with one person from each role, starting with your SDRs, AEs and sales manager, then marketing, RevOps, onboarding and customer success. They do their normal work on a screen share.
Nothing. The engineer may ask one or two follow-up questions.
The engineer writes the ontology, the workflows, the roadmap and the gap list from what was seen.
60 to 90 minutes. The four documents arrive the same day.
The engineer takes your team through the findings. Invite as many people as you like.
One person from each role joins, the person who does the work, not their manager. They work on a real, recent example.
Four documents, delivered the same day as the walkthrough. You keep all four whatever you decide next.
The definitions your team and your tools share: what counts as a lead, a qualified meeting, an opportunity and a customer, and where each one lives.
How each workflow runs today and how it should run, role by role. For every step: automate it, let a tool assist, or keep it with a person. Plus the fields, rules and connections to set it up.
Where you stand on the Tenbound Standard, then what to fix first, in order. Every item has an owner, a date and a way to check it was done.
Every place your tools should share data and do not, and every step nobody owns. Each gap comes with the fix and what fixing it saves.
The roadmap opens with your score. Each of the six areas of the Tenbound Standard gets a level: Manual, Assisted, Orchestrated or Autonomous. Your overall level is your lowest area. Every score points to something the engineer saw, and an area the engineer did not see is marked as not seen.
See the four levelsIt comes in two parts: what your team can fix alone, and what needs a decision from you.
Examples of the kind of gap the list contains, not findings from a client.
Your team can build from the workflows and the roadmap, or hand them to any vendor. If you would rather we build it, the same engineer and a team will, scoped and priced after you have read the findings. You are not locked in either way.
The review itself does not build anything, and nobody promises you a revenue number. What happens next depends on which fixes get made.
People who are watched at work assume they are being assessed. They are not. The engineer looks at the process and the tools, not at how well someone does their job.
Something like this works:
An engineer is going to sit with one person from each team for 45 minutes to see how our process runs, before we plan next year. It is about the process, not about anyone's performance.
The account executive will tell you the same on the call.
One person from each role that touches revenue: SDR, AE and sales manager, then marketing, RevOps, onboarding and customer success, and any other role the work passes through. As many roles as the work requires.
45 minutes per role, on a screen share, while they do their normal work.
It can be done in a couple of days. How long it takes depends on how quickly the sessions can be booked with each role.
No system access. A screen share and what is publicly visible. More access makes the plan sharper, and the engineer will ask, but it is never required.
Someone to book the sessions, 45 minutes from one person in each role, and a sponsor who can decide when two teams disagree.
Four documents: your ontology, your workflows, a roadmap and a gap list, delivered the same day as the walkthrough. You keep all four whatever you decide next.
Build it yourselves, hand it to any vendor, or ask us. The same engineer and a team will build it, scoped and priced after you have read the findings.
One fixed price, the same however many roles you have.
See the priceA graph8 account executive asks how your team works today, gives you a first read on where the problem probably is, and tells you straight whether the review is worth doing now.
Book a discovery callYour receipt has a link to pick your start date, and a one page prep sheet for each role. The roles get agreed with your sponsor, then the sessions are booked.
Buy the blueprintOne fixed price, the same however many roles you have. It is on the pricing page with every term. The call with an account executive is free.
It can be done in a couple of days. How long it takes depends on how quickly the sessions can be booked with each role.
45 minutes from one person in each role, a short kickoff with your sponsor, and the walkthrough at the end. Nobody prepares anything.
It is 30 minutes with a graph8 account executive about how your team works. If the review would only tell you what you already know, the account executive says so.
No. The engineer looks at the process and the tools, not at how well someone does their job. Tell your team that before the first session.
Most teams can name what breaks. The review shows whether fixing it needs one person or needs a decision from you, which decides how fast it gets fixed.
No. Where a fix needs a tool, the plan says so, and it is often a tool you already pay for.
Yes, for free, in six questions. The review checks that score against what the engineer actually sees.
Free, with a graph8 account executive. Or buy the blueprint and book your sessions.
One email. Two weekly sends: the Tenbound research report with the invite to the Tuesday community call, and the graph8 changelog with the invite to the weekly demo. Written by the Institute and the builders. Unsubscribe any time.
