The maintenance loop
Client sends a request
In any practical form — email, document, meeting notes, phone call, or a simple text. No special tool or portal required.
Developer implements in source
The change is made in the Next.js codebase in Cursor, on a branch, with a clear commit message. The source of truth is Git, not a live database.
Client approves on a preview
A preview link is shared when a review step makes sense. The client checks the result in a real browser before anything goes to production.
Commit, push, deploy
Once approved, the branch is merged to main. Vercel builds and the change goes live. The public site advances in traceable steps.
How this differs from WordPress
WordPress-style
Log in to a browser-facing admin panel
Edit content or install plugins directly on the live server
Changes go live immediately — no version control
Risk of breaking the live site mid-edit
Plugin updates can introduce conflicts or vulnerabilities
This workflow
Client sends a request in any form
Developer implements in source on a branch
Change is previewed and approved before going live
Every deploy is a traceable, reversible Git commit
No admin panel, no plugins, no public login surface
Scheduled update days and urgent requests
For ongoing clients, the contract includes a designated update day each period — a recurring scheduled window where routine service requests (a text change, a new section, a small fix) are handled as part of the agreement.
If a request is urgent and cannot wait for the next scheduled day, off-schedule work is available at an agreed hourly rate — charged upon the client's explicit approval before any work begins. There are no surprise invoices.