BUSI 439 Week 3 Group Case Study Project 2 Example

Reviewed by Thomas Kerrigan, MBA, CPA · Liberty University · Updated

This BUSI 439 Week 3 sample is the second Group Case Study Project, in which the composite team, now with rotated roles, takes on a business software company whose website attracts small business owners but turns few of them into paying customers. The paper defines two linked conversion problems, a weak sign-up rate for the free trial and a low share of trials that become subscriptions, and traces both to usability and trust. Four studies support the analysis: one on how website usability shapes buying in electronic channels, one on how visible investment in a website builds trust, one on how trust and ease of use combine in online purchase decisions, and one on adapting a site to each visitor's style. Liberty University BUSI 439 grades the project at 80 points; BS in Business Administration students finish one more case before the strategy plan.

CourseBUSI 439 Conversion and Optimization (BUSI439)
Module/Week3
AssignmentGroup Case Study Project 2
Paper typeGroup case study paper
Lengthabout 1,530 words, 6 double-spaced pages plus title page and references. Course guide: a research-based group paper of at least 1,500 words in current APA style, defining the business problem and a conversion and optimization web strategy with clearly measurable results, citing at least 3 primary sources plus the textbook
FormatAPA 7 student paper
Points80
SchoolLiberty University Online
ProgramBS in Business Administration
Where it sitsModule/Week 3 in Liberty's published BUSI 439 course guide; current sections can differ
UpdatedOctober 2026

Free sample paper for BUSI 439 Week 3

1

From Visitor to Paying Customer at Brightline Payroll: Fixing a Software Trial Funnel

 

[Student Name]

School of Business, Liberty University

BUSI 439: Conversion and Optimization

Group Case Study Project 2

[Instructor Name]

[Date]

 

Team 3: Avery Brooks, Project Leader; Casey Morgan, Editor; Jordan Ellis, Technical Writer. Brightline Payroll, its figures and the team are composites standing in for the instructor's assigned case; the textbook and the research cited are real.

2

From Visitor to Paying Customer at Brightline Payroll: Fixing a Software Trial Funnel

The Business Problem

Why this part earns its pointsThe problem has two stages, and the paper keeps them separate from the first paragraph.
3

Brightline Payroll sells online payroll software to businesses with fewer than 50 employees for $45 a month plus $6 per employee. Its website draws about 38,000 visits a month, mostly from paid search and comparison articles. Visitors are invited to start a 30-day free trial. Two numbers define the problem. Only 2.2 percent of visitors start a trial, about 840 a month, and only 11 percent of those trials become paying subscriptions, about 92 new customers a month. The company spends about $64,000 a month on paid search, so each new customer costs nearly $700 to acquire, which takes more than a year of subscription revenue to recover for a typical ten-person business. Roberts and Zahay (2018) note that conversion does not end at the first transaction, and Brightline's case shows why: a trial sign-up is only a promise, and the real conversion happens weeks later.

The Funnel in Numbers

StageMonthly countConversion
Website visits38,000
Sign-up page views6,10016 percent of visits
Trials started84014 percent of sign-up page views
Trials that run a first payroll26031 percent of trials
Paid subscriptions9211 percent of trials

Two leaks stand out. On the sign-up page, 86 percent of visitors who reached it left without starting a trial. Inside the trial, 69 percent of new users never ran a single payroll, and almost none of them later subscribed; of the 260 who ran a payroll, about 35 percent became customers.

Diagnosing the First Leak: The Sign-Up Page

Why this part earns its pointsThe diagnosis uses session recordings and form data from the case, then explains the pattern with research.
4

The sign-up form asks for eleven fields, including the company's tax identification number, the number of employees, the current payroll provider and a phone number, before the visitor sees any part of the product. The page offers no screenshots, no prices beyond a link, no customer names and no statement about how the company protects payroll data. Session recordings in the case show many visitors scrolling up and down the form and leaving at the tax identification field.

Research explains the pattern. Venkatesh and Agarwal (2006) found that customers' perceptions of a website's usability, including its content, its ease of use and how well it fits the online medium, shaped their intentions to purchase and their actual purchase behavior, with different elements mattering for different kinds of products and services. A long form placed before any product content is poor usability by every measure: it demands effort and offers little information.

Trust is the second problem. Payroll software handles employees' bank accounts and tax records, so visitors must trust the company before they enter any data. Gefen et al. (2003) showed that whether shoppers meant to buy rested jointly on how far they trusted the seller and how useful and easy they judged the site, with trust growing from familiarity, visible safeguards like security promises, and a site that behaved the way a real business's site normally does. Schlosser et al. (2006) found that visitors who perceived that a firm had invested in its website formed stronger beliefs in the firm's ability and integrity, which raised their intentions to buy. Brightline's bare form signals little investment and offers no assurances, so the page asks for sensitive data at the moment trust is lowest.

Diagnosing the Second Leak: The Empty Trial

