Skip to content

What I build

Three things done properly.

Rather than ten things done adequately. Here is what I actually build, the tools I build it with, and how a project tends to run.

[01]

Automation builds

Stop paying people to copy and paste

Orders, leads, invoices and reports move between your apps on their own. The work still gets done — your team just stops doing it by hand.

What you get

  • Manual data entry between apps removed
  • Follow-ups that fire without anyone remembering
  • Reports that build themselves overnight
n8nMakeZapierGoogle WorkspaceAirtable

[02]

CRM setup & migration

A pipeline your team actually uses

Most CRMs fail because they were set up for the software, not the sales process. I map how your team really sells, then build the CRM around that.

What you get

  • Every lead captured, none sitting in someone's inbox
  • One clear pipeline instead of five spreadsheets
  • Clean migration from your current setup, nothing lost
HubSpotZohoPipedriveGoHighLevelAirtable

[03]

AI for business

AI that does real work, not demos

Not a chatbot bolted onto your homepage. AI placed at the specific points in your operation where it saves hours — quoting, sorting, drafting, summarizing.

What you get

  • Inbound enquiries read, sorted and routed automatically
  • First-draft quotes and replies in seconds
  • Documents and calls turned into structured records
ClaudeOpenAICustom workflows

How it works

Four steps, no open ends

You know the shape of the whole thing before you commit to any of it.

  1. 01

    Discovery

    You walk me through how work actually moves through your business. I tell you what I would automate first and what I would leave alone.

  2. 02

    Blueprint

    Before you spend anything, you get the plan in plain English: what gets built, what it costs, how long it takes, what changes for your team.

  3. 03

    Build

    You see working pieces every week instead of waiting months for one big reveal. If something is not right, we catch it early and cheap.

  4. 04

    Handover

    Built in your accounts, documented for your team, with a support window after launch. It keeps running whether or not I do.

Questions

Straight answers

What does a project usually look like?

Untangle the process first, agree what gets built, then build it in weekly pieces so you can see it working rather than waiting for one reveal at the end.

Do I have to switch the tools we already use?

Usually not. The first move is almost always connecting what you already pay for. Replacing a tool only comes up when it is genuinely the thing holding you back, and that is your call to make, not mine.

Our process is messy. Is that a problem?

No — that is the normal starting point. Part of the work is untangling how things actually flow today. Automating a messy process just makes the mess run faster, so the shape of it gets fixed first.

What happens after handover?

Everything is built in your own accounts and documented for your team rather than for a developer. If we stop working together, nothing switches off and nothing is held hostage.

What kind of businesses do you work with?

[PLACEHOLDER: describe the businesses you actually know best — size, sector, and the kinds of operational problems you have solved most often.]

Get in touch

Got something manual you want gone?

johndale.freelancer@gmail.com

Philippines — working with clients worldwide · PHT (UTC+8)