Implementation proposal template (plus SOW and emails)

Short answer: a good implementation proposal fits on one page: the client's situation in their words, three measurable goals, what you will set up across their operations (calls and texts, booking, scheduling, jobs, quotes, invoices, website chat, automations), a dated timeline, the investment as a setup fee plus a monthly retainer, one ROI line and one next step. The details go in a separate statement of work (SOW) that fixes scope, deliverables, client responsibilities, acceptance criteria and what happens to the data. Copy the templates below, replace every [bracket], and send the proposal within 48 hours of discovery.

These templates are a starting point, not legal advice. Have a lawyer review your SOW before you use it with clients.

What you get on this page

The proposal sells the outcome. The SOW protects both sides. Keep them separate: a client who has to read ten pages of clauses before seeing the price rarely says yes fast.

These templates are built for a project that sets up how a service business runs day to day, often replacing four or five separate tools with one app, plus bots and automations. They also work for a smaller scope, such as booking and invoices only: just list fewer items.

If you haven't run discovery yet, start with the discovery questions. Every section of the proposal is filled from those answers.

1. One-page proposal template

PROPOSAL: [Project name] for [Client name]
Prepared by [Agency name] on [Date]
Valid until [Date + 30 days]

YOUR SITUATION
[2-3 sentences in the client's own words. Today you
run [business] with [tools]. [Main pain, with a
number from discovery].]

GOALS
1. [Measurable goal, e.g. every call or text
   answered the same business day]
2. [Measurable goal, e.g. no double-booked jobs]
3. [Measurable goal, e.g. invoices sent the day the
   job closes]

WHAT WE'LL SET UP
- [e.g. phone calls and texts in one shared inbox]
- [e.g. online booking from your website]
- [e.g. scheduling and dispatch for [number] techs]
- [e.g. jobs, quotes and invoices, with follow-up]
- [e.g. customers with service history]
- [e.g. website chat with a bot for common questions]
- [Number] automations, e.g. [visit reminder text]
- Import of [data: customers, open quotes, equipment]
- Training for [number] people

REPLACES
[Tool 1], [Tool 2], [Tool 3]

TIMELINE
Kickoff [date]. Live by [date]. [Number] weeks total.

INVESTMENT
Setup: [amount], one time, [payment terms]
Monthly retainer: [amount]/month, starting at
go-live. Covers support and up to [number] changes
per month.
Software plan: [amount]/month, billed separately.

WHY IT PAYS
Replaces [tools] costing [amount]/year and removes
about [hours] of admin per week. Pays back in about
[number] months.

NEXT STEP
Reply "yes" by [date] and we send the statement of
work to sign. Kickoff can be [date].

How to fill each section

• Your situation: quote the client. If the owner said "half my day is returning calls from my truck", write that. They should nod while reading it.
• Goals: three, each with a number or a yes/no test. "Better organization" is not a goal. "Every quote followed up within two days" is.
• What we'll set up: name what the team will do in the app (answer texts, book visits, dispatch jobs, send invoices), not the technology. Leave out anything you didn't discuss. The customer records module (the CRM part) is one line among several, not the whole project.
• Replaces: list the tools the client named in discovery. Owners understand "one app instead of five" faster than any feature list.
• Investment: use the setup fee plus retainer model from the pricing guide. Show the software plan on its own line so the client sees every recurring cost.
• Why it pays: use only figures the client gave you in discovery. If they never agreed to a number, leave it out.
• Next step: one action and one date. Not "let us know your thoughts".

2. Statement of work (SOW) template

The SOW is where you prevent the three most common problems in an implementation project: scope creep, endless "is it done?" debates and a client who never sends their data.

STATEMENT OF WORK
[Project name]
Between [Agency name] ("Agency") and
[Client legal name] ("Client")
Effective date: [Date]

1. SCOPE
Agency will set up and configure [Client name]'s
operations app for [team size] users, covering:
[list the modules from the proposal].

2. IN SCOPE
- [e.g. one business phone number, with calls and
  texts in a shared inbox]
