// the workflow proof
Show us the workflow your team still does by hand.
For $1,500 fixed, The Mad Botter uses your real or representative data to build a working automation proof in five business days.
One workflow. One agreed output. No production access. No open-ended consulting.
One sentence is enough. We'll tell you whether it fits.
Fit checked before payment · full credit toward production · refund if we accept it and cannot meet the agreed output
source export
↓
spreadsheet cleanup
↓
manual reconciliation
↓
review and correction
↓
report / dataset / upload / email
representative input
↓
repeatable Alice workflow
↓
exceptions made visible
↓
agreed output produced twice
// illustrative — not customer data
// what fits
The best proofs have a clear beginning and end.
The workflow does not have to be simple. It does have to be explainable. The person doing it today should be able to show us what comes in, what decisions or rules are applied, and what correct output looks like.
A good fit:
- It happens repeatedly: daily, weekly, monthly, or for every job.
- It begins with files, exports, database extracts, or a supported source.
- It ends with a concrete file, report, dataset, reviewed package, or delivery action.
- It follows rules a knowledgeable operator can explain.
- It is the same cleanup and reconciliation, done repeatedly by one person or a small group.
- It can run without changing production or validated systems.
For example:
- Reconcile repair-order, inventory, and shipment exports.
- Turn project-system and accounting exports into a weekly owner report.
- Prepare a controlled quality or operations report from approved exports.
- Clean and transform a legacy-system extract for a new destination.
- Compare two operational records and flag exceptions for human review.
// what does not fit the $1,500 proof
Some work deserves a larger engagement. We say that before taking payment.
Live writes into production systems.
Changes to validated GxP systems.
Hardware, PLC, scanner, sensor, or serial-device integration.
A new custom application or user interface.
Several unrelated workflows.
Undefined cleanup of an entire data estate.
On-site work.
Security or compliance certification.
A request whose finish line cannot be defined.
// those may still be good Mad Botter projects — they are not secretly $1,500 projects
// deliverables
You receive a working result, not a strategy deck.
A repeatable Alice workflow running against the agreed representative data.
The file, dataset, report, or exception list defined before the work begins.
Inputs, assumptions, transformations, exceptions, and outcome made visible.
A recorded or live review showing the workflow and where human approval belongs.
The live sources, security requirements, deployment model, timeline, acceptance test, and fixed price required 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.
// price and next step
$1,500 is the entire proof price.
There are no hourly overages. If the agreed proof needs to change, we stop and agree on the change rather than letting the bill drift.
If you put the workflow into production within the approved credit window, the full $1,500 is applied to the implementation.
// production guidance
Simple live deployments typically start at $3,500.
Multi-system, on-premises, or regulated implementations typically start at $7,500.
Managed operation starts at $500 per month.
You receive the fixed production quote before deciding.
// intake
Describe the workflow in plain English.
No architecture diagram required. One sentence about the thing your team still does by hand is enough to start.
Prefer a conversation? Book a short call with Michael.
// what happens after submission
1 · Fit decision. We confirm whether the workflow fits the proof or needs a different fixed-scope engagement.
2 · Scope note. You receive the input, output, acceptance test, exclusions, and timing in writing.
3 · Secure start. After approval and payment, we provide the data-transfer path and schedule the day-five review.
> send workflow-proof-request
+ request received
+ routed directly to Michael Dominick
You will receive a fit decision within one business day. If the workflow fits, the next message is a written scope note with the input, output, acceptance test, exclusions, and timing.
Fifteen Monday boards, roughly 14,000 records, and a 1.6 TB document archive consolidated into one operational system.
More than 500 API endpoints, 70+ data models, warehouse applications, and packing-line hardware operating as one production system.
One equipment, inspection, certification, and transfer system across five operating companies and 15+ active sites.
// what happens after submission
A fit decision, then a written scope.
1
Fit decision
We confirm whether the workflow fits the proof or needs a different fixed-scope engagement.
2
Scope note
You receive the input, output, acceptance test, exclusions, and timing in writing.
3
Secure start
After approval and payment, we provide the data-transfer path and schedule the day-five review.
// before you send it
Common questions
Is this an audit or discovery workshop?
No. It produces a working automation proof against the agreed data. The production recommendation is a byproduct of building the proof, not the only deliverable.
Can we use redacted or representative data?
Yes. The proof does not require production credentials. Use data representative enough to test the real rules and output.
Can you sign an NDA?
Yes. Procurement and confidentiality requirements can be handled before data transfer.
Where is our data stored, and when is it deleted?
We agree on the transfer method before receiving data, restrict access to the delivery team, and document the retention and deletion date in the scope note. A detailed security and data-handling page is being finalized — ask for the current process during the fit check.
What if we discover a new requirement halfway through?
We do not allow scope to become an uncapped hourly bill. We finish the agreed proof where possible, then define and price the new requirement separately.
Can you deploy into our environment afterward?
Yes. The proof includes the fixed production recommendation. Deployment, live credentials, scheduling, monitoring, and service levels begin only after you approve the production scope and price.
Does Alice replace our ERP, QMS, maintenance system, project system, or BI tool?
No. Alice handles the recurring work between the systems and outputs your team already uses. Replacement is not required for the proof.
Can you automate a physical production line?
That is a Vorpal engagement rather than a standard Workflow Proof. Describe the equipment and operating problem in the form, and we will tell you whether the hardware path is currently available.
Start with the workflow that makes someone say, “I’m the only person who knows how to do this.”
Put the current process into a few sentences. We will tell you whether it fits before asking you to buy anything.