Turn a project brief into an evidence-based time and cost estimate
Web designers underestimate projects by 2-3x because they forget about responsive variants, browser testing, revisions, and CMS setup. This recipe breaks any brief into granular tasks, estimates hours based on industry benchmarks, and adds realistic buffers.
Create a skill called "Scope Calculator". When I paste a project brief or intake notes, break it into granular tasks. Not high-level — granular. For a "5-page business website," that means: discovery/kickoff, sitemap and wireframes, homepage design (desktop), homepage design (mobile), 4 inner page designs (desktop), 4 inner page designs (mobile), design revisions (2 rounds), development of each page, responsive testing (3 breakpoints), cross-browser testing, CMS setup and content entry, client training, accessibility check, launch checklist, and post-launch support. Estimate hours for each task using web design industry benchmarks. Detect hidden complexity indicators in the brief: migration, e-commerce, multilingual, custom integrations, animations, user accounts — and flag additional hours. Add buffers for revisions, testing, and project management. Output: total hours (optimistic, likely, pessimistic), cost at my rate of [your rate], and a client-ready estimate document.
Paste a client's project brief or your intake notes. Your Claw breaks it
into granular tasks — not just "design homepage" but "design homepage desktop,
design homepage mobile, code homepage, responsive testing, 2 revision rounds,
CMS integration." Each task gets an hour estimate based on industry benchmarks,
with buffer for the stuff designers always forget.
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.
Convert "quick asks" into logged change requests with impact analysis and approvals
Scope creep is a margin killer and a schedule killer. This recipe creates a strict-but-practical change control loop: capture request, classify, analyze impact (time/cost/scope/risk), propose options, and route for approval. It keeps a change log so Slack decisions don't silently rewrite the project.
Update pricing across all your Airbnb listings without clicking through each one
Automate bulk rate changes across multiple Airbnb listings using your Claw. Useful for seasonal pricing updates, last-minute discounts, or syncing rates after a change in your hosting strategy.
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.