DBA 820 Topic 3 payments startup valuation example

Emerging Issues in Financial Management Grand Canyon University Free custom sample in 24 to 48h

This DBA 820 Topic 3 sample paper values a composite regional bank's proposed 10 percent stake in a small-business payments startup as a range rather than one figure. It forms part of GCU DBA 820, Emerging Issues in Financial Management, catalog code DBA-820, a doctoral finance course in the Grand Canyon University DBA. The stake is offered at 40 million dollars, a 400 million post-money headline. Public multiples describe a different business, and Gornall and Strebulaev showed headline values overstate shares with protective terms. Three scenarios, embedded, niche and failure, weighted 30, 45 and 25 percent and discounted at 15 percent, put the stake near 28 million within about 24 to 36, below the price.

CourseDBA 820 Emerging Issues in Financial Management
TopicTopic 3
Paper typePayments startup valuation
LengthAbout 960 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramDBA
UpdatedOctober 2026

Free sample paper for DBA 820 Topic 3

1

Three Futures, Not One Multiple: Valuing a Bank's Proposed Stake in a Small-Business Payments Startup as a Range

[Author Name]

College of Doctoral Studies, Grand Canyon University

DBA-820: Emerging Issues in Financial Management

Topic 3 Payments Startup Valuation

[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 method and the form of the answer. The bank, startup and every figure are a composite, marked illustrative where they are judgment; the sources are real.
2

Three Futures, Not One Multiple: Valuing a Bank's Proposed Stake in a Small-Business Payments Startup as a Range

The Proposal

A composite regional bank has been offered a 10 percent stake in a payments startup that processes card and bank payments for small businesses, priced at 40 million dollars in a new round of convertible preferred shares, which values the company at 400 million dollars after the investment. The bank's interest is strategic as well as financial: the startup's software could be built into the bank's accounts for small-business customers. The question is what the stake is worth to the bank, and whether 40 million dollars is a price it should pay. Figures are illustrative and, where marked, are judgment rather than measurement.

Why the Usual Anchors Fail

The usual starting points do not fit. Listed payments processors trade at multiples of revenue or earnings that describe large, profitable, diversified businesses; the startup is small, unprofitable and dependent on a few hundred thousand merchants, so applying those multiples would value a different business. The startup's own last funding round implies a headline value, but that figure is misleading for a different reason. Venture investors buy preferred shares with protective terms, such as liquidation preferences that return their money first if the company is sold cheaply. The headline post-money value multiplies the price of those protected shares by all shares outstanding, including common shares without protection. Gornall and Strebulaev (2020) showed that this practice tends to overstate what a venture-backed company's equity is worth, sometimes substantially. Young companies with negative earnings and short histories also defeat conventional discounted cash flow models built on steady growth (Damodaran, 2009).

Three Scenarios

The valuation therefore builds three futures, each with an exit value in five years and a probability, both judgment. In the first, the platform becomes embedded in the bank's and other banks' small-business accounts and the company is sold for about 1.2 billion dollars; the bank's 10 percent would convert to common and be worth about 120 million. Probability: 30 percent. In the second, the startup survives as a niche processor and is sold for about 200 million dollars; the bank's 10 percent of that would be 20 million, but its liquidation preference returns its 40 million first, so it recovers 40 million. Probability: 45 percent. In the third, the startup fails and its assets are sold for about 30 million dollars, shared among several classes of preferred investors; the bank recovers about 10 million. Probability: 25 percent.

Table 1

Scenarios for the Bank's Stake, Illustrative

ScenarioExit value in five yearsBank's proceedsProbability, judgment
Embedded in bank accountsAbout 1.2 billionAbout 120 million, converted to common30 percent
Niche processorAbout 200 millionAbout 40 million, through the preference45 percent
FailureAbout 30 millionAbout 10 million25 percent
Probability-weighted proceeds| About 56.5 million
Present value at 15 percent| About 28 million

From Scenarios to Value

The probability-weighted proceeds are about 56.5 million dollars in five years. Discounting at 15 percent a year, a rate for equity-like risk that does not double-count the failure risk already in the scenarios, gives a present value of about 28 million dollars, well below the 40 million price. The preference matters: without it, the bank would recover only 20 million in the niche scenario, and the present value would fall to about 24 million.

Sensitivity to the Success Probability

One assumption dominates. Holding the failure probability at 25 percent and shifting probability between success and the niche outcome, the stake's present value is about 24 million dollars at a 20 percent chance of success, 28 million at 30 percent, 32 million at 40 percent and 36 million at 50 percent. Even at an even chance of becoming embedded across the banking market, the stake is worth less than 40 million on these assumptions. Metrick and Yasuda (2021) emphasize that venture valuations rest heavily on such exit assumptions, which is why they should be presented as ranges.

The Strategic Value

The bank may value the stake beyond its financial return, because the startup's software could help it keep small-business customers. That value should be estimated separately, for example as the contribution from customers the bank would otherwise lose, rather than folded into the probability of success. The same benefit might also be obtained through a commercial agreement to use the startup's software without buying equity. If the bank's analysts estimated that integrated payments would retain small-business customers worth, say, 1.5 million dollars a year in contribution, that benefit would be available under either arrangement, and only the part requiring ownership should be added to the stake's value.

Recommendation

On financial grounds alone, the stake is worth roughly 24 to 36 million dollars, with about 28 million most likely, and the bank should not pay 40 million. It should either negotiate a lower price or stronger terms, such as a senior preference, or pursue a commercial partnership, buying equity only if the strategic value, separately estimated, closes the gap. The assumption that dominates, the probability of becoming embedded in bank accounts, is one the bank can partly test through a pilot with its own customers before investing.

Conclusion

Neither public multiples nor the last round's headline price describe what this stake is worth: the first values a different business and the second overstates equity carrying protective terms. Three scenarios, weighted by explicit judgment and discounted once, put the stake at about 28 million dollars, within a range of roughly 24 to 36 million driven mainly by the chance the platform becomes embedded in banks' small-business accounts. The 40 million price exceeds that range. The bank should price the stake as a range, test the dominant assumption through a pilot and treat any strategic benefit as a separate calculation.

References

Damodaran, A. (2009). Valuing young, start-up and growth companies: Estimation issues and valuation challenges. SSRN Electronic Journal. https://doi.org/10.2139/ssrn.1418687

Gornall, W., & Strebulaev, I. A. (2020). Squaring venture capital valuations with reality. Journal of Financial Economics, 135(1), 120-143. https://doi.org/10.1016/j.jfineco.2018.04.015

Metrick, A., & Yasuda, A. (2021). Venture capital and the finance of innovation (3rd ed.). Wiley.

DBA 820 Topic 3 instructions, in plain terms

In Topic 3, DBA-820 asks doctoral students to value a young company where the usual valuation anchors fail. Strong valuations explain why public comparables and the last funding round mislead, then build explicit scenarios with cash outcomes a reader can inspect and probabilities the writer states and defends. Students should account for the security being bought, including liquidation preferences, discount once at a rate suited to the risk, and test which assumption carries the value. The paper should keep any strategic benefit to the buyer separate from financial value and recommend a price or a next step, not merely a number.

Inside the DBA 820 Topic 3 example

The finished valuation begins by explaining why the usual anchors fail. Listed payments processors are far larger, profitable and diversified, so their multiples describe a different business. The startup's last venture round implies a headline value, but that price bought preferred shares with liquidation preferences, and Gornall and Strebulaev showed that such post-money figures tend to overstate what the equity is worth. The paper therefore builds three scenarios instead: the platform becomes embedded in the bank's small-business accounts, it survives as a niche processor, or it fails and investors recover only what the preferences return. Each scenario carries a cash flow path and a probability, all illustrative and marked as judgment. A sensitivity table shows value moving with the success probability. The recommendation prices the stake as a range and states which assumption dominates it.

Reading the DBA 820 Topic 3 rubric

Faculty reward a valuation stated as a range. An Excellent paper explains why listed processors' multiples and the round's headline price both fail, citing Gornall and Strebulaev on preferred terms. Credit goes to a scenario table with exit values, the bank's proceeds through conversion or preference, and stated probabilities. The rubric values Damodaran's guidance on young firms, Metrick and Yasuda on venture securities, and sensitivity to the success probability. Strong papers separate strategic value from financial value. Top marks go to a pilot that tests the assumption carrying the value.

Common DBA 820 Topic 3 mistakes, and how to avoid them

The most costly error on this topic is a single valuation figure presented with precision it cannot have. Without a market to compare against, every number rests on assumptions, and a point estimate hides them from the reader who has to decide. Papers that borrow public processor multiples without adjusting for scale, profitability and risk import a valuation from a different business. Treating the last funding round's post-money value as the worth of every share ignores the preference terms that price reflected. Scenario weights stated without reasons read as numbers chosen to reach an answer. Sensitivity work is often absent or limited to the discount rate, when the success probability matters more. A recommendation that never says what evidence would revise it after a year of operating data leaves the estimate unaccountable to anyone.

Get a DBA-820 Topic 3 example written to your instructions

Send the DBA-820 Topic 3 instructions and the rubric posted in your classroom, along with the company or valuation case your section provides. We write a custom example to them, with the failing anchors explained, scenarios built from stated drivers, probabilities defended and a priced range in place of a point figure, in 24 to 48 hours. The first one is free.

More DBA 820 papers and DBA samples

DBA 820 Topic 3 questions, answered

Why not value the startup from its latest funding round?

Because the round priced a particular security, usually preferred stock with liquidation preferences and other protections, and the headline post-money figure applies that price to every share as if all were identical. Gornall and Strebulaev showed that this convention tends to overstate fair value. The example uses the round as a reference point and values the stake through scenarios instead.

What replaces comparables when none exist?

Explicit scenarios, each with a cash flow path built from drivers a reader can inspect, weighted by probabilities the writer states and defends. The approach does not remove judgment; it makes the judgment visible. A sensitivity table then shows which assumption carries the value, so a decision maker knows where further evidence would narrow the range most.

Can this be used to value an actual company?

No. The bank, the startup, the scenarios and every figure were built for this exercise to show valuation without a comparable market. A real valuation requires the company's actual financial records, its capital structure and security terms, current market data and a professional's judgment. The example is DBA-820 coursework and offers no investment or valuation advice to anyone relying on it.

Where can I find a free DBA 820 Topic 3 sample paper?

The valuation is shown here complete: the proposal, why the usual anchors fail, three scenarios, from scenarios to value, sensitivity, strategic value, the recommendation and the conclusion. List your startup's terms and figures and a valuation follows free.

Why is the stake worth less than its 40 million price in DBA 820 Topic 3?

Weighted across three scenarios and discounted at 15 percent, the bank's proceeds are worth about 28 million, within roughly 24 to 36 million. The price sits above that range unless the embedded scenario is more likely than 30 percent.