Find a use case
We map one workflow with the people who do the work. We look at the inputs, handoffs, exceptions and outputs, then agree what a useful first version should demonstrate.
← Home
The engagement
See it work. Then decide.
Start with one workflow. See a working proof of concept. Agree what it takes to build and operate the full solution.
See a working version
We build a focused proof of concept and review it with your team. It is a chance to test the workflow and identify what needs to change before scoping the full build.
Make it production-ready
We agree scope and commercial terms, then implement the required connections, permissions, testing and deployment. Your environment and operating requirements shape this stage.
Own it and operate it
Your agreement defines ownership of the delivered code, infrastructure and documentation. We also agree who maintains the system and how support, hosting and third-party costs are handled.
Clear expectations
Before we start.
When do we make a paid commitment?
The proof of concept comes before the full-build commitment. We agree the scope and any terms for each stage with you before work begins.
How long does it take?
A focused proof of concept can often be built within a week. Production timing depends on scope, access, integrations and review requirements. We agree the delivery plan for your project.
How does the delivery guarantee work?
Tenfold’s delivery promise is: delivered on time, or your build is free. The agreed scope, delivery date, client dependencies and applicable terms need to be set out in your project agreement.
What will we need to provide?
A workflow owner, representative inputs and outputs, and the access needed for the agreed scope. We can establish the right way to handle sensitive data during discovery.
What costs remain after the build?
Hosting, third-party software, model usage and ongoing support can have recurring costs. We identify these separately so you can assess the cost of operating the delivered system.
Who handles security and access?
Production requirements are agreed with your team. Identity, permissions, data handling, environment and review processes are part of implementation, not assumptions made by the prototype.
Start with the problem
Show us the process you’re tired of doing by hand.
Tell us what your team does today and where it gets stuck. You don’t need a technical brief. We’ll work through whether custom software would help.
Tell us what’s slowing you down