A campaign can work, a sale can close, and an order can arrive late. If each function celebrates its result in isolation, no one explains why the customer had a poor experience.
Marketing, sales, and operations form a system of commitments. Coordination starts well before a company hires separate departments: even one person who sells through social media, collects payment, and prepares orders performs all three functions. The U.S. Small Business Administration (SBA) includes operations and post-sale service when explaining why marketing and sales must be planned together [R01]. ASCM uses the term sales and operations planning (S&OP) for the mechanism larger organizations use to reconcile demand, supply, and resources [R02]. Here we adapt that principle to everyday decisions without requiring a corporate structure.
1. Distinguish the three functions without trapping them in an org chart
Marketing identifies audiences worth reaching and communicates an offer through appropriate messages and channels. Its work may generate attention, inquiries, or opportunities; an advertising impression is not a sale. Sales helps a person or organization evaluate terms, answers questions, and turns a decision into a specific agreement: what is being purchased, at what price, when, and within what scope. Operations verifies the agreement can be fulfilled, organizes resources, produces the item or delivers the service, fulfills the order, records execution, and handles exceptions.
| Function | Typical decision | Useful evidence | Risk when working alone |
|---|---|---|---|
| Marketing | Who do we reach, and when? | Relevant inquiries and understandable promises | Attracting orders the business cannot fulfill |
| Sales | What terms can we confirm? | Order with accepted price, scope, and date | Selling a condition no one has checked |
| Operations | How will we fulfill the agreement? | Recorded delivery, payment, quality, and exceptions | Efficiently providing something no one wants |
For example, payment collection may start in sales, be processed by a payment gateway, and be reconciled by administration. Every activity does not need a universally assigned department. What matters is knowing who decides, who executes, and who confirms that the customer received what was promised.
2. Define a shared outcome and avoid competing metrics
Each function needs its own signals, but its objectives should converge on delivered value and sustainable economics. Marketing may lower cost per inquiry by advertising an offer that is too broad; sales may improve its close rate by promising unrealistic deadlines; operations may improve units per hour by rejecting difficult cases without informing customers. All three metrics improve on paper while the experience deteriorates.
When coordination requires a forecast by day or time slot, use the operational demand forecasting guide before turning commercial interest into commitments.
Establish a shared measure, such as accepted orders delivered according to agreed terms, with positive contribution and no critical failures. Do not reduce it to a single score: examine its components. A process-wide perspective makes inputs, outputs, responsibilities, and connections between activities visible [R03].
| Signal | Decision it supports | Caution |
|---|---|---|
| Qualified inquiries | Are people reaching us with compatible needs and coverage? | They are not confirmed orders |
| Committed orders | How many promises must we fulfill by date and time slot? | Keep tentative reservations separate |
| Complete, on-time fulfillment | Did we deliver the agreed quantity, quality, and time? | Do not conceal canceled orders |
| Delays and complaints | Where did a commitment break down? | Severity and cause still need assessment |
| Contribution per order/channel | Does revenue cover variable selling and fulfillment costs? | It is not the company's final profit |
3. Map the entire flow: from promise to service recovery
Start when someone receives a message and end when fulfillment and any subsequent commitments are resolved. A minimum map is: message or campaign → inquiry → coverage and availability check → offer and terms → order acceptance → capacity reservation → preparation or service delivery → quality control → fulfillment → payment or outstanding balance → support and learning.
To turn this cross-functional agreement into executable steps, map the complete operating and logistics workflow, including owners and exceptions.
At each arrow, write down the information that must cross it. An inquiry without a date, address, or specific need is not automatically a firm order. If a sale is confirmed but nobody reserves the required materials or time slot, operations does not have an executable commitment. If delivery happens but an outstanding refund is never recorded, the business has not finished handling the transaction.
Do not assume a perfect sequence. A customer may pay before or after delivery, change the order, cancel, request an invoice, or reject a substitute. Draw at least one alternative route for a common failure. ASQ recommends checking process maps with the people who perform the work and examining unclear handoffs and sources of errors [R04].
4. Establish a minimum information-handoff contract
A handoff is not merely “I mentioned it in chat.” It transfers a commitment another person can execute without guessing. Record the following for each confirmed order:
| Minimum field | Illustrative example | Who maintains it |
|---|---|---|
| Identifier and status | AC-042 · confirmed | Sales owner |
| Offer, quantity, exclusions | 2 lunches, no beverage | Person confirming terms |
| Price, method, payment status | S/ 80, card, paid | Payment-control owner |
| Coverage area, time, necessary contact | Covered zone, 12:30–13:00 | Sales, validated by operations |
| Reserved capacity or materials | 2 kitchen and delivery slots | Operations |
| Change, incident, authorization | Customer asks for 13:30, pending | Commitment owner |
Collect only the personal data needed, with access and retention appropriate to the activity and applicable law. The same record should be the shared reference; forwarding three contradictory screenshots creates three competing versions of the promise.
Acceptance rule: a request moves to “confirmed” only after its price, terms, and relevant capacity have been verified. If something remains uncertain, say “pending confirmation” rather than inventing a date.
5. Assign ownership, decision authority, and internal service rules
Distinguish the person performing the task, the person authorized to decide an exception, and the person communicating with the customer. One person may fill all three roles in a microbusiness. In a team, for example, sales records the order, operations validates the slot, an authorized owner approves a substitution, and customer service communicates the option. You need not teach a full RACI matrix again: identify decision ownership and accountability at handoffs where failures arise.
When multiple people can approve or perform the same decision, use the RACI responsibility matrix to clarify authority without duplicating owners.
An internal service rule can be as simple as “do not offer same-day delivery without checking capacity before 11:00,” “changes after cutoff require a new confirmation,” or “do not dispatch an order without a verified address.” These rules are not universal legal promises; adapt them to the offer, communicated terms, and buyer rights.
When a third party distributes, collects, or delivers, include how its status is tracked and who acts when it fails. A customer should not need to discover which external supplier is at fault before receiving an answer.
6. Resolve the conflict between commercial volume and capacity
When demand increases, the answer is not to accept everything and “figure it out later.” Before a promotion compare expected requests, existing committed orders, capacity by time slot, materials, personnel, and required cash. Distinguish daily capacity from the capacity of the promised hour: being able to handle 60 orders during a day does not mean delivering all 60 at noon.
When demand exceeds capacity, options include displaying a limited number of slots, opening another time window, offering a wait with consent, shortening or changing a promotion, maintaining a waitlist, or transparently declining a request. Each option has costs and consequences; an extra discount does not automatically compensate for a broken promise. Record who approved the new limits and what messaging changed.
Do not hide declined inquiries. They may indicate unmet demand, but they are not completed sales or guaranteed future conversions. The distinction becomes essential when forecasting demand and calculating capacity.
7. Establish a short coordination cadence
A ten-minute routine can be more useful than lengthy reports. Before the critical period, review (1) confirmed orders, (2) new inquiries and promotions, (3) capacity and materials by slot, (4) open risks and incidents, and (5) pending decisions and communications. At the end, record what was delivered, what was not, who still needs an answer, and what data must be corrected.
A microbusiness can review a single sheet once a day and before advertising a campaign. A small team may agree to a daily commercial–operations check-in and a weekly view of future demand. An organization with multiple product lines and supply chains may use a more formal S&OP process [R02]. Review frequency should fit the pace of decisions, not a methodology's calendar for its own sake.
A productive meeting leaves a minimal record: decision, reason, owner, deadline, and expected effect on commitments. If the only output is a discussion with no decisions, coordination is not working.
8. Track shared indicators and early warning signs
More inquiries do not automatically mean success. Consider commercial and operating signals together. If 50 inquiries arrive but only 30 match the supported coverage and schedule, the qualified-inquiry rate for the period is 30/50 = 60%; this does not mean 30 orders were sold. If 23 out of 25 committed orders are delivered completely and on time, fulfillment is 23/25 = 92%, assuming that legitimate cancellations did not change the denominator.
Define what is counted, over what period, and how cancellations, returns, and date changes are handled. Add practical alerts: confirmed orders without reserved capacity; campaigns with insufficient slots; complaints beyond an internally defined severity threshold; contribution by channel approaching zero; and rescheduled deliveries without explicit confirmation. A small dashboard with clear definitions beats twenty indicators nobody owns.
9. Keep a commitment and exception log without erasing history
A commercial or operational exception should include ID, affected order, time, original promise, deviation, impact, offered response, customer acceptance where appropriate, owner, review date, and evidence of closure. It does not replace a full complaint-management system; it makes responsibilities visible while the order remains open.
Separate an immediate correction from later improvement: informing a customer and offering another time resolves the immediate situation if accepted; understanding why campaigns repeatedly exceed slots requires further investigation. The detailed handling of complaints and procedures belongs in other zoom-ins in this pillar.
10. Avoid five coordination mistakes
Optimizing functions in isolation: do not reward lead volume or close rate alone. Duplicating records: decide where the current order lives. Launching campaigns without notice: integrate available slots before communicating. Handing off without ownership: an unanswered chat is not a confirmation. Automating before agreeing on rules: a system can spread an incorrect promise faster.
The objective is not to multiply approvals. A proportional rule resolves routine decisions quickly and gives exceptions a clear route.
Worked example: “Lunch Nearby” receives twice as many requests
Hypothetical case; quantities and times are illustrative. A normal day brings 24 qualified lunch inquiries. A promotion increases the number to 48. For the 12:30–13:00 window, kitchen and delivery operations have 36 verified slots; there are not 48 slots just because 48 people are interested. Assume all 48 requests contain the necessary information and ask for the same window, but none is yet a confirmed order.
Before accepting new orders, the team agrees to cap that window at 36 orders, offer the other 12 a second time slot only if operations verifies its capacity and each customer accepts it, and suspend the advertising message promising delivery at 12:30 once the first window fills up. The other 12 requests do not automatically become sales.
| Step | Functional owner | Decision and evidence |
|---|---|---|
| Marketing | Communication | Updates the message to show real slots and times |
| Sales | Confirmation | Records up to 36 orders subject to availability; checks alternatives with the other 12 |
| Operations | Fulfillment | Reserves up to 36 slots and validates a possible second window |
| Customer service | Recovery | Communicates changes, records declines, and confirms consent |
If 36 orders were confirmed and fulfilled, the fraction of initial inquiries converted into deliveries would be 36/48 = 75%. This does not describe future campaign performance or total market demand. If the second slot is confirmed, each additional order is recorded under its own window; otherwise, the business clearly explains the limit and retains an aggregate count of unmet inquiries, without making promises.
Decision: protect fulfillment before expanding the campaign. At close, compare accepted promises to what was actually delivered, unconverted inquiries, reasons, and complaints. Only then consider capacity adjustments, subject to repeatable demand and costs.
Template: minimum coordination system
| Record | Fields to fill out | Review rule |
|---|---|---|
| Handoff map | Stage, input, owner, check, output | Review after errors or offer changes |
| Shared order | ID, status, price, terms, slot, capacity, payment | Update for every confirmed change |
| Daily plan | Firm orders, slots by window, active campaigns, exceptions | Review before accepting critical orders |
| Decisions and exceptions | ID, risk/deviation, decision, owner, communication | Keep open until verifiable closure |
Start with one offer and a week of activity. If someone cannot answer what was promised, who confirmed it, and how it was fulfilled, fix the handoff before adding tools.
What you should have by the end
A map from first inquiry to fulfillment, owners for critical points, a single commitment log, a capacity-confirmation rule, a coordination routine, and a small set of shared metrics. You have not proven that growth is advisable: you have established how to sell without separating the promise from the ability to fulfill it.
References
- [R01] U.S. Small Business Administration, Manage your business — Marketing and sales. https://www.sba.gov/counseling/manage-your-business/
- [R02] Association for Supply Chain Management (ASCM), Sales and Operations Planning (S&OP). https://www.ascm.org/topics/sales-and-operations-planning/
- [R03] American Society for Quality (ASQ), Process View of Work. https://asq.org/quality-resources/process-view-of-work
- [R04] ASQ, What is a Flowchart?. https://asq.org/quality-resources/flowchart