Skip to content
All offers
OFFER

named job

Pick one job nobody wants to own. I build the agent that runs it. A person still approves spend, outbound messages, or record changes.

01 - The situation

The leak is one repetitive job. Catalog copy drifts. Prices move while someone is in another tab. Listing health sits in reports nobody reads until sales dip. Auditing hundreds of SKUs by hand takes days. The cost is the labor and the window between something breaking and someone noticing.

02 - How it runs

Name the job and the gate: spend, outbound messages, or record changes. A person stays on that gate.

I build the agent against the systems you already use. Next.js, Supabase, Vercel, and the APIs the job already talks to.

The agent drafts. A person still approves the calls that move money, messages, or records. A job can land as a governed workspace.

You leave with that job running. It is not a standing engagement until something is live.

03 - Already running

Catalog QA against a golden record, with a human-in-the-loop approval queue before anything is pushed back through SP-API.

A daily repricer with margin floors and an exceptions list instead of a race to the bottom.

Catalog health scored before a suppression, so standup starts from a ranked list.

04 - Related work

Autonomous Catalog Agent

Agentic system that monitors marketplace listings, detects content drift, and pushes corrected copy and imagery back through Amazon SP-API. Compresses catalog QA from days to minutes.

Read case study

Repricing Engine

Daily competitive repricer across thousands of SKUs with rule-based guardrails. Tracks margin floor, buy-box position, and competitor velocity to keep pricing honest without eroding profit.

Read case study

Catalog Health Dashboard

Internal tooling for marketplace ops teams: surfaces broken listings, missing variants, and policy violations before they cause suppressions. Next.js + Supabase, Vercel-hosted.

Read case study

Multi-agent operations platform

A self-hosted orchestrator coordinating five domain-specialist agents with persistent memory, operated through a secure messaging interface on private infrastructure.

Read case study

05 - What you leave with

That named job running, with a person still on the approval queue. Searching, diffing, and drafting leave their week. The exceptions list stays.

06 - What this is not

A file you import and run alone.

A full desk rebuild.

A standing engagement until something is live.

Unattended spend, outbound messages, or record changes.

If this is the wrong door, I will say so.

If it still fits after the work, start a conversation. Say what you sell, which channels you are on, and what is stuck.