Helvetic Vault
Book a call
Our method

An agent that asserts is not evidence. An agent that shows its work is.

The prepared / observed / verified grid is our internal standard. It separates what the system intended to do, what it did, and what a human checked. That is what makes an automation defensible.

  • Prepared

    What the agent proposes

    Before acting, the agent writes down what it intends to do. You can read it, refuse it, or change it.

  • Observed

    What actually happened

    Every executed action is logged with its timestamp and outcome, failures included. Nothing is erased.

  • Verified

    What a human signed

    Nothing reaches you until a human has checked it. If I can't verify it, I don't ship it.

Real log extract

Three examples, from the same farm

This is the only thing I sell: you see what the agent proposed, what it actually did, and who signed off on it.

Thursday 06.08 · today's boxes 38 boxes
Prepared · 07:12

38 boxes composed from today's harvest, 2 substitutions proposed (fennel → chard).

Observed · 07:14

38 delivery notes printed, 4 client emails sent, 1 delivery failure reported.

Verified · 08:03

Checked and signed — substitution rejected for 1 client with an allergy, corrected by hand.

Estimated saving: 4 h 20 per week
Friday 31.07 · month-end close 52 invoices
Prepared · 06:40

52 invoices drafted from the delivery notes, 3 quantity discrepancies flagged.

Observed · 06:44

49 invoices sent, 3 held back, 1 invalid email address.

Verified · 09:15

Checked and signed — 2 discrepancies confirmed by the client, 1 corrected before sending.

Estimated saving: 6 h per month
Monday 04.08 · overdue payments 7 cases
Prepared · 08:05

7 reminders drafted, tone matched to how long the payment has been overdue. None sent.

Observed · 08:31

5 reminders sent after your approval, 2 set aside at your request.

Verified · 08:34

Checked and signed — 1 client in dispute removed from the list before sending.

Estimated saving: 2 h per month

How it runs, from the first call to going live

  1. Assessment
    45 min · free

    We look at your typical week and list what repeats. You leave with a written map, whether or not we work together.

  2. Scoping
    1 week

    One process is chosen: the best ratio of time saved to risk. Scope, agent boundaries and success indicators are written down before a line of code exists.

  3. Build
    2 to 4 weeks

    The automation is built and runs alongside your current process. You receive the logs from day one, errors included.

  4. Switch-over
    when the numbers agree

    We only switch when the agent's results and the human's results agree over an agreed period. Otherwise we fix it, or we drop it.

  5. Operation
    monthly mandate, optional

    Monitoring, adjustments and a monthly report. Cancellable on 30 days notice, no penalty, with full handover of code and documentation.

The engine

The method is not a sales argument. It is code you can read.

The four guarantees behind my method are not commercial promises: they are written into an execution engine whose code is public. You can download it, read it, and have your own IT people audit it.

The engine

Four guarantees, written into the contract

  • A human signs

    No deliverable goes out until a named person has read and approved it. That person is me.

  • Complete logs

    Failures are logged alongside successes. A log containing only successes is a doctored log.

  • Immediate stop

    You can shut the agent down in one action, without going through me, at any time.

  • Reversibility

    Code, configuration and documentation belong to you. You can walk away with them, or roll back.

Who does what

What stays on your side.

An honest automation also states what it does not cover. These four things stay with you, deliberately.

  • Your backups

    I work on your systems, I do not replace them. Your backups remain your safety net, and I check they exist before starting.

  • Access

    Credentials and permissions stay yours. You give me what is needed, and you take it back whenever you decide.

  • The decision to switch over

    I show you the numbers from the parallel run. Switching over — or dropping it — is your call.

  • A named approver

    One person on your side follows the work and can say no. Without them an automation project drifts, however good the engineering.

The assessment is free and commits you to nothing.

Forty-five minutes, a written map of what can be automated in your business, and a number. What you do with it is up to you.

Book a call Take the questionnaire