MADTech / Automation

Business automation that removes repeat work.

Automating systems and processes is my specialty. Most of it is unglamorous: the same information typed into three places, a hand-off that only happens when someone remembers, a report rebuilt by hand every Monday. Every one of those is a place where hours disappear and mistakes get made. I remove the mechanical part and leave the judgment calls with people.

Request a quote

What this covers

Mapping the manual path

Every step someone repeats by hand, including the judgment calls. What gets automated is the mechanical part; the decisions stay with people.

Connecting the tools

Your CRM, inbox, forms, spreadsheets, billing and whatever else the business already depends on, wired together so data stops being re-typed and stops going out of sync.

Visible state and honest failure

You can see what ran, what did not and why. When something fails it says so loudly rather than silently dropping work on the floor — which is how most automation quietly stops being trusted.

Handed over so you can adjust it

Documented and built to be changed. The point is to remove work from your week, not to make you dependent on me for every tweak.

Questions before you start

Can you connect the tools we already use?

Send the names of the tools and explain what information needs to move between them. We need to check what each system allows through its API or other supported connections before agreeing the scope. Naming the tools up front helps establish what is possible without replacing them.

Which parts of a process should stay with a person?

Repeated data entry and predictable hand-offs are candidates for automation. Approval, judgment and unusual exceptions may still need a person. We map both paths so the automation has a clear place to stop and the people using it can see what needs attention.

What should I send for an automation quote?

Choose one recurring task and describe its start, each manual step, and what finished looks like. List the tools involved, how often it happens, and the mistakes or failures you need to catch. That gives us a concrete workflow to scope before expanding to other parts of the business.

A good fit when

The same information is being typed into more than one place
A recurring task eats hours and nobody enjoys owning it
Small human errors keep costing you money or credibility
Things fall through the cracks between two tools

Probably not when

The process changes so often there is nothing stable to automate
The real problem is the process itself, not the tooling around it
You also need someone to run the campaigns the automation feeds

I would rather say so up front than take work that will not land well.

How I work

Priced per project, never by the hour

Every project is different, so every price is worked out from your actual requirements rather than read off a list. You get a figure in writing before anything starts, and you are buying a finished thing rather than my time.

Custom code, not drag-and-drop

I do not build on page builders or theme editors. If you already run a platform that allows real custom code — GoHighLevel, for instance — I can build inside it. What I will not do is assemble something from blocks and call it bespoke.

Fast is possible, and it is priced as fast

Tight deadlines are often doable — a website in a few weeks is realistic. Compressing a schedule costs more, and how much depends on the size of the build. I will tell you what is achievable before you commit to a date.

Building only, not marketing

I design and build. I do not run ads, SEO or marketing campaigns, and I would rather say so than take money for something outside what I do well.

How it works

01
Send the messy version
A paragraph is enough. What it is, who it is for, and what is broken or missing today. I read it myself and reply — including an honest no if I am not the right fit.
02
Scope and a price range in writing
Before anything is built you get what is in scope, what is not, a range rather than a fantasy number, and a timeline. Nothing starts without that agreed.
03
Built in the open
You see it as it comes together, not at the end. Feedback lands while changing course is still cheap, which is the whole point of working this way.
04
Handed over properly
You get the code, the accounts in your name, and a walkthrough of how to run it. No hostage situations, no rented access to your own product.

Bring the messy version.

Tell me what you are trying to build and you get a straight answer on scope, cost and timeline — or an honest no.