Build a Sales Follow-Up and Communication System

A. Finished-Project Specification

Quantity: one approved pipeline structure with defined stages and statuses, one lead and opportunity record format, one contact-log format, one set of follow-up message templates, one objection-and-question library, one discount-approval process, one decline-and-referral procedure set, one sales-to-operations handoff checklist, and one management dashboard, all dated and reviewed by at least one qualified professional.

B. Document Schedule (Component Schedule)

Document	Quantity	Format	Content Required	Preparation / Purpose
Pipeline Stage Definition	1	Table	Stage name, entry criteria, exit criteria, and responsible owner	Controls where every opportunity sits and what moves it forward
Lead / Opportunity Record	1 per opportunity	Structured record	Identifier, customer, property, service, source, size, authority, budget, timing, risk, consent	The single tracked unit of the pipeline
Contact Log	1 per opportunity, cumulative	Structured log	Date, method, participants, factual summary, decision, next action	Factual record of every customer communication
Follow-Up Templates	Set (minimum 5)	Written templates	Receipt, clarification, selection, schedule/price validity, closing status	Compliant, non-pressuring communication at each proposal stage
Objection-and-Question Library	1	Reference table	Common question or objection, factual approved response, escalation trigger	Consistent, factual answers to scope, price, schedule, warranty, disruption, permit, and process questions
Discount / Concession Approval Matrix	1	Table	Discount type, sales-personnel limit, manager approval threshold, documentation requirement	Controls who may offer what without unauthorized commitments
Sales-to-Operations Handoff Checklist	1	Checklist	Confirmed contract terms, selections, deposit, and startup readiness before estimating/contract handoff	Prevents an accepted proposal from stalling between sales and Chapter 13 startup
Management Dashboard	1	Summary view	Lead source, stage, value, age, probability, next action, conversion, backlog	Monthly sales review and capacity planning

C. Information Takeoff

• Business-model information: approved service menu, customer definition, geography, and project-size range from Chapters 1 and 6, gathered before Step 1.
• Compliance information: applicable marketing, telemarketing, email, text, and privacy requirements for every jurisdiction served, gathered before Step 5.
• Sample data: at least one real or representative lead, one issued proposal, one decline, and one accepted project, used to test the system in Section H.
• Professional input: at least one qualified reviewer identified before Section H, with attorney or marketing-compliance review specifically for consent, follow-up, and discount language.

D. Acceptance Standards

Check	Standard
Stage definition	Every pipeline stage has a specific entry criterion, exit criterion, and responsible owner
Lead and opportunity fields	Every opportunity record carries a unique identifier and complete customer, property, service, source, size, authority, budget, timing, risk, and consent fields
Contact log	Every material conversation is recorded factually with date, method, participants, decision, and next action; no speculation, insults, or protected-characteristic notes appear
Follow-up templates	Every template is free of false scarcity, false deadlines, fabricated discounts, or unsupported urgency, and matches the customer's recorded consent and channel preference
Objection library	Every response is factual, does not disparage competitors, and includes an escalation trigger for legal, technical, insurance, financing, complaint, discrimination, or safety questions
Discount control	Every discount or concession above the sales-personnel limit is routed through the approval matrix and documented before being offered
Decline and do-not-contact handling	Every decline is recorded using a consistent business category, and no further outbound communication occurs after a do-not-contact request
Professional review	At least one qualified reviewer has reviewed the completed system and their comments are recorded and addressed before approval

E. Pipeline Structure and Lead Intake Fields

1. Define pipeline stages from inquiry through qualification, site visit, estimating, proposal, follow-up, accepted, declined, expired, waitlisted, or referred. Record each stage name in the order an opportunity actually moves through it.
2. Define entry and exit criteria for each stage. State the specific condition that moves an opportunity into the stage and the specific condition that moves it out.
3. Create unique lead and opportunity identifiers. Assign a non-reusable identifier to every opportunity at the moment it is created.
4. Create fields for customer, property, service, source, estimated size, decision authority, budget alignment, timing, and risk. Build these as structured fields on the opportunity record, not free-text notes.
5. Create consent and preference fields for phone, email, text, platform, and postal communication. Record the customer's affirmative consent and preferred channel for each communication type at intake.
6. Follow applicable marketing, telecommunication, email, text, privacy, and do-not-contact requirements. Confirm the consent fields in the previous step match the current requirements for every channel the business intends to use.

F. Communication Log, Proposal Status, and Follow-Up

1. Create a contact-log format with date, method, participants, factual summary, decision, commitment, and next action. Build this as a structured, dated entry format attached to each opportunity.
2. Do not record insults, speculation, protected characteristics, or irrelevant personal information. Write the contact-log standard as an explicit rule reviewed with every person who will use it.
3. Create proposal issue, revision, expiration, and status fields. Attach these fields to the opportunity record and link them to the specific Chapter 8 proposal document.
4. Create follow-up timing based on proposal type, customer commitment, validity, and business policy. State a specific follow-up interval for each proposal type and status.
5. Create professional follow-up templates for receipt, clarification, selection, schedule, price validity, and closing status. Draft each template using the message-purpose categories in Component Schedule row two.
6. Do not create false scarcity, false deadlines, fabricated discounts, or unsupported urgency. Review every drafted template against this standard before it is approved.
7. Create fields for unresolved questions, selections, financing, design, permit, and co-owner approval. Attach these as open-item fields on the opportunity record so nothing pending is lost between contacts.

G. Objection Handling, Escalation, and Discount Control

1. Create a common-question and objection library based on approved scope, price, schedule, warranty, disruption, permits, and process. Populate the library from Component Schedule row five with at minimum one entry per listed category.
2. Answer objections factually and avoid disparaging competitors. Review each drafted response against this standard.
3. Create escalation rules for legal, technical, insurance, financing, complaint, discrimination, or safety questions. State the specific role or professional each escalation category routes to.
4. Create a discount and concession approval process. Build the approval matrix from Component Schedule row six with a specific sales-personnel limit and manager threshold.
5. Prohibit unapproved changes to scope, price, payment terms, warranty, or schedule during sales follow-up. State this prohibition explicitly in the objection library and the follow-up template set.
6. Create reminders and ownership for every open opportunity. Confirm every opportunity record carries a next-action date and a named responsible person.

H. Status Management, Referral, Reporting, and Approval

1. Create dormant, nurture, lost, and do-not-contact statuses. Add these statuses to the stage list from Section E with the specific condition that triggers each.
2. Record decline reason using consistent business categories. Build a fixed decline-reason list and require one selection per declined opportunity.
3. Do not pressure a customer who declines or asks not to be contacted. Confirm the do-not-contact status stops every scheduled follow-up in Section F.
4. Create referral procedures for projects outside the business model. Link this procedure to the Chapter 1 stop-work / decline-work list and Chapter 6 referral rules.
5. Create a handoff checklist from sales to estimating and from accepted proposal to contract and operations. Build the checklist from Component Schedule row seven and confirm it links to the Chapter 13 job-start packet.
6. Prevent duplicate customer records and conflicting proposals. Add a duplicate-check step to the opportunity-creation procedure in Section E.
7. Create a dashboard for lead source, stage, value, age, probability, next action, conversion, and backlog. Build the dashboard from Component Schedule row eight using current pipeline data.
8. Do not treat speculative pipeline value as cash or committed revenue. Label the dashboard's value fields "Pipeline Value — Not Committed Revenue."
9. Create monthly sales review procedures. State the specific recurring date, attendees, and agenda for the review.
10. Compare lead quality, estimate cost, proposal rate, conversion, margin, service type, and source. Add these comparison fields to the monthly review procedure.
11. Review complaints, misunderstandings, lost jobs, and underpriced wins for process improvement. Add this review item to the monthly review procedure with a named responsible reviewer.
12. Test the system with one new lead, one revised proposal, one decline, and one accepted project. Run each test case through the full pipeline and record the result.
13. Verify that communication records and privacy controls function. Confirm the contact log, consent fields, and do-not-contact status behave as specified during the test cases.
14. Review templates with attorney, marketing, sales, estimating, and customer-service personnel. Obtain and record specific comments from at least one qualified reviewer.
15. Approve the system and assign pipeline ownership. Sign, date, and name the responsible pipeline owner.
16. Create record-retention and deletion procedures. State the specific retention period and deletion trigger for lead, contact-log, and proposal records, consistent with the Chapter 2 record-retention controls.