How we work
In stages, with success defined up front.
Every stage has a fixed proposal and a defined deliverable, and ends with your decision. The next one starts only after the last one was measured.
Stages
From the first call to operation.
You can stop at the end of any stage and keep everything delivered so far.
-
Intro call
A conversation with people who know the operation and people who decide.
What we do
- We learn how the plant runs, which systems it uses and which problem hurts most.
- We check fit and who sponsors the project.
What you get
A fixed proposal for the assessment, or a clear note that it is not a fit.
-
Assessment
A picture of the areas, the data and where AI is worth the effort.
What we do
- Interviews with one or two people per area.
- An inventory of data and systems with IT: ERP, MES, spreadsheets, documents and records.
- Effort and risk estimates for each opportunity.
What you get
A report with the opportunity map, a recommended pilot and its success criterion. The report is yours either way.
-
Pilot
The first real use, small enough to measure.
What we do
- We build the part of the operations brain the pilot needs.
- We build the agent or screen and train the people who will use it.
- We measure the success criterion before and after.
What you get
A pilot in use, with the agreed measurement and a recommendation on what to expand.
-
Staged rollout
Other areas follow in the order the pilot suggests.
What we do
- Each new area has its own scope, owner and criterion.
- Integrations with your systems are built together with IT.
What you get
Each area in use, documented, with its criterion measured.
-
Managed operation
Support once the agents are part of daily work.
What we do
- Monitoring of usage and answer quality.
- Tuning, new use cases and training for new staff.
What you get
A monthly report on usage, issues solved and next steps.
Delivery structure
One technical lead, plus specialists when the scope calls for them.
From day one you know who is accountable and who else will work on the project.
One technical lead
One person answers from assessment to operation
Today that is Henrique Pett, founder of Torno. He runs the interviews, designs the solution, writes code and answers for each stage.
On-demand specialist network
Specialists named in the proposal
Data, security, UX, infrastructure and industry specialists join when the scope calls for them, each named with a role in the proposal.
Governance
Simple cadence, decisions in writing.
Leadership can follow the project without diving into technical detail.
Sponsor and point of contact
A sponsor in leadership and a point of contact in operations, named in the proposal.
Biweekly review
Progress, blockers and pending decisions, with an agenda sent ahead.
Criterion per stage
Each stage has a success criterion agreed before it starts and measured at the end.
Monthly report
What was done, what was measured, what changed and what comes next.
Decision log
Technical and scope decisions recorded with date, reason and approver.
Security and privacy
Your data follows your IT rules.
IT approves the architecture before any data moves.
-
Where data lives
In your infrastructure or a cloud your IT approves.
-
Role-based access
Each person sees only what their role allows in the source systems.
-
Usage logs
Questions, answers and agent actions are logged for audit.
-
Third-party models
Your data is never used to train third-party models.
-
Confidentiality
An NDA signed before the assessment, when you ask for one.
-
Data protection
Personal data used only for the agreed purpose, with each party’s role set in the contract.
Continuity
You are never locked in.
What we build keeps running with or without us.
In your name
Code, documentation, access and cloud accounts are yours from day one.
Runbook
How it works, how to monitor it, what to do when something fails and how to add a use case.
Handover to IT
When IT wants to take over, we hand over with working sessions and follow-up.
On your side
What we need from you.
The internal effort is small, but it has to be on the calendar.
A sponsor
Someone in leadership who decides at the end of each stage.
A point of contact
Someone in operations who books interviews and unblocks access.
Time from each area
About an hour per person interviewed, and a key user during the pilot.
IT on board
System access agreed with IT, read-only where possible.
Questions
How much does it cost?
Each stage has a fixed proposal. The assessment is quoted after the intro call; the pilot and rollout after the assessment, because the price depends on areas, systems and data volume. Managed operation is a monthly fee.
Is Torno just one person?
Torno has one technical lead, Henrique Pett, who is accountable for the whole project. Data, security, UX, infrastructure or industry specialists join by scope and are named in the proposal.
Do we need to replace our ERP?
No. We work on top of what you already use, whether TOTVS, SAP or another system, with the access your IT grants.
Can we stop halfway?
Yes, at the end of any stage. You keep everything delivered so far, including code and documentation.
Start with an intro call.
45 minutes, free, to understand your operation and see whether an assessment makes sense.