Build the Tool. Test It in Real Opportunities. Scale What Works.
A Revetorque Pilot starts with one focused commercial decision.
We agree the specification and build the working hosted tool in approximately two weeks. Then a small group of your selected users puts it to work for 2–3 months on real sales opportunities.
Only after that do you decide whether the tool deserves the next 12 months — and how broadly you want to deploy it.
A Pilot is a working tool — not a prototype
You should not spend three months discussing what the application might eventually become.
Once you decide to purchase a Revetorque Pilot, we move into a short Building Phase.
Together, we refine the use case, agree the specification, validate the core logic and build the working hosted application.
The objective is straightforward:
Get a real tool into the hands of real users quickly enough to test it in real sales situations.
At the end of the Building Phase, you are not receiving a mock-up or a clickable concept.
You are receiving the working Pilot tool with the agreed core functionality.
Then the actual field test begins.
1. Build the Working Pilot Tool
Approximately 2 weeks
The Building Phase starts immediately after the Pilot purchase decision.
You do not need to arrive with a finished software specification.
You do need to bring the commercial problem and access to the people and logic behind it.
Depending on the use case, we may start from:
- an existing spreadsheet,
- ROI or TCO methodology,
- technical calculation,
- application workflow,
- decision rules,
- sample customer opportunities,
- product data,
- expert knowledge,
- or an existing manual sales process.
Together, we define what the Pilot tool actually needs to do.
What happens during the Building Phase?
We define the decision
What does Sales or the customer need to understand, calculate, compare or justify?
We agree the tool specification
Which inputs, workflows, calculations and outputs belong in the Pilot?
We structure the logic
That may include:
- formulas,
- assumptions,
- technical rules,
- value drivers,
- conditional workflows,
- scenarios,
- exception handling,
- escalation rules.
Your experts validate the model
Relevant Sales, Product, Application Engineering or other subject-matter experts confirm the logic before it becomes embedded in software.
We build the hosted application
The agreed model becomes a working tool.
Depending on the use case, core functionality may include:
- guided inputs,
- customer-specific calculations,
- saved calculations,
- calculation history,
- scenario comparison,
- PDF generation,
- customer-facing outputs,
- user access,
- basic usage instrumentation.
We prepare your first users
Pilot Champions receive the instruction or training needed to start using the application.
What you receive after the Building Phase
At the end of approximately two weeks:
A working hosted Pilot tool, ready to be used in real sales opportunities.
That distinction matters.
The following 2–3 months are not additional months of waiting for software.
They are the period in which your team discovers whether the tool works where it actually matters:
in the field.
2. Put the Tool in the Hands of Real Users
2–3 months of live Pilot use
Once the tool is released, you select a small group of Pilot Champions.
These are the people who will actually use the tool in relevant sales situations.
The Pilot is not a demo programme.
It is not a workshop where users click through a few screens and tell us whether they like the interface.
Your Champions use the tool with:
- real opportunities,
- real customer situations,
- real inputs,
- real decision workflows.
The key question changes from:
“Does this tool look useful?”
to:
“Does this tool earn a place in the way our team actually sells?”
Choose Champions who will actually put the tool under pressure
The best Pilot Champion is not necessarily the most senior salesperson.
A useful Champion should:
- actively work the type of opportunity the tool was built for,
- understand the existing process,
- have access to real opportunities during the Pilot,
- be willing to use the tool repeatedly,
- provide concrete feedback,
- expose the workflow to realistic customer situations.
You need active users.
Not ceremonial sponsors.
A small group is enough to start.
The point is to generate useful evidence before expanding access.
3. Generate Evidence — Not Just Opinions
A successful software build and a successful Pilot are two different things.
Building proves that the logic can become a working tool.
The Pilot tells us whether the tool deserves to become part of the commercial workflow.
That requires evidence.
Usage
Did Champions actually use the tool?
Repeat use
Did they return to it across multiple opportunities?
Real-opportunity use
Was the tool used in genuine customer situations — not only internally?
Workflow fit
Did it perform the decision job it was built for?
Could users obtain the inputs?
Did the workflow make sense in practice?
Did the outputs support a useful next step?
User behaviour
Where did users:
- progress smoothly,
- hesitate,
- abandon the process,
- need additional support,
- work around the tool?
Customer and stakeholder signals
Where observable:
- Was the output used in customer discussions?
- Was it challenged?
- Was it shared internally?
- Did it trigger additional questions?
- Did another stakeholder engage with the case?
Commercial outcomes
Metrics such as:
- win rate,
- discounting,
- deal size,
- sales-cycle length,
- conversion,
may matter over time.
But they require enough opportunities and enough evidence to interpret responsibly.
We do not jump from:
“someone used the tool”
to:
“the tool improved revenue.”
Claim strength should follow evidence strength.
Define success before the live Pilot begins
Pilot success should not be invented after the results arrive.
Before Champions begin using the tool, we agree what we are trying to learn.
That may include:
- who should use it,
- which types of opportunities should qualify,
- how often we expect it to be used,
- which workflows need to function,
- which outputs need to be produced,
- what user feedback matters,
- which operational behaviours should be observed,
- which longer-term commercial signals are worth tracking.
The exact Success Definition depends on the use case.
The principle does not:
Decide what evidence matters before you see the evidence.
A Pilot is allowed to uncover problems
The first version does not need to prove that every assumption was perfect.
The Pilot may reveal that:
- an important input is difficult to obtain,
- one part of the workflow is too complex,
- the output needs to change,
- an assumption was unrealistic,
- users ignore a feature,
- Sales needs another path,
- the original problem was framed too broadly,
- or the tool is solving the wrong part of the decision.
Those are not useless outcomes.
They are exactly the kind of information a Pilot is supposed to uncover.
The point is not to prove that V1 was perfect.
The point is to understand whether the underlying use case deserves continued investment — and what needs to change before wider deployment.
4. Decide Whether the Tool Has Earned the Next 12 Months
At the end of the 2–3 month live Pilot, we review the evidence together.
The decision is not automatic.
The questions are:
Did the intended users actually use the tool?
Did they use it more than once?
Did it fit real opportunities?
Did it perform the job it was built for?
What needs to change?
Is there enough value to keep using it?
From there, the client makes the next commercial decision.
Continue
The Pilot provides enough evidence to justify ongoing use.
The tool moves into a 12-month agreement.
Iterate
The use case still appears valuable, but the evidence reveals a specific blocker or improvement that should be addressed.
That issue can be corrected before or as part of the next stage, depending on scope.
Stop
The evidence does not justify continued investment in the current tool or use case.
Access can end.
That is a valid outcome.
The purpose of a Pilot is not to make rollout inevitable.
It is to make the next decision better informed.
5. Choose the User Band
If the decision is to continue, the next question is:
How broadly should the tool be deployed?
You do not need to answer that before the Pilot.
The annual Revetorque model uses User Bands — defined ranges based on the number of people who need access.
That means you can first learn:
“Does this tool work for us?”
and only then decide:
“Who should have access to it?”
Depending on what the Pilot proves, the annual deployment may expand to:
- more Sales users,
- additional teams,
- wider geographies,
- more products or applications,
- broader customer-facing use.
The Pilot validates the workflow first.
Access scales second.
Pilot validates the tool. Annual access operationalises it.
The live Pilot is deliberately temporary.
Its purpose is to generate enough evidence for a longer-term decision.
If the client continues, the next 12 months turn the validated Pilot into an ongoing operating tool.
Depending on the agreed commercial package, that may include:
- hosted application access,
- the selected User Band,
- user accounts,
- saved calculation history,
- maintenance,
- support,
- usage monitoring,
- agreed updates,
- periodic review.
The exact annual structure follows the validated use case and agreed scope.
What we need from you
You do not need a software specification.
But building a useful decision tool does require access to the logic behind the decision.
Typically, we need:
A commercial owner
Someone who understands why the problem matters.
Relevant subject-matter experts
For example:
- Sales,
- Application Engineering,
- Product,
- Finance,
- another technical or commercial specialist.
Existing materials
Where available:
- spreadsheets,
- calculations,
- sales workflows,
- product data,
- assumptions,
- decision rules,
- sample proposals.
Real opportunity examples
Enough context to test whether the model reflects actual sales situations.
Timely validation
Especially during the Building Phase.
Two weeks only works if key decisions do not spend ten days waiting in someone's inbox.
Pilot Champions
A small group prepared to use the tool during the live Pilot.
What Revetorque owns
You provide the domain truth.
Revetorque turns it into a usable decision product.
Our role includes:
- structured discovery,
- decision modelling,
- specification,
- value-model design,
- workflow design,
- UX,
- software implementation,
- hosted delivery,
- usage instrumentation,
- Pilot setup,
- user instruction or training,
- evidence framework.
We do not replace your technical experts.
We make validated parts of their knowledge usable inside the tool.
One decision is enough to test whether the model works
You do not need to redesign your entire sales organisation.
A strong first Pilot usually starts with:
one meaningful commercial problem
+
one defined product or use case
+
a small group of active Champions
+
real opportunities
+
a clear Success Definition
That is enough to learn something useful.
If the model works, you can expand.
If it does not, you have learned that before committing to wider deployment.
The Revetorque Pilot at a glance
Building Phase
Approximately 2 weeks
Define the specification, validate the logic and build the working hosted Pilot tool.
Live Pilot
2–3 months
Selected Champions use the tool in real opportunities.
Evidence Review
Evaluate usage, repeat use, workflow fit, user feedback and available business signals.
12-Month Decision
Decide whether the tool deserves continued use.
User Band
If continuing, select the level of access appropriate for the organisation.
Build → Use → Learn → Decide → Scale
Have one decision problem worth testing?
Bring us:
- the recurring sales problem,
- the workflow or spreadsheet you use today,
- the people who understand the underlying logic,
- and the kind of real opportunities where the tool could be tested.
We can determine whether the use case is focused and repeatable enough for a Revetorque Pilot.
You do not need to know what the final application should look like.
That is part of the Building Phase.
Discuss a Pilot
Tell us what decision you want the tool to support and how your team handles it today.
Discuss a Pilot