New trial users land in a dashboard with seven menu items and no guidance. To run a first payroll they must add the company's bank account, add each employee with tax details and set a pay schedule, a process the case estimates takes 40 minutes. Users who complete it see the product's value; most never start. The usability research applies here as well: a product that is hard to begin feels less useful, and Gefen et al. (2003) link perceived ease of use directly to perceived usefulness and intention.

Problem Statement

Brightline Payroll loses most interested visitors at a long, unassuring sign-up form and most trial users before their first payroll, so it pays nearly $700 to win each customer from traffic that already wants payroll software.

Conversion and Optimization Web Strategy

Shorten and Reassure the Sign-Up

The form will drop to three fields: name, work email and password. Company details will be collected inside the trial, when the user is ready to run payroll. The sign-up page will show three product screenshots, the full price with a calculator for the visitor's number of employees, the names and short quotes of three customer businesses, and a plain statement of how payroll data is encrypted and who can see it. These changes act on the usability, assurance and investment signals the research identifies.

Show Visitors the Product Before the Form

A two-minute video of a payroll being run, and an interactive demo with sample employees, will be placed on the home and pricing pages. Visitors who watch the demo reach the sign-up page already knowing what they will get.

Guide Every Trial to a First Payroll

New users will see a setup checklist with four steps and a progress bar, and the product will offer to import employee data from a spreadsheet or another provider. An onboarding specialist will offer a 15-minute call to any trial user who has not run a payroll within three days. Emails on days one, three and seven will each address one setup step.

Adapt the Path to the Visitor

Not every visitor wants the same thing. Hauser et al. (2009) tested website morphing, in which a site infers a visitor's cognitive style from early clicks and automatically adjusts its presentation, for example toward detailed comparisons or toward simple summaries, and found that matching the site to the visitor raised purchase likelihood. Brightline can apply a simple version: visitors who arrive from comparison articles will see a detailed feature table, while those who arrive from searches such as "easy payroll for small business" will see the video and a short list of benefits.

Measurable Results

Why this part earns its pointsEach strategy is paired with the funnel stage it should move, so results can be credited correctly.
5
StrategyMetricBaselineTarget in 120 days
Short, reassuring sign-upTrials started per sign-up page view14 percent24 percent
Demo before the formVisits reaching sign-up page16 percent20 percent
Guided setupTrials running a first payroll31 percent55 percent
Adapted pathsTrial starts per visit, comparison traffic2.0 percent2.8 percent
All changes togetherPaid subscriptions per month92190

If the targets are met, Brightline will win about 190 customers a month from the same advertising, cutting the cost of each to about $340. A free trial that never reaches its first payroll is a sign-up the company paid for and then abandoned.

Financial Impact

The case's figures allow a simple payback estimate. A typical Brightline customer has ten employees and pays $105 a month. At today's acquisition cost of about $700, the company needs nearly seven months of revenue just to recover its advertising for each customer, before counting the cost of support and software hosting. At the target cost of about $340, payback falls to a little over three months. Because subscription customers who stay for years produce most of a software company's profit, a shorter payback lets Brightline grow faster from the same budget, or keep its growth steady and spend less on search. The improvement also reduces risk: if search prices rise, as they often do in competitive categories such as payroll, a company with a strong conversion rate can absorb the increase.

Tracking the Whole Path

The case shows that Brightline's analytics currently stop at the trial start. Paid search reports count a trial as a conversion, so campaigns that produce many casual sign-ups look better than campaigns that produce fewer but more serious ones. The team recommends connecting the website analytics to the billing system so that every paid subscription can be traced to its first visit and campaign. With that link in place, the marketing staff can shift search spending toward the keywords and articles that bring paying customers, not just trial users, and every test in the plan below can be judged on revenue.

Testing Plan

Each change will be tested against the current version with randomly assigned visitors or trial users. The sign-up form and the guided setup are the highest priorities, since they address the two largest losses. Because only 840 trials begin each month, the trial tests will run for at least six weeks so that differences in paid conversion are large enough to trust. The team will judge every test on paid subscriptions, not on trial starts alone, since a shorter form could attract more casual sign-ups who never pay. The adapted paths will be tested last, after the simpler changes have set a new baseline.

Risks and Limits

A shorter form may bring in more trial users who are not serious buyers, which would raise sign-ups while lowering the trial-to-paid rate; measuring paid subscriptions guards against misreading that result. Onboarding calls cost staff time, so the company will track the calls' effect on paid conversion to confirm they earn their cost. Payroll is a regulated activity, so any statement about data protection must be accurate and reviewed before publishing. Finally, the case data cover only one quarter, and small businesses often switch payroll providers at the start of a calendar year, so January results may run higher than the rest of the year and should be compared with the previous January.

Role Rotation

For this project Avery Brooks served as Project Leader, setting the schedule and writing the problem and testing sections. Casey Morgan, the first project's Technical Writer, edited the combined paper and wrote the diagnosis. Jordan Ellis, who led the first project, served as Technical Writer, building the tables and checking APA style. The team applied the instructor's feedback from Project 1 by giving every strategy its own baseline.

