The problem: Ad-hoc ChatGPT prompting or generic Word/Google Doc proposal templates, which have no built-in estimation logic and lead to underquoting or inconsistent scope-to-price mapping.
This fixes it: Turn any client brief into a defensible scope, hour estimate, and polished proposal in under 15 minutes using a structured 6-stage prompt chain built on a rate-card + risk-buffer rubric.
- Stage 1: Client brief intake & requirement extraction prompt - Stage 2: Task decomposition & complexity scoring prompt - Stage 3: Hour estimate with built-in risk buffer formula - Stage 4: Rate-card driven price calculation prompt - Stage 5: Client-tone calibrated proposal draft generator - Stage 6: Follow-up/negotiation email templates - Editable variable schema (rates, buffer %, scope categories)
You are a freelance-operations analyst. Build a single reusable JSON configuration object that will be referenced by every later scoping prompt in this chain. Fields must include: hourly_rates (by role), currency, complexity_buffer_table (mapping complexity score 1-5 to a buffer percentage), scope_categories (list of standard work types e.g. design, backend, integration, testing, PM), minimum_project_hours, and contingency_percent for scope-creep risk. Ask clarifying questions only if a required field is missing. Output only the finished JSON object, no explanation, so it can be pasted into downstream prompts verbatim.
My roles/rates: {roles_and_rates}. Currency: {currency}. Risk buffer per complexity level 1-5: {buffer_percentages}. Standard scope categories I bill: {scope_categories}. Minimum billable project size: {minimum_hours} hours. Contingency %: {contingency_percent}.Roles/rates: Dev $80/hr, Design $65/hr. Currency: USD. Buffers: 1=5%,2=10%,3=20%,4=30%,5=45%. Categories: backend, frontend, integration, QA, PM. Minimum hours: 20. Contingency: 8%.The other 7 in the pack