Practical AI tools for everyday business work.

Copying details, sorting requests and checking the same things by hand eats into every week. I build small, practical tools that take over that routine. Your team keeps the decisions and gets the time back.

Independent developer in Stockholm. More than ten years in ad tech and media. A few selected projects at a time.

Scroll to see the pieces fall into place.

Busywork costs more than time.

Most teams have a few tasks that follow the same steps every time. Copy the details from an email. Paste them into a sheet. Check them. Send a reply. Each step is small. Together they take hours.

Hours disappear

Small manual steps add up to hours every week. Nobody plans for them, and nobody gets them back.

Focus suffers

Skilled people spend their energy on copying and checking instead of the work they are good at.

Errors creep in

Repetitive work is where typos and missed details happen. Not because people are careless, but because the work is dull.

Routine belongs to software. Judgement belongs to people.

Services

Three kinds of work. Each one starts small, with a scope we agree on before I begin.

Small internal tools

A focused tool for one job your team does by hand. For example, a page that turns rough notes into a structured summary. Or a helper that drafts standard replies for someone to review.

The aim: one task done in a few clicks instead of by hand.

Typical scope

  • One clear task
  • Used by a few people
  • A simple interface with clear limits

Repetitive workflow automation

Automation for steps that happen in the same order every time. Moving details from emails or forms into a spreadsheet. Collecting numbers from several systems into one weekly report. Preparing a draft for a person to approve.

The aim: the routine runs on its own, and a person checks what matters.

Typical scope

  • One workflow at a time
  • A person reviews what matters
  • Clear handling when something does not fit

Practical prototypes

A working first version of an idea. You test it on real tasks before you invest more. Then you decide what happens next.

The aim: a clear answer on whether the idea deserves more investment.

Typical scope

  • Built to learn, not to scale
  • Sample or limited data
  • Ends with a short review

What I do not take on

Large system replacements, change programmes across a whole company and work that needs a full team. I keep projects small on purpose.

I started by building tools for myself.

I know what it is like to lose hours to the same small steps.

I am Mike Herbst. I have worked in ad tech, advertising and media for more than ten years, in Stockholm and Los Angeles. Every day I work with digital campaigns, measurement and reporting, together with media agencies and advertisers. I know where the manual work piles up.

Next to that, I build tools. The first was Vargna, a training app for hybrid fitness racing. After that came small tools that make my own daily tasks faster.

Now I help others do the same. I start with one concrete task. I build something that works. Then I improve it based on real use.

I run this independently and take on a small number of projects at a time. I explain what I build in plain language. If a tool is not the right answer, I say so.

Mike Herbst
Background
Ad tech, advertising and media, more than ten years
Based in
Stockholm, Sweden
Personal project
vargna.com
Profile
LinkedIn

Work you can look at

A personal project that is live, and a demonstration I built for this page. Both are here so you can judge the work yourself.

Personal project

Vargna, a training app for hybrid fitness racing

I built Vargna as a personal project. It is live at vargna.com and on the App Store for iPhone.

You can build your own timed workout from race stations, running and accessory movements. Or you can pick one of 100 ready made classes in five categories. A guided work and rest timer then runs the session, with audio cues at every change.

It is free to use. It is an independent product and is not affiliated with any race organiser.

Demonstration with fictional data

From a full inbox to replies ready to send

A small workflow I built for this page. A fictional webshop gets customer emails all day. The workflow reads each message, works out what the customer wants and finds the order. Then it drafts a reply for a person to approve, or sends the case to a person when it needs judgement.

All names, orders and messages are invented. The demonstration runs in your browser with fixed example data. It does not call an AI model and it does not send anything. In a real project, an AI model could handle the reading and the drafting.

Inbox for Ekbacka Living (fictional)

Demo day: Monday

Incoming messages

    Workflow

    1. Read Open the next message.
    2. Extract Find the customer, the order and what they want.
    3. Check Compare with the rules and the order details.
    4. Prepare Draft a reply, or send the case to a person.
    Rules in this example
    • Each message gets a request type: order status, return, change, product question or problem.
    • Order status, returns, changes and product questions get a drafted reply for a person to approve.
    • Damaged goods and anything about payments go straight to a person.

    Case list

    Cases prepared by the demonstration workflow
    CustomerRequestPreparedStatus

    Press Run the workflow to process six example messages.

    How a project works

    Four steps. Each one ends with something you can look at and decide on.

    1. Understand the problem

      We talk through one task. How it works today, where the time goes and what a good result looks like.

    2. Agree on a small scope

      I describe what I will build and what I will leave out. We agree on it before I start.

    3. Build a prototype

      I build a working first version. You try it on real examples from your work.

    4. Review the result

      We look at what works and what does not. Then you decide to keep it, improve it or stop there.

    Timelines and pricing

    A fixed price for each step. You know the cost before I start.

    First conversation
    Free, 30 minutes
    We find out if the task is a good fit.
    Proposal
    4,000 SEK
    A written description of what I will build, what is included and what is not, with price and timeline. The amount is deducted if you go ahead.
    Prototype
    From 30,000 SEK
    A fixed price agreed in the proposal. Usually 3 to 6 weeks in calendar time.
    After the prototype
    1,200 SEK per hour
    Improvements or support when you need it. Or a fixed monthly fee from 3,000 SEK.

    All prices exclude VAT. Curious what a tool could be worth to you? Try the calculator.

    Step one is a short conversation about your task.

    Discuss a project

    Is your task a good fit?

    Answer five quick questions about one task. You get an honest first read. Nothing is sent or stored.

    Does the task happen at least once a week?
    Does it follow roughly the same steps each time?
    Is the information digital, such as emails, forms or spreadsheets?
    Could a person easily check the result?
    Could we start small, with one part of the task?

    Your answers stay in your browser.

    What changes

    The goal of every project is simple. Less routine for people, and a tool you understand.

    Without a tool

    • Hours go to copying and checking.
    • Details get missed on busy days.
    • The routine grows as the business grows.

    With a small tool

    • The routine runs in the background.
    • A person reviews only what matters.
    • Your team spends its time on work that needs them.

    Put a number on your task

    Pick one task your team does by hand and use your own numbers. The calculation runs in your browser and nothing is sent.

    For example answering order emails.

    How often does it happen?

    Salary plus employer fees, roughly.

    A person usually stays to check the result, so 100 percent is rare.

    Your estimate

    Time spent today
    Time back
    Worth

    Discuss a project

    Tell me about one task that takes too much time. A few sentences is enough. I will reply by email.

    Useful details

    • What the task is and who does it
    • How often it happens
    • Which tools are involved today

    Prefer email? Write to mike@herbstai.com.

    What happens today, step by step, and what you would like to change.

    How often does it happen? Optional

    Read how your details are handled in the privacy notice.