Skip to content
Agency Pilot

Proposals

A proposal the prospect can click through, sign and pay

Build the proposal from the saved geo grid scan and audit you already ran for the prospect. They open a private page, see where they show up today, move the revenue calculator, pick a plan and accept. You're told when they open it and which plan they looked at, and acceptance creates the client, the invoice and the monthly billing.

A proposal page showing the prospect's Google Maps visibility, with a ranking for each pin and the website score
What the prospect sees: their own map scan, with the plans, calculator and signature further down the page.

Their own data, on the page

A saved map scan with real pins, the audit findings, a competitor comparison and the keywords you chose. Nothing is pulled live when they open it.

A calculator they can move

Leads, booking rate and ticket size feed a revenue estimate with three scenarios. The numbers they settle on are saved as the client's baseline.

Signed and sealed

They type their name and tick the consent box. The agreement is signed as a contract, and both sides get the sealed PDF.

Private by default

An unguessable link, an optional passcode and an expiry date. Void it and the link stops working.

Know what they did

A notification when they first open it, come back, click a plan, ask for changes, decline or accept, and a timeline of the rest.

Acceptance does the setup

The client record, the first invoice, the recurring monthly invoice and your automation all start without anyone re-typing the deal.

From scan to proposal in one sitting

The builder has seven steps: the prospect, the services, the scan and audit to show, the keywords, the calculator, the pricing, and sending. The scan, audit and keyword lists are your agency's saved work for that business, so a proposal for a prospect you already pitched takes minutes.

Pricing is up to three plans plus optional add-ons, or a single flat price. Mark one plan as recommended, set a one-time setup fee and a term, and choose what is collected when they accept: setup and the first month, setup only, or nothing.

Save a finished proposal as a template to start the next one from, and use Preview as client to see exactly what the prospect will see. Nothing you do in preview is recorded or sent.

What the prospect sees

A single scrolling page in your agency's name and colours, readable on a phone. It opens with a headline and the numbers that matter most, then walks through the map, the website audit, how they compare with the businesses ranking above them, the keywords and ad budget, and what you would do over the first months.

The revenue calculator lets them change their own lead volume, booking rate and average job value and see the estimate move. The estimates are labelled as estimates, with a disclaimer you can edit.

Plans sit side by side with add-ons they can switch on, and the monthly total updates as they choose. If you set a passcode, they enter it first. If you set an expiry, the page says so and stops working after it.

Accepting means signing, and paying if you ask for it

Acceptance asks for a full name and a consent tick. Their choice of plan and add-ons is checked against the prices you saved, never against anything the browser sends, and the agreement they sign states the plan, the price, what is due now and the term.

When you collect money on acceptance, they go to a secure checkout on your own Stripe account and come back to the page, which confirms the payment. If they leave before paying, the page remembers their choice and lets them finish.

Once the signature and any payment are in, the proposal is locked and a signed PDF is available to both sides.

  • The client is found by email or created, and linked to the proposal
  • An invoice for the setup fee and first month, marked paid by the payment
  • A monthly invoice schedule that starts the month after the first month collected
  • The calculator numbers saved as the client's baseline for later reports
  • You and the prospect emailed, and your automation run

Automations that follow the proposal

Ten triggers are available in the automation builder: proposal sent, opened, plan clicked (optionally for one plan), accepted (at the signature), paid, onboarding completed, declined, changes requested, not opened, and step stalled (signed, but the next step has sat for a few days). Use them to create a follow-up task when someone opens it and goes quiet, text the owner when they click your top plan, or kick off onboarding the moment they accept.

The not-opened trigger runs once, after the number of days you set on the proposal. Pick an automation on the Send step and it runs then, and you get a notification either way.

The numbers

At a glance

PlansUp to three, plus add-ons, or one flat price
SignatureTyped name with a consent tick, sealed into a PDF
PaymentHosted checkout on your own Stripe account
AccessPrivate link, optional passcode, optional expiry
TriggersTen, from sent to step stalled

What this does not do

