AI SYSTEMS ARCHITECT

The work that repeats should not need a person

Copy-pasting between tools. Chasing follow-ups by hand. Rebuilding the same report every Monday. I build the systems that do that work instead, so your team gets its week back.

THE ORDER

  • Audit the workflow before touching a tool.
  • Build it, then document it so your team owns it.
  • Wire it into the site so a lead never waits on a person.

Audit first

nothing is built before the workflow is understood

THE ORDER

Audit first

nothing is built before the workflow is understood

THE APPROACH

Most automation fails because the tool arrived before anyone mapped the work.

I do it in the other order — audit, map, design, then build. A slower start and a much faster finish, because nothing gets built twice.

  1. 01

    Call

    You describe the workflow that eats the most hours. I tell you whether it is worth automating.

  2. 02

    Audit

    I walk the process end to end — every handoff, every approval, every point it waits on one person.

  3. 03

    Design

    You get the system on paper and a straight answer on what to build and what to leave alone.

  4. 04

    Build

    It gets built and tested against the cases that actually break, not the happy path.

  5. 05

    Handover

    Documented so your team runs it without me. A system only I can operate is a dependency.

Where I usually come in

01

Find where the hours go

Before anything gets built I go through the workflow step by step: every handoff, every approval, every place a person is quietly holding the process together. You get a written system design and a straight answer on what is worth automating and what is not.

  • Workflow audit
  • Bottleneck mapping
  • System blueprint
  • What to buy, what to skip

02

Build it and hand it over

Then it gets built, tested against the cases that actually break, and handed over with documentation your team can follow without me. A system only I can operate is a dependency, not a solution.

  • A working system, tested
  • AI agents where they earn their place
  • n8n, Make, API and webhook builds
  • Documentation and handover

03

Catch the lead before it goes cold

Most leads are lost in the gap between the form and the follow-up. I build the site and wire it straight into the system behind it, so an enquiry is captured, qualified and routed before anyone opens their inbox.

  • Design and build
  • Loads fast on a phone
  • CRM/CMS wiring
  • Automated lead capture

01 — THE SITUATION

Hours disappearing into work nobody chose to do

The same information was being re-entered in more than one place. Follow-ups only went out when someone remembered. The weekly numbers were rebuilt by hand, from scratch, every week. It was eating the hours that were supposed to go into growth.

02 — WHAT I BUILT

A system, designed before it was built

I mapped the workflow end to end before touching a tool: every step, every handoff, every point where the process was waiting on one specific person. The design was agreed on paper before anything was configured. Then I built it, tested it against the cases that actually break, and wrote the documentation the team now runs it from.

03 — WHAT CHANGED

Then the backlog started moving

Work that had sat in the "when we get to it" pile for months started getting done, because the hours it needed were no longer going into maintenance. Inside the first two months the scope widened past what was originally agreed, and the engagement was retained and expanded rather than closed out.

PORTFOLIO

Systems I can walk you through

MY OWN BUILD01

Follow-up that happens without anyone

A quote request lands and the system does the next four things itself: tags the enquiry so it is segmented from the moment it arrives, sends the welcome email while the person is still on the page, and opens the opportunity in the pipeline so it is already sitting in someone’s view. Nothing waits for a person to notice a form came in — which is where most leads actually go cold.

  • GoHighLevel
  • Workflows
  • CRM
MY OWN BUILD02

Nobody forgets the appointment

A slot gets booked and the confirmation goes out before the customer closes the tab. Then the workflow waits — a reminder the day before, another an hour out. Nobody keeps a list of who needs chasing, and nobody drives out to a house where the customer forgot. A no-show costs a service business the trip and the slot.

  • GoHighLevel
  • Calendar
  • Email
MY OWN BUILD03

One video becomes every post

A video lands in a Drive folder and the system takes it from there: transcribes it, turns the transcript into a written post, then loops through every channel and publishes it. Nobody watches a folder, writes the copy, then pastes it four times.

  • Zapier
  • Google Drive
  • AI by Zapier
  • Discord
  • Facebook
  • Instagram
  • TikTok
MY OWN BUILD04

From a done task to a filed CSV

Someone ticks off an accounting task in Asana and the rest happens on its own: the matching records come out of Xero, get written into a sheet row by row, turned into a CSV and attached back to the task. The sheet is scratch paper — wiped at the end, ready for the next run.

  • Make.com
  • Asana
  • Xero
  • Google Sheets
MY OWN BUILD05

A won deal announces itself

Every five minutes the system asks HubSpot what closed since the last pass, skips anything already announced, pulls the deal and its line items and writes the alert itself. It lands in Slack and the manager’s inbox at once, and the deal is logged so it never fires twice.

  • n8n
  • HubSpot
  • Slack
  • Gmail
  • Google Sheets
MY OWN BUILD06

Every rep gets their numbers at seven

On weekdays at 07:00 the system reads the sales facts and each rep’s targets from a sheet, builds one report per rep — what they sold against target — and emails it before the day starts. If there is nothing to send it tells the owner, so silence is never read as nothing happened.

  • n8n
  • Google Sheets
  • Gmail
