# Done-For-You Service Quote Funnel

## Objective

Turn service interest into a scoped quote request with the details you need to price it.

Build a done-for-you service quote funnel that captures project scope, qualifies the prospect, and routes a complete brief to the team for a quote.

## Before You Begin

This funnel is being added to an application or site that may already exist.
Do not scaffold a new project unless the user explicitly asks for one, and
do not assume a blank slate.

Inspect the codebase first and establish:

- The source Markdown files, docs, URLs, or repo files supplied for this funnel build.
- The offer, audience, funnel stage, price point, and desired conversion action.
- The existing application structure and where landing pages, forms, checkout, or tracking code already live.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this funnel needs to persist leads, applications, purchases, or events.
- The existing authentication and authorization system, if this funnel is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this funnel, extend it rather than replacing it.

Do not invent testimonials, revenue claims, scarcity, guarantees, legal
disclaimers, or endorsement language. Use only what appears in the source
files, and call out missing claims or assets in your final summary.

## Implementation Instructions

Build a done-for-you service quote funnel that captures project scope, qualifies the prospect, and routes a complete brief to the team for a quote.

1. Identify the service, the scope variables that drive price, and the qualifying signals from the source files.
2. Build a page that positions the done-for-you outcome, then a form that captures scope, timeline, and budget.
3. Add routing that flags complete, quotable briefs and follows up on incomplete ones for missing details.
4. Create confirmation and next-step states and a placeholder for handing the brief to the quoting workflow.

## Edge Cases

- If source files conflict, preserve the facts from the newest or highest-authority file and call out the conflict in the final summary.
- Do not invent claims, testimonials, legal disclaimers, revenue numbers, scarcity, or guarantees that are not present in the provided files.
- Use generic funnel strategy language only. Do not name or imply endorsement by any specific public marketer or brand.
- If payment, email, analytics, or CRM integrations are missing, build clear placeholders and document the exact variables or endpoints still needed.

## Acceptance Criteria

- [ ] The funnel can be built from linked Markdown/source files without requiring the agent to guess the offer.
- [ ] Every page or step has a clear primary action and one measurable conversion event.
- [ ] The output includes page structure, copy blocks, component notes, and implementation tasks.
- [ ] Mobile, tablet, and desktop layouts are accounted for.
- [ ] The agent reports which source files it used and which assumptions remain unresolved.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  funnel fit. Adapt the funnel to the app, not the app to the funnel.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.
- Use generic funnel strategy language. Do not name or imply endorsement by
  any specific public marketer, course, book, or software brand.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the funnel end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the funnel on mobile, tablet, and desktop widths.
5. Check forms, buttons, keyboard navigation, and focus handling.
6. Summarize what changed: files added, files modified, source files used,
   assumptions made, and anything you deliberately did differently because
   of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.