BUSI 4004 Week 7 CRM System Review Example

Could a Customer Record System Remember Six Hundred Regulars for Two Counter Clerks? A Feature-by-Feature Review of a Generic Cloud System for a Neighborhood Dry Cleaner, Weighed by Use at the Counter and Costed in Dollars and Hours

Student Name

Walden University

BUSI 4004: Customer Relationship Management for Small Business

Instructor Name

Month Day, Year

Could a Customer Record System Remember Six Hundred Regulars for Two Counter Clerks? A Feature-by-Feature Review of a Generic Cloud System for a Neighborhood Dry Cleaner, Weighed by Use at the Counter and Costed in Dollars and Hours

The Memory Problem

The shop studied all term, an invented Lansing cleaner, serves about 600 regulars and two counter clerks. The clerks know perhaps a hundred regulars by face and preference. For the rest, the shop relies on a basic ticket system that stores a phone number, a running order history and a short free-text note. Earlier work in this course found three things that system cannot do: it sends "ready" texts when a ticket is marked rather than when the order is bagged, it has no way to flag regulars who stop coming, and its notes do not print on garment tags, so pressers never see customers' preferences.

This review asks whether a typical cloud-based customer record and ticketing system for dry cleaners would solve those problems, and at what cost. No specific vendor is named; the features and prices are typical of systems in this category, taken from three vendors' published plans and one demonstration.

Features Weighed by Use at the Counter

Table 1

Features Against the Shop's Needs

Grand River Cleaners is composite; features reflect typical systems in this category.

Reading the Features

The four high-need features all match the problems the shop has already identified. Profile fields for finish preferences would replace the free-text note with something a presser can read on the tag. The bagging scan would stop "ready" texts from going out early, which was the most common complaint in the reviews. And the lapsed-regular report would have flagged the weekly customer who stopped coming in March weeks before anyone noticed.

The medium-need features are useful but not decisive. Photographing a stain at drop-off would settle disputes about whether damage was already there, and consent tracking matters for the data practices discussed next week.

The loyalty points feature is one the shop would not use. Most systems in this category lead their sales pitch with it, but the shop's loyalty proposal later in the course favors free minor repairs over points, so the feature adds nothing here.

Costs in Dollars and Hours

Table 2

First-Year Cost of the System

Prices are typical of published plans in this category; staff wage is the shop's counter rate.

After the first year, the cost falls to about $1,548 a year plus occasional equipment.

Is It Worth It

The retention analysis found that regulars who suffer two or more service failures in a short period leave at a much higher rate, and a weekly regular is worth about $1,500 to $3,600 a year in orders. If the system's bagging scan and tag printing prevent the failures that drive away even two regulars a year, its yearly cost is covered several times over. Reinartz et al. (2004) found that the way firms implement customer relationship management processes was associated with better performance, and that technology alone was not what made the difference. Rigby et al. (2002) warned that many CRM projects fail because firms install software before deciding what customer relationship they want; this shop has done the opposite, defining its needs from its own failures first.

Risks of Adopting It

Three risks stand out. Data migration will expose messy records: duplicate phone numbers, old addresses and notes that do not fit the new fields. The owner's fifteen hours are an estimate and could double. The clerks may resist scanning every bag at a busy counter, and if they skip it, the ready texts fail exactly as before. And a cloud system depends on the shop's internet connection; a backup paper ticket process is needed for outages.

Recommendation

Adopt the system, but implement only the four high-need features in the first three months: profiles, tag printing, bagging-triggered texts and the lapsed-regular report. Add stain photos and consent tracking in the second quarter, and leave loyalty points off. Payne and Frow (2005) describe CRM as a strategy that technology supports rather than a technology in itself; the phased start keeps the clerks' attention on the few features that address the shop's known failures.

References

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

Reinartz, W., Krafft, M., & Hoyer, W. D. (2004). The customer relationship management process: Its measurement and impact on performance. Journal of Marketing Research, 41(3), 293-305. https://doi.org/10.1509/jmkr.41.3.293.35991

Rigby, D. K., Reichheld, F. F., & Schefter, P. (2002). Avoid the four perils of CRM. Harvard Business Review, 80(2), 101-109.