AI, in the work itself.
We start with a three-month programme and continue with an ALTAI engineer who works with your team every month. Larger work is planned as its own project.
- The first 90 days: We agree where to start and build 2–3 small implementations.
- Every month: An ALTAI engineer works with your team: observation, prototypes, small automations.
- Its own project: Larger work runs with its own team, budget and timeline.
- Measured: We compare the result with the baseline.
Diagram: a calendar line. In the first 90 days three small implementations are built; every month after that a small piece of work is completed; in month six larger work turns off into a separate project; the result is compared with the baseline.
A start, ongoing work or a project.
Most teams begin with the three-month programme and move on to monthly support as long as the need lasts. With a defined software need, you can also start with a project.
The first 90 days
We look at processes with your people, agree data-use rules and run the training that is needed. We aim for 2–3 small implementations and a plan for what comes next.
An ALTAI engineer on your team
An embedded engineer works with your team every month, with an ALTAI AI Lead supporting technical decisions. Short prototypes and small automations are included.
A development project
A dedicated team for a defined application, model or agent. Scope, budget and delivery timeline are agreed up front.
ALSO
- Training: Learning built around each role’s own work: leaders, office teams, frontline staff and builders.
- AIthon: One or two days of prototyping around problems your people bring forward.
- Data and models: Data preparation, model training, access rules and MLOps support.
How does our engineer work?
- Observes: Sees how the process runs today with the people who do the work; agrees the users, the data and what counts as success.
- Builds: Builds the first prototype and tests it with users. Small work is finished on site; larger work becomes a project.
- Measures: Compares the result with the measurement taken before the work began.
How we measure results.
Before we start, we record the current time, error rate or cost. We then take the same measurements on what we built.
What we measure
- Completion and waiting time
- Error and rework rates
- Cost per transaction
- Regular use
What we need from you.
The work runs on site every week; every month we review what is done and choose what comes next together.
Your contribution
- A process owner who follows the work and makes decisions.
- Access to the data and systems needed, within agreed permissions.
- Time from the people doing the work for testing and feedback.