The traditional proposal process is backwards. You have a discovery call. You take notes. You go build a proposal in Google Docs. You email a PDF. The client looks at it two days later with zero context and no memory of why they were excited on the call.

The AI-powered proposal system we run works differently. The proposal is built during the qualification process, not after it. By the time the client sees it, it already contains their actual site data — their broken pages, their SSL status, their competitor gaps, their core metrics. It's not a template with their name swapped in. It's a document that knows them.

"A proposal that arrives knowing the client's problems before they tell you is a different kind of document. It doesn't ask for trust. It earns it."

Intake to Calculation

The intake form is the first part. Not a contact form — a structured questionnaire that collects the business inputs the rules engine needs. Service type, average ticket, rough lead volume, current close rate, primary lead source, how long they've been in business. Fifteen questions, maybe five minutes.

The rules engine takes those inputs and runs calculations. If your average ticket is $4,200 and your close rate is 28%, and you're getting 12 leads a month, you're closing 3.36 jobs worth $14,112. The engine knows your current baseline. It also knows industry benchmarks for your vertical — what a realistic close rate improvement looks like with a better site, better follow-up automation, better trust signals. It prices the gap.

That gap calculation is the heart of the proposal. Not "here's what we build" but "here's what you're leaving on the table every month, here's why, and here's how we fix it."

The Site Scan Layer

While the intake form is being filled, a background process runs a site scan on the prospect's URL. SSL certificate status. Page load scores from PageSpeed Insights. Down-page checks. Technology stack detection. Broken link sampling. The results feed directly into the proposal as the "audit" section.

The client opens their proposal and sees:

  • Their homepage load score: 41/100 mobile
  • SSL status: Valid through Oct 2026
  • Site technology: WordPress 6.1 on shared hosting
  • Three pages with broken links the client didn't know existed
  • Mobile layout issues on the contact form

None of this was in the discovery call. You didn't ask them if their site was slow. You showed up with the answer. That's a completely different dynamic.

The Business Rules Engine

The rules engine is where accumulated experience lives. Years of knowing which problems cost which kinds of businesses the most money, translated into if-then logic that the AI can apply consistently.

A roofing contractor with a mobile load score below 50 loses approximately 34% of mobile visitors before the page finishes loading. That number comes from real data. The engine knows it. So when it encounters a roofing contractor with a 44/100 mobile score, it doesn't say "your site could be faster." It says "you're losing approximately one in three mobile visitors before your page loads, and mobile is where 67% of home-service searches happen."

The specificity is what makes it credible. Generic proposals get generic responses. Specific proposals close.

The Confidential Panel

Every proposal has two views. The public view is what you share with the client: investment summary, deliverables, timeline, ROI projection. The confidential view is for you: the honest assessment of what's actually wrong, what you're fixing (and why), and what the client doesn't need to see in writing to understand.

The "Honest Truth" panel has two lists: what we found and what we're fixing. It's not the pitch. It's the real diagnosis. Keeping that separate means the client proposal stays focused on outcomes and value while you maintain a clear record of the actual technical work.

Live Proposal Pages

The proposal isn't a PDF. It's a live URL. The client gets a link to a page that only they can see — a branded proposal page that loads their scan data, their calculations, their pricing, their timeline. No attachment to download. No version confusion. The link is the proposal.

That means it can be updated. If the scope changes in conversation, you update the page. The client's link shows the new version. No "please disregard the previous attachment." No re-send. Just a live document that reflects the current agreement.

What This Replaces

The old workflow was: call, notes, Google Doc, PDF, email, wait, follow up, lose track, re-send. The new workflow is: intake form, rules engine, live proposal URL delivered during or immediately after the call. Discovery to proposal in under an hour.

The close rate difference comes from timing and specificity. Proposals delivered fast, while the conversation is fresh, close at a measurably higher rate. Proposals that contain the client's actual data close faster than ones that don't. The system optimizes for both.