A paid two-month pilot, structured around what we're trying to prove together.
A short overview of how a Pleras pilot is shaped. We'll work through the specifics with you in conversation.
A paid two-month engagement with clear success criteria
A Pleras pilot runs for two months and is structured around success criteria we agree with you upfront, so there's no ambiguity about what would make the pilot a success.
-
Week 1Kick-off
We align on goals, scope, and the success criteria we'll measure the pilot against. The initial site analysis begins.
-
Week 4Mid-point review
We assess what's running and what's worked, and adjust scope or success criteria if anything needs revisiting.
-
Week 9Results session
We review what happened together and decide: move to a paid plan, extend the pilot, or wrap up.
Pleras delivers experiment code on a rolling basis through a shared Slack channel. Your team deploys it into the existing testing tool you already use (Optimizely, VWO, GrowthBook, or whichever). Async support throughout.
A short extension is possible if more time is needed to reach a clear answer. No long-term commitment is required to start.
A clear split of responsibilities
A pilot works best when both sides know what's on them from day one.
Platform access for the pilot period, the initial site analysis and experiment backlog, experiment code delivered on a rolling basis, revisions when something needs changing, the three working sessions, and async support via a shared Slack channel throughout.
A named champion and someone using the platform day-to-day, engineering time to deploy experiments into your existing testing tool, access to that tool for setup and analysis, and attendance at the three working sessions.
The easiest next step is a short conversation.
We'll talk through what success criteria make sense for your context and what a fair experiment volume looks like for your traffic. From there we put together a pilot plan with you. You'll see the full pilot document before anything is signed.