The work you keep doing by hand, done by software.
Veck is one person. I find the process your team still runs by hand, rebuild it inside the tools you already use, and hand it back running. Hours back, and the same result every week.
- 09:14:02Form receiveddone
- 09:14:02Checked against existing recordsdone
- 09:14:03Record created, owner assigneddone
- 09:14:04Welcome email sentdone
- 09:14:04Posted to the team channeldone
- +48hNudge, only if it stallsqueued
What one finished process looks like from the inside. Nobody is watching this happen.
Every business runs on a pile of work nobody was hired to do.
It never shows up on a job description and it never appears in a budget. It just quietly eats the week.
- 01Copying the same information between two systems that do not talk
- 02Chasing a lead because nobody remembered whose turn it was
- 03Rebuilding the same report every Monday morning
- 04Answering the same six client questions in writing, again
- 05Reconciling a spreadsheet against an invoice line by line
- 06Onboarding a customer through eleven manual steps
- 07Writing the follow-up email that should have sent itself
- 08Finding out a week late that something silently failed
Put a number on it.
These are your numbers. Most people are surprised, and the surprise is the point.
Calculated over 46 working weeks, so leave, public holidays and dead time are already taken off.
R 32 200 every month
If automation removes even 60% of it, that is R 231 840 a year back, and 83 working days returned to work people were actually hired to do.
The Manual Work Audit
Three sliders is a guess. The audit is the measured version, and it is the only thing on this site with a price on it.
- Every repetitive process in your business, mapped and timed
- What each one costs you a year, in rand, from your numbers
- Ranked by what is worth automating, and what is not
- A fixed quote for the top three, so you know the price upfront
One week. If it turns out your back office is already tight, I will tell you, and you will have spent R5 000 to know it.
Credited in full against your first build
Book the auditOne process, fixed scope, live in two weeks. R20 000 to R35 000, quoted as one number off the audit. When that one is running you pick the next.
What it looks like afterwards.
Three processes that used to need a person every week. Each one is a build I shipped and handed over. None of them are a promise about yours.
Manual steps left in a client onboarding that used to be worked through by hand
Roughly the reporting time given back, once the weekly report started building itself
Lifecycle emails and Zoho CRM workflow rules firing on their own, including the one that chases a signup that has stalled for two days
Every number here comes from a system I built and handed over. Ranges and averages from other people's case studies are not on this page.
What you end up with.
The points where someone moves information from one system into another, gone. Integration between the tools you already run, so the copying stops. This is usually where the hours are, and usually the least glamorous part of the job.
- CRM routing, ownership and handoff workflows that actually fire
- Onboarding and approval flows that move themselves along
- Reporting that builds itself and lands where people already look
- Lead capture and follow-up that fire on what someone actually did
- Lifecycle and transactional email, including the deliverability work
- A stalled queue or failed send showing up in Slack while there is still time to fix it
LLM systems scoped to one named job and wired into the tools you already run, for the work where a rule cannot decide the answer.
- Agents that read, decide and write back into your systems
- Document and email processing that ends in a record inside your system
- Internal assistants that work from your actual written procedures
- A human checkpoint wherever the cost of being wrong is real, and a log of what the system decided
Short engagements. Nothing open-ended.
Map the work
Find where the hours actually go. Usually it is not where anyone expects, and usually it is not the thing you were about to buy software for.
Build the smallest thing
The narrowest system that removes the biggest chunk of it, inside your existing stack. No platform migration, no eighteen-month programme.
Hand it over running
Documented, and owned by you. If it needs Veck to keep working, it was built wrong.
Veck is one person, and that is the point.
I am Antony Veck. Veck is the shorter name for work that ran as Veckflow. Same hands, fewer syllables.
I have spent about two years building AI and automation systems, and have run that independently since 2024. The work behind the numbers above is mine end to end: the CRM workflow rules, the lifecycle email infrastructure they sit on, the reporting that stopped needing a person, and on the AI side a document processor that turns a photographed receipt into a structured record, running in production.
It means you talk to whoever is actually building the thing. There is no account manager in the middle, no handover to someone junior once the contract is signed, and no bench of people who have to be kept busy.
It also means capacity is genuinely finite. I run a small number of engagements at a time and turn down the rest, which is why the first conversation is mostly me working out whether this is something Veck should build at all.
- Based
- Cape Town, South Africa. Remote across South Africa by default, onsite for Cape Town clients
- Works with
- Small and mid-sized South African businesses, and the ops or finance lead who owns the problem
- Does not do
- Staff augmentation, retainers for their own sake, or replacing systems that already work
- Engagements
- Scoped and fixed. Nothing open-ended
The questions people ask first.
The audit is R5 000, fixed, and it is credited in full against the first build. Builds are priced one process at a time, most between R20 000 and R35 000, and you get that number as a fixed quote off the audit before anything starts. Deliberately small, because a two-week project that works is worth more to you than a three-month one that might. When the first is running you decide whether there is a second. You are never approving an open meter, and you are never committed past the thing in front of you.
No. The default is to build inside whatever you already run. Replacing a working system is expensive, slow, and usually solves a problem you did not have.
Everything ships with a status report on a schedule, so a silent failure surfaces within days. Where the platform has its own alerting, that gets switched on and pointed at you. You own the system outright and can have anyone maintain it. Support is available if you want it, but it is never a condition of the build. If you do want me keeping it current as suppliers change their formats, new document types appear and volumes shift, that is R2 500 a month per automated process, month to month, stop whenever you like. The system runs without it. That is the difference between keeping something current and needing someone to keep it alive.
Sometimes, when that is genuinely the right answer and the cheapest thing that will hold. Where it will not hold, it gets written properly. The decision is made on what the system has to survive.
AI is used where the input is messy and the judgement is genuinely fuzzy: reading documents, drafting, classifying, summarising. It is not used where a rule would do the job, because a rule is cheaper, faster and cannot invent an answer.
Yes. Most of the work is remote and clients are spread across South Africa, because building inside Zoho, Slack, Google Workspace or Microsoft 365 does not need anyone in the room. Cape Town clients can have me onsite when it helps, usually during the mapping week when watching someone actually do the work is faster than describing it.
Scoped deliberately small so the first working piece lands early. Exact timelines depend on how many systems have to be touched and how quickly your side can grant access, which is usually the real bottleneck.
Tell me what you are still doing by hand.
Four questions, about a minute. If it is not something Veck should build, I will say so.
- you want your whole stack replaced
- you need someone available full time, ongoing
- nobody internal has time to be involved at all
Any of those and I would say so on the call, so it is cheaper to say it here.
That is with me.
It arrived the moment you pressed send, and my phone already knows about it. You will hear from me personally within one working day.
Would rather not wait? Take a slot from my calendar.
Your mail app should have opened.
Something on my side did not answer, so everything you typed is in a draft instead, addressed and ready. Press send and it is with me.
Nothing happened? Mail it straight to antony@veck.online, or book a call instead.