Make the stupid work disappear.

I build lightweight internal tools, integrations, and automations for the repetitive work your team does by hand: the copy-paste between systems, the cursed spreadsheet, the report someone assembles every Friday. Practical automation, boring reliable tech, and no AI shoehorned into places it doesn't belong.

Show me a workflow you hate  See real builds

The first look is free and takes 15 minutes: you show me one annoying process, I tell you honestly whether it's worth automating. No slide deck, no discovery-call theater.

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

The operating principles

Automation where it helps.
Boring tech where it's safer.

  • Sometimes the answer is a database trigger, not an "AI agent." You'll get the cheap, reliable version, even when the expensive version would bill more.
  • Sometimes you already own the software that solves your problem, and the honest deliverable is me telling you that.
  • Consequential judgment stays human. I automate collection, transformation, and routing aggressively, and keep approval steps visible and inspectable: logs, timestamps, who did what, when.
  • You own everything I build. Your accounts, your data, your infrastructure. If we part ways, it all keeps working and it's all still yours.

How an engagement works

Small doorway. Fixed prices. No open tab.

1 · Workflow look (free, 15 min)

You show me one process that annoys you, exactly how it happened last time. I tell you honestly if it's worth automating, and what I'd do.

$0

2 · Workflow audit

I follow the process end to end, map every step and system, and deliver a written plan: what to automate, what to leave human, what it costs. Credited in full toward the build.

$300 fixed

3 · Small automation

One annoying process, 1–3 systems, a clear finish line. Most first projects live here.

$500–$1,500 fixed

4 · Internal tools & multi-system workflows

Dashboards, integrations, data pipelines, the bigger builds, scoped and priced before work starts.

scoped per project

Prices are here because you shouldn't need a sales call just to find out whether we're in the same universe. Ongoing support is available after a build, but nothing requires a subscription.

Fair questions

What you're probably wondering.

Is this "AI consulting"?

No. It's making repetitive work disappear with whatever tool is genuinely right: sometimes that's a language model, more often it's a webhook, a database, and thirty lines of code. If someone has pitched you an AI solution that made you nervous, a second opinion is exactly the kind of thing the free look is for.

What systems do you work with?

Whatever you already run. Forms, spreadsheets, CRMs, email, databases, ad platforms, e-commerce, industry-specific software. If it has an export button, an API, a webhook, or even just a predictable screen, it can usually be connected. Learning your weird software is part of the job.

What if my process turns out not to be worth automating?

Then I say so, at the free stage or in the audit, and you keep the written plan either way. Charging you to build unnecessary software is a worse business than telling you the truth.

Who is this for?

Small businesses and teams doing manual glue-work between systems, and agencies whose clients keep asking for things beyond a normal website build. For agencies: I do fixed-scope, white-label work, so you can say yes instead of referring it out.

Start here

Show me a workflow you hate.

Describe the annoying thing in a sentence or two. You'll get a plain answer about whether it's fixable and what it would cost. No call required unless you want one. Prefer to talk? (323) 300-2012. Prefer email? contact@forgelit.com.

You'll hear back within two business days. No newsletter, no follow-up sequence, no "just circling back."