MKT 443 Topic 7 post-launch usage review example

Customer Relationship Management Grand Canyon University Free custom sample in 24 to 48h

This MKT 443 Topic 7 sample paper reviews a composite staffing agency's CRM nine months after launch, setting aside the vendor's 140 licenses and full training as outputs, not outcomes. It is part of GCU MKT 443, Customer Relationship Management, catalog code MKT-443, in the Grand Canyon University BS in Marketing. In a typical week 58 license holders change a record. All four key job-order fields are complete 46 percent of the time. The Eastside branch records about 94 percent of orders by running its Monday meeting from the system, while two branches keep a spreadsheet, and lapsed-client calls brought 23 new orders.

CourseMKT 443 Customer Relationship Management
TopicTopic 7
Paper typePost-launch usage review
LengthAbout 970 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramBS in Marketing
UpdatedOctober 2026

Free sample paper for MKT 443 Topic 7

1

140 Licenses Is Not an Outcome: A Nine-Month Usage Review of a Staffing Agency's CRM by Activity, Completeness and Changed Decisions

[Author Name]

Colangelo College of Business, Grand Canyon University

MKT-443: Customer Relationship Management

Topic 7 Usage Review

[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.

What this page is doingThe title states what the review refuses to count and the three things it counts instead. The agency and every figure are a composite; the sources are real.
2

140 Licenses Is Not an Outcome: A Nine-Month Usage Review of a Staffing Agency's CRM by Activity, Completeness and Changed Decisions

The Vendor's Figures

Nine months after a composite staffing agency went live on its customer relationship management system, the vendor's closing report declared the project a success: 140 licenses deployed and every recruiter and account manager trained. Both statements are true. Neither describes an outcome. A license shows that someone can use the system; training shows that they were shown how. Neither shows that anyone uses it, that what they enter is useful, or that the agency works differently because of it. This review measures those three things instead. All figures are illustrative.

Who Actually Uses It

In a typical week over the last quarter, 58 of the 140 license holders, about 41 percent, created or updated at least one record. The review counts logins without any change separately, because opening a screen proves little: another 31 license holders logged in during a typical week without changing anything, many of them looking up a phone number they could have found elsewhere. The remaining 51 did not log in at all.

Whether Records Carry What Matters

Account managers need four fields on every job order to fill it: the client contact, the pay rate, the start date and the required certifications. Across job orders created in the last quarter, all four were complete in 46 percent of cases. Pay rate was the field most often missing, usually because it was agreed by phone and recorded only in the account manager's email. A job order without a pay rate cannot be matched to candidates in the system, so recruiters call the account manager instead, which is what the system was meant to replace.

Usage by Branch

Usage splits sharply by branch. The Eastside office runs its Monday meeting from the system's open-orders view: each account manager walks through their open orders on the screen, and anything missing is filled in during the meeting. Eastside records about 94 percent of its job orders in the system, with all four fields complete on most of them. Two other branches still work from a shared spreadsheet that predates the system, entering orders in the CRM afterward if at all; they record fewer than half their orders there.

Table 1

What the Review Measured, Illustrative

MeasureResultWhat it shows
Licenses deployed140Capacity to use the system, not use
Weekly users who create or update records58 of 140 (about 41%)Actual use
Weekly logins without changes31Lookups only
Job orders with all four key fields46%Whether records are useful
Eastside orders recorded in the systemAbout 94%Use where meetings run from it
Two spreadsheet branchesUnder half of orders recordedParallel tool still in charge

Why Eastside Is Different

Eastside's managers did not receive different training or a different system. What differs is that the system is where the branch's weekly work happens. If an order is not in the open-orders view, it is not discussed in the Monday meeting, and an account manager whose order is not discussed does not get recruiters working on it. The system is useful to the people entering data, because it directly affects whether their orders get filled. Usefulness to the person entering data is what drives a system's use (Davis, 1989), and in the unified model of Venkatesh et al. (2003), what users expect a system to do for their own results weighs most heavily. At Eastside, that belief has a concrete basis; at the spreadsheet branches, the spreadsheet still decides what gets discussed.

What the Spreadsheet Branches Say

Interviews with account managers at the two spreadsheet branches explain part of the gap. They say the spreadsheet is faster for entering an order during a phone call, that they can see all their orders on one screen, and that their branch manager still asks for the spreadsheet each week. The first two complaints are partly fair: the system's order form has more fields than they need during a call, and its list view was not set up for their branches. The third is the decisive one. As long as the branch manager runs the week from the spreadsheet, the system remains an extra copy, and account managers are behaving sensibly by keeping their effort where the decisions are made.

One Decision That Has Changed

One decision across the agency has changed because of the system. Account managers now call lapsed clients, those with no job order in six months, from a last-contact list the system produces each Monday. Before the system, nobody tracked lapsed clients systematically. In the last quarter, account managers called about 120 lapsed clients from the list, and 23 placed new orders. This is the kind of result a CRM exists to produce: a decision made differently because the system makes something visible (Payne & Frow, 2005).

Recommendations

The review makes four recommendations. Retire the shared spreadsheets at the two lagging branches on a fixed date, and have their managers run weekly meetings from the open-orders view as Eastside does. Make pay rate a required field before a job order can be saved, with a quick option to mark it pending. Reduce the license count at the next renewal to the people who actually need to enter data, about 90, saving the cost of the rest. And report to leadership each quarter on weekly active users, field completeness and lapsed-client orders, rather than licenses and training.

Conclusion

After nine months, the system is used actively by about four in ten license holders, its job orders are complete less than half the time, and its value is concentrated in one branch and one changed decision. Those are the measures that matter, and they show a project that has worked where it shapes the weekly routine and not yet elsewhere.

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

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

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

The MKT-443 Topic 7 assignment instructions

The Topic 7 brief in MKT-443 asks students to evaluate a CRM after launch. Strong reviews explain why licenses and training are not outcomes, then measure who actually uses the system, whether records carry the fields that matter, how use varies across units and which decisions have changed. Students should explain differences in use with technology acceptance research and evidence from users, recommend specific changes such as retiring parallel tools and requiring key fields, and propose the measures leadership should receive in future. The review should report what users at lagging units say about why they work elsewhere.

Inside the MKT 443 Topic 7 example

The finished review opens with the vendor's two figures and explains why neither describes an outcome. It then reports its own, all labeled illustrative. In a typical week, 58 of the 140 license holders create or update a record, and logins without any change are counted separately, since opening a screen proves little. On job orders created in the past quarter, the four fields account managers need, contact, pay rate, start date and required certifications, are all filled in 46 percent of cases. Usage splits sharply by branch: the Eastside office runs its Monday meeting from the open-orders view and records nearly every order, while two branches still work from a shared spreadsheet. One decision has changed. Account managers now call lapsed clients from a last-contact list the system produces.

Reading the MKT 443 Topic 7 rubric

Faculty reward a review that counts outcomes rather than deployment. An Excellent review separates 58 weekly record-changers from 31 lookup-only logins. Credit goes to measuring complete job orders at 46 percent and finding pay rate most often missing. The rubric values explaining Eastside's 94 percent through its Monday meeting with Davis and with Venkatesh and colleagues. Strong reviews report what the spreadsheet branches say and name one changed decision, lapsed-client calls producing 23 orders. Top marks go to retiring spreadsheets, a required pay field and right-sized licenses.

MKT 443 Topic 7 help: mistakes that cost marks

Repeating the vendor's success figures and stopping there is the surest way to lose credit, because licenses and training certificates measure the project's delivery and say nothing about use. Counting logins as usage runs a close second, since a recruiter can open the system every morning and record nothing in it. Drafts that report one agency-wide adoption rate hide the branch differences that usually explain the problem. Completeness measured across every field in the database produces a low number nobody can act on; scoring the fields a decision depends on produces one somebody can. Papers rarely look for changed decisions, and that is the measure closest to whether the investment mattered. A review closing on more training, with no reference to what set the high-usage branch apart, misses the finding it had already made.

Get an MKT-443 Topic 7 example written to your instructions

Send the MKT-443 Topic 7 instructions and the rubric provided in your classroom, with the implementation or case your section supplied. We write a custom example to those criteria, with deployment figures ranked below use, active users defined, key fields scored, branches compared and changed decisions documented, in 24 to 48 hours. The first one is free.

More MKT 443 papers and BS in Marketing samples

MKT 443 Topic 7 questions, answered

Why are logins a weak measure of CRM adoption?

Because opening an application is not the same as working in it. Staff may log in because a manager checks, because the system opens automatically or to look up one number, and then keep the real work elsewhere. Creating or updating records shows that information is flowing into the system, which is what makes every later report, list and decision possible. The example counts both and trusts only the second.

What does it mean to judge an implementation on decisions changed?

It means asking whether anyone now chooses differently because the system exists. A CRM that stores records nobody consults has cost money and changed nothing. In the example, account managers began calling lapsed clients from a list the system generates, a concrete decision that did not happen before launch. One such case is modest evidence, and the review says so while treating it as the most important finding.

Why compare branches instead of reporting one adoption figure?

Because an average hides the variation that explains it. If one branch uses the system heavily and two barely touch it, the agency-wide figure describes none of them. Comparing branches shows what the successful one does differently, in this case a manager who runs weekly meetings from the system, which gives the agency something specific to copy rather than a general instruction to try harder.

Where can I find a free MKT 443 Topic 7 sample paper?

The usage review is printed here in full: the vendor's figures, who uses the system, whether records carry what matters, usage by branch, why Eastside differs, what the spreadsheet branches say, one changed decision, recommendations and the conclusion. Bring your system's usage data and we will review it free.

Why is Eastside's usage so much higher in MKT 443 Topic 7?

Its Monday meeting runs from the open-orders view, so an order missing from the system is not discussed or worked by recruiters. Entering data directly affects whether an account manager's orders get filled.