Three automated steps became twelve

The case study in statements

1. 01

   Finding

   Capture, evaluation and communication hang on one process instead of three tools. Where a case currently stands can be read off without anyone having to ask.

2. 02

   Starting point

   The process was a sequence of manual handovers between disconnected tools. Something could stall at any handover, and none of them was visible from outside.

3. 03

   Build

   One central application and several automations join capture, evaluation and communication into a single flow. What used to travel between three tools is now one case with one state.

   1. Capture
   2. Evaluation
   3. Message
   4. Record

   The joins between the steps are exactly where it used to stall.

   Stack

   • TypeScript
   • AI
   • Automation
   • APIs
   • Cloud
4. 04

   Limit

   What was automated is what repeats. The decision is not part of it. Every step leaves a record, so that it can be read back later why a case went the way it did.

5. 05

   Share

   Concept, application and automation chain. CoderConda took the process apart, decided which steps could be automated and built the chain that connects them.

6. 06

   Result

   More process steps run predictably, and the state of a case stays visible at all times.

   3 → 12from 3 to 12

   automated process steps

   Operating figure, not a business figure

1. —

   Reach

   The figure holds for this one case. RecRobot is a recruiting process, not a sales project and not a client portal.

2. —

   Effect

   What the system earned the client is not stated here. That figure belongs to the client, and no release has been given.

3. —

   Steps

   The twelve steps are not listed one by one here. What the system looks like inside can be seen on a screen during the first call.