| Course | MKT 443 Customer Relationship Management |
|---|---|
| Topic | Topic 5 |
| Paper type | CRM data entry discussion post |
| Length | About 490 words, 1 pages |
| Format | Discussion post, APA 7 citations |
| School | Grand Canyon University (GCU) |
| Program | BS in Marketing |
| Updated | October 2026 |
Free sample paper for MKT 443 Topic 5
Topic 5 DQ 1: Initial Post and Reply
Sellers Stop Logging When Each Record Costs Minutes and Returns Nothing: A Flooring Distributor's CRM, Month One to Month Six
Initial Post
Sellers abandon data entry once each record costs them minutes and hands them nothing in return. Our composite flooring distributor shows the pattern clearly. Its twelve reps logged about 18 customer visits a week each in the first month after launch and about 3 a week by the sixth. The figures are illustrative, but the three causes behind them are common.
First, the cost was real and the return went elsewhere. Each logged visit took about four minutes on a phone form with eleven fields. The only output was a weekly activity report sent to the regional manager. A rep who logged eighteen visits gave up over an hour a week and received nothing that helped sell flooring.
Second, reps recorded everything twice. Most kept their own spreadsheets of jobs, contractors and contacts, because the CRM did not show them what they needed, such as which contractors had projects starting next month. Entry into the CRM was an extra copy, not a replacement.
Third, the data began to be used against them. By month three, activity counts appeared in pipeline reviews as criticism of reps who logged fewer calls. Reps learned that a logged call was evidence that could be used to question them, and the safest number to log was a small one.
In Davis's original studies, how useful people expected a system to be for their own work predicted their use of it better than how easy it was to operate (Davis, 1989). A later synthesis of eight acceptance models reached the same ranking, putting expected gains in personal job results first among the predictors of intent (Venkatesh et al., 2003). On both counts, this system gave reps no reason to use it.
My proposed change is one thing a rep actually wants: a pre-call summary on the phone before each visit, showing the contractor's open jobs, last three orders and any unresolved complaint. To produce it, the system needs the visits logged, so logging finally returns something to the person doing it. I would also cut the form to four fields.
Reply to Sam
Sam, you argue that the reps are simply resisting accountability and that the company should require a minimum number of logged visits, with logging tied to bonuses. I agree that managers are entitled to know what their sellers are doing, and a minimum might raise the counts quickly. My concern is what it would raise. Reps who are paid to log visits will log visits, including short drop-ins and calls that would not otherwise be recorded, and the data will become less useful as it grows. The month-three reviews already showed that reps adjust what they log to protect themselves. A requirement treats the symptom. If the system gave reps a reason to open it before every visit, would a quota still be needed?
References
Davis, F. D. (1989). Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS Quarterly, 13(3), 319-340. https://doi.org/10.2307/249008
Venkatesh, V., Morris, M. G., Davis, G. B., & Davis, F. D. (2003). User acceptance of information technology: Toward a unified view. MIS Quarterly, 27(3), 425-478. https://doi.org/10.2307/30036540
Reading the GCU MKT 443 Topic 5 instructions
MKT-443 Topic 5 asks students to explain why salespeople stop entering data after a CRM launch. A strong post states its position first and supports it with specific evidence about the time each entry costs, what the system returns, duplicate record keeping and how the data is used, connecting these to technology acceptance research. Students should propose a change that gives users something they value. The reply should take a classmate's view seriously, show what a mandate would and would not achieve, and end with a question.
How the MKT-443 Topic 5 example is put together
Its first sentence carries the position: sellers abandon entry once each record costs them minutes and hands them nothing in return. The flooring distributor supplies three pieces of evidence, all labeled illustrative. Each logged visit took about four minutes on a phone form, while the only output was a weekly activity report sent to the regional manager. Most reps still kept their own spreadsheets of jobs and contacts, so the system asked them to record everything twice. And activity counts began appearing in pipeline reviews as criticism, which taught reps that a logged call was evidence against them. The post connects these to Davis's technology acceptance model, where perceived usefulness and ease of use shape whether people adopt a system, and proposes one change: a pre-call summary the rep actually wants.
MKT 443 Topic 5 rubric: what Excellent looks like
Faculty reward a post that locates the cause in the exchange. An Excellent post starts from the exchange: each entry costs minutes and returns nothing to the rep. Credit goes to three pieces of evidence: four-minute entries feeding only a manager's report, parallel spreadsheets and activity counts used as criticism. The rubric values Davis on perceived usefulness and Venkatesh and colleagues' unified model. Strong posts propose a pre-call summary and a shorter form. The highest marks reward a reply arguing that paying for logged visits would inflate the data rather than improve it.
Common MKT 443 Topic 5 mistakes, and how to avoid them
A character explanation, lazy or resistant salespeople, sinks more posts than anything else, because it offers no fix and ignores that the same reps logged faithfully in the first month. Recommending more training misses almost as badly, since the reps know how to use the form and have concluded it is not worth using. Many drafts name the technology acceptance model and never locate usefulness or ease of use in the case, which turns a citation into decoration. Overlooking the private spreadsheets misses the double entry that makes every record cost twice. Proposals to mandate logging, or to pay on it, raise counts while degrading what the counts mean, and many rubrics reward noticing that trade. The reply draws marks down too when it echoes the classmate's proposal without testing what mandatory entries would record.
Get an MKT-443 Topic 5 example written to your instructions
Send the MKT-443 Topic 5 discussion question and the rubric shared in your classroom, with the company or scenario your section named. We write a custom example to those instructions, with a direct answer, causes shown in case evidence, adoption theory applied and one concrete return proposed, plus a reply that tests an idea, 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 4: Current-state Process Map
- 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 5: Pipeline Optimism Dq Post
- MKT 415 Topic 5: Effective Frequency Dq Post
- MKT 315 Topic 5: Positioning Dq Post
- MKT 345 Topic 5: Purchase Intention Dq Response
MKT 443 Topic 5 questions, answered
Why does training not fix low CRM adoption?
Because most users who stop entering data know how to do it. They have judged that the effort returns too little, or that the records will be used against them. Training changes knowledge, and knowledge was not the problem. It helps where a system is genuinely confusing, and the example concedes that, but it cannot make an unrewarding task worth doing.
What is the technology acceptance model?
A model proposed by Fred Davis holding that people adopt a technology largely according to two beliefs: that it will help them do their work, perceived usefulness, and that it will be easy to use, perceived ease of use. Later versions added factors such as social influence. In the example, the phone form was reasonably easy and plainly not useful to the rep, which predicts exactly the decline recorded.
Would paying salespeople to log activity solve the problem?
It would raise the number of entries and probably lower their value. When a count is rewarded, people produce what is counted, so calls get logged that were brief, repeated or never happened. The pattern is often described as Goodhart's law, the observation that a measure turned into a target stops measuring well. The example's reply grants the short-term rise and argues that a useful return lasts longer.
Where can I find a free MKT 443 Topic 5 sample paper?
The discussion post and reply are printed here: the position, three causes from the flooring distributor, the research and the proposed change, and the reply on mandates. Bring the discussion question from your course and the initial post will be written free.
What change does the post propose in MKT 443 Topic 5?
A pre-call summary on the rep's phone showing the contractor's open jobs, last three orders and any open complaint, which requires logged visits to produce, plus cutting the entry form from eleven fields to four.