Skip to content
CoderConda

Data & automation

Requests run through an automation. Switch the controls off one at a time and see what reaches the customer.

Test bench: 8 requests, 4 controls

Controls
  1. 1Laying parquet, 40 m², Cologne, wk 42waits for approvalsentwaits for approvalsent
  2. 2Tiling, 12 m², Bonn, no dateAsked back: Date missingAsked back: Date missingwrong draft waits for approvalsent wrong
  3. 3Painting walls, 180 m², Düsseldorf, wk 43waits for approvalsentwaits for approvalsent
  4. 4Screed work, 4,000 m², Cologne, wk 43with a person: Quantity outside 1 to 500 m²with a person: Quantity outside 1 to 500 m²wrong draft waits for approvalsent wrong
  5. 5Laying parquet, 25 m², Bonn, wk 44waits for approvalsentwaits for approvalsent
  6. 6Tiling, forty m², Cologne, wk 44Asked back: Quantity is not a numberAsked back: Quantity is not a numberwrong draft waits for approvalsent wrong
  7. 7Painting walls, forty m², Bonn, wk 45Asked back: Quantity is not a numberAsked back: Quantity is not a numberwrong draft waits for approvalsent wrong
  8. 8Laying parquet, forty m², Cologne, wk 45Asked back: Quantity is not a numberAsked back: Quantity is not a numberwrong draft waits for approvalsent wrong
Sent correctly
0
Sent wrong
0
With a person
4
Asked back
4
Sent correctly
3
Sent wrong
0
With a person
1
Asked back
4
Sent correctly
0
Sent wrong
0
With a person
8
Asked back
0
Sent correctly
3
Sent wrong
5
With a person
0
Asked back
0

Log on: All 8 requests have an entry saying what arrived and what became of it.

Log off: None of the 8 requests has an entry. Who approved what can no longer be said.

Limit set: After 3 asks in a row (requests 6 to 8) the automation stops and reports in. Request 9 and all after it wait.

No limit: Nothing stops the run. Request 9 and all after it hit the same ask, and the sender gets a message every time.

Limit set: It caps runs and cost. Without rules it cannot see a run of failures, because nothing counts as one.

No limit: Nothing caps runs or cost. Request 9 and all after it go through the same way.

The rules in the example: quantity 1 to 500 m², date not before week 41. What each request triggers, the page works out from these rules.

In operation

Operating figures from the case studies, not business figures. What the systems earned the clients is in their books. Projects

  • 3 min

    KI-Exposé-Generator

    per proposal · previously 45

    If a detail is missing, the system asks for it instead of inventing it. Approval is manual.

    Shows Rules at the door, Approval by a person

  • 3 → 12

    RecRobot

    automated process steps

    What got automated is what repeats, never the decision. Every step leaves a record.

    Shows Approval by a person, Log

  • 2,500

    Snipeflip

    operations per day · one server

    The state is readable on one surface at any time, not buried in logs.

    Shows Log

What I use it for

  1. 01Generating brochures, proposals and reports automatically
  2. 02Pre-sorting applications and candidates
  3. 03Watching prices and offers in the market
  4. 04Content production from a single source
  5. 05Recurring reporting without manual work

Matching offers

Automation comes at a fixed price, in tiers. They are on Services.

Which requests would your automation get?

Write me three sentences about the work that repeats in your company. On the call I go through it with you: which rules apply at the door, who approves and when the automation stops.

Your part
Three sentences
Reply
Two working days, Mon to Fri
First call
15 minutes, video, no cost
Book the intro call

Or directly: info@coderconda.com

Other technologies