Conclusion

Brightline Payroll attracts the right visitors but loses them twice, first at a sign-up page that asks too much and proves too little, then in a trial that leaves new users to set up a complex product alone. Shortening and reassuring the sign-up, showing the product early, guiding every trial to a first payroll and adapting the path to each visitor address both leaks. Measured stage by stage and tested before adoption, the changes could roughly double monthly customers without adding advertising.

6

References

Gefen, D., Karahanna, E., & Straub, D. W. (2003). Trust and TAM in online shopping: An integrated model. MIS Quarterly, 27(1), 51-90. https://doi.org/10.2307/30036519

Hauser, J. R., Urban, G. L., Liberali, G., & Braun, M. (2009). Website morphing. Marketing Science, 28(2), 202-223. https://doi.org/10.1287/mksc.1080.0459

Roberts, M. L., & Zahay, D. (2018). Internet marketing: Integrating online and offline strategies (4th ed.). Cengage Learning.

Schlosser, A. E., White, T. B., & Lloyd, S. M. (2006). Converting web site visitors into buyers: How web site investment increases consumer trusting beliefs and online purchase intentions. Journal of Marketing, 70(2), 133-148. https://doi.org/10.1509/jmkg.70.2.133

Venkatesh, V., & Agarwal, R. (2006). Turning visitors into customers: A usability-centric perspective on purchase behavior in electronic channels. Management Science, 52(3), 367-382. https://doi.org/10.1287/mnsc.1050.0442

What the BUSI 439 Week 3 instructions ask

In Module/Week 3, BUSI 439 students read chapter 15 of Roberts and Zahay, work through a case study, post the Forum 2 thread, take the chapter 15 MindTap quiz and submit Group Case Study Project 2, worth 80 points. The requirements match the first project: the team diagnoses the case's business problem and proposes measurable conversion and optimization web strategies in a paper of 1,500 or more words, formatted in current APA style and drawing on three or more primary sources plus the textbook. Members switch roles, so the student who led the first project now edits or writes. Teams receive the case in the module/week materials.

How this BUSI 439 Week 3 example is built

The sample treats the case as a funnel with two leaks rather than one. It opens with the numbers for each stage, from landing page visit to trial sign-up to paid subscription, then diagnoses each leak separately: the sign-up page asks for too much and proves too little, and the trial leaves new users alone with a complicated product. Research on usability and trust explains both. The strategy section gives each fix a cause and a metric, a table sets targets for both conversion points, and a testing plan describes how the team would confirm each result. A paragraph on role rotation closes the paper.

BUSI 439 Week 3 grading rubric: where the points go

Team members share one grade for Project 2. Instructors look for a business problem defined in the case's own numbers, an analysis that uses the case data and primary research to explain causes, and web strategies that each come with a measurable result such as a target rate and date. Length, sources and style still count: 1,500 words, a minimum of three primary sources with the textbook, and APA formatting. Strong papers keep the logic visible from cause to change to metric, and they recognize when a problem has more than one stage, as software trials often do. A consistent voice shows that the Editor did the job. Tables that follow the funnel help the reader see the logic.

BUSI 439 Week 3 help: mistakes that cost points

Rotate roles as the guide requires and agree on a timeline in the first two days. List every figure in the case before analyzing it, and sketch the funnel stage by stage so the team agrees where the losses occur. Look for research on the behavior at each stage, such as usability, trust or onboarding, and connect each study to one specific change. State each result as a number with a baseline and a target. Because this is the second project, review the instructor's comments on the first one and correct any repeated weaknesses before submitting. Ask the Technical Writer to confirm that every table's figures match the case exactly.

Related BUSI 439 sample papers

Other BUSI 439 weeks

More BS in Business Administration sample papers

BUSI 439 Week 3 questions, answered

What is BUSI 439 Group Case Study Project 2?

Due in Module/Week 3 for 80 points, it asks each team to diagnose a second assigned case and propose web fixes with measurable targets, backed by primary research and the textbook.

Where can I find a free BUSI 439 Week 3 sample paper?

Below is a complete BUSI 439 Week 3 group case paper on raising free trial sign-ups and paid conversions for a small business software company.

How do trust and usability affect online conversion?

Research shows that visitors buy more readily from sites that are easy to use and that signal competence and care, because both reduce the effort and the risk of a purchase.

Do BUSI 439 group members keep the same role?

No; roles rotate, so across the three projects every member serves once as Project Leader, once as Editor and once as Technical Writer.

What else is due in BUSI 439 Module/Week 3?

The Forum 2 thread with two scholarly articles and Scripture and a 40-point MindTap quiz on chapter 15, both after reading chapter 15 and the week's case study.

Use it as a model, or ask for your own

This paper is an original model written by our desk for study. It is not a submitted student paper and not an official Liberty University document. Read it for structure and reasoning, then write your own to the instructions in your Canvas course. If you want a version built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.