Better to find this out here than three weeks in.

  • Signatures are typed names. There is no drawn or uploaded signature.
  • Payment on acceptance is one charge for the setup fee and first month. Later months are invoiced on the schedule created at acceptance.
  • The map, audit and keyword sections show what you saved. They don't refresh after you send, so run a new scan and send a new proposal if the picture changes.
  • A signed proposal is locked. To change the deal, void it and send a new one.
  • Acceptance doesn't create the kickoff project or send an onboarding link by itself. Use the accepted trigger to start those.
  • Interactive proposals aren't included on every plan. See pricing for what each plan has.

Questions

Does the prospect need an account?
No. They open the link, and sign and pay without signing up for anything.
Can I send the same proposal to someone else?
Each proposal has its own link. Duplicate it to send a second one, and void the first if you want its link to stop working.
What if they want something changed?
They can send a message from the page. It reaches you as a notification, shows on the proposal, and runs your changes-requested automations.
What if the payment fails?
They stay on the page with their choice kept, and can try again. A failed payment shows on the proposal's timeline.
Can I see who opened it?
You see when it was opened, how often, which sections they spent time on and which plan they clicked. Visits from known bots and link previews aren't counted.

Send your next proposal as a page

Start from a scan you already ran and see how far the prospect gets.

Make the proposal a decision document

Interactive proposals for agencies should help a prospect understand the problem, the proposed work and the commitment they are considering. Start with a short explanation of the business outcome the engagement is designed to pursue. Then select the scan, audit and keyword evidence that is relevant to that outcome. A page full of impressive findings can still be difficult to decide on if the connection to the service is unclear. Explain why each included section matters, what your team would do about it and what the prospect needs to contribute. The interactive format supports the decision, but the scope and reasoning still need to be written clearly.

Use saved evidence with an explicit date

The proposal shows the scan, audit and keyword material saved for the business rather than fetching a new result every time it opens. This keeps the presented evidence tied to a particular assessment. Before sending, check that the business, location, keyword and scan settings are correct, and explain when the work was performed. If the market or website changes materially, consider whether a new proposal is appropriate. Avoid presenting an old snapshot as a live monitor. A dated baseline gives both sides a clearer starting point for discussing the opportunity and later evaluating the work that was agreed.

Explain calculator assumptions before discussing upside

A revenue calculator is a way to explore assumptions, not a promise that an agency can produce a specified return. Walk through the lead volume, booking rate and average job value with the prospect and ask which inputs they can support from their own records. Where the business does not know a value, label the assumption and show how a different value changes the estimate. Keep the disclaimer clear and specific to the model. This makes the calculator a useful conversation about capacity and commercial expectations rather than a persuasive number that the delivery team may later be expected to guarantee.

Make plan differences easy to compare

When offering several plans, distinguish them through meaningful differences in scope, service coverage or delivery cadence. Avoid forcing the prospect to infer why one option costs more from a long list of vague benefits. Explain what is included, what is optional, the one-time setup amount and the recurring charge. Review add-ons in the same way so the selected total reflects a deliberate choice. The recommended plan should have a reason connected to the prospect's needs. A single flat-price option can also be appropriate when the engagement has one clear scope and extra choices would create uncertainty rather than useful flexibility.

Preview the complete acceptance journey

Use the client preview to check the proposal from beginning to end before sending. Verify the prospect details, selected evidence, calculator language, plans, add-ons, term and amount due at acceptance. Confirm that any passcode or expiry fits the sales process. If payment is requested, make sure the intended agency Stripe account is ready for the workflow. Review the agreement language in the context of the actual service being offered. A polished opening section cannot compensate for an unclear recurring charge or an unexpected payment step at the end, so evaluate the page as a complete commercial handoff.

Plan what happens after signature and payment

Acceptance creates important records, but the agency should still define the operational next step. Decide which proposal event should trigger a follow-up task, onboarding work or an internal notification. Signature and payment are different events, and the appropriate delivery milestone depends on the agreement. Avoid telling the team that every signed proposal is fully paid or that a kickoff project appears automatically without the corresponding setup. Test the intended handoff and inspect the resulting records. A good proposal process ends with clear ownership of the new engagement rather than a successful acceptance notification that no one knows how to act on.

