| Course | MT362 Artificial Intelligence Applications for the Marketing Professional |
|---|---|
| Unit | Unit 9 |
| Paper type | Vendor comparison matrix |
| Length | About 870 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Business Administration |
| Updated | October 2026 |
Free sample paper for MT362 Unit 9
Contract Terms Before Demonstrations: An MT362 Unit 9 Vendor Comparison Matrix for Churn Prediction
[Student Name]
Purdue University Global
MT362: Artificial Intelligence Applications for the Marketing Professional
Unit 9 Vendor Comparison Matrix
[Instructor Name]
[Date]
The vendors are composites described by type, and their terms, prices and claims are illustrative; the regulations and sources cited are real.
Weights Fixed Before the First Demonstration
The weighting memo is dated two weeks before the first sales call and signed by the director of lifecycle marketing, and the matrix shows it first so a reader can confirm that no criterion was reweighted after a vendor impressed the team. Data use and training restrictions carry 25 percent of the score. Deletion, subprocessors and data location carry 10 percent. Score explanations carry 15 percent, access for the chain's own bias audits 15 percent, integration effort 15 percent and three-year cost 20 percent. Each cell holds a score from 1 to 5 and the clause or page that supports it.
The Three Vendors
The vendors are described by type. Vendor E is a churn module inside the email platform Fernbrook already uses. Vendor S is a standalone retention-prediction firm. Vendor D is a predictive add-on to a customer data platform. Nothing in the matrix describes how any vendor's model works internally; every cell rests on a document the vendor supplied.
Who May Learn From the Chain's Data
Data terms carry the most weight because the Unit 4 review made them the condition of using customer records at all. Vendor E's terms allow it to use de-identified customer data to improve products for all of its clients. Vendor S's terms forbid any use of Fernbrook's data beyond Fernbrook's own service. Vendor D's terms permit use for its own product improvement with an opt-out. Under California's regulations, a service provider generally may not use a business's personal information to build or improve services for other businesses, beyond narrow exceptions (California Privacy Protection Agency, 2023), so a vendor that trains for all clients may not qualify as a service provider at all. The matrix routes that question to counsel and scores Vendor E a 2, Vendor D a 4 and Vendor S a 5. That single clause moves more points than any price difference.
One clause about whose models may learn from the chain's data decides the comparison more than any demonstration did.
Deletion, Subprocessors, Location
Each vendor's promised deletion window after termination, its list of subprocessors and the location of stored data are quoted directly. Vendor E deletes within 30 days and lists five subprocessors, scoring 5. Vendor S deletes within 45 days and lists four, scoring 4. Vendor D names eleven subprocessors and could not say which of them touch subscriber records, scoring 2.
Scores the Chain Can Audit
The Unit 7 bias review needs every score and its top reasons exported each month. Vendors S and D offer that export and score 4 for audit access. Vendor E shows scores and reasons only inside its own dashboard, which earns it a 2, since the chain could not join them to birth years for the audit. On explanations themselves, Vendors E and S each provide top reason codes for every score and score 4; Vendor D provides only general feature importance and scores 3.
Integration and Cost
Vendor E integrates with no new data connections and scores 5, at about $21,000 a year, $63,000 over three years, also a 5. Vendor S needs about 220 analyst hours to connect order and schedule data and costs $48,000 a year, $144,000 over three years plus the integration time, scoring 3 for integration and 4 for cost. Vendor D needs similar integration work and costs $62,000 a year, $186,000 over three years, scoring 3 on both.
The Totals
Weighted totals are 4.10 for Vendor S, 3.65 for Vendor E and 3.30 for Vendor D. Vendor S leads despite costing more than Vendor E because its data terms and audit access are the two criteria the earlier units made conditions of the project. A sensitivity check confirms the order is stable: even if cost were weighted at 30 percent and data use cut to 15, Vendor S would still finish first, narrowly.
Claims Held for the Pilot
Vendor S's case study reports a 23 percent reduction in cancellations for another retailer, and Vendor D's materials state 92 percent accuracy. Both sit in a separate column marked claim to be tested, and neither enters the totals. In September 2024 the Federal Trade Commission announced a set of enforcement actions against deceptive claims about artificial intelligence (Federal Trade Commission, 2024), and that sweep is the reason vendor assertions are treated as hypotheses here. The Unit 8 pilot is named as the only evidence the chain will accept, consistent with Kohavi et al. (2020), who argue that controlled experiments, not vendor reports, show what a change does in one's own setting.
Recommendation
Proceed to contract negotiation with Vendor S for the pilot only, on a quarter-to-quarter term, with the data-use clause, monthly score exports and deletion window written into the contract. If Vendor S declines quarter-to-quarter terms, Vendor D becomes the alternative, conditional on naming which subprocessors touch subscriber data.
References
California Privacy Protection Agency. (2023). California Consumer Privacy Act regulations (Cal. Code Regs. tit. 11, ยง 7000 et seq.). California Privacy Protection Agency.
Federal Trade Commission. (2024, September 25). FTC announces crackdown on deceptive AI claims and schemes [Press release]. Federal Trade Commission.
Kohavi, R., Tang, D., & Xu, Y. (2020). Trustworthy online controlled experiments: A practical guide to A/B testing. Cambridge University Press.
The Purdue Global MT362 Unit 9 instructions
Unit 9 asks students to compare AI vendors for a defined use, using criteria that follow from the earlier units. Weights should be set and dated before any vendor is scored, so demonstrations cannot reshape them. Instructors expect every score to rest on a document someone outside the team could inspect: a contract clause, a published policy or a price sheet. Data terms, deletion, subprocessors and audit access usually matter as much as features or price, especially after a privacy review and a bias review. Vendor performance claims should be treated as hypotheses, not scored. A recommendation should name conditions, including what happens if the preferred vendor will not accept them, and how the claims will be tested.
How the MT 362 Unit 9 example is put together
The weighting memo and its date come first in the sample, followed by the three vendors described only by type. Data-use terms get the longest section, quoting each vendor's training clause and citing California's service-provider rules, under a highlighted line about the clause that decided the comparison. Deletion windows and subprocessor lists are quoted. Audit access and explanations are scored against the Unit 7 export requirement. Integration and three-year costs follow. Totals are reported with a sensitivity check. Vendor claims are quarantined with the FTC's 2024 actions and Kohavi and colleagues on experiments. The recommendation proceeds with one vendor on conditions, including a quarter-to-quarter term, and names a fallback with its own condition.
MT362 Unit 9 rubric: what earns full points
Vendor matrices are commonly judged on whether weights were fixed in advance, whether each score is evidenced, whether the criteria follow from earlier findings and whether the recommendation is conditional and testable. A dated weighting memo shows discipline. Scores tied to quoted clauses earn more than impressions from demos. Rubrics reward giving data terms heavy weight when a privacy review has made them a condition. Treating performance claims as untested shows skepticism appropriate to AI products. A sensitivity check on the weights demonstrates that the result is not fragile. A recommendation with contract conditions and a fallback shows practical judgment. Regulations and sources appear in APA 7, and the vendors stay anonymous composites described only through their documents.
MT362 Unit 9 help: mistakes that cost points
Comparison matrices in this unit often score vendors on how impressive their demonstrations were, which rewards sales skill rather than fit. Weights are frequently adjusted after scoring, sometimes without anyone noticing. Many matrices score accuracy claims from vendor case studies as if they were verified. Data-use terms are often skipped because they are buried in contracts. Some students describe how a vendor's model works internally without any document to support it. Before scoring, write and date the weights, then require a document for every cell. Any cell you cannot support with a document should stay blank and become a written question for the vendor before the next call.
Get an MT362 Unit 9 example written to your instructions
List the vendors or vendor types Unit 9 names and any documents supplied, and say whether weights are given or yours to set. With the prompt and rubric in hand, a first matrix is free and ready in 24-48h, every score sourced and every vendor claim kept out of the totals. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More MT362 papers and BS in Business Administration samples
- MT362 Unit 1: AI Retention Offers Post
- MT362 Unit 2: AI Use Case Assessment
- MT362 Unit 3: Customer Data Inventory
- MT362 Unit 4: Privacy and Consent Review
- MT362 Unit 5: Personalization Strategy Memo
- MT362 Unit 6: AI Disclosure Seminar Reflection
- MT362 Unit 7: AI Model Bias Review
- MT362 Unit 8: AI Pilot Test Design
- MT362 Unit 10: AI Adoption Proposal
- MT361 Unit 9: Contract-to-Close Transaction Timeline
- MT359 Unit 9: IMC Evaluation Plan
- MT358 Unit 9: Social Media Analytics Report
- MT357 Unit 9: Digital Measurement Framework
MT362 Unit 9 questions, answered
Can I use real vendors in the matrix?
Often yes, if the prompt allows it, but describe them only through their public documents: pricing pages, terms of service, data processing agreements and published security material. Date each source, since terms change. Avoid claims about how a real product performs or works internally unless an independent source supports them, and keep marketing claims separate from verified terms.
How should I set the weights?
From the business's priorities and earlier findings, stated before any scoring. If a privacy review made data terms decisive, weight them heavily and say why. Graders usually accept a range of reasonable weights; what draws comment is weights that look reverse-engineered from a preferred winner. A short sensitivity check, showing whether the ranking survives a reweighting, strengthens the result.
What counts as evidence for a vendor score?
A document a reader could check: a contract clause, a published policy, a pricing sheet or a written answer from the vendor. Demonstrations and sales conversations can raise questions but rarely settle a score on their own. Where evidence is missing, score conservatively and note the gap, since an unanswered question about data handling is itself a finding.
Where can I find a free MT362 Unit 9 sample paper?
The complete MT362 Unit 9 vendor comparison matrix is printed on this page, weighing three churn-prediction vendors on contract terms and cost.
Why do vendor accuracy claims stay out of the totals in the MT362 Unit 9 sample?
They come from the vendors' own case studies and cannot be checked, so they are held as claims to be tested in the pilot, the only evidence the chain will accept.