seigfred
systems nominal

Systems that keeps working after everyone logs off.

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.

See the work
workflow/client-reporting.json executing
trigger
Webhook·n8n
process
Claude·AI Agent
store
Supabase·SQL
Done
--:--:--waiting for trigger… 1,204 runs 99.9% uptime ~3.2s avg
// the toolchain

The tools I reach for.

Chosen for reliability and how cleanly they hand off to each other — most of my systems are two or three of these wired together.

01orchestrate
n8nWorkflow orchestration
Make.comVisual automation
02ai & llm
OpenAIModels & scoring
ClaudeReasoning & agents
03data & backend
SupabasePostgres & auth
AirtableStructured ops data
Node.jsCustom logic & APIs
04interface
ReactFront-end & dashboards
05client & deploy
GoHighLevelClient CRM & comms
RenderDeployment
// how i work

I build backward from the output.

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.

01 — output

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.

02 — input

Work back to what it needs

Identify the data, triggers, and knowledge the output depends on, and where each piece actually lives today — not where I wish it lived.

03 — process

Build the path between

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.

// the human node

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.

Based inPhilippines · GMT+8
FocusAutomation & AI systems
Core stackn8n · Supabase · Node.js
Off-stageMartial arts, speaking, hiking
Open toBuild & automation work
// talk to my assistant

Rather just say it out loud?

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.

Seigfred the human behind it
Tap to start talking

It listens, asks a couple of questions about your manual process, and books a call if it makes sense — no typing, no forms.

Answers questions Scopes the work Books a call
AI assistant · not a live person
// open a connection

Got something that should be running on its own?

Tell me what the manual version looks like today, and I'll tell you what it could look like as a system.

seigfred@ciots.io LinkedIn