Business financial servicesSource-backed brief

How did Mercury build trust before its first public launch?

Mercury’s founder account begins with banking frustrations at Immad Akhund’s earlier company, Heyzap. Before building, he held roughly 90 conversations with fintech founders, lawyers and investors about sponsorship, risk and compliance. The team changed its original sponsor arrangement and rebuilt parts of onboarding before launching in April 2019. That sequence makes preparation and operational credibility central to the early growth story. [1]

Evidence and interpretation

This story condenses a source-backed brief. Some historical details and internal metrics are not established. [Inference] marks analysis. Source numbers keep the numbering of the full case, and the evidence is from the 10 Nov 2026 research edition. Read the research method.

The difficult work preceded the launch test

Akhund told First Round that around 60 supporters, including investors, shared the launch. Four days later, an unknown customer deposited $1 million without contacting sales. The account does not identify the first paying customer or establish that this depositor was first in every sense. It documents a striking self-service action after public launch, with the founder’s interpretation of the company’s path to product-market fit. [1]

[Inference] The discovery conversations addressed constraints that a simple interface prototype could not settle. In a trust-sensitive financial product, the meaningful first experience needs an operating arrangement behind it. The lesson is not that all startups should delay launch until every feature is complete. It is that a valid demand test must include the capabilities necessary for the customer’s consequential action to be possible.

Supporters opened a door the product had to justify

The interview presents Mercury as Akhund’s fourth startup and identifies his earlier Heyzap experience as part of the motivation. It also gives a concrete launch-distribution detail: supporters publicly helped introduce the service. Those are documented founder resources. The supplied record does not disclose a paid campaign budget, quantify the contribution of each supporter or establish that network-led discovery remained the dominant channel later. [1]

[Inference] Credible supporters can help a new provider receive consideration, but they cannot make every subsequent interaction trustworthy. A customer moving a substantial balance needs confidence that the service can support the intended business activity. The deposit anecdote is evidence of one customer taking that action. It does not establish a universal response, an average deposit size or a repeatable acquisition cost.

Money moved is not revenue earned

The reported $1 million was a customer deposit, not Mercury revenue. The source also describes changes to sponsorship and onboarding before launch, but does not provide a full subsequent customer-success organization, named account managers or measured account expansion. These boundaries are important because financial activity can produce impressive numbers that describe customer assets rather than the provider’s commercial result. [1]

[Inference] A stronger activation analysis would ask whether a business continued using the service for its intended financial workflow after the initial deposit. Initial trust, repeated activity and paid or otherwise monetized value are different stages. A one-time transfer can be meaningful without proving that the provider has become central to the customer’s operations or that the relationship is economical to serve. The practical question is what the customer does next: whether the account supports recurring business work and whether assistance is needed to complete that work. A deposit alone cannot answer either part of that question.

Account for the responsibilities behind the experience

Historical and current prices, CAC, gross margin, payback and retention cohorts were not established in the supplied brief. It also does not substantiate a particular failed marketing channel. The changed sponsor arrangement is a documented operational development, but the record does not quantify its cost or isolate its effect on conversion. Those facts should not be replaced with an invented financial model. [1]

[Inference] Mercury’s transferable lesson is to test the full trust-dependent workflow and separate customer balances from revenue. Acquisition should be assessed against sustained activity and actual monetization, including partner and servicing costs. The founder’s preparation and launch network make the initial conditions visible; durable growth would require the service repeatedly earning the confidence that the first striking deposit appeared to express.

GO DEEPER

Mercury: the full GTM case

The complete case holds the named people, the economics, the available historical evidence, the critique and the open research questions.

Read Mercury’s full GTM case

Terms in this story

Customer onboardingProduct-market fitActivationCustomer acquisition costGross marginCustomer retention

Questions behind the story

How do I choose between product-led and sales-led growth?Why does the site leave CAC and retention blank for some companies?All 104 GTM questions answered

Sources

Numbers match the source list of the full Mercury case. A source’s publication date and the date of the event it reports can differ.

  1. Mercury’s Path to Product-Market Fit — Do the Hard Part First review.firstround.com