Commercial proposal template

What it is for and who it suits

It suits consultancies and agencies that send a similar proposal to every client. The structure runs from discovery findings through scope, plan, investment, success measures, assumptions and next steps, and the speaker notes inside the file say which parts stay the same from one client to the next and which are rewritten.

What is inside

The slides of this deck, in order, as they appear in its source file.

1. 01Online Booking That Dispatch Doesn't Retype
2. 02What We Heard in Discovery
3. 03What We're Proposing
4. 04In Scope and Out of Scope
5. 05An 11-Week Plan
6. 06Investment
7. 07How We'll Measure Success
8. 08Assumptions and Risks
9. 09Next Steps

The source

This is the whole file, the same text SlideWeave stores and the ZiraDocs compiler reads. Copy it, change the company and the numbers, and you have your own version.

---
mode: flex
title: "Online Booking Proposal for Hollisfen Home Services"
author: "SlideWeave Team"
theme: "minimal"
category: "deck"
blurb: "A services proposal for a home repair company: the problem in the client's own numbers, scope, an 11-week plan, phased pricing and the metrics that define success."
order: 2
lang: "en"
share_url: "https://app.slideweave.com/viewer/8306e049-e4c0-4b9d-90fc-e896bcf43204?share=b44d8020ae54d6f57d4ca03de03bc374fcaa64ef18a54e40"
---

# Online Booking That Dispatch Doesn't Retype
## A proposal from Tessaline Studio for Hollisfen Home Services, September 2026

---

## What We Heard in Discovery

- Hollisfen runs HVAC and plumbing crews out of 14 branches
- 71% of service bookings still come in by phone, and peak-hour hold time averages 9 minutes
- About 1 in 6 callers hangs up before booking
- The web form sends an email that a dispatcher retypes into the scheduling system, roughly 20 hours of work a week

::: info
**Customers are willing to book online.** The current form just can't show them a
real time slot, so most of them call anyway.
:::

---

## What We're Proposing

1. A booking page that shows real technician availability by branch and service type
2. Two-way sync with your field service software, so a web booking lands on the dispatch board with no retyping
3. Text confirmations and a reminder the day before, with a link to reschedule
4. A short playbook and training for dispatchers and branch managers

---

## In Scope and Out of Scope

| In scope | Out of scope |
|----------|--------------|
| Booking page for repair and maintenance visits | Quotes for new system installs |
| Integration with your current field service software | Replacing that software |
| Text confirmations and reminders | A native mobile app |
| Reporting on online vs. phone bookings | Changes to the payment process |

---

## An 11-Week Plan

<<mermaid>>
  gantt
      title Online booking project
      dateFormat YYYY-MM-DD
      axisFormat %b %d
      section Discovery
      Integration audit and booking rules :a1, 2026-10-05, 14d
      section Design and build
      Booking flow design                 :a2, after a1, 21d
      Build and integration               :a3, after a1, 42d
      section Launch
      Beta at two branches                :a4, after a3, 14d
      Rollout to all 14 branches          :a5, after a4, 7d

---

## Investment

| Phase | Length | Main deliverable | Fee |
|-------|--------|------------------|-----|
| Discovery | 2 weeks | Integration plan and booking rules signed off | $18,000 |
| Design and build | 6 weeks | Working booking page connected to dispatch | $96,000 |
| Beta and rollout | 3 weeks | Live at all 14 branches, staff trained | $14,000 |
| **Total** | **11 weeks** | | **$128,000** |

Fees are fixed per phase and invoiced when each phase is accepted. After
launch, an optional support plan runs $3,500 a month, month to month.

---

## How We'll Measure Success

| Metric | Today | Target, 90 days after launch |
|--------|-------|------------------------------|
| Share of bookings made online | 29% | 55% |
| Callers who hang up before booking | 17% | Under 8% |
| Dispatcher hours spent retyping web requests | ~20 a week | None |

We re-measure the baseline during discovery with full data. If it moves,
the targets move with it before the build starts.

---

## Assumptions and Risks

::: warning
**Text message sender registration can take two to four weeks.** We start it in
week one so it's approved before the beta; if it slips, the beta runs with email
confirmations only.
:::

- Your field service software vendor grants API sandbox access in week one
- A lead dispatcher is available four hours a week through the beta
- Branch managers at the two beta branches agree to the beta dates by October 19

---

## Next Steps

1. Walk through this proposal with Operations and Customer Service, week of September 28
2. Sign the statement of work by October 1
3. Kick off discovery on October 5

**Contact**: proposals@tessaline.example

@notes
This proposal is built to be reused. The section order, the in-scope and
out-of-scope table and the rule about re-measuring the baseline stay the same
for every client. The discovery findings, the numbers, the plan and the fees
are rewritten each time.