AMDG Consulting
Approach

Slow to start. Fast once we understand.

Most automation projects fail because someone bought the tool before they understood the work. We invert that. We do not build anything until the process is clear to both of us and the trade-offs are written down.

“Plans are worthless, but planning is everything.”
Dwight D. Eisenhower
The five steps

Every engagement follows this arc. No exceptions.

  1. I
    Watch
    We spend time in the room with your operators. We take notes on what's actually happening — not what the org chart says is happening. Nothing gets built in this phase.
  2. II
    Frame
    We write a short document — two to five pages — describing the process today, the version we'd build, and the honest trade-offs. You read it, push back, and approve it before any code gets written.
  3. III
    Build
    Small releases. Real code in your repository. An operator can watch every run and kill it at any time. No black boxes, no vendor lock-in, no long silent work.
  4. IV
    Hand off
    The people who will operate the system learn it while it's being built. By the time we're done, they know where every piece lives and what to do when it breaks.
  5. V
    Stay useful
    We remain available — typically on a light monthly retainer — to tune, upgrade, and answer questions. When you no longer need us, we leave.
House rules

What we will and won't do.

I

We recommend against automation more often than we recommend it.

II

Every system has a shutoff switch. Operators use it.

III

We write code in your repository, not ours.

IV

We don't charge for discovery calls.

V

We don't use the word 'platform.'

If this sounds like the way you'd want someone to work, say so.

Start a conversation