Packages & pricing

Fixed scope. Fixed fee. No hourly surprises.

Five ways to work together, priced up front. Most people start with a teardown because it costs the least and tells you the most, including whether you should hire me at all.

01

Ops Teardown

$3,500 fixed · ~2 weeks

Find out exactly where the hours are going before you spend a dollar automating anything.

You get

  • Every system mapped: POS, booking software, CRM, email, the spreadsheets nobody admits to
  • A data-flow diagram of how information actually moves today
  • Every manual handoff itemized, with hours per week attached
  • A prioritized roadmap ranked by hours saved per dollar spent
  • Written report, recorded walkthrough, and a 90-minute working session

Not included

No implementation. This is diagnosis only, and deliberately so, which keeps the recommendation honest.

03

Automation Retainer

from $4,500 per month

An engineer on the hook for the systems you depend on, without a headcount req.

You get

  • Monitoring and on-call for every integration I’ve built you
  • A fixed block of new build hours each month
  • New n8n workflows as the operation changes
  • Direct access: you message me, not a ticket queue
  • Quarterly review of what’s worth building next

Best for

Operators running several connected systems who can’t afford a full-time engineer but can’t afford breakage either.

04

Website & Conversion Build

from $9,500 fixed scope

A fast, search-visible site wired into the systems behind it, not a brochure that emails you a PDF.

You get

  • Custom build with no page builder and no theme bloat
  • Quote and intake forms that write straight into your CRM
  • Technical SEO and schema done properly at build time
  • Core Web Vitals in the green on mobile, not just desktop
  • Training so your team can edit it without calling me

Proof

Twelve-plus live sites across catering, hospitality, events and retail. See the work →

05

Custom Platform Build

from $45,000 scoped engagement

When the software you need doesn’t exist and the workarounds have stopped working.

You get

  • Discovery and architecture before any build commitment
  • A production system, not a proof of concept
  • Auth, roles, billing and audit trails handled properly
  • Deployed on infrastructure you own and control
  • Handover documentation and optional ongoing support

Proof

PetCarePilot, a full custom platform for pet-care operations, designed, built and shipped end to end.

How it runs

No discovery theatre.

  1. 1

    Thirty minutes on the phone

    You describe the workflow that’s eating the week. I tell you whether it’s worth automating. Sometimes the answer is no, and that’s a free answer.

  2. 2

    Teardown

    Two weeks mapping what you actually run and where the hours leak. You end up with a diagram, a ranked roadmap and real numbers, whether or not you hire me to build it.

  3. 3

    Build

    Fixed scope, fixed fee, thirty days. You see it working in staging before it touches production, and the field mapping is agreed before I write code.

  4. 4

    Keep it running

    Integrations break when vendors change APIs. Monitoring, alerting and a person who answers, either on retainer or handed over documented. Your call.

Common questions

Before you book a call.

My software doesn’t have an API. Can you still connect it?

Usually, yes. A surprising amount of catering and spa software has no public API but does have scheduled CSV exports, a reporting endpoint, an email digest, or a database you own a copy of. I’ve built reliable syncs on all four. If it genuinely cannot be reached, I’ll tell you during the teardown rather than after you’ve paid for a build.

How is this different from hiring an agency?

An agency sells you a team and assigns you whoever is free. You get me, every time. The tradeoff is honest: I have finite capacity and I turn work down. If you need twenty people, I’m the wrong call.

Do I have to replace the software I’m already using?

Almost never, and I’d push back if you wanted to. Your booking system stays the system of record. Ripping out working software is expensive, disruptive, and usually solves a problem that better plumbing would have solved for a tenth of the cost.

What happens if an integration breaks after you’re gone?

Everything I build ships with error alerting, so a failed sync notifies a human instead of quietly losing data, which is the actual failure mode that hurts. You also get documentation written for whoever comes next. Retainer clients get me on call; everyone else owns a system another developer can pick up.

Are you only for catering and med spas?

No. Those are just where I have the deepest pattern library, so you get there faster and cheaper. The underlying work is systems integration and automation, and I’ve done it across construction, legal tech, ISPs, private equity and e-commerce. If your operation runs on software that won’t talk to itself, the problem is familiar regardless of industry.

Where are you based, and does it matter?

Fort Lauderdale, Florida, working with clients nationwide. Nearly all of this work is remote by nature: I’m in your systems, not your office. For larger builds I’ll come on site for discovery if it’s genuinely useful.