Working together in four stages
Each stage has its own goal and deliverable. You can stop there or hand the next stage to your own team.
Understand the problem
We investigate the process, establish the cost of the problem, identify constraints and key unknowns, and compare possible solutions.
What you get: A process map, a baseline for measuring impact, options and an experiment plan. An initial agreement on maintenance.
Decision: test the proposed approach
Prove the value
We build a prototype or a working part of the solution. We test it with users, using agreed data and conditions relevant to the process.
What you get: Working evidence, measured results and a recommendation. You know what has been validated and what still needs testing.
Decision: move towards production
Deliver to production
We build and integrate the solution, meet the agreed production requirements and prepare users for everyday work.
What you get: A deployed system, automated tests, observability and documentation. Agreed deployment and incident procedures.
Decision: readiness for handover
Handover and maintenance
Your team takes over, or ANSLAN maintains and develops the solution within an agreed scope. Preparation starts in the first stage.
What you get: Code, documentation, operating procedures and transferred knowledge. Clear responsibilities for the system’s ongoing operation.
Your team or ongoing ANSLAN support
The price depends on the number of systems, data availability, the number of departments involved and security requirements. Time ranges are indicative and apply to individual stages. We agree the schedule with access to environments, data and people in mind.
One team takes the problem through to an agreed outcome.
We combine process discovery, architecture, experimentation and delivery. You work directly with the experts building the solution.
Start with the work itself.
We get to know the people, data, exceptions and constraints. Together, we define the outcome and how to assess it. You do not need a finished specification.
Test before committing further.
We choose the smallest experiment that can resolve an important unknown. If further investment is not justified, we say so.
Plan for life after delivery.
We agree who will own and maintain the solution. Your IT standards and the capabilities of the team taking over inform our decisions from the start.
Review real progress every 1–2 weeks.
During prototyping and production development, iterations usually last one week and never more than two. Each ends with a review of a working increment or experiment result.
Need a head start for your own team? We can investigate a difficult problem, build a prototype and hand over the foundations for production development in-house.
We do not provide staff augmentation or developers by the hour. We take on a defined problem, from understanding it to delivering the agreed scope.