Client Discovery and Proposals

Convert vague interest into a decision-ready offer without overpromising or doing unpaid custom delivery.

Discovery workflow

1. Gather the available context from the opportunity, CRM, messages, and prior work. Mark assumptions and protect personal or confidential data.
2. Clarify the desired business outcome, current pain, users, workflow, constraints, deadline, budget range, decision maker, approval process, and definition of success.
3. Qualify fit against Solo Empire capabilities, evidence, capacity, urgency, access to the client, and expected value. Do not claim experience or results that are not verified.
4. Offer the smallest useful engagement. Define deliverables, exclusions, client responsibilities, dependencies, milestones, acceptance criteria, change handling, and support boundary.
5. Prepare proposal options when useful: a focused starting scope, a fuller scope, and explicit tradeoffs in time, risk, and price.
6. Draft a proposal with executive summary, outcome, approach, scope, timeline, assumptions, risks, price and payment milestones, proof, validity period, and a clear next step.
7. Review for feasibility, margin, privacy, security, and contractual risk. Use approved legal templates or obtain professional advice for legal or tax questions.
8. Keep the proposal as draft until the user authorizes external sending. Log the opportunity, next action, owner, and follow-up date in the appropriate CRM or dashboard.

Decision rules

• Vague request → ask the fewest questions that materially change scope, price, or feasibility.
• No access to required data or systems → state the dependency and provide a discovery or setup phase.
• No credible proof for a requested outcome → reduce the promise to an observable deliverable.
• Unpaid custom work → provide a bounded sample or paid discovery, not a hidden implementation project.
• Legal, tax, employment, or regulated advice → flag the issue and route to the approved professional or compliance workspace.
• External message or proposal → distinguish draft, approved, sent, and accepted states; never imply that a draft was sent.

Handoff

Once accepted, move the work into the client's own bookchaowalit-freelance/<client> repository, preserve the signed scope and assumptions, create milestones and acceptance checks, and identify the person responsible for client communication.