About Expertise Work Managed Apps
Business Website Online Store Sales CRM Team Drive Online Academy Newsletter System Booking System Shared Inbox Knowledge Base Short Links Business Manager Photo Gallery Survey Platform Community Forum Project Boards Estate Agency Car Workshop Restaurant Clinic Photography Studio
AWS
Assess & advise Build & migrate Automate & operate Secure & comply Urgent & go-live
Projects
Hosted Monitoring & Dashboards Self-Hosted Observability Stack Bulk Document Data Extraction Email Deliverability Diagnosis & Repair SEO Migration Recovery AWS Security Review VPS Hardening & ModSecurity Cloud Architecture & Resilience Review SSL & Server Configuration Container Security Review DNS & Email Troubleshooting DevOps Deployment & Rollback Review WordPress Hardening Retainer Data Pipeline Rerun Review Metric Reconciliation
Free Tools
Website Health Check Email Domain Health Check DNS Health Check SSL Certificate Checker Redirect Chain Checker Robots.txt Checker XML Sitemap Validator Docker Compose Checker WordPress Security Check AWS IAM / S3 Policy Checker Domain Registration Lookup Uptime Monitoring Trial Downtime Cost Calculator AWS Cost Estimator Cloud Architecture Self-Assessment DevOps Engagement Builder Self-Managed VPS vs Managed AWS
Blog Certifications Hire Me

Go-Live / Cutover Support

A booked window with someone watching, a rollback prepared, and a decision point agreed in advance.

Price and scope

From $349

Typically $349–$899, fixed in writing before anything starts.

1–2 days
Working days, counted from the moment I have access — not from the day you agree.

What moves it up

  • A weekend or overnight window, which is charged at the out-of-hours rate
  • A rehearsal beforehand, which is usually worth more than the window itself
  • Several systems cutting over together, where the order and the dependencies matter

Some of this you can check yourself, right now, for free: Uptime Monitoring Trial →

Why the go/no-go time is set in advanceA ninety-minute maintenance window. The final thirty minutes are reserved for a rehearsed rollback, so the go/no-go decision falls at sixty minutes. Three successive decisions to continue push past that line until rolling back no longer fits in the window.the workrollbackrehearsed: 30 minthe window: 90 minutesgo / no-go, agreed while everyone is restedalmost workinganother 20 minanother 20 minand anotherpast this line, rolling back no longer fits either
Go-Live / Cutover Support

What actually goes wrong

Cutovers go wrong on the decision, not on the steps. The plan says what to do and says nothing about when to stop — so at 2am, forty minutes into a ninety-minute window, with one thing not quite working, somebody has to decide whether to push on or roll back. That decision gets made by whoever is most tired and most invested, which is the worst possible person, and it is nearly always "give it another twenty minutes" — repeated until the window is gone and rolling back is no longer possible either.

How I find it

  • The rollback executed in a rehearsal, timed, so the window includes the time to undo it
  • A go/no-go checkpoint set at a clock time agreed before anyone is tired
  • TTLs lowered and confirmed expired in advance, not on the night
  • A checklist with an owner per step, so nobody is waiting on somebody who thought you had it

What you get

  • A written runbook with the steps, the owners and the point after which rollback stops being possible
  • A rehearsed rollback, with its own duration measured and built into the window
  • A go/no-go decision time fixed in advance, and I will call it even when it is unwelcome
  • Monitoring watched during and after, so the verdict is data rather than "it looks fine"
  • A short written record afterwards of what happened and what to change next time

Questions

Do you work weekends and nights for this?

Yes, for a booked window agreed in advance — that is what this exists for, and it is charged at the out-of-hours rate. What I do not offer is unscheduled night cover, which is a different thing and needs a team.

What happens if we have to roll back?

We roll back, at the time we agreed, and nobody has to argue about it at 2am — which is the entire value of setting that time while everyone is rested. A rollback inside the window is a successful outcome, not a failed one.

Can you run the cutover, or only supervise?

Either. Some clients want their own team executing with me watching and making the call; others want me driving with theirs on standby. Both work — what does not work is leaving it unclear until the night, so it gets decided in the runbook.

Is this worth it if the change is small?

Often not, and I will say so. A small change with an easy rollback does not need a booked window and a second pair of eyes. This is for the ones where undoing it is hard, or where several things move at once.

Want this done?

Tell me what you are running and I will come back with a fixed price and a date. If it turns out you do not need this, I will say that instead.

Prefer to talk? Book a free call ↗  ·  Or hire me on Upwork ↗  ·  Typical reply within one business day.

When I answer

Sunday to Thursday, 09:00–18:00 EET. Outside that I will still look, but I will not promise a time.

No 24/7 desk, and I will not pretend otherwise

One person, one time zone. If round-the-clock cover is what you need, you need a team, and I will say so rather than sell you a plan that cannot deliver it.

Your AWS bill stays yours

You pay Amazon directly and you keep control of the account. Nothing here resells your infrastructure or sits between you and your own billing.

A price that starts with "from" is a starting price

Every service page lists exactly what pushes a quote above it, before you ask. You get a fixed number in writing before any work begins.