Skip to content
Use caseBuilding motionsAdvanced

Turn a motion into something repeatable

Four steps from a purpose to an activated play: overview, timeline and actions, eligibility and goal, review and activate.

RRRevTech RevOpsRevenue operations team 3 minUpdated

The job

“I want to take the motion my best rep runs from memory and have everybody run it.”

  • RevOps
  • Sales leaders
  • Marketing leaders

Every revenue team has motions that work and exist only in somebody’s head. They are visible in that person’s numbers and invisible everywhere else, and the standard response — writing them into a playbook document — reliably produces a document nobody opens.

The difference between a documented motion and a running one is whether the steps arrive as work. A play is the version where they do: the same sequence, for every qualifying account, landing in the right person’s queue on the right day.

What it moves

  • Consistency of execution
  • Coverage without headcount
  • Play contribution to KPI

The division of labour

What RevTech does, and where you decide

Agent workKeeps eligibility evaluated continuously, prepares each step for its account, and routes it to the owner
Human gateYou design the motion, set the autonomy, and do the work that reaches the customer
Workflow KPIConsistency of execution

In the product

How to do it

  1. Step 1 of 7

    Choose a motion that deserves to be one

    The test is repeatability: stable inputs, a visible owner, an output somebody can inspect. A motion that requires a different judgement every time should stay a judgement. Trying to encode one is how playbooks acquire a reputation for being wrong.

  2. Step 2 of 7

    Overview: name, purpose, stages, KPI

    The first step carries the play’s identity and, importantly, the KPI it is meant to move. That link is what makes the impact report possible later, and it is much harder to add convincingly after the fact.

  3. Step 3 of 7

    Timeline and actions: lay it out in days

    The motion is a timeline rather than a chain of triggers, and each step carries actions with instructions an agent can prepare against and a role that should hold them. Day-based steps are easier to reason about than trigger chains, and they match how the humans in the motion already think.

  4. Step 4 of 7

    Eligibility and goal: who this is for

    Eligibility is a standing condition over account properties rather than a list you select. Accounts keep becoming eligible while the play is active, which is the property that makes it a motion. Start deliberately narrow and widen once it has proven itself.

  5. Step 5 of 7

    Review and activate: read it whole

    The last step lays the motion out in order, which is the only point at which certain errors become visible. Anything required and still missing is listed beside the Activate control, each blocker linking to the step that needs it. There is no readiness score to interpret: a field is filled or it is not.

    RevTech: The RevPlay review screen brings the audience, lifecycle, classifications and action timeline together before activation.
    The RevPlay review screen brings the audience, lifecycle, classifications and action timeline together before activation. Captured from the current application with illustrative sample data. Screenshot of the RevTech application; sample data.
    The finished motion read back in order, with its blockers listed rather than scored.
  6. Step 6 of 7

    Check the size before you activate

    The reach summary tells you how many accounts currently match, and says so plainly when some could not be evaluated. Convert that into the number of actions your team will actually receive before you activate, because that number lands in somebody’s queue and it is much easier to narrow eligibility now than to apologise later.

  7. Step 7 of 7

    Know where a new version is decided

    Where your workspace routes a new play version for sign-off, it arrives as a PlayPublishApproval card carrying the version diff and a governance summary. Approve, Request changes or Reject are recorded decisions, and only a role allowed to publish plays sees them. After it is live, RevPlay Portfolio is where you watch its reach, its actions and how its enrollments end.

What arrives

What this puts in your Action Center

ItemWhat is preparedHow it resolves
RevPlayActionInstanceThe instruction, objective, KPI and account context for one activated stepOpens the account; completion goes through the play
PlayPublishApprovalThe version diff and a governance summaryApprove, Request changes or Reject — recorded

What to take away

  • Repeatable means stable inputs, a visible owner and an inspectable output.
  • Link the KPI at the start. It is what makes the impact read possible.
  • Eligibility is a standing condition, not a selected list. That is what makes it a motion.
  • Size the action volume before activating. It lands in a real queue.
  • A new version’s sign-off is a recorded decision, made by a role allowed to publish.
Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo