the whole process, in the open

A plan you approve one milestone at a time.

Fixed price. Each milestone has a scope, a price, and a definition of done. You approve it, it gets built, delivered, documented, and taught. Then we keep it running.

  • 01fixed price by default
  • 02milestones billed on sign-off
  • 03nothing ships without docs and training
  • 04retainer is month to month

How the work runs

From first call to running.

The same five phases every time. Discovery before anything is built, a plan read for holes before anything is written, and every milestone proved on your system before it counts as done.

Five phases, from the first conversation to the retainer. Each milestone is taken from the plan and built, and that pair repeats until the plan is finished.

  1. 1. Conversation

    30 minutes

    Bring: your tools and subscriptions, who logs into what, the two things that break most

  2. 2. Discovery

    what you have now

    We map every flow, every field, and every place the same thing is typed twice. Nothing is built yet

  3. 3. Plan, reviewed

    written, milestones

    Contains: milestones in order, what each replaces, access we need, rollback for every cutover. Read for holes before anything is built

    next milestone

  4. 4. Build, prove, deploy

    per milestone

    Built with tests. The tests are read, not assumed, and the work repeats until they pass. Then it deploys, and the deployment is proved on your system

  5. 5. Retainer

    monthly, optional

    Every month: a note of what was patched and changed, what to watch, security review of each automation

Delivery

Done means handed over.

Two documents close every engagement. You get both. Your next engineer gets both.

handoff checklist

The checklist you sign

Nothing is invoiced as complete until every line is true and you have said so.

  • Running in production, in accounts you own
  • Tested with your staff on real records, results recorded
  • Runbook: what it does, how to change it, how to turn it off
  • Training delivered and recorded
  • All credentials rotated to you; ours removed
  • Backups verified by a restore, not a green light
  • Rollback path written and tested once
  • Old tools exported, archived, cancelled
runbook

The runbook you keep

Written for the person who has never seen the system. Sanitized table of contents from a real one.

  • 01What this system does, in one pagep. 1
  • 02Architecture: where data lives, what talks to whatp. 3
  • 03Accounts, access, and who holds which keyp. 6
  • 04Every automation: trigger, action, what it may touchp. 8
  • 05How to change a form, a template, a rulep. 15
  • 06Backups, restores, and the monthly drillp. 19
  • 07When something breaks: first ten minutesp. 21
  • 08How to turn it all offp. 24

Retainer

After delivery.

Month to month. Reported every month. If you leave, the system keeps running.

Covered

  • Monitoring, patching, and updates to the platform it runs on
  • Security review of each automation: what it can touch, whose credentials it uses, rotation
  • Hosting on our managed platform, if you choose it, on a stack of your own
  • Backups with a monthly restore drill
  • Small changes: a field, a template, a rule, a report
  • A private copy of your site where changes are built and signed off before they go live
  • A monthly note: what changed, what was patched, what to watch
  • A monthly check-in call and a quarterly review of the numbers

Not covered, quoted as a milestone

  • New automations or integrations
  • New forms, portals, or applications
  • Migrations and infrastructure changes
  • Anything beyond the small changes listed
Month to month 30 days notice Scope set in the plan, reported monthly Hosting optional, never assumed

Questions

The questions everyone asks.

Do you charge hourly?

Rarely. Milestones are fixed price, quoted before work starts, and that is how nearly every engagement runs. The retainer is a fixed monthly amount. If you would rather pay by the hour, we will.

When is a milestone billed?

On sign-off. It is built on a private copy of your site, demoed, and signed off by you before it is invoiced. If it is not delivered as written, it is fixed until it is, at no charge.

Who owns the code and the data?

You do. It runs in your accounts, on your site, in your database. Documentation is written so you can hand it to anyone.

What if we want to leave?

Thirty days notice on the retainer. Everything keeps running. You have the runbook, the credentials, and the backups.

What if the plan changes halfway?

The affected milestone is rewritten, re-priced if the scope moved, and re-approved before work continues. Milestones already signed off stand as delivered.

Do you host it?

If you want. Hosting is a line in the retainer, never a requirement. The system runs anywhere your site runs.

Next

Let's start with the conversation.

Give us 30 minutes, bring your concerns. You leave with all concerns broken down in an email with a fix for each, and pricing.

Book a conversation Email instead (386) 232-8118 fixed price · no long contract