stampp.consulting

for freelancers

An AI workflow for the admin you keep postponing

As a freelancer you run the company as well as doing the work. We set up an AI workflow in the bookkeeping, mail and calendar you already use. It prepares the admin, and you approve what goes out.

you
bot team
bookkeepingmailcalendar
fig. 01 · you talk to one bot team; it works in your own systems
§ 01 / 09examples

What the workflow takes on

The workflow is built around your work. These four examples come from our own freelance practice.

N° 01

Appointments in the calendar

You name the job and the date. The workflow puts the appointment in your calendar, checks that it does not clash with another job and sends the customer a confirmation.

calendarconfirmationno double bookings
N° 02

Invoices from your hours

At the end of the day you give your finish time. The workflow adds up the hours and kilometres, drafts the invoice in the same format as the previous one and sends you a link to the draft.

hourskilometresdraft
N° 03

Sent after your approval

When you approve the draft, the invoice is sent from your own bookkeeping system, not from an outside server.

your bookkeepingyour approval
N° 04

Bookings prepared

Receipts and journal entries are booked once you have marked them as business or private. New customers are created from their public company details, and differences with earlier records are flagged.

receiptsjournal entriescustomer records
§ 02 / 09how it works

One invoice, from appointment to booking

The workflow prepares every step. Anything that cannot be undone, such as sending, paying or filing, waits for your approval.

  1. 01Appointmentin the calendar, confirmation sent
  2. 02Workdayyou give your finish time
  3. 03Hours and kilometresadded up and checked
  4. 04Draft invoicesame format as the last one
  5. 05Your approval“approved, send”
  6. 06Sent and bookedfrom your own bookkeeping
fig. 02 · the bots prepare the work; you approve before anything leaves
§ 03 / 09the setup

From intake to handover

  1. Intake

    We look at where your admin stalls and which systems you use.

  2. Rules

    We agree what the bots may do on their own and what waits for your approval.

  3. Setup

    We build the bot team and connect each bot to the one system it needs.

  4. Handover

    You receive the instructions in plain language, so you can adjust the workflow yourself.

§ 04 / 09price

A one-time setup, then the workflow is yours

The setup costs between €500 and €1,500, depending on how many systems, bots and rules your workflow needs.

one-time setup

€500

The connections and the bots

Your bookkeeping, mailbox and calendar connected to Grok bots or a Claude integration, so quotes and invoices are ready quickly.

€1,500

The full workflow

More systems, more specialised bots and more rules, covering the calendar, the kilometres, the receipts and the bookkeeping.

  • You pay once for the setup. There is no monthly fee to us.
  • Your subscriptions stay in your name and you pay them directly. This includes the AI model the bots run on, your bookkeeping system and your mailbox.
  • Placeholder whether the prices include or exclude VAT.
  • Placeholder how long the intake takes, and when the workflow is running.
§ 05 / 09

Grok bots, or another model

We usually build the team on Grok bots, because each bot can be given one narrow task with its own instructions and its own connection. That leaves little room for guessing, and when information is missing, the bot asks for it.

If you prefer Claude, or your work runs on other systems, we build on those instead. The one requirement is that we can connect to your systems. Most of them offer an API or another way in.

§ 06 / 09

Tested in our own practice

The workflow runs in our own freelance practice, on Moneybird, Outlook and Grok bots. Some of what it has handled so far:

  • It matched the inbox against the books and booked nothing until each item was marked as business or private.
  • It counted the kilometres per job, and estimated them from the route where they were missing.
  • It blocked days in the calendar so that jobs did not clash.
  • It drafted follow-ups and a refund claim in Outlook, which the owner then sent.
  • It flagged an open VAT quarter. Filing the return stayed with the owner.
§ 07 / 09

What stays with you

Sending, paying and the tax return stay with you. The workflow does not mix household costs into the company books, does not make up an amount or a VAT rate, and does not answer customers on its own. The quarterly VAT return is still filed by you, in Mijn Belastingdienst.

§ 08 / 09

After the handover

The workflow depends on services that neither of us controls: the AI model, your bookkeeping system and your mailbox. When one of them changes, a connection can break, and that part of the workflow stops until it is fixed.

The setup is a one-time job. We do not offer hosting, maintenance or an uptime guarantee, and our access ends at the handover. If something breaks, we fix it on request, at a price agreed in advance that is always below the setup price. Scope, access and liability are set out in a one-page agreement that we both sign before the setup starts.

§ 09 / 09

What you need

  • Your bookkeeping system, mailbox and calendar, with a way to connect to them. Most systems have one.
  • An account for the AI model the bots run on. Placeholder which Grok subscription a Grok bot team needs.

contact

Where does the work get stuck?

Describe where work stalls between teams, suppliers, partners or customers. In the first conversation we talk about the process, before any software.