Skip to content

Kelvin van Wyk / AI automation consulting

Less busywork.
More business.

Turn the tasks you repeat into workflows that work for you.

I help small teams explore, build and test practical AI workflows. Less copying, sorting and starting from scratch. More room for the work that needs you.

One real task. A clear scope. A human in control.

Kella / Workflow architecture01—04

Tasks in. Useful work out. You stay in control.

An illustrative three-dimensional workflow: incoming tasks pass through an AI-assisted system and become organised work for a person to review.

Built around your business

Understand the taskTest a useful workflowHand it over clearly

01 / Start with the friction

You don’t need more tools.
You need less to do twice.

The best place to start is usually a small, repetitive task. We look at what slows your team down, then decide whether AI, a simple automation or a better process is the right fix.

01

Less retyping.

Turn the notes, forms and documents you already have into structured information your team can check.

From scattered details to a clear draft
02

A clearer next step.

Sort incoming requests, find the useful details and prepare the next action, instead of starting over.

From a busy inbox to an organised handoff
03

More control.

Know what the workflow can do, what it cannot do and where a person needs to approve or take over.

From a black box to something you understand

02 / Make it tangible

See the work.
Then see the difference.

Choose a task. Follow it from the first input to a useful next step. No technical knowledge needed.

Illustrative workflow · Customer enquiries

Less sorting. A clearer next step.

Example, not a live system

Step 1 of 4/Receive

The step

A message arrives

Start with a channel your team already uses. The connected channel and permissions are agreed first.

Example only

“Can you quote for our event next month?”

Prepared for the next step

Without a workflow

An enquiry arrives. Someone reads it, copies the details, finds the right person and starts a reply from scratch.

With a considered workflow

The enquiry is organised, the useful details are pulled out and a first reply is prepared for your team to check.

These are possible applications, not past client results. Nothing here is connected to your tools or sends messages. Suitability, access and human review are agreed before a prototype is built.

Read every step without the animation

Customer enquiries

  1. A message arrives. Start with a channel your team already uses. The connected channel and permissions are agreed first.
  2. Find what matters. Identify the request, highlight missing details and route it to the right person.
  3. Prepare the next step. Draft a helpful reply using your approved information. No invented prices, promises or availability.
  4. Your team decides. A person reviews and sends. Unclear or sensitive requests are handed over, not guessed.

Repeated admin

  1. Bring the details in. Use the specific forms, notes or documents included in the agreed scope.
  2. Organise the information. Extract the fields your team needs, keeping a link back to the source.
  3. Flag the gaps. Prepare a structured record and highlight anything missing or uncertain.
  4. Approve the update. Your team checks the draft before it is written to the agreed destination.

Team knowledge

  1. Ask a real question. Start with the questions your team repeats most often.
  2. Search approved sources. Only use the documents the person is allowed to access. Keep permissions in the design.
  3. Show the source. Prepare an answer with references so the team can check where it came from.
  4. Check before acting. If the source is missing, outdated or unclear, flag it and ask a person.

Content workflows

  1. Start with your material. Use an approved brief or source, together with examples of your tone and format.
  2. Shape the essentials. Pull out the key points and match them to the intended reader.
  3. Build a first draft. Prepare a draft in the agreed format. Treat claims and factual details as things to verify.
  4. Keep human direction. Your team checks the facts, adds judgement and decides what gets published.

03 / A practical way forward

Start small.
Prove it useful.

No big transformation pitch. We agree one task, decide what success should look like and test the idea before making it part of your day.

  1. 01

    Understand

    Map the real task.

    Walk through how it works today, where time goes, what information it touches and who makes the decisions.

    What we define

    The problem, the boundaries and a sensible first scope.

  2. 02

    Build & test

    Make it tangible.

    If there is a good fit, build a scoped prototype. Test it on agreed examples, including the awkward ones, and compare it with the current process.

    What we check

    Useful output, errors, review effort and whether it actually helps.

  3. 03

    Hand over

    Keep it understandable.

    Walk through how to use it, where it needs a person and what to do when something goes wrong. Further rollout or support is scoped separately.

    What you leave with

    The agreed prototype, clear notes and a practical next step.

04 / Built with judgement

AI does the repeat.
People keep the say.

A useful workflow needs boundaries, not just a clever demo.

Your data, by agreement.

We discuss what data is needed, where it goes and who may access it before connecting anything.

Approval where it matters.

Decide which outputs need review. Messages, sensitive decisions and uncertain answers should not be left to guesswork.

A fallback, not a dead end.

Define when the workflow should stop, flag a problem and hand the task back to a person.

Evidence before promises.

No guaranteed savings or invented results. The prototype is there to find out whether the idea works for your task.

Meet the person behind the workflow

Hi, I’m Kelvin.

Filmmaker. Creative technologist.
Someone who likes making complicated things clear.

I work across filmmaking, AI-assisted creative work and web experiences. My approach to business workflows is the same: understand the brief, build with purpose and keep a person’s judgement at the centre.

Based in South Africa · Working worldwide

Explore my creative work

The portfolio shows creative production work. The workflows above are illustrative, not AI automation case studies.

Good questions

Before we start.

Only what the agreed task needs, and that's discussed before anything is built. Confidential data is handled by agreement, not assumption.

No. The prototype is there to test whether the workflow helps on your real examples.

It depends on the task and scope. You'll get a clear proposal after the first conversation.

Not published yet. The examples on this page are possible applications, not past results.

Let’s find a useful starting point

What do you wish
you didn’t have
to do twice?

Tell me the task, how often it happens and what you use today. A few lines is enough to start a practical conversation.

WhatsApp Kelvin

Scope, availability, pricing and any software costs are discussed before work starts. Opening WhatsApp prepares a message for you to send.

Open WhatsApp with my brief

WhatsApp opens your own app to review and send. Email opens a short form that sends your enquiry through this site.

Email