Paste their proposal. See what they're really saying.

Dev shops write proposals in weasel-phrases. "As needed." "Best efforts." "Standard industry practices." Each one is a blank check. Paste the proposal text, we flag every trap with translation and negotiation counter-language.

Runs in your browserNever sent to a server24 red-phrase patterns

// PASTE PROPOSAL TEXT

Nothing to analyze yet.

// WHY THIS EXISTS

Most disputes start in the contract, not the code.

Every vague phrase in a dev proposal is a future argument. When the site launches 8 weeks late and the agency says "that was out of the original best-efforts estimate," they're not wrong. They wrote "best efforts" into the contract and you didn't catch it.

This tool catches 24 of the most common weasel patterns seen in dev proposals: open-ended scope, hidden change fees, auto-renewal lock-ins, IP ownership traps, vague deliverable language, and billing practices that favor the agency when anything slips.

If a red flag fires on your proposal, it doesn't always mean walk away. It means negotiate specific language before signing. The counter-language field shows exactly what to ask for. Usually a 2-sentence edit saves 10k of scope creep.

// WANT A SECOND OPINION?

Have a proposal reviewed by a working dev.

Share the file, get a 15-minute review call with concrete red-line suggestions. No cost. No upsell pitch. MGT wins when you avoid a bad contract even if you never hire us.

Send it over