The service page says, "We connect any accounting system." Sales promises a report using the client's own measures, then the specialist explains at the first meeting that only two systems and standard tables are supported. The client has already spent time preparing an export. The CRM closes the deal as "product did not fit", although the company created the expectation itself.
Take the analytics reporting service for small retail chains from the strategy lesson: a monthly package at 60,000 ₸, variable fulfilment of 20,000 ₸ and contribution of 40,000 ₸. Prices, terms and figures in the example are made up. The shared process exists so that the same offer travels from advertising to delivered service, and any mismatch goes straight to the person who can fix it.
One offer sheet
The sheet records what the team is authorised to promise. It has an owner, version and change date. A salesperson can explain the service in the client's language, but a new capability or deadline first needs confirmation from the owner of that part of the product.
The service's sheet looks like this:
| Part | Terms in the example |
|---|---|
| Client | A small retail chain needing to consolidate sales and assortment data |
| Compatibility | Two accounting systems on a confirmed list; versions and export format are established before the pilot |
| Start | The specialist accepts a permitted export and agrees the start date with the client |
| Pilot | Seven calendar days at no charge, with one sample report on agreed data |
| Boundary | Standard tables; a new integration and custom report are outside the pilot |
| After the pilot | The client separately agrees to the monthly service at 60,000 ₸ and pays |
| Ownership | The product owner confirms terms; the coordinator updates touchpoints |
A free pilot is a choice for this example. Another service might charge for it, which should be stated before the enquiry. Both need a starting point, deliverable and next step. Otherwise, "seven days" on the website and "a week after we sort out the data" from the specialist become different services.
Confirm compatibility against the actual export. A system name in an enquiry may not be enough: versions, permissions and data structures differ. Before the specialist has inspected the file, sales can promise to assess connectivity rather than a completed integration.
What changes with the sheet
When terms change, the coordinator lists where they appear: ads, page, form, enquiry confirmation, pilot email, presentation, CRM prompts and support responses. Each location gets a change owner. The new version then becomes more than a file known only to the meeting participants.
Handle existing promises separately. A client may have booked through an old ad. Sending a new link does not change what they were told yesterday. Sales explains the difference and agrees on a deliverable option with the product owner, recording the agreement.
Product Marketing Alliance connects product marketing with market understanding, positioning, sales preparation and launch. Different people may perform these tasks in a small team. The offer coordinator moves changes through the process; authority over product capabilities remains with the product owner.
When an enquiry can move forward
A suitable enquiry for the service is a company with the task in the offer sheet, supported data and willingness to discuss a pilot. A phone number or email enables contact but does not answer those questions. The CRM needs the fields without which the next person cannot do their part.
Every enquiry needs an owner, next action and deadline. Sales receives the promise from the originating ad or page and what is known about the company's task. If the export needs checking, assign that to a specialist. Until compatibility is confirmed, the status should reflect that uncertainty.
Choose response times around working hours and customer expectations. A daytime team cannot promise an evening enquiry a call within a few minutes. State the available process on the page and in the confirmation; the CRM helps expose queues and overdue actions.
Review one hundred enquiries
For a separate review, take 100 unique new enquiries after the agreed handling window. This is a different set from the channel table in the P&L. At the review date, each lead belongs to exactly one group:
| State | Enquiries | Next action |
|---|---|---|
| Suitable task and data | 60 | Follow progression into a pilot and payment |
| Require an unsupported system | 20 | Find the source of the compatibility promise |
| Insufficient information to assess | 10 | Assign clarification and a deadline |
| Nobody has handled them | 10 | Restore handoff and ownership |
60 + 20 + 10 + 10 = 100. Confirmed suitable enquiries are 60% of the whole set. Among the 80 assessed for fit, they are 75%, but the other twenty can still change the overall picture. Writing "75% of leads are good quality" drops from the report twenty enquiries about which nothing is known yet.
Merge repeated enquiries from one company under the agreed ID. Use the same assessment window when comparing channels. A fresh enquiry that a manager has not reviewed yet should not automatically become bad quality. Closed enquiries also need a reason: unsupported system, different task, rejected timing and rejected price call for different actions.
What a wrong promise costs
Suppose the manager and specialist spent a combined 30 minutes of staff time on each of the twenty companies with an unsupported system. That is ten hours. At an internal valuation of 5,000 ₸ per hour, the company used 50,000 ₸ of capacity before explaining a limit it could have shown before the meeting.
This values time; it is not automatically lost cash or sales. If pay is fixed, that money is already inside P&L fixed expenses. Do not deduct another 50,000 ₸ from profit. Reducing these conversations frees time for suitable clients; whether that becomes extra payments depends on the work that follows.
Investigate causes through the enquiries themselves. If the client came from an "any system" ad, fix the ad. If they understood the limitation but still asked about a new integration, send the request to product as research input. Twenty requests do not yet require building it: establish the task, willingness to pay, support cost and strategic fit.
End the shared meeting with an action
Marketing brings promises and enquiry sources. Sales brings status and reasons. Product confirms delivery capability. Together they choose an action: remove an unsupported claim, change a form question, assign the queue or investigate a new task.
Each action has an owner, deadline and check. After correcting an ad, walk the path yourselves, then review a comparable set of enquiries. If lead volume falls while the suitable share rises, the final decision also depends on payment counts and costs. One convenient metric cannot replace the whole journey.
Reconcile payments using the financial source and deal ID. The ad account, CRM and payment system may describe the same purchase, so their revenue cannot be added. The shared result is paid service delivered and contribution after costs; each stage retains its own quality and timing metrics.
Exercise: forty bad leads
Take your product's ten most recent enquiries. Put the ad or source, page, first message and CRM record side by side. Find a difference in the promise or establish that terms match. Name the fix owner and the handoff criterion for the next participant.
Now the manager looks at the hundred-enquiry table and says, "Forty are bad. Switch the channel off. And those ten unhandled leads cost us 600,000 ₸ revenue." Which parts need correcting?
Twenty require an unsupported system, ten lack information and ten are unhandled. These groups need different actions. Lost sales from the unhandled ten are unknown; they cannot be treated as ten guaranteed payments. In a scenario where two would have paid, first-month revenue would be 120,000 ₸, fulfilment 40,000 ₸ and contribution 80,000 ₸ before acquisition and fixed expenses. That remains an estimate of a possible result until the clients' actual circumstances are known.
The practical response names owners for fixing the promise, clarifying data and restoring handling. The channel decision uses a comparable picture of payments and costs after that review.