stampp.consulting

tools AI assistants and agents

AI-assisted workflows

We use AI for three kinds of work: admin for freelancers, building and maintaining websites, and testing an idea with a working prototype before it gets a budget.

Palm silhouettes
a task
assistant
bookkeepingwebsite codeprototype
fig. 01 · one assistant per job, inside the systems where the work happens
§ 01 / 06three uses

Where we put AI to work

N° 01

Admin for freelancers

A team of specialised Grok bots prepares appointments, quotes, invoices and bookings in your own systems. You approve before anything is sent.

grokmoneybirdcalendaremail
N° 02

Website development

This website is built, maintained and published in one AI-assisted workflow with Claude Code.

claude codeplain-text contentdeployment
N° 03

Test before you pay

We build a working prototype with Grok Build first. If it proves its worth, it is built properly. If not, it has cost hours rather than a budget.

grok buildprototypesdecisions
§ 02 / 06how we set it up

Five agreements before an assistant starts

  1. One task first

    A task that repeats, is clearly defined and is worth the time it saves.

  2. One connection per bot

    Each bot gets access to the system it needs and nothing else.

  3. Agreed checks

    What the assistant may do on its own, and what a person approves first.

  4. Data agreements

    Which information may go in, and which model and provider process it.

  5. Handover

    The instructions in plain language, so you can adjust them yourself.

§ 03 / 06when it fits

Where an assistant helps, and where it does not

it fits when

  • The same tasks, emails or documents come back every week.
  • The knowledge exists, but it is spread across systems, inboxes and people.
  • An idea needs testing before it is worth a budget.

it does not fit when

  • A decision must be right every time without anyone checking it.
  • Sensitive data may not leave your own systems under the provider's terms.
  • The process itself is not clear yet. An assistant only speeds up what is already there.

An AI assistant is useful when it takes over real, repeated work and is connected to the systems where that work happens. We build each setup around a process, not around a chat window.

§ 04 / 06

Admin for freelancers

For freelancers we set up a team of Grok bots, each connected to one system such as Moneybird, the mailbox or the calendar. How it works, what it costs and what stays with you is described on the page for freelancers →

§ 05 / 06

Website development

This website is the example. It is built, maintained and published with Claude Code, Anthropic’s coding assistant, which works inside the project itself. It reads the files, makes the changes, runs the checks and explains what it changed.

  • All text is kept in plain files per language, and every build checks that nothing is missing.
  • The house style is kept in one place, so the look can change without rebuilding the pages.
  • Publishing, the domain and the files for search engines are part of the same workflow.

A person decides what goes on the site and reviews every change.

§ 06 / 06

Test before you pay

Before we invest in an app or a workflow, or pay someone to build it, we build a working test version with Grok Build, xAI’s coding agent for the command line. It plans the work, searches the code and builds, with several agents working on one task at the same time.

← All tools

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.