4 min read
A client change-request template that actually helps your developer
A copy-pasteable website change request template — what, where, current, desired, scope — that gets you a fixable ticket instead of a week of back-and-forth.
Read moreBlog
Notes on client feedback, care plans, and shipping website changes without the back-and-forth.
4 min read
How to collect website change requests from non-technical clients
Requests arrive by email, text, and cropped screenshots — and the details never come with them. A working intake system for clients who aren't technical.
Read more5 min read
Autofix: turn a client's edit into a dev-approved PR
The small-but-frequent change requests are what eat a care plan. Autofix turns a client's captured edit into a proposed fix you approve — with guardrails so it can never redesign or break the site.
Read more3 min read
Turn vague client website change requests into dev-ready tickets
Non-technical clients can't write a good bug report — and shouldn't have to. Here's what a truly dev-ready ticket contains and how to collect it without the back-and-forth.
Read more4 min read
Why website care plans need a better feedback loop
Care-plan margin dies from the drip of small, badly-specified requests. Fix the intake loop — not your speed — to keep the retainer profitable.
Read more