No system access. Card or invoice. You keep all four documents.
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.
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.
You 45 minutes from one person in each role. Nobody prepares anything.
The engineer writes the ontology, the workflows, the roadmap and the gap list from what was seen.
You Nothing. The engineer may ask one or two follow-up questions.
The engineer takes your team through the findings. Invite as many people as you like.
You 60 to 90 minutes. The four documents arrive the same day.
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 each.
A graph8 engineer whose whole job is revenue operations and the tools behind it, working to the Tenbound Standard. The kind of person who could build the fixes, which is why your team or any vendor can build from the plan.
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. There is no waiting list.
None required. The engineer watches on a screen share and looks at what is publicly visible: your site, your forms, your sending domain. A look at your CRM or Search Console makes the plan sharper, and the engineer will ask, but it is never required.
Every session is recorded and transcribed, because that is how the analysis is done. Your team is told before it starts, and you see everything the engineer observes.
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. Nobody is locked in.
Most problems sit between roles: the lead marketing passes to an SDR, the meeting an SDR passes to an AE, the deal an AE passes to onboarding. So the engineer sits with one person from every role the work passes through, and the price stays the same. Covering them is our investment, not your cost.
It is a small first step: one fixed price, and you decide what to do next with the plan in your hands.
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.
Every link between your data is carried by a system, by a person, or by nothing. The ontology marks each one, so you can see which of your numbers you can trust today and what is missing for the rest.
Every step gets one of three answers.
The step is the same every time and needs no judgement: the research a rep does by hand each morning, routing an inbound lead, filling in missing company data. The plan says which tool and which fields.
A person still decides, but stops doing the typing. The draft is written for them, the account is scored before they open it, the next step is suggested.
Some steps should stay with a person: which replies get a human answer, who settles an unclear account, what a rep may promise. The plan writes the rule down so the same question gets the same answer.
The roadmap opens with your score. Each of the six areas of the Tenbound Standard gets a level from what the engineer saw. Your overall level is your lowest area, because that is the one holding the rest back.
An area the engineer did not see is marked as not assessed, never guessed. The score is about the process, not your people.
From an example readout for Harborline, a made-up company used to train account executives. It is not a client, and the numbers are invented.
Measured: 6 of 20 sampled inquiries had no named owner at the first handoff.
Not estimated: lost revenue. One sample does not support a number.
Still unknown: whether those six were picked up later, and how long each waited.
Each item names the finding it closes, an owner, and how you check it was done.
The setup document is written for your team or any vendor you choose, and often the first fixes are things you can do in house. If you would rather we build it, the same engineer and a team will. Nobody is locked in.
An AI tool needs to know what a lead, a qualified meeting and a customer mean at your company. The review writes those definitions down, in your words, before you buy one.
Every gap comes with what fixing it saves, so you can use it in your 2027 budget and hiring plan.
The short version, to forward.
An engineer reviews how our revenue team works and gives us a written plan to fix it.
$5,000, one time, the same however many roles. Card or invoice.
45 minutes from one person in each role, a short kickoff, and a 60 to 90 minute walkthrough at the end.
No system access and no admin credentials. The engineer watches on a screen share and looks at what is publicly visible.
Sessions are recorded and transcribed for the analysis. The team is told before each one.
Four documents: the ontology, the workflows, a roadmap and a gap list. No lock in.
Fewer sessions, one per job you do, and the same four documents. Every step you run by hand gets written down, so your first sales hire starts with a process instead of your memory.
One SDR and one account executive they pass meetings to is enough to map your team's steps and the handoff out of it. The readout marks every role the engineer did not see.
The engineer covers the roles you can bring and says which ones were not seen. Marketing usually joins once they hear their side of the handoff gets written down too.
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. The engineer watches on a screen share and looks at what is publicly visible. Access to your CRM or Search Console makes the plan sharper, and the engineer will ask, but the work does not depend on it.
45 minutes from one person in each role, a short kickoff with your sponsor, and the walkthrough at the end. Nobody prepares anything. They work on a real, recent example.
One person from each role that touches revenue: sales, marketing, RevOps, onboarding, customer success, and any other role the work passes through. The list is agreed with your sponsor at the kickoff.
Good, nothing replaces it. The engineer looks at what your team does around the CRM: where follow-up actually lives and which fields get filled in properly. If your team works the way your CRM says, the readout says so.
No. For $5,000 you get the review and the four documents. Fixing things is separate work, scoped after you have read the findings. You can do it yourselves, with a vendor, or ask us.
No, and anyone who does is guessing. The engineer reports what was seen and what to change first. What happens after depends on which changes get made. If you want a guaranteed number of meetings, that is a managed service, and CIENCE runs one.
No. An engineer watches how your team works today and writes down what to fix. Some fixes use AI and many do not. You do not have to buy anything from graph8 or CIENCE to use the plan.
As soon as your team can book the sessions. There is no waiting list. The roles are agreed at the kickoff and the sessions booked from there.
Yes. Order it here and a Stripe invoice follows within one business day, or talk to an account executive first and get a quote. Net terms are fine.
No. The plan is complete on its own. You keep all four documents whether you build it yourselves, with a vendor, or with us.
No. The engineer maps the process and the tools. You see everything the engineer observes, and the problems found belong to the process, not to people.
Not by default. The plan separates what needs setting up, what needs connecting, what needs building, what you keep, and what only you can decide.
The readout says so, and shows what is holding your lowest area back. A team with nothing to fix is told that at the walkthrough.
No. You keep all four documents whatever you do with them. If we cannot deliver what is described here, we say so before the sessions start and refund you.
The call is a first read from an account executive. The self-score is your own view of your team. The blueprint is what an engineer actually saw, written down and scored.
$5,000, one time, however many roles you have. You keep all four documents whatever you decide next. Or talk to an account executive first.
Book a discovery call: thirty minutes, free, about how your sales team works. After the call, your graph8 account gets unlimited B2B contact, company, website visitor and intent data for a year, whether or not you buy the blueprint.
