After launch
Month two: updates without roulette
A sane path for changes—$75/hr maintenance, not “don’t click Update All.”
JMP is the jump into a modern stack. This topic is what that looks like in practice.
Launch day is not the finish line. The site needs copy tweaks, new photos, and occasional features—and a plan that does not risk the contact form.
Drag the divider to compare typical setup with a JMP build.
At a glance
Typical setup → JMP build
Typical
Afraid to update plugins
With JMP
Small, tested deploys
Typical
Emergency agency ticket
With JMP
Same builder who shipped it
Typical
Site rots until redesign
With JMP
Incremental improvements
Plan for month two
Decide how the site will be cared for
Launch is not the end. Know whether updates are scary plugin roulette, a retainer, or small deploys you can schedule—before something breaks on a Friday.
List what changed since launch
Plugins updated? Forms touched? Note anything that broke once—patterns repeat until there is a process.
Separate DIY vs. developer work
What can marketing change in a dashboard vs. what still needs a ticket? Gray areas become emergency calls.
Set a response expectation
Who do you email, and for what? A one-page “when to call” doc prevents silent rot or panic updates.
We offer maintenance at a published hourly rate and dashboard edits that do not need a deploy. What handoff should include.
Working with JMP
What you can change yourself vs. when to email
Response expectations spelled out
Optional retainer or pay-as-you-go
