Signature consultation path

Request the Signature consultation without forcing custom work into a fixed-price box.

Signature should collect the business context, goals, and scope constraints that explain why a fixed package would stop being commercially honest.

Implementation note

Inquiry routing, proposal logic, and live scheduling are not configured in this repo yet. This screen captures the approved consultation inputs and then moves into an honest confirmation state instead of faking automation.

Visible flow

Stage 01

Review Signature fit

The buyer understands why the custom route stays separate from the fixed-path packages.

Stage 02

Request consultation

This step captures the business context and scope signals needed to prepare the right manual follow-up.

Stage 03

Prepare project setup

Once direction is confirmed, the approved setup step gathers stakeholders, materials, and delivery realities.

Stage 04

Kickoff confirmed

When scope and readiness are clear, the engagement can move into active production without pretending it was fixed-scope work.

Why this step exists

Signature stays consultation-led because custom work should not pretend to be a fixed checkout path.
The intake should gather useful strategic context without turning into a full proposal workshop on the first screen.
Manual follow-up timing needs to stay explicit because live routing and proposal logic are not wired in this repo yet.