The problem

Vague project scopes lead to unpaid work, while messy pricing estimates invite haggling. Freelancers lose projects not due to lack of skill, but because their proposals fail to project professional authority or clear boundaries.

What it does

• Extracts deliverables and implied requirements from messy client emails or call notes.
• Drafts a detailed Scope of Work with explicit inclusions and exclusions to prevent scope creep.
• Generates a line-itemized quote where every price is backed by specific reasoning.
• Creates a milestone-based timeline that accounts for client feedback loops and realistic durations.
• Writes a client-facing cover letter and plain-language contract terms for payment and revisions.

Why this beats prompting it yourself

Generic prompts often hallucinate credentials or ignore the financial risks of vague scoping. This skill enforces a professional defensive structure, ensuring every deliverable has a boundary and every price has a logical justification that you can actually defend in a meeting.

Use cases

• Turning a "quick chat" or fragmented email thread into a formal project proposal.
• Generating tiered pricing options (lean vs. premium) when a client has an unconfirmed budget.
• Defining clear boundaries for a project where the client is prone to asking for "just one more thing."
• Onboarding a new client with a professional package that includes a timeline and payment schedule.

Known limitations

It cannot invent portfolio pieces or results you haven't provided. Contract terms are business-logic drafts and require legal review.