I build systems businesses can leave running.

The system checks the facts before it acts. When it reaches a limit, it stops and hands the work to a person. I stay around after launch to keep it working.

Message me on Contra View the work

What I do

Most automations work until the real world shows up.

Someone buys after entering a recovery sequence. A lead replies after the owner has already stepped in. A customer asks for something the policy does not cover. That is where I start.

I map those handoffs, build checks around them, and make the system stop cleanly when it needs a person. The projects below show the approach, not the limit of what I can build.

Selected work / 01–04

The homepage is the index. The full proof lives inside.

Open any project for the screenshots, testing record, results, limits, price, and disclosure. Nothing is hidden behind a vague portfolio summary.

Cart recovery / DTC ShopifyCart Recovery That Stops After PurchaseThe sequence sends up to three emails, but it checks the original Shopify checkout before every step. If the shopper has already paid, the work stops.3/3 TOUCHES DELIVERED · $47.60 SHOPIFY TEST VALUE · POST-PURCHASE SEND BLOCKEDAI support / DTC commerceAI Support That Escalates Instead of GuessingLeaf answers only from the store’s approved facts. If a request is private, sensitive, or unsupported, it hands the conversation to a person.30/30 LOCAL · 25/25 DIRECT · 25/25 PUBLICSpeed-to-lead / Local servicesSpeed-to-Lead With the Owner Still in ControlBrightFlow replies to an approved test lead in under a minute and alerts the owner. Follow-up stops as soon as a person takes over.5/5 ACCEPTED · 48.286 S MEDIAN · ZERO DUPLICATE OR ERROR DELIVERIESReview and retention / DTC ShopifyReview Follow-Up Without Rating-Based GatingThe wait depends on what the customer bought. A low rating can start a recovery flow, but it never hides the public review link.LIVE TWO-STAR PATH PASSED · OWNER ALERT RETRY ISOLATED · REBOOT PERSISTENCE PASSED

How I work

I start with the part that keeps going wrong.

  1. 01

    Find the leak

    Follow the work, find where it loses time or money, and decide where a person needs to stay in charge.

  2. 02

    Build the system

    Connect the real tools, then add checks, stop conditions, and a fallback for the messy parts.

  3. 03

    Stay accountable

    Test the failure paths, document the limits, and keep the agreed system healthy after handoff.

Services / Starting prices

A practical place to start.

These are starting prices, not automatic quotes. Final scope depends on volume, integrations, access, compliance, and the support you need. Third-party costs are separate.

SystemOutcomeBuildMaintenance
AI Support AgentAnswers from approved facts, verifies private lookups, and knows when to hand off.$600$120/month
Cart Recovery SystemUp to three recovery emails, with purchase checks before every send.$900$150/month
Review & Retention EngineProduct-specific timing for review requests, recovery, and replenishment.$500$99/month
Lead-to-Client AutopilotProtected intake, fast replies, owner alerts, and controlled follow-up.$700$150/month
DTC Automation BundleOne connected foundation for support, cart recovery, and retention.$1,800$299/month

About

You get a working system. I remain responsible for it.

I build automation systems for e-commerce brands and local service businesses.

First, I find the process that is wasting time or losing money. Then I build the checks and human handoffs that keep it useful.

Every project includes a working system and a walkthrough. If it needs ongoing care, I can keep owning it after launch.

Start here

What keeps falling between people and tools?

Message me on Contra