Choose
Select one asset class, site group, route, inspection process or field-evidence workflow.
Bounded paid pilot
Start with one asset class or workflow.
A Tensile pilot is designed to test whether asset records, assigned work, field evidence, defects and office review can stay connected clearly enough to improve day-to-day operations.
Indicative range: £2,500–£7,500. Final scope, users, data and measures are agreed before live work starts.
What a pilot is not
A first pilot is not intended to replace every asset, works, finance, contractor or reporting system at once. It should prove one bounded workflow before wider rollout is discussed.
Process
Choose, configure, run, review.
The pilot keeps scope visible from the first conversation through to the end-of-pilot decision.
Configure
Set up the workspace, fields, users, starter records and evidence rules for the selected workflow.
Run
Complete real work with the web portal and worker app, with support from Tensile during the pilot.
Review
Compare the pilot with agreed measures and decide whether to stop, continue or expand.
Indicative range: £2,500–£7,500One asset class or workflow, starter-data support, initial-user support and agreed success measures.
Included support
Enough support to test the workflow without expanding silently.
Pilot support is founder-led and focused on setup, configuration, initial user guidance, issue triage and pilot review. New requirements discovered during the pilot are logged and considered separately.
- Workspace setup and configuration for the selected workflow
- Starter-data support for one controlled asset class or workflow
- Agreed users, roles and initial user support
- Assigned work or inspections using the web portal and worker app
- Field evidence capture and office review
- End-of-pilot review against agreed success measures
Measures
Agree the review measures before the pilot starts.
The measures are used to decide whether the workflow improved visibility, evidence quality and review for the selected asset class or field process.
Work completed in the selected workflowCompleted tasks with required evidenceField completion to office visibilityRecords requiring correctionLinked defects and follow-upOffice-user and field-user feedbackSupport effort required during the pilot
These are example pilot measures, not published customer results.
Data and setup
What needs to be clear before live use.
The selected workflow, users, starter data, evidence requirements, support route and exit expectations should be agreed before the pilot begins.
One asset class, route, site group or field process selected for the pilot
Confirm this before live rollout so the pilot stays bounded and reviewable.
Starter records with identifiers, descriptions, status and location context where available
Confirm this before live rollout so the pilot stays bounded and reviewable.
Inspection requirements, defect categories and evidence rules for the chosen workflow
Confirm this before live rollout so the pilot stays bounded and reviewable.
Named office users, field users, supervisors and workspace administrators
Confirm this before live rollout so the pilot stays bounded and reviewable.
Agreement on what data should be exported, deleted or retained if the pilot stops
Confirm this before live rollout so the pilot stays bounded and reviewable.
Decision
Stop, continue or expand.
The pilot should end with a practical decision rather than an open-ended trial.
Stop
Close the pilot cleanly and follow the agreed export, deletion or retention process.
Continue
Move the selected workflow into an annual workspace proposal.
Expand
Scope another workflow, asset class, team or integration requirement separately.
Pilot FAQ
Early questions before scoping.
Who is the pilot for?
The pilot is for infrastructure operators, contractors and operational businesses that want to test one bounded office-to-field workflow before discussing wider rollout.
What is the indicative price range?
The current indicative paid-pilot range is £2,500–£7,500 depending on scope, data, users and support needs.
Can we start with imperfect data?
Yes, but poor data should be made visible. A pilot can expose data-quality issues, but it should not be sold as a complete data-cleansing project unless that is explicitly scoped.
What happens at the end?
The pilot should end with one of three decisions: stop because it is not a good fit, continue with the selected workflow, or expand into another asset class, team or workflow.