Our Process


At the start of a project we use design thinking to gather requirements. This means we try to draw up quick prototypes as we go, draw insights, then redesign. The core feature of design thinking is the workshop. This process works with everything from model writing to interface design. The advantage of this process are:

  • Close contact with the client making it easier to achieve a shared understanding
  • Rapid iteration
  • Reduction in development time


We plan upfront to give our client a clear view of the lifecycle of a project. We look closely at:

  • Timelines
  • Milestones
  • Roles
  • Tools
  • MVP
  • Deliverables
  • Success measures
  • Risk management measures

We understand that it is often the talent and energy of individuals that is the magic sauce in a project. We think of our process as a safety net. We examine our process on a daily basis to ensure it working best for a particular client.


We have a multi-disciplinary team on hand to execute your project coming from Maths, Software Development, User Experience Quality Assurance, Product Management, as well as domain specialists.

Our development practices are agile. A good way of thinking about agile is that the less we know about the end-user’s needs the more agile a project needs to be. Feedback cycles become shorter to account for possible changes of direction mid project.

We aim to define requirements as clearly as possible so projects can be lean.


Our software and modelling solutions are deployed on the Expert Models platform. Expert Models gives powerful primitive building blocks in the following areas:
Data science interfaces: File management systems, editors and wizards.
Scalability & power: Our systems run on AWS and can scale in real time.
Security & privacy: Our cloud based platform allows strong perimeters and surveillance, access control, superior auditing and data obfuscation.


Measurement is how we improve. Some of the metrics we track are:

  • Software analytics / engagement
  • Customer success (education / training / onboarding)
  • Retrospectives post sprint (a sprint for us is a two week block of work)
  • Return on investment

We think a lot about feedback loops and how we can shorten the time between doing and measuring.