I build the software your team keeps postponing.

Fixed-scope implementation for agencies and small teams. One build at a time: reply and booking flows, LLM integrations, data pipelines, and the internal tools that hold them together.

Email me with what you need built and the deadline.

What I do

  • Reply and booking flows

    Answer a new inquiry in minutes, qualify it, and put a tour or a call on the calendar. Email, forms, and calendar, wired to a database you can read.

  • LLM integrations

    Document extraction, classification, and support triage that return structured data, not chat. Validated outputs, retries, and a cost ceiling.

  • Data pipelines and internal tools

    Postgres, scraping, dedupe, dashboards, and the cron jobs that keep them honest. A small console your team actually opens.

  • Workflow automation

    n8n, Make, Zapier, and custom glue between the tools you already pay for. Fewer copy-paste handoffs, fewer silent failures.

The system I run

Outreach engine architecture A cron job dispatches work, a worker qualifies and drafts, the Gmail API sends, a poller captures replies, and Postgres holds the ledger. A watchdog checks health. outreach engine production pg_cron four slots a day dispatch discovery + qualify worker research + draft Gmail API send + drafts poll replies + routing Postgres ledger jobs, outreach, replies, heartbeats watchdog 15-minute health
A simplified map of the outreach engine I built and run. Solid lines are the send path; dashed lines are state and health. It sends, polls replies, classifies intent, keeps a ledger, and raises its own health alerts.
  1. 01
    pg_cron

    Four dispatch slots a day.

  2. 02
    dispatch

    Discovery and qualification.

  3. 03
    worker

    Research and draft.

  4. 04
    Gmail API

    Send and store drafts.

  5. 05
    poll

    Replies, routing, and classification.

  6. 06
    Postgres ledger

    Jobs, outreach, replies, heartbeats.

  7. 07
    watchdog

    Fifteen-minute health check.

How I work

  1. 01

    Scope

    A short call and a written scope. No discovery project.

  2. 02

    Price

    A fixed price and a finish line, agreed before I start.

  3. 03

    Build

    One build at a time, about a week, with a working demo early.

  4. 04

    Handover

    The code, the deployment, and a walkthrough. You own it.

Selected work

  • Outreach engine

    In production

    A prospecting and outreach system on Supabase, Postgres, pg_cron, edge functions, the Gmail API, and Claude. It sends, polls replies, classifies intent, tracks a ledger, and reports its own health.

    TypeScript, Postgres, Supabase, edge functions, Gmail API, Claude

  • Childcare enquiry engine

    Deployed

    A measured inquiry and response-time system for childcare centers. It sends a parent-style inquiry, times the reply, and turns the result into a one-page report.

    TypeScript, Supabase, edge functions, Gmail API

About

I am a software engineer based in Abuja, Nigeria. I build production systems with TypeScript, Postgres, Supabase, edge functions, and LLM APIs. I care about the unglamorous parts: idempotency, claims, retries, and the watchdog that tells you when something is wrong.

I work remotely. If the scope is not clear, I will tell you before you pay.

Contact

Tell me what you need built.

Send the outcome, the deadline, and anything you have already tried. I will reply with a scope and a price, or tell you if it is not a fit.