Docs
How Nudge works.
No jargon. Just a walk-through of what happens between the moment you send a request and the moment your website is updated.
1. You send a request
Text or email Nudge like you would a teammate. "Can you swap the homepage photo?" "Please update our office hours." "Take down last weekend's event." Anyone on your team can send a request — no login, no CMS, no training.
2. Nudge understands and checks permissions
Nudge interprets the request as a conversation. It knows who you are, what you're allowed to do, and asks clarifying questions when it isn't confident about what you mean.
3. Nudge classifies the risk
Every change gets a risk level: low (typo, expired event, alt text), medium (new page from a template, homepage callout), or high (nav changes, forms, brand). Low-risk changes can be auto-published; medium and high always route to an approver.
4. Nudge plans the change
You get a plain-language plan back: what will change, where, and what it'll look like. Approvers can approve, revise, or reject from the same text or email thread.
5. Nudge publishes safely
Every change creates a rollback point. Nudge runs quality checks before publishing, and if anything looks off, it pauses and asks first.
6. Nudge watches over your site
In the background, Nudge does weekly health checks — broken links, expired events, missing alt text, slow pages, SEO gaps — and sends a short digest so you know what's up.
Ready to hand off your website chores?
Try the demo. Text a request. Watch Nudge take it from there.
Try the demo