Skip to content
RevTech Launchpad
DoLesson 6 of 6Run something

Build and run your first RevPlay

Cross from working prepared work to defining it, by building and activating a real play end to end.

33 minBeginner
Part 1 of 2

Why this is last in the track

Building a play is authoring work: you are deciding what arrives in other people's queues, in what order, with what instructions. Doing that without having worked a queue yourself produces plays that look reasonable in the builder and are unworkable in practice, steps that assume context they never provide, instructions written for someone with unlimited time.

Having spent a week on the receiving end, you have the thing that is hard to get any other way: a concrete sense of what a good action looks like when it lands, and of the specific ways instructions fail. That is exactly the knowledge the builder asks for.

Part 2 of 2

How to approach the course

The course runs twelve lessons across four modules, following the builder's own order: choose a motion worth encoding, lay out the timeline, define eligibility, then review and activate. Work them in sequence, the modules build, and the eligibility work depends on decisions made in the timeline.

Pick a small, well-understood motion for the first play. The measure of success is a completed loop (built, activated, and read two weeks later) rather than the importance of the motion you chose. A modest play carried all the way through teaches you more than an ambitious one abandoned at the review step.

  • Work the four modules in order; they build on each other
  • Choose a motion you already understand well
  • Aim for a completed loop, not an impressive first play
The RevPlays library in RevTech: repeatable GTM plays and their enrolment.
The RevPlays library: repeatable GTM plays, the accounts enrolled in each, and the actions they generate. Screenshot of the RevTech application; sample data.
The plays library. After the course your motion is a row here, with the accounts it enrolled and the actions it generated.

Now take the course

Build and run your first RevPlay

This lesson is the orientation. The material itself lives on its own page, kept in one place so it stays current everywhere it is referenced.

Key questions

You should be able to answer each of these from memory before opening it. Recalling the answer is what makes it stick; recognizing it when you read it does not.

Why does authoring a play come after a week of working a queue?

Because you are deciding what lands in other people's queues. Having been on the receiving end gives you a concrete sense of what a good action looks like and how instructions fail, which is exactly what the builder asks for.

Covered in full: Build and run your first RevPlay

What counts as success for a first play?

A completed loop: built, activated, and read two weeks later. A modest play carried all the way through teaches more than an ambitious one abandoned at the review step.

What to take away

  • Bring a motion your team already runs the same way. The course standardizes an agreement; it cannot create one.
  • This sits last because it assumes the queue habits you have just spent a week practising.

Teach this lesson

The argument in 4 slides, for presenting it to your team
Slide 1 of 4

The step from consumer to author

Everything so far has been about working what arrives. This is where you decide what arrives, for a whole motion, for everyone it routes to.

Slide 2 of 4

You are better prepared than you think

  • You have worked a queue, so you know what a good action looks like
  • You have rejected things, so you know how instructions fail
  • Both are exactly what authoring a play requires
Slide 3 of 4

Start with a small motion

The goal of the first play is a completed loop, not coverage. Narrow eligibility, few steps, something you already understand well.

Slide 4 of 4

The full course is twelve lessons

Choose a motion, lay out the timeline, define eligibility, then review and activate. Work through it in order.

Demo

Try the demo.

See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.

Explore the demo