Real builds, not demos
Three things I've actually built.
marketing opsSupabaseGoogle Adshuman-in-the-loop
A lead-qualification loop that taught Google which clicks make money
A manufacturer's ad campaigns were optimizing on form-fills, treating a $40k buyer and a spare-parts
question as equal "conversions." I built the missing feedback loop: every form submission lands in a
database with its ad click ID, a human qualifies it in a small dashboard, and qualified leads flow back
into Google Ads nightly as offline conversions, so the bidding system learns from real outcomes.
form → webhook → database + click ID → human qualification UI → audit-logged sheet →
nightly Google Ads import
Result: the pipeline tracked more than $2.3 million in attributed sales orders from a
single quarter, matched order to click, against roughly $4,000 in ad spend. That figure is a floor: only
orders the tracking could individually prove.
middlewareWebflowSupabaseno-code enablement
Giving no-code designers a real database, without a developer on call
Webflow designers can build beautiful front ends but hit a wall the moment a site needs live data, logins,
or role-based content. I built an attribute-driven data layer: designers add plain HTML attributes in the
tools they already use, and the runtime handles querying, rendering, auth gating, and form submission
against a real backend. It runs in production on a manufacturer's dealer platform: gated portal,
role-based dashboards, live catalogs.
HTML attributes → runtime → Supabase / CMS → rendered live data, auth, forms
Result: a marketing site that behaves like an application, still fully editable by non-technical staff.
productclient-sideprivacy-first
Forgelit itself: 18+ tools born from workflows that annoyed me
Every tool on this site exists because a routine task was slower or leakier than it
should have been: converting files, cleaning metadata, extracting tables, styling code blocks. Each one
runs in the browser wherever technically possible, touching a server only when the job genuinely requires
it. That architectural judgment, use the simplest thing that safely works, is the same judgment I bring to
client systems.
Result: a live, growing product used by strangers, built and maintained by one person.
the stack, in practice: Webflow · Supabase · JavaScript · APIs & webhooks
· Google Workspace · custom integrations