| Course | MKT 443 Customer Relationship Management |
|---|---|
| Topic | Topic 4 |
| Paper type | Current-state process map |
| Length | About 980 words, 2 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | BS in Marketing |
| Updated | October 2026 |
Free sample paper for MKT 443 Topic 4
Quote to Delivery as It Runs Today: A Current-State Process Map for an Equipment Rental Branch, Drawn Before Any Software Is Chosen
[Author Name]
Colangelo College of Business, Grand Canyon University
MKT-443: Customer Relationship Management
Topic 4 Process Map
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Quote to Delivery as It Runs Today: A Current-State Process Map for an Equipment Rental Branch, Drawn Before Any Software Is Chosen
Why Map Before Choosing
A composite construction equipment rental company had sat through two vendor demonstrations of customer relationship management software when its operations manager asked a simple question: what is our quote-to-delivery process today? Nobody could draw it. This map records that process as it actually runs at one branch, based on two weeks of observing 86 quotes. Hammer (1990) warned that automating a process without first examining it mostly makes an inefficient process run faster. Rummler and Brache (1995) argued that the biggest opportunities for improvement usually lie in the handoffs between departments, the white space on the organization chart, which nobody owns. A current-state map makes those handoffs visible. All figures are illustrative.
The Lanes
The map is a swimlane diagram with five lanes, one for each party in the process: the customer, the counter staff who take calls, the branch manager who approves pricing, the yard crew who check and prepare equipment, and the driver who delivers it. Each step is placed in the lane of whoever performs it, and arrows between lanes mark handoffs.
The Steps
Table 1 lists the steps in order, with what triggers each one and the median time it waits before the next step begins. On the diagram, every wait is labeled in hours and every rework loop is drawn in red.
Table 1
Quote-to-Delivery Steps at One Branch, Two Weeks of Observation, Illustrative
| Step | Lane | Trigger | Median wait before next step |
|---|---|---|---|
| 1. Customer calls or emails for a quote | Customer | Job needs equipment | None |
| 2. Counter staff record the request on a paper form | Counter | Call received | About 0.5 hours |
| 3. Counter staff walk to the yard to check the availability whiteboard | Counter, then yard | Form complete | About 1 hour |
| 4. Counter staff enter the quote in the rental system | Counter | Availability confirmed | About 1 hour |
| 5. Quote sent to branch manager for price approval | Manager | Any quote over the standard rate or with a discount | About 26 hours |
| 6. Approved quote emailed to customer | Counter | Approval received | About 2 hours |
| 7. Customer accepts | Customer | Quote received | Varies |
| 8. Yard crew prepare and inspect equipment | Yard | Acceptance entered | About 6 hours |
| 9. Driver delivers | Driver | Equipment ready and truck free | About 4 hours |
What the Map Shows
The picture is not flattering. A quote passes through three handoffs before it reaches the customer: counter to yard, yard back to counter, and counter to manager. The longest wait by far is for the manager's price approval, a median of 26 hours, because the manager reviews approvals between site visits and most quotes need one. Customers who called in the morning often did not receive a quote until the next afternoon, and several told counter staff they had already rented from a competitor.
The map also shows a rework loop. About one in five quotes, 18 of the 86 observed, was keyed twice. Availability lives on a whiteboard in the yard, updated by the yard crew when equipment comes back, and it was often out of date. When a counter employee entered a quote for a machine the board showed as available, then learned it was still out on another job, the quote had to be re-entered for a different machine, sometimes after the manager had already approved the first price.
Problems Software Would Only Speed Up
Some of these problems a CRM system would help with, but only by making the current process faster. Moving the paper request form into the system would save the half hour of transcription. Emailing quotes automatically would save some of the two hours after approval. These gains are real but small compared with the 26-hour approval wait, and software alone would not touch that wait: a manager who reviews approvals between site visits would do the same thing on a phone screen.
Problems a Policy Could Remove This Month
Other problems need a decision, not software. Most of the approval wait exists because nearly every quote needs approval. If counter staff could approve quotes within a set band, for example up to 10 percent below the standard rate for existing customers, the manager would see only the exceptions, and most quotes would skip the 26-hour wait entirely. That policy could start this month. Similarly, the double keying exists because availability is kept on a whiteboard. Asking the yard crew to mark returns in the rental system they already have, rather than on the board, would remove most of the rework loop without buying anything.
How the Map Was Built
The map came from observation rather than interviews alone. For two weeks, the operations manager sat with counter staff for part of each day and logged every quote: when the request arrived, when each step began and ended, and who handled it. Interviews were used afterward to explain what the log showed, such as why the manager reviews approvals between site visits. Building the map from observed times matters because people describe the process as they believe it runs, and the waits they forget, such as walking to the yard to read the whiteboard, are often the ones that add up.
What This Means for the Software Decision
Payne and Frow (2005) described CRM as a set of cross-functional processes, of which technology is only one support. The map shows that the branch's slowest points are a pricing policy and an availability record, not missing software. The recommendation is to make the two policy changes first, measure quote turnaround again after a month, and then evaluate software against the improved process. Vendors should be asked to show how their system handles the counter staff's approval band and live availability, rather than to demonstrate features in general. A future-state map, drawn after the policy changes have run for a month, should become the specification the vendors are asked to meet.
References
Hammer, M. (1990). Reengineering work: Don't automate, obliterate. Harvard Business Review, 68(4), 104-112.
Payne, A., & Frow, P. (2005). A strategic framework for customer relationship management. Journal of Marketing, 69(4), 167-176. https://doi.org/10.1509/jmkg.2005.69.4.167
Rummler, G. A., & Brache, A. P. (1995). Improving performance: How to manage the white space on the organization chart (2nd ed.). Jossey-Bass.
The MKT-443 Topic 4 assignment instructions
In Topic 4, MKT-443 asks students to document a current business process before selecting technology. Strong maps use swimlanes for each party, record each step's trigger and wait from observation, and mark handoffs and rework loops. Students should explain why mapping comes first with research on process improvement, describe how the map was built, separate problems software would merely speed up from problems a policy decision could remove, and state what the map means for the software decision, including how vendors should be evaluated. The commentary should say which fixes need software and which need only a decision.
How this MKT 443 Topic 4 example is built
The finished map is a swimlane diagram with five lanes: the customer, the counter staff who take calls, the branch manager who approves pricing, the yard crew and the driver. Each step carries a label for what triggers it and how long it waits, drawn from two weeks of observed quotes and labeled illustrative. The picture is not flattering. A quote passes through three handoffs, waits a median of 26 hours for a manager's price approval, and about one in five is keyed twice because availability lives on a whiteboard in the yard. Every rework loop is marked in red and every wait in hours. Beside the drawing, a short commentary separates the problems software would merely speed up from the ones a policy decision could remove this month.
MKT 443 Topic 4 rubric: what Excellent looks like
Faculty reward a map drawn from observation, not memory. An Excellent map places nine steps in five lanes with triggers and median waits. Credit goes to Hammer on not automating a broken process and Rummler and Brache on handoffs. The rubric values finding the 26-hour approval wait and the double keying caused by the yard whiteboard. Strong maps explain that logged times caught waits people forget. Top marks go to separating software gains from policy fixes, such as an approval band for counter staff, and testing vendors against the improved process.
MKT 443 Topic 4 help: mistakes that cost marks
Mapping the procedure manual instead of the work is the costliest mistake, because the documented process is usually the one nobody follows. A diagram with steps but no times shows sequence and hides where the customer actually waits. Drafts frequently skip the rework loops, and those loops are where duplicate keying, and later bad data, begin. Proposing software for every problem on the map misses the point of drawing it: some delays exist because of an approval rule, and a faster screen keeps the rule in place. Without a stated boundary, the map sprawls into billing and returns and never finishes. Another recurring loss comes from mapping the ideal future process first, which lets a vendor's standard workflow replace the analysis of what is broken now.
Get an MKT-443 Topic 4 example written to your instructions
Send the MKT-443 Topic 4 instructions and the rubric your classroom posts, with the organization or process your section assigned. We write a custom example to those criteria, with the boundary stated, steps observed and timed, handoffs, waits and rework marked and the fixes needing no software listed first, in 24 to 48 hours. The first one is free.
More MKT 443 papers and BS in Marketing samples
- MKT 443 Topic 1: Crm Purpose Statement
- MKT 443 Topic 2: Customer Data Quality Audit
- MKT 443 Topic 3: Identity Resolution Analysis
- MKT 443 Topic 5: Crm Data Entry Dq Post
- MKT 443 Topic 6: Personalization Boundary Analysis
- MKT 443 Topic 7: Post-launch Usage Review
- MKT 443 Topic 8: Crm Adoption Plan
- MKT 433 Topic 4: Compensation Plan Behavior Audit
- MKT 415 Topic 4: Reach and Frequency Media Plan
- MKT 315 Topic 4: Targeting Refusal Memo
- MKT 345 Topic 4: Attitude-behavior Gap Paper
MKT 443 Topic 4 questions, answered
What is a swimlane diagram?
A process map divided into horizontal or vertical lanes, one for each person, role or department, with every step drawn in the lane of whoever performs it. Arrows crossing between lanes show handoffs, which is where delays and lost information tend to gather. The layout makes it easy to see how often work changes hands, something a simple flowchart of steps leaves hidden.
Why map the current process before choosing software?
Because a system configured around an unexamined process preserves its faults and adds licensing costs. If quotes wait a day for a manager's approval, a CRM will record that wait precisely without shortening it. Mapping first separates problems that software solves, such as re-keying, from problems created by policy or habit, which cost nothing to fix and should be fixed before any purchase.
How are the wait times in the example measured?
By following real quotes from call to delivery over two weeks and noting when each step started and finished, a simple form of time study. The figures are labeled illustrative because the company is a composite, and in your own paper they would come from observation, system timestamps or the case data your section supplies. Medians are reported because a few very slow quotes would distort an average.
Where can I find a free MKT 443 Topic 4 sample paper?
The process map and commentary are shown here in full: why map before choosing, the lanes, the steps, what the map shows, how it was built, what software would only speed up, what a policy could remove and what it means for the software decision. Describe your process and we will map it at no cost.
Why is the approval wait a policy problem in MKT 443 Topic 4?
Nearly every quote needs the manager's approval, so quotes wait a median of 26 hours. Letting counter staff approve within a set discount band would remove most of that wait without any new software.