When Only a Few People Know How to Build the Case Properly
Your company may already know how to calculate customer value, qualify an application or build a strong business case.
The problem begins when that logic depends on a specific spreadsheet, specialist or years of tacit experience.
Revetorque turns validated expert logic into dedicated tools that make repeatable parts of the workflow easier for Sales to use — without hiding assumptions or removing expert ownership of technical truth.
You may not need a new methodology. You may need a better way to use the one you already have.
In many industrial companies, the knowledge is already there.
It may live in:
- Excel models,
- engineering calculators,
- product-selection logic,
- ROI worksheets,
- application questionnaires,
- pricing and value frameworks,
- decision trees,
- rules of thumb,
- or the judgement of experienced specialists.
That is often valuable intellectual property.
The first step should not be to replace it.
It should be to understand:
what works, what repeats, what requires expert judgement and what should become easier for others to use.
Excel is often the starting point — not the final operating model
Spreadsheets are excellent for developing logic.
They are flexible, familiar and fast to adapt.
That is exactly why so much expert knowledge begins there.
But once the same logic needs to be used across more people, more opportunities and more customer situations, the limitations can become visible.
For example:
- users need to know which cells they are allowed to change,
- assumptions become difficult to govern,
- different versions begin to circulate,
- formulas are edited locally,
- the workflow depends on knowing undocumented rules,
- outputs need manual formatting before they can be shown to customers,
- or specialists still need to check every case.
At that point, the problem is no longer whether the spreadsheet calculates correctly.
The question becomes:
Is the underlying logic packaged in a way the organisation can use reliably at scale?
That is where a dedicated tool becomes relevant.
The problem starts when using the knowledge depends on knowing the workaround
Expert-dependent workflows often reveal themselves through small operational symptoms.
Sales repeatedly returns to the same specialist
The calculation may be theoretically available, but only a few people know how to use it correctly.
Different versions of the model circulate
The organisation loses certainty about which assumptions, formulas or logic are current.
The same work is reconstructed again and again
Customer data is collected, cleaned, copied and recalculated manually for every opportunity.
Important assumptions remain implicit
Experienced users know what a value means.
Newer users see only a field in a spreadsheet.
The tool works for its creator — but not naturally for everyone else
The workflow depends on familiarity rather than guided logic.
Internal models are difficult to expose to customers
A powerful engineering spreadsheet may still be a poor sales interface.
None of these automatically mean the methodology is weak.
They may simply mean the knowledge has outgrown the format it originally lived in.
A spreadsheet contains calculations. An expert workflow contains much more.
Turning an existing model into a dedicated tool is not just a matter of copying formulas into a nicer interface.
A real expert workflow also contains decisions such as:
Which questions come first?
Which inputs are genuinely required?
Which fields depend on earlier answers?
Which assumptions are acceptable?
Which values should come from the customer?
Which calculations require engineering validation?
What happens when the case falls outside normal limits?
When should Sales stop and escalate to an expert?
What output should the user receive?
The most valuable part of the process is often not the formula.
It is the decision logic around the formula.
That is what needs to be captured.
Productising expert knowledge should not mean removing the expert
Revetorque is not designed to automate technical judgement out of complex industrial sales.
Experts remain responsible for:
- technical truth,
- calculation methodology,
- operating limits,
- assumptions,
- exception rules,
- validation.
The goal is to identify which parts of their methodology are genuinely repeatable and make those parts easier for the wider organisation to use correctly.
Our working principle is:
Automate the repeatable logic. Escalate the exceptions.
Routine cases can follow validated logic.
Cases outside the validated boundaries still go to the people with the expertise to handle them.
That is a much more realistic model than pretending every technical sales decision can be fully automated.
Turn the workflow into a guided tool
Once the underlying decision logic has been mapped and validated, it can become a structured workflow.
Depending on the use case, a dedicated tool may include:
- guided questions,
- conditional fields,
- technical validation rules,
- units and conversions,
- customer-specific inputs,
- calculation logic,
- assumptions,
- scenario modelling,
- warnings,
- escalation triggers,
- product or configuration logic,
- output generation,
- version control,
- or auditability.
Not every tool needs all of these.
The structure should follow the decision.
From expert model to reusable workflow
A typical transformation looks like this:
Existing knowledge
Spreadsheet
+ expert methodology
+ product data
+ application knowledge
Knowledge extraction
Inputs
+ rules
+ formulas
+ assumptions
+ dependencies
+ exceptions
Expert validation
Engineering
+ Application
+ Commercial review
Guided workflow
Dedicated value-selling or decision-support tool
Real opportunity
Sales applies validated logic using customer-specific data.
The software is the final layer.
The difficult work comes first:
understanding and structuring the decision correctly.
Example: turning a complex application workflow into a guided sales process
Consider a technical equipment manufacturer where the correct recommendation depends on both customer operating data and specialist interpretation.
The existing process may require Sales to collect information such as:
- required performance,
- operating conditions,
- current system data,
- application requirements,
- process constraints,
- customer priorities.
A specialist then interprets those inputs using:
- product knowledge,
- technical rules,
- application experience,
- calculation logic,
- exception handling.
That methodology can be mapped into a structured workflow.
Sales enters the relevant customer data
The tool guides the user through the required information rather than exposing every possible technical field at once.
Validated logic determines what matters next
Questions and calculations can adapt based on the application.
Defined rules handle standard cases
Repeatable relationships are applied consistently.
Exceptions remain visible
When a case falls outside validated boundaries, the tool does not guess.
It escalates.
The user receives a structured output
The result may support:
- qualification,
- technical handoff,
- scenario comparison,
- business-case development,
- or another defined next step.
The point is not to replace specialist expertise.
It is to stop requiring that expertise for every part of every repeated case.
Repeatable logic does not require identical customers
A common objection to productising expert workflows is:
“Our customers are all different.”
They usually are.
That does not mean every decision is unique.
Different customers can still move through the same underlying framework while providing different:
- operating data,
- application requirements,
- assumptions,
- configurations,
- scenarios,
- priorities.
A good tool preserves that flexibility.
The principle is:
Standardise the decision framework — not the customer.
The workflow becomes repeatable.
The answer remains customer-specific.
Configuration and economic justification are different decision jobs
Some industrial companies already use CPQ or product configurators.
Those systems may be excellent at answering questions such as:
What should we configure?
Which option is technically valid?
What does it cost?
Revetorque typically focuses on a different layer of the decision:
Why does this solution make operational or economic sense for this customer?
Depending on the use case, those workflows can overlap.
But configuration and value justification are not necessarily the same problem.
Productisation makes most sense when valuable logic is already repeating
This use case is especially relevant when:
- the same expert workflow appears across opportunities,
- several salespeople need access to the logic,
- customer inputs change but the underlying decision structure repeats,
- formulas and rules can be validated,
- specialists repeatedly support similar cases,
- customer-facing use requires a cleaner workflow,
- methodology needs controlled updates,
- or the current process is becoming difficult to govern.
The opportunity is weaker when the work is genuinely unique every time or cannot responsibly be formalised.
The key question is not:
“Can we automate this?”
It is:
“Which parts of this expertise should become repeatable — and which parts should remain expert judgement?”
Have a spreadsheet or expert workflow that only a few people can use properly?
Bring us:
- the spreadsheet,
- methodology,
- calculation process,
- application workflow,
- decision rules,
- or recurring Sales → Engineering handoff.
We will first identify:
- what knowledge already exists,
- what logic repeats,
- what assumptions need validation,
- what should remain expert-controlled,
- and where a dedicated tool could make the workflow easier to use.
Then we determine whether it makes sense to productise that logic.
Discuss This Use Case
Tell us where expert knowledge currently becomes a bottleneck in a real sales opportunity.
Discuss This Use Case