- [e.g. online booking with [number] visit types]
- [e.g. schedule and dispatch for [number] techs]
- [e.g. job, quote and invoice templates with
  Client's logo]
- [e.g. one sales pipeline with up to 6 stages]
- [e.g. website chat and bot, answering from up to
  [number] help articles or FAQs]
- [e.g. [number] automations, listed in Appendix A]
- [e.g. import of up to [number] customer records
  from [source], in one pass]
- [e.g. two training sessions of 60 minutes]

3. OUT OF SCOPE
- [e.g. accounting system migration]
- [e.g. new website design]
- [e.g. cleaning data in the source files]
- Anything not listed in section 2. These items can
  be quoted as a change request.

4. DELIVERABLES
- [e.g. working app with the modules above]
- [e.g. automations in Appendix A, each tested]
- [e.g. imported customer list]
- [e.g. one-page guide per role]

5. PHASES AND DATES
Phase 1, Discovery and data: [date] to [date]
Phase 2, Setup: [date] to [date]
Phase 3, Training and pilot: [date] to [date]
Phase 4, Go-live: [date]
Dates move by the same number of days as any Client
delay in section 6.

6. CLIENT RESPONSIBILITIES
- Name one decision-maker: [name]
- Send data exports by [date], in [format]
- Send business details needed for the phone and
  texting setup by [date]
- Answer questions within [2] business days
- Attend training: [who]
- Test and give feedback during the pilot week

7. ACCEPTANCE CRITERIA
The project is accepted when:
- [e.g. a text to the business number shows in the
  shared inbox and can be answered]
- [e.g. a visit booked online shows on the right
  technician's schedule]
- [e.g. a quote can be created and sent from the
  app in under 5 minutes]
- [e.g. each automation in Appendix A runs once
  in a test]
- [e.g. imported customer count matches the
  source file]
Client has [5] business days after go-live to report
a criterion that fails. If none is reported, the
project is accepted.

8. CHANGE REQUESTS
Any request outside section 2 is written down,
priced as a fixed amount and approved by Client in
writing before work starts. Small changes after
go-live are covered by the retainer, up to [number]
per month.

9. FEES AND PAYMENT
Setup: [amount]. [50]% at signature, [50]% at
go-live.
Retainer: [amount]/month from go-live, billed
[monthly], cancel with [30] days' notice.
Software plan: billed by [platform] to Client.

10. SUPPORT
Retainer includes: support by [email/chat], answered
within [1] business day, [hours, time zone], and up
to [number] changes per month. Unused changes do not
roll over.

11. DATA OWNERSHIP AND ACCESS
Client owns its account and all data in it.
Agency works with access that Client can remove at
any time. Agency will not copy Client's customer
data outside Client's account.

12. TERMINATION
Either party can end the retainer with [30] days'
written notice. Fees for work already delivered are
due. On termination, Client keeps its account, app
and data, and Agency's access is removed.

Signed: _____________ (Agency)  Date: ________
Signed: _____________ (Client)  Date: ________

Common SOW mistakes

• Scope creep. "Set up the app" is not a scope. List counts (visit types, automations, records to import, phone numbers) and write an explicit out-of-scope list. The line "anything not listed is a change request" does most of the work.
• Vague acceptance. "Client is satisfied" never ends. Write tests anyone can run in five minutes, one per module, plus a deadline after which silence means accepted.
• Automations with no list. "Automate follow-ups" turns into twenty requests. Put each automation in an appendix: what starts it, what it does, and the test that proves it works.
• No client responsibilities. Most delays come from the client: a late data export, missing business details for the phone setup, an owner who skips training. If the SOW doesn't say who sends what by when, every delay becomes your fault.
• Hourly change requests. Price changes as fixed amounts. It keeps you out of timesheet arguments, as the pricing guide explains.
• Silence on data. Small business owners worry about being locked in. Saying plainly that they own their data and can remove your access builds trust and costs you nothing.

3. Follow-up email after the proposal

Send it three business days after the proposal if you haven't heard back. Keep it short and give them an easy way to answer.

Subject: [Client name] proposal: any questions?

Hi [First name],

Following up on the proposal I sent [day]. The short
version: [main goal] by [go-live date], for [setup
fee] and [retainer]/month.

Would a 15-minute call [day] or [day] help to go over
it? Or if the timing isn't right, just tell me and
I'll check back in [month].

[Your name]

Why it works: it restates the outcome and price in one line, offers two specific times and gives a polite way to say "not now". A "no" or "later" is useful too: you can update the deal and move on. For where this step sits in the whole cycle, see the agency sales process.

4. Kickoff email

Send it the day the SOW is signed. It turns the client responsibilities into a to-do list with dates.

Subject: Kickoff: [Project name], live by [go-live date]

Hi [First name],

Thanks for signing. Here's how the next [number]
weeks go.

Kickoff call: [date, time], [link]. [30] minutes.
Who should join: [names/roles].

What we need from you by [date]:
1. Customer list export from [source] ([format])
2. Your current price list or quote examples
3. Your logo, as a PNG
4. The names and emails of [number] team members
5. Your service area, hours and visit types
6. The questions customers ask most often

Key dates:
- [Date]: setup done, first look
- [Date]: training for [team]
- [Date]: go-live

Your contact at [Agency name]: [name], [email],
[phone]. Questions answered within [1] business day.

Talk soon,
[Your name]

The detailed week-by-week plan behind these dates is in the software implementation plan, and the import itself follows the data migration checklist.

Worked example: an 8-person HVAC company

Here is the proposal filled in for a fictional company. The prices are examples in USD to show the structure, not a recommendation for your market.

PROPOSAL: The whole office in one app for Maple
Ridge Heating & Air (fictional company)
Prepared by Northline Digital on November 2, 2026
Valid until December 2, 2026

YOUR SITUATION
Maple Ridge has 8 people: the owner, one office
manager and 6 technicians. Calls go to the owner's
cell, texts sit on two phones, visits are booked in
a scheduling app, quotes are in Word, invoices in a
separate tool, and the website form gets no answer
after hours. In your words: "Half my evening is
returning calls, and some quotes never get followed
up."

GOALS
1. Every call and text answered the same business
   day
2. Every quote sent within 24 hours of the visit
   and followed up after 3 days
3. Invoices sent the day the job closes

WHAT WE'LL SET UP
- Business number with calls and texts in one
  shared inbox
- Online booking for maintenance visits
- Technician schedule and job dispatch
- Customers with equipment and service history
- Quotes from your price list, with follow-up
- Invoices and payment reminders
- Website chat with a bot for common questions
- 4 automations, including a reminder text the day
  before each visit
- Import of 1,400 customers and 35 open quotes
- Training for the office manager and 6 technicians

REPLACES
Scheduling app, invoicing tool, texting app,
website form tool, quote spreadsheets

TIMELINE
Kickoff November 16. Live by December 18. 5 weeks.

INVESTMENT
Setup: $8,500, one time, 50% at signature
Monthly retainer: $500/month from go-live. Covers
support and up to 3 changes per month.
Software plan: billed separately, monthly, by the
platform.

WHY IT PAYS
Replaces 4 paid tools costing $8,400/year and
removes about 10 hours of office admin per week
(about $15,000/year at $30/hour). Pays back in about
6 months.

NEXT STEP
Reply "yes" by November 9 and we send the statement
of work to sign. Kickoff can be November 16.

How the ROI line was built: tools replaced ($8,400) plus time saved (10 hours × 50 weeks × $30 = $15,000) is about $23,400 a year, or $1,950 a month. After the $500 retainer, that leaves about $1,450 a month, so the $8,500 setup pays back in about six months. Every input came from the owner during discovery, which is why it holds up when they read it.

Doing this on Alori

The templates work with any tool. If you deliver on Alori through the partner program, one app covers the modules in the example (customers and deals, quotes, online booking, schedule, jobs, invoices, calls and texts, email, website chat, a bot and automations), and a few clauses map to how agency mode works:

• Data ownership: each client gets their own account. You set it up, then invite the owner, and the account becomes theirs. Their customers and records stay in that account.
• Access: the client's owner can stop your access from their settings at any time. Your SOW's termination clause should say the same thing in plain words.
• Software plan: the client pays Alori directly. Your markup is a percent added on top of what Alori charges them, so the "software plan" line in your proposal already includes your share. If the client removes your access, their plan moves back to Alori's own price at the next renewal.
• Faster delivery: you can build a demo app for a trade once and copy it for each new client, then adjust it. The copy brings its setup (pipelines, templates, price list, website chat settings) but none of the source's customers or jobs, and gets its own business number. That shortens phase 2 of the SOW.

FAQ

How long should an implementation proposal be? One page. Put the details in the statement of work, which you send after the client agrees to the proposal.

What's the difference between a proposal and a statement of work? The proposal sells the outcome and the price. The SOW defines exactly what is delivered, by when, who does what and how the work is accepted. Clients sign the SOW.

Should the proposal cover only the CRM? Rarely. Most service businesses lose time across calls, scheduling, quotes and invoices, not only in customer records. Scope the project around the work the team does every day and list the tools it replaces.

Should I include the software subscription in my price? Show it on its own line. Clients compare recurring costs, and hiding the software inside your retainer makes your fee look bigger than it is.

How do I stop scope creep in an implementation project? List counts in scope, write an out-of-scope list, and say that anything not listed is a change request priced before work starts.

Can I use these templates for automation or AI projects? Yes. List each automation or bot in an appendix and write an acceptance test for each one, such as "a new web lead gets a reply within 5 minutes".