Define what must exist
Name the working artifact first: the report that has to land, the dashboard someone opens, the workflow that has to fire. That's the target.
I'm Seigfred — I design and ship AI-powered automation. Data pipelines, internal tools, and agents that turn manual, repetitive operations into systems that run on their own.
A few of the things I've designed end-to-end — from the trigger that kicks them off to the report that lands in someone's inbox.
A multi-tenant operations dashboard for martial-arts academies — attendance, performance, and billing surfaced in one place, scoped per organization.
View projectPulls Facebook & Google ad data from three Google Sheets, normalizes it through n8n into Supabase, then a custom app I built turns it into a ready-to-send client email.
View projectA recruiting pipeline with an AI evaluation layer that scores interview responses against a rubric, so the team reviews ranked candidates instead of raw transcripts.
View projectA multi-tenant SaaS that lets martial-arts schools run realistic AI voice roleplays, auto-scores every call with OpenAI, and manages staff, scenarios, analytics and plans across schools.
View projectChosen for reliability and how cleanly they hand off to each other — most of my systems are two or three of these wired together.
Most automation projects stall because they start from the tools. I start from the thing that has to exist, then trace the path to it. Output, then input, then process.
Name the working artifact first: the report that has to land, the dashboard someone opens, the workflow that has to fire. That's the target.
Identify the data, triggers, and knowledge the output depends on, and where each piece actually lives today — not where I wish it lived.
Wire the pipeline, automate the handoffs, and make it observable — so when something breaks, it's obvious where, and the system keeps running until then.
I'm an automation specialist based in the Philippines, working in an agency context where the goal is always the same: take work that's being done by hand and turn it into something that runs on its own.
That instinct started on the mat. I spent years competing in martial arts — learning to read a situation fast and trust a framework I'd drilled until it was automatic. More recently I took it to the stage, competing in impromptu speaking at the national level: building a structured argument in the minute before I walk on, no script, under pressure. Both are the same move as the systems work — a reliable framework you can lean on when it counts.
Away from all that I run and hike, and I track the numbers while I'm at it, because I'd rather measure a thing than guess at it.
Press the button and talk through what you're trying to automate. You'll be speaking with my AI assistant — not me directly — and it can answer questions about how I work and set up a call.
the human behind it
It listens, asks a couple of questions about your manual process, and books a call if it makes sense — no typing, no forms.
Tell me what the manual version looks like today, and I'll tell you what it could look like as a system.