Practical systems for work that is still too manual.

Not sure which one you need?

Pick the line that sounds most like your week.

• The same information gets typed into two or three tools, and somebody has to remember to do it.

  Explore business automation

• Work arrives as messy email, documents or notes, and a person has to read all of it before anything can happen.

  Explore AI integrations

• The site in front of the business does not match the business behind it.

  Explore websites

• None of these quite fits, or the problem is that you cannot tell which one it is.

  Then start with a conversation rather than a service. I can review what you already have, work out where the cost actually sits, design the approach, or lead the build. Consulting is how I enter any of the three above. It is not a fourth thing to buy. I work independently, Part-time / freelance.

• Business AutomationI connect the tools your team already uses and automate the repetitive handoffs between them.
• AI IntegrationsI add AI to workflows for classification, extraction and assistance, then put validation and human review around uncertain or risky actions.
• Websites & Digital SystemsClear positioning, strong design, fast performance, accessible interactions and the forms, analytics and integrations behind the page.

You do not need to arrive with a finished specification. I can work with you and your team to understand the problem, review the current setup, design the approach, or lead the build. That can include automation, AI, websites, integrations and SharePoint-related development.

How a project usually runs

1. A short messageYou tell me what is still manual. I tell you whether automation is likely to help, and what I would look at first.
2. DiscoveryI map the real process with the people who run it, including the parts that only exist in somebody's head. You come out of it with a written scope, the assumptions behind it, and a fixed quote.
3. BuildThe smallest useful version first, tested against messy inputs rather than clean ones. You see it running before it touches anything real.
4. HandoverDocumentation, a walkthrough, and every account in your name. The system should not become a black box the moment I stop touching it.
5. AfterOngoing support can be scoped separately if you want it. If you do not, the system still runs and you still own it.

• How pricing works

What every project includes

A written scope before anything gets built.

The assumptions go in writing too, so we can both see later which ones were wrong.

Accounts in your name.

Scoped credentials, service accounts where they exist, and no shared logins.

Failure handling, not just a happy path.

Retries where retrying is safe, deduplication so the same thing is never processed twice, and an alert when something needs a person.

A human review path

for anything uncertain, expensive, or hard to undo.

Backups, and a way back.

Recovery is designed at the start, not added after the first bad day.

Documentation and a handover walkthrough

written for whoever will run it rather than for me.

Review discipline on anything AI helped write.

I use AI coding tools every day. Nothing they produce reaches a real account without being read line by line, tested against safe fake data, and dry-run first.

No lock-in.

If you want to take it in-house or hand it to somebody else, everything needed to do that is part of the delivery.

What kind of businesses do you work with?

I work with businesses in different industries. I am most useful when a process is repeated, spread across several tools, or important enough that silent failure is not acceptable. The problem and the fit matter more than the industry.

How do I know what to automate first?

Start with the process that creates the most repeated data entry, chasing, missed handoffs or avoidable delay. Map the process before choosing the tool.

How do you handle credentials and access?

Accounts should stay in the client’s ownership. I use scoped credentials or service accounts where possible and keep secrets out of code and workflow nodes.

Who maintains the system?

That depends on the project. I provide documentation and handover so the system is not a black box. Ongoing support can be scoped separately. I have handed systems over to teams on three continents, so this is a normal part of the work rather than an afterthought.

How much does a project cost?

Cost depends on five things: how much scope the system covers, how many workflows it needs, how many systems it has to talk to, how messy the source data is, and whether the work includes a human review path and ongoing support. Most engagements start with a short discovery step. You come out of it with a written scope, the assumptions behind it and a fixed quote, before anyone commits to a build. If you already know roughly what you need, tell me what is manual today and I will tell you quickly whether it is worth automating and roughly what shape the work takes.

Is this even worth automating for us?

Usually, if two or more of these are true: the same information gets copied between tools, someone watches an inbox so nothing is missed, documents arrive through more than one channel, a handoff depends on someone remembering, or nobody finds out quickly when something fails.

How do you work so fast on your own?

I use AI coding tools every day, with the same review discipline I put on any production work. It makes the first version faster. It does not change what gets reviewed before anything touches a real account.

Can we book a call?

There is no booking calendar. Message me on WhatsApp or use the contact form and tell me what is manual today. On WhatsApp: Normally a reply the same business day. On the contact form: I reply within one business day. If a call makes sense after that, we arrange one directly.