MKT 443 Topic 1 crm purpose statement example

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

This MKT 443 Topic 1 sample paper is a purpose statement for a composite heating and cooling contractor whose owner wants a CRM because two rivals bought one. It was written for GCU MKT 443, Customer Relationship Management, catalog code MKT-443, in the Grand Canyon University BS in Marketing. It names no software. Three jobs replace the owner's reason: tune-ups offered to all 2,400 agreement customers, up from 61 percent reached before June; equipment history on technicians' phones; and follow-up on the 38 percent of estimates left silent. Each job names who enters what, how long it takes and what they get back.

CourseMKT 443 Customer Relationship Management
TopicTopic 1
Paper typeCRM purpose statement
LengthAbout 1,020 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramBS in Marketing
UpdatedOctober 2026

Free sample paper for MKT 443 Topic 1

1

What Will Be Different on an Ordinary Tuesday: A CRM Purpose Statement for a Heating and Cooling Contractor That Names No Software

[Author Name]

Colangelo College of Business, Grand Canyon University

MKT-443: Customer Relationship Management

Topic 1 CRM Purpose Statement

[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 the question the purpose statement answers first. The contractor and every figure are a composite; the sources are real.
2

What Will Be Different on an Ordinary Tuesday: A CRM Purpose Statement for a Heating and Cooling Contractor That Names No Software

The Reason Set Aside

The owner of a composite heating and cooling contractor wants a customer relationship management system because two competitors bought one last year. That is an understandable reason and a poor basis for a decision. Rigby et al. (2002) found that a common cause of failed CRM projects is implementing the technology before deciding what customer strategy it should serve. Payne and Frow (2005) described CRM as a strategic process for creating value with customers, of which the technology is only one part. This statement therefore sets the competitors aside and asks a harder question: once a system is running, what will be different on an ordinary Tuesday, and who will have to type what to make it so? No vendor or product is named. All figures are illustrative.

Job One: Every Agreement Customer Offered a Spring Tune-Up

The contractor has about 2,400 customers on maintenance agreements, each entitled to a spring tune-up of their air conditioning before the summer rush. Today, offering it depends on the dispatcher remembering, working from a paper list she rebuilds each March from invoices. Last spring about 61 percent of agreement customers had their tune-up before June; the rest were reached late or not at all, and some called in July with failed units and complaints.

Once the system runs, every agreement customer appears on a tune-up list generated automatically in February, sorted by area, and the dispatcher books from it. The target is 90 percent of agreement customers tuned up before June.

Who enters what: the office manager enters each agreement's start date and equipment once when it is sold, about three minutes each. What she gets back: she no longer rebuilds the list by hand each March, which took about four days last year.

Job Two: History on the Technician's Phone

A technician walking into a basement today often knows nothing about the furnace or air conditioner in front of them beyond what the customer remembers. Technicians call the office for history about six times a day across the 14-person crew, and the office often has to search paper invoices to answer.

Once the system runs, the technician can see on a phone each unit's make, model, age and last three repairs before starting work.

Who enters what: the technician records the model and serial number and what was done at the end of each job, about two minutes. What they get back: they stop phoning the office for history, and they arrive knowing whether a part was replaced last year.

Job Three: No Estimate Left in Silence

The contractor writes about 1,100 replacement estimates a year for new furnaces and air conditioners. Today, an estimate that the customer does not answer is usually never followed up; about 38 percent of estimates receive no further contact after ten days. Many of those customers buy from someone else.

Table 1

Three Jobs, Who Enters What, and What They Receive

JobWho enters dataTime per entryWhat they get back
Spring tune-up listOffice manager, once per agreementAbout 3 minutesNo longer rebuilds the list each March
Equipment history on the phoneTechnician, after each jobAbout 2 minutesNo calls to the office for history
Estimate follow-upComfort advisor, per estimateAbout 4 minutesA daily call list and more closed sales

Once the system runs, any estimate unanswered after ten days produces a task for the comfort advisor who wrote it to call the customer.

Who enters what: the comfort advisor enters each estimate with its amount and status, about four minutes. What they get back: a daily list of customers to call, and more closed estimates, on which they are paid commission.

Why the Exchange Matters

Each job is described with what it costs the person entering the data and what that person gets back, because a system that asks for entry without returning anything useful to the person entering it tends to be abandoned. Davis (1989) found that perceived usefulness, the belief that a system will help a person do their own job better, was a stronger predictor of whether people used a system than how easy it was to use. A technician who types a serial number and then never sees it again will soon stop typing it. A technician who sees the last repair before opening a furnace has a reason to keep the record complete.

What the Owner Must Decide First

Two decisions belong to the owner before any vendor is called. The first is who owns the customer record: today the office, the technicians and the comfort advisors each keep partial records, and the system will only work if one person is responsible for keeping each customer's details correct. The second is whether the contractor will change how it works, not only what it records. The estimate follow-up job, for example, only helps if the owner expects advisors to make the calls and asks about them in the weekly meeting. A system that records a task nobody is expected to do changes nothing.

Features, Derived From the Jobs

Only now does the statement list features, and each comes from a job. The system must store agreements with equipment and generate a list by date and area. It must run on technicians' phones and show history by customer address, with simple entry at the end of a job. It must track estimates with a status and create a follow-up task after a set number of days. Anything a vendor offers beyond these, such as marketing automation or detailed reporting, is optional until the three jobs work.

How Success Will Be Judged

The project will be judged on the three jobs, not on the system's features. Success means at least 90 percent of agreement customers tuned up before June, technician calls to the office for history reduced to near zero, and every estimate followed up within ten days. If after one season those changes have not happened, the problem lies in how the system is being used, and adding features will not fix it.

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

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

The MKT-443 Topic 1 assignment instructions

Topic 1 in MKT-443 asks students to state the purpose of a CRM initiative before any product is chosen. Strong statements set aside weak reasons such as imitating competitors, then define the specific jobs the system must do in terms of what will be different in daily work. Students should name, for each job, who enters the data, how long it takes and what that person receives in return, explain with research why that exchange determines use, identify decisions the owner must make first, derive features from the jobs, and say how success will be judged.

Inside the MKT 443 Topic 1 example

Two pages long, the finished statement names no software at all. It opens by setting aside the reason the owner gave, that competitors have one, and replaces it with three jobs. Every maintenance-agreement customer is offered a spring tune-up before the cooling rush, which today depends on a dispatcher remembering. A technician walking into a basement can see the furnace's model, age and last repair on a phone. An estimate left unanswered for ten days produces a follow-up call instead of silence. For each job the statement names who enters the data, how long it takes them and what they receive for it: the technician stops phoning the office for history, and the dispatcher stops rebuilding the tune-up list by hand each March. Features appear last, derived from the jobs.

Where the marks sit in the MKT 443 Topic 1 rubric

Faculty reward a statement that defines change before software. An Excellent statement sets aside the competitor argument with Rigby, Reichheld and Schefter on strategy before technology. Credit goes to three jobs with baselines, such as 61 percent of tune-ups before June and 38 percent of estimates never followed up. The rubric values a table of who enters what, at what time cost, for what return, grounded in Davis on perceived usefulness. Strong statements name ownership of the customer record as the owner's decision. Top marks go to features derived only from the jobs.

MKT 443 Topic 1 help: mistakes that cost marks

The heaviest deduction on this topic goes to a feature wish list presented as a purpose, because contact management, dashboards and email integration describe what software can do and say nothing about what this contractor needs done. A purpose written entirely for the owner, with forecasts and reports flowing upward and no line on who feeds the system or why they would, follows close behind. Drafts often borrow the operational, analytical and collaborative categories and never say which one the business needs, so the definitions sit unused. Jobs stated as aspirations, better relationships or improved service, cannot be checked later, and the closing topics of the course usually return to exactly that check. Naming a vendor inside the purpose settles the purchase before the purpose is agreed. Leaving out the first job to launch gives the project no starting point.

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

Send the MKT-443 Topic 1 instructions and the rubric from your classroom, with the company or case your section assigned. We write a custom example to them, with the motive for buying tested, jobs stated as outcomes, a data keeper and a return named for each job and features derived last, in 24 to 48 hours. The first one is free.

More MKT 443 papers and BS in Marketing samples

MKT 443 Topic 1 questions, answered

What is the difference between operational and analytical CRM?

Operational CRM supports work done with customers as it happens: logging a call, scheduling a visit, sending a reminder. Analytical CRM studies the records afterward to find patterns, such as which customers lapse or which estimates close. Collaborative CRM shares customer information across departments and channels. A small contractor mostly needs the operational kind, and analysis becomes possible only once the operational records are kept reliably.

Why does the purpose statement name who enters the data?

Because every job a system performs depends on somebody typing a record at a busy moment, and that person decides whether the job works. A technician finishing a call in the rain will skip a form that gives nothing back. Naming the keeper, the time the entry takes and the return it brings exposes, before any money is spent, which jobs the business can realistically expect to run.

Should a purpose statement recommend a vendor?

No. It exists to define what the system must accomplish so that vendors can be judged against it later. Recommending a product at this stage lets a demonstration's most impressive features decide what the business wants. In the example, required features are listed only as consequences of the three jobs, which gives the selection work that usually follows a fixed standard to measure products against.

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

The purpose statement is shown here in full: the reason set aside, three jobs with who enters what and what they receive, why the exchange matters, what the owner must decide, features derived from the jobs and how success will be judged. Describe your business and we will draft its CRM purpose at no cost.

Why name who enters the data in MKT 443 Topic 1?

Because entry that returns nothing to the person doing it is soon abandoned. A technician who logs a serial number and then sees the unit's history on the next visit has a reason to keep doing it.