Catch "one more thing" before it eats your margin
Clients always slip in extra pages, features, and revisions that weren't in the original scope. This recipe monitors your project communication and flags scope-expanding requests the moment they appear — with a draft change order ready to send.
Create a skill called "Scope Creep Detector". I'm a freelance web designer. I'll give you my project scope document (proposal or SOW). Learn what was agreed to — pages, features, revision rounds, deliverables. Then monitor my email and Slack for client messages. When a client request falls outside the original scope (new pages, additional features, extra revision rounds, new integrations), alert me immediately. For each flagged request, generate a draft change order that references the original scope, describes the new request, estimates additional hours, and calculates the cost at my rate of [your rate]. Keep a running log of all scope additions with their status (pending, approved, declined).
Give your Claw the original project scope document (proposal, SOW, or
contract). It learns what was agreed to. Then, as client messages come in
via email or Slack, it watches for requests that fall outside scope —
new pages, additional features, "can you also..." requests — and alerts
you immediately with a draft change order.
Get alerted when a client edits the live site and breaks something
Clients with CMS access can make well-meaning edits that accidentally break layouts, navigation, or content structure. This recipe monitors the live site and alerts you when unexpected changes appear, with a visual diff showing what changed.
Stop waiting on clients for copy, images, and bios
Content bottlenecks stall launches. This recipe builds a structured content request from your sitemap, sends it to the client, and follows up until everything lands. It keeps the project moving without turning you into a full-time chaser.
Generate button labels, error messages, tooltips, and empty states
Nobody budgets for UX writing but it makes or breaks usability. This recipe generates complete microcopy sets for your UI components — error messages that actually help, empty states that guide action, button labels that are clear, and tooltips that explain without patronizing.
Turn finished projects into polished portfolio pieces without the 10-hour writing slog
Your portfolio is 3 years outdated because writing case studies takes longer than the projects themselves. This recipe takes your project files, Figma history, and a few bullet points from you, and drafts a complete case study — challenge, process, solution, results.