Frequently asked questions

What evidence should I include in a first proposal?

Choose findings that explain the specific service you are proposing. A relevant map scan and a few clear audit issues can be more useful than every available metric. State the assessment date and connect each finding to proposed work so the prospect understands why the evidence belongs in the decision.

Can a calculator estimate be treated as a revenue guarantee?

No. It depends on assumptions about lead volume, booking rate and job value, and real outcomes can differ. Review the inputs with the prospect and keep the estimate language visible. Use the calculator to discuss plausible scenarios and capacity rather than promise an exact amount of future revenue.

How should I set the recommended plan?

Choose the option that best matches the prospect's agreed priorities, resources and scope. Explain that recommendation in the proposal instead of assuming the label speaks for itself. The prospect should be able to understand both why that plan fits and what changes if they choose a different option.

What should I check before reusing a proposal template?

Review every client-specific element, including the business details, saved scans, audit findings, keywords, assumptions and commercial terms. A template can preserve structure while still requiring careful adaptation. Reusing another prospect's evidence or estimate without checking it can undermine trust even when the rest of the page looks polished.

Does the proposal map update when rankings change?

The documented proposal displays saved evidence. It does not refresh the map and audit after sending. If a changed situation makes the original assessment misleading, run the appropriate new work and prepare a new proposal rather than assuming the recipient is seeing current search results automatically.

Should I use an expiry date?

Use one when the commercial offer or assessment has a meaningful review window. Explain the deadline and leave enough time for the prospect's decision process. An expiry is useful for controlling an outdated offer, but it should not replace a clear conversation about availability, scope or the reason a deadline exists.

When is an optional passcode useful?

It adds a step before a recipient can view the private proposal page. Consider it when sharing material that should be restricted to the intended decision group. Coordinate the passcode handoff clearly so the prospect can access the page without an unnecessary support exchange at the moment they are ready to review.

How should I interpret a prospect clicking a plan?

Treat the event as a sign of interest in that section, not proof that the prospect has decided to buy it. Review the broader conversation before following up. A useful response asks about their needs or unresolved questions rather than assuming that a recorded interaction establishes commercial agreement.

What should happen when a prospect requests changes?

Review the request against the scope, pricing and delivery commitments before sending a revised offer. Clarify ambiguous wording and make sure the final page reflects the agreement you intend to deliver. The changes-requested event can support your follow-up workflow, but a person still needs to assess the substance.

Are signature and payment the same milestone?

No. A prospect can sign while a required next step remains outstanding. Use the appropriate proposal event for the action you want to initiate, and inspect payment status where it matters. The agency's operational handoff should reflect the actual agreement rather than treating every acceptance-related notification as interchangeable.

How are later monthly charges handled?

The documented workflow creates a monthly invoice schedule after acceptance, with the timing based on the first month collected. Review that schedule and the agreement before presenting the payment process to a prospect. Do not describe the initial checkout as automatically collecting every future month through the same one-time charge.

Can I edit a signed proposal to change the deal?

A signed proposal is locked. The documented approach is to void it and send a new proposal when the deal changes. Coordinate the revised agreement with the client and review any related commercial records rather than treating an updated sales conversation as an automatic amendment to the signed document.

What does the signature experience include?

The prospect enters a full name and checks consent, and the agreement is captured as a signed contract with a sealed PDF. The documented experience uses a typed name rather than a drawn or uploaded signature. Review the actual agreement text and signer information before relying on the completed record.

How can I avoid a confusing payment request?

Show the setup fee, recurring amount, selected add-ons and amount due now clearly before the prospect reaches acceptance. Check the configured collection option in preview. A prospect should not have to calculate which charges are immediate or discover an unexpected payment requirement only after choosing a plan.

What is a useful follow-up after sending?

Give the prospect a clear route to ask questions and agree a reasonable review window. Use engagement events as context for a helpful conversation, not as a reason to send a message after every click. The strongest follow-up addresses a decision or uncertainty that could prevent the prospect from moving forward.