Stop Writing Unpaid Proposals: An 8-Question Client Intake SOP for Freelance Developers

Many freelance software engineers and technical consultants know this painful ritual:

1. A prospective client reaches out with an exciting vision ("We need an AI workflow to automate our logistics pipeline" or "We want to rebuild our customer dashboard").
2. They ask you for a "quick proposal" or an estimate of your hourly rate.
3. You spend six to eight unpaid hours analyzing their requirements, mapping out system architectures, drafting a Statement of Work, and estimating milestones.
4. You send the proposal.
5. Radio silence. Or worse: "Thanks so much! This is very thorough, but our budget for this phase is $400."

You just donated a full working day of senior technical architecture work for zero dollars.

Here is a simple rule that protects those hours:

Never draft a proposal, scope a sprint, or write technical architecture documents until a prospect has passed a structured qualification screen.

Below is a simple standard operating procedure (SOP) for qualifying technical leads in about 15 minutes, before you write a single line of scope.

The 4-Pillar Qualification Framework (BANT-AI)

Before agreeing to a 30-minute discovery call or typing up any scope, score every inbound inquiry across four criteria:

Scoring system:

• Score 6–8: High-intent lead. Proceed immediately to a focused 20-minute discovery call.
• Score 3–5: Incomplete information. Reply with asynchronous clarifying questions before booking time on your calendar.
• Score 0–2: Disqualified. Politely decline or refer to off-the-shelf no-code tools.

The 8-Question Client Intake Discovery Script

When a prospect passes your initial filter, run these 8 questions on your discovery call or send them as an intake questionnaire:

1. Core Problem: What specific business bottleneck, manual task, or architectural failure is causing the most operational friction right now?
2. Quantified Impact: What does this problem cost your team each month in lost revenue, wasted engineering hours, or missed opportunities?
3. Desired Solution: In plain terms, what does the ideal outcome look like once this project is delivered and in production?
4. Existing Systems: What software, databases, hosting environments, or third-party APIs must this solution interact with (e.g., Stripe, PostgreSQL, AWS, HubSpot, custom REST/GraphQL APIs)?
5. Key Stakeholders: Who will review technical deliverables, give code/testing feedback, and provide official sign-off on completion?
6. Project Timeline: When is the hard launch or delivery deadline, and what business event (funding round, marketing launch, board meeting) drives that date?
7. Investment Range: What budget range has been formally approved for solving this ($2k–$5k, $5k–$10k, $10k+)?
8. Previous Attempts: Have you tried solving this with internal staff or previous contractors? What worked and what failed?

Notice question 7: Never ask "What is your budget?" Ask "What budget range has been approved for solving this?" That subtle shift in phrasing filters out tire-kickers who are price-shopping freelancers.

The 6 Red Flags That Mean You Should Walk Away

If you spot two or more of these signals during the intake phase, do not issue a proposal unless you require 100% upfront payment:

• [ ] The Hourly Rate Trap: Unwilling to discuss project outcomes, insisting on: "Just tell me your hourly rate first."
• [ ] Moving Target Syndrome: Vague, shifting requirements ("We'll know what we want once we see the first version.")
• [ ] The Free Spec Trap: Asking for unpaid proof-of-concept prototypes, code trials, or full architecture diagrams before signing a contract.
• [ ] The Serial Contractor Victim: Blames multiple previous developers for failed deliveries without acknowledging their own management breakdowns.
• [ ] The Hydra: Multiple uncoordinated decision-makers who give conflicting technical requirements.
• [ ] Artificial Urgency: Demands delivery "yesterday", but takes 5 days to respond to an email or grant repository access.

Automated Pre-Screening: Copy-Paste AI Intake Prompt

To save time, you can pre-screen messy inbound client emails by running them through an LLM (Claude, ChatGPT, or your local model) using this exact prompt:

You are an intake screening assistant for a solo software consultant.
Evaluate this client inquiry using the BANT-AI framework:
- Budget (0 = none/unrealistic, 1 = vague, 2 = clear/realistic)
- Authority (0 = no decision power, 1 = unclear, 2 = direct decision-maker)
- Need (0 = vague idea, 1 = moderate, 2 = quantifiable business bottleneck)
- Timeline & Tech Readiness (0 = none, 1 = unclear, 2 = clear deadline + ready systems)

For each pillar, quote the exact sentence from the inquiry that supports your score.
Then list any red flags (no budget, vague scope, spec work requests, contractor blaming, fake urgency).
End with the top 3 specific clarifying questions I should send back.

Client Inquiry:
<PASTE CLIENT EMAIL HERE>

Security note: Never paste sensitive proprietary customer credentials or confidential company data into cloud models.

Take This SOP for Free (or Grab the Entire Solo Stack)

If you want this exact intake framework, questionnaire, and scoring rubric as a formatted PDF and Markdown document to drop directly into your agency or consulting workflow, you can download it completely free ($0) from our Gumroad shop:

👉 Download the Free Client Intake & Lead Qualification SOP ($0)

If you want the complete, end-to-end consulting operational system, this SOP is Module 1 of The 2026 Solopreneur AI Operations Kit ($9), which includes:

• SOP 01: Client Intake & Lead Qualification Protocol
• Module 02: Master Services Agreement (MSA) & Statement of Work (SOW) Templates
• SOP 03: 72-Hour Client Onboarding & Project Kickoff Workflow
• Module 04: Production AI Prompt Engineering Library for Consultants (5 copy-paste prompts)
• SOP 05: Project Delivery Sign-Off & Testimonial Protocol
• Module 06: Solopreneur Consulting Pipeline & Margin Calculator (.csv)

Drop this system into your practice, stop doing free spec work, and protect your development hours.

Disclosure: this article was drafted with AI assistance and edited by the author. It is general business guidance, not legal advice. The links above go to our own Gumroad shop.