MY OWN BUILD07

The week’s invoices, recapped and attached

Every Friday the system pulls the week’s paid invoices from Stripe, reads the targets sheet and sends each rep a recap of what they invoiced against target. The same run turns the invoices into a CSV and emails it to the manager — the file finance asks for on Monday, sent on Friday.

  • n8n
  • Stripe
  • Google Sheets
  • Gmail
MY OWN BUILD08

One table of truth, rebuilt every night

Every night the system walks HubSpot for every won deal with its line items and company, pulls the paid invoices from Stripe and rebuilds one facts table in a sheet from scratch, so yesterday’s mistakes never survive. A webhook on the same workflow serves the KPIs as JSON.

  • n8n
  • HubSpot
  • Stripe
  • Google Sheets
  • Webhook
MY OWN BUILD09

A whole sales sandbox from one click

One click builds the sandbox the four n8n builds alongside it run on: a custom deal property, demo companies, deals and line items in HubSpot; customers and paid invoices in Stripe; a targets tab in the sheet. Every workflow can be run, broken and rerun on data nobody will miss.

  • n8n
  • HubSpot
  • Stripe
  • Google Sheets
MY OWN BUILD10

The site you’re on, built by an AI dev team

I set up Claude Code as a full dev team — design, build, tests, review — directed it, and shipped this site: the scroll-driven hero, the motion, a layout that holds on every screen. The contact form below is the live build: send an enquiry and it is delivered to me directly. Try it.

  • Claude Code
  • GSAP
  • Vercel

2 mo

FROM START TO EXPANDED SCOPE

100%

OF WHAT I BUILD IS DOCUMENTED AND HANDED OVER

2×

AWARDED FOR UI AND MOBILE DESIGN AT UNIVERSITY

Symon Dural

Where this comes from

I came to automation from web development, which is why I start with the system and not the tool. Before anything gets built I want to know what the workflow actually does, where it stalls, and which parts of it never needed a person in the first place.

So I work in order: audit, map, design, then build. I document what I ship and I hand it over properly, and I do it alongside the people who have to live with it rather than around them. A system nobody else can operate is not finished.

I learned this the long way. I taught myself first, out of documentation and other people’s broken workflows, then took the courses to find out what I’d been getting wrong. I work from the Philippines, mostly with teams several time zones away — which is its own argument for building things that keep running when nobody is watching them.

Disciplined about the process. Flexible about the answer.

QUESTIONS

What people ask before they message me

What does Symon Dural do?

I design and build AI automation systems for businesses. I audit the workflow first, design the system on paper, then build it, test it against the cases that actually break, and hand it over documented so your team runs it without me. I also build the website and wire it into the system behind it, so an enquiry is captured, qualified and routed without waiting on a person.

Which tools do you build with?

n8n, Make, Zapier and GoHighLevel for the automation itself, connected to whatever the business already runs. The builds in the portfolio connect HubSpot, Stripe, Xero, Asana, Slack, Gmail, Google Sheets, Google Drive and Discord, and post to Facebook, Instagram and TikTok. AI agents go in where they earn their place, and API and webhook builds cover whatever has no ready-made connector.

What kind of work is worth automating?

The work that repeats: copy-pasting between tools, follow-ups that only go out when someone remembers, the report rebuilt by hand every week, the lead that goes cold between the form and the reply. On the first call you describe the workflow that eats the most hours, and I tell you whether it is worth automating. If the answer is no, I say so.

How does a project run?

In five steps: call, audit, design, build, handover. I walk the process end to end before touching a tool, and you get the system on paper with a straight answer on what to build and what to leave alone. Then it gets built, tested and documented. It is a slower start and a much faster finish, because nothing gets built twice.

How much does an automation project cost?

It depends on the workflow, so I do not quote before I have seen it. Bring me the one workflow that eats the most hours and I will tell you whether it can be automated and roughly what it would cost. The first call is 30 minutes, with no pitch.

Will my team be able to run the system without you?

Yes, and that is the point of the handover. Everything I build is documented so your team can follow it without me. A system only I can operate is a dependency, not a solution. Your data stays in your own tools and accounts.

Can I see the systems you built for clients?

The systems built under NDA stay off this page. What you see in the portfolio are my own builds: the same approach, real working systems, built on accounts I own. I can walk you through any of them line by line on a call.

Where are you based, and do you work with teams abroad?

I work from the Philippines, mostly with teams several time zones away. I reply within a working day, and WhatsApp is the fastest way to reach me.

NEXT STEP

Tell me what keeps repeating

Bring me the one workflow that eats the most hours. I’ll tell you whether it can be automated, roughly what it would cost, and if the answer is no I’ll say so.

REPLY TIME
Within a working day
FIRST CALL
30 minutes, no pitch
YOUR DATA
Stays in your own tools and accounts
WhatsApp
The fastest way to reach me

Send a message

A sentence is enough. “Every order gets re-typed into two systems” tells me plenty.