CM Platform Maintenance: How to Document a New Service Offer Before Updating Your Setup
A practical checklist for recording what changed in a service offer, identifying which customer conversations may be affected, and preparing focused questions for a CM platform check-in before changing your setup.

Before updating your CM platform setup for a new service offer, write down exactly what changed, who the offer is for, and how a customer moves from inquiry to estimate and follow-up. Then compare those details with your current process and ask the CM team which available features and setup changes fit. This keeps the discussion focused without assuming that every offer needs a new workflow or that a particular feature is available.
Record the offer in plain language
Start with a short description a customer could understand without extra explanation. Note the service name, what is included, who it is intended for, and any meaningful limits or conditions. If the offer is still being developed, label uncertain details as undecided rather than presenting them as settled. This gives your team a shared reference and helps prevent different versions from appearing in conversations, estimates, or advertising.
Next, identify what is genuinely new. Is this a new type of work, a different package of existing services, a new way to describe the same work, or a change in the customers you want to reach? The distinction matters: a wording change may call for updated communication, while a different scope may affect the questions you ask before preparing an estimate. Keep the description factual and avoid claims about outcomes that you cannot support.
- Offer name and one-sentence description.
- Included work, exclusions, and details still undecided.
- Intended customer or situation, described without overstating who you serve.
- Any change to how a customer requests information or an estimate.
Document the offer as it is currently defined, not as you hope it will work later.
Trace what changes in the customer conversation
Map only the steps that could be affected by the new offer. For example, a customer may ask about the service, share details about the job, receive a request for more information, and then discuss an estimate. At each step, note what your team needs to know and what the customer should understand next. This is a planning exercise, not a claim that the platform automates every step.
A clearly illustrative example: a cleaning business adds a move-out cleaning option. The owner might note that the team needs to ask whether the property is empty and what areas are included before preparing an estimate. That example does not describe a CM customer or a confirmed platform feature; it simply shows how a change in offer can alter the information needed in a conversation. Your actual questions depend on your service and how you prepare estimates.
- Write the customer’s likely first question about the offer.
- List the details your team needs before deciding on the next conversation step.
- Note what information belongs in an estimate discussion, if applicable.
- Record who handles each handoff and what should happen if information is missing.
Focus on changes to the conversation, not on adding platform fields or stages before you know they are needed.

Separate confirmed details from open questions
Before changing a setup, mark each item as confirmed, proposed, or unknown. Confirmed details are decisions your business has made. Proposed details are options you are considering. Unknowns include both business decisions you have not made and platform capabilities you need to ask about. Keeping these categories separate makes it easier to discuss the right issue with the right person.
For example, you may have decided what the new service includes but not whether it needs a separate inquiry category. That is a business-process question to evaluate. Whether the current app supports a particular category or workflow is a feature-availability question for the CM team. Do not assume a feature exists based on a general description; ask what is currently available for your plan and intended use.
| Status | What to write down | What to do next |
|---|---|---|
| Confirmed | Decisions about the offer and customer process | Use these as the working brief |
| Proposed | Changes your team is considering | Discuss trade-offs before adopting them |
| Unknown | Unresolved business details or platform capabilities | Ask a focused question; do not treat it as settled |
A useful maintenance note distinguishes your decisions from questions that still need answers.
Prepare a focused platform check-in
Bring the offer description, the affected conversation steps, and your confirmed-versus-open list to a discussion with the CM team. Explain what your business does, where you work, how inquiries arrive, and how you currently follow up. Then ask which available features could support the process you described, what would need to change, and whether any part of the request falls outside the current setup.
CM plan enrollment and app access are arranged manually through guided onboarding, and current feature availability is discussed with the team. The platform subscription and any advertising spend are separate costs. If the new offer also needs website content or SEO work, clarify that separately: SEO has its own agreed scope. The platform discussion should not be treated as confirmation of advertising services, SEO work, or a particular feature unless the team confirms it.
- What specific customer-process change are we trying to support?
- Which relevant features are currently available for our plan?
- Does the proposed change affect inquiry handling, estimate preparation, or follow-up?
- What information or decisions should we provide before any setup change?
- Are platform, onboarding, advertising, or SEO needs being discussed as separate scopes?
Ask the team to confirm availability and next steps before treating a proposed setup change as agreed.
Common questions
Should every new offer get its own workflow?
Not necessarily. First compare the new offer with your existing process. If the same information, handoffs, and follow-up still apply, a separate workflow may add complexity without addressing a real need. If the offer changes what you must ask, how an estimate is prepared, or who handles the next step, document that difference and discuss options with the CM team. The right approach depends on your service and the features currently available.
What should I send before asking about an update?
Send a concise description of the offer, what is included or undecided, the customer details your team needs, and the process steps that may change. Add a short list of confirmed decisions and open questions. You can discuss your plan and arrange guided onboarding with the CM team through the CM platform and guided onboarding. Avoid sending assumptions as if they were confirmed requirements.