Is analysis always required?
No. When the process is unclear or uncertainty is high — paid analysis. When scope and acceptance criteria are already clear — a quote for the first delivery stage.
Before we start
Questions before cooperation
Answers that come up before kick-off: analysis, code ownership, stabilisation and what stays on the company side.
What remains after a stage?
After analysis: agreed materials and decisions. After delivery: stage code, documentation and sign-off notes. Functionality is first in a test environment; production follows sign-off.
Who owns code and accounts?
Agreed materials and stage code remain after the stage. Infrastructure accounts and third-party licences stay with the company unless the quote says otherwise. Another vendor can take over maintenance.
What is stabilisation versus support?
Stabilisation is the agreed period after go-live in the launch quote. Ongoing support and development are a separate service contract. Hours and any SLA are set there — we do not offer 24/7 support.
What stays on the company side?
A process owner, access to people and systems, agreed requirements and sign-off. TensorFrog takes the agreed IT scope — not the company’s entire IT, nor vendor licences and infrastructure.
How do we judge whether the project pays off?
Before we start we agree the current state, volume, the cost of errors if it can be estimated, implementation and running cost, and a success measure. Using the current tool instead of a new build can be the recommendation.
Other process pages
Describe the company situation — we will propose the first stage and a quote before work starts.
Go to contact