// $1,500 · 5 business days Request the proof →

// the workflow proof

Show us the workflow your team still does by hand.

For $1,500 fixed, we build a working automation proof on your real or representative data in five business days. One workflow. One agreed output. No production access.

Fit is checked before you pay anything at all.

Full credit — the entire $1,500 applies toward production.

Refunded if we accept it and miss the agreed output.

1
workflow
5
business days
$1,500
entire price
0
production credentials

// two minutes, four fields

Describe the workflow in plain English.

// no sales sequence · nothing to pay yet · prefer a call?

// is it a fit

The best proofs have a clear beginning and end.

// good fit

It repeats — daily, weekly, monthly, or per job.

It starts with files, exports, or a database extract.

It ends with a concrete file, report, or dataset.

The rules can be explained by the person doing it.

It runs without touching production or validated systems.

// needs a larger engagement

Live writes into production or validated GxP systems.

Hardware, PLC, scanner, or serial-device integration.

A new custom application or user interface.

Several unrelated workflows, or an entire data estate.

On-site work.

Security or compliance certification.

Anything whose finish line cannot be defined.

// still good Mad Botter projects — just not $1,500 projects. Send it anyway; we say so before taking payment.

// what you get on day five

A working result, not a strategy deck.

Working proof

A repeatable Alice workflow running on your representative data.

Agreed output

The file, dataset, or exception list defined before work begins.

Run record

Inputs, assumptions, transformations and exceptions made visible.

Production plan

Fixed price, timeline and acceptance test to put it into operation.

// five business days

A small engagement with a hard finish line.

day 0

Fit and finish line

We review the workflow, confirm it fits, define the input and output, and document what counts as correct. Payment follows acceptance of that scope.

day 1

Data and rules

You provide the representative export and explain the current decisions, corrections, and exceptions.

days 2–4

Build and test

We implement the workflow, compare results, expose exceptions, and prepare the repeatable run.

day 5

Replay and review

We run the agreed input, produce the output, walk through the result, and deliver the production recommendation.

// The five-business-day clock begins after the usable input and written acceptance test are confirmed.

// aerospace and mro

Fifteen Monday boards, roughly 14,000 records, and a 1.6 TB document archive consolidated into one operational system.

// industrial agriculture

More than 500 API endpoints, 70+ data models, warehouse applications, and packing-line hardware operating as one production system.

// heavy civil

One equipment, inspection, certification, and transfer system across five operating companies and 15+ active sites.

Read the case studies →

// before you send it

The four things people ask first.

Can we use redacted or representative data?

Yes. No production credentials are needed — just data representative enough to test the real rules and the real output.

What if a new requirement appears halfway through?

Scope never becomes an uncapped hourly bill. We finish the agreed proof, then define and price the new requirement separately.

Where does our data live, and can you sign an NDA?

Yes to the NDA. We agree the transfer method before receiving anything, restrict access to the delivery team, and document retention and deletion in the scope note.

What does production cost afterward?

Simple live deployments typically start at $3,500. Multi-system, on-premises, or regulated implementations typically start at $7,500. You get the fixed quote before deciding — and the $1,500 is credited.

Start with the workflow only one person knows how to do.

Put it into a few sentences. We tell you whether it fits before asking you to buy anything.

// contact

Tell us what you're trying to build.