Pre-launch capital check: survive to first live customer

ABFinance announced on August 14, 2026 that it had suspended operations. It canceled the launch and began liquidation before it opened to customers. A pre-launch capital check should answer the question: can the company pay its way from licensed rails to first live customer? If the answer is no, the launch becomes a financing problem rather than a product milestone.

Helen Liu, who previously served as Bybit co-CEO, headed ABFinance, a venture intended to provide a U.S.-regulated platform for deposits, earnings, trading, and spending. In March 2026, she introduced ABFinance on X as a U.S.-based platform that already held compliant U.S. licenses. The gap was visible. 17 major crypto businesses and about 95 total projects had already closed in 2026. Four centralized platforms had announced closures since early July.

For a regulated or capital-intensive startup, the pre-launch period is where that risk concentrates. The company must build the product, satisfy compliance, and line up the partners who will make the first transaction possible. Each of those tasks consumes cash before a customer pays. The check forces the team to name the gap instead of hiding it behind the approval.

Approvals do not fund the gap to first revenue

Approvals can make a product legal. They do not make it solvent. A regulated startup can spend time building the structure while the cash needed to reach a first customer quietly grows.

A license is the most visible part of a pre-launch plan, and the easiest to mistake for progress. The harder question is what happens after the approval is granted: who pays for the team, the systems, the legal work, and the partner integration that turns the approval into a usable product?

When the answer is unclear, the launch date becomes a bet. The company is betting that revenue will arrive before the cash runs out. That bet is fine only when the plan shows the money, the dependencies, and the date.

These tests separate a launch from a plan

Run each test against current documents, not the pitch. Each test should be answerable in a short review.

• Licensed rails. Identify the exact regulatory permission that lets the product move money or serve customers. If the permission is conditional, note the condition and the date it must be met.
• Funding to first live customer. Count the cash needed from today to the first paying customer, including payroll, compliance, infrastructure, and partner costs. If the number exceeds committed capital, the plan fails.
• Partner commitments. List the partners whose participation is required for the first customer, and confirm whether each commitment is signed, verbal, or assumed. A verbal promise does not count as a funded dependency.
• Dated path to first revenue. Put a date on the first live customer and the first revenue event. If the date depends on an approval, a partner, or a market condition, name the owner and the trigger.

The list is short because the gap is simple. If a company cannot show the rails, the cash, the partners, and the date, it has a plan, not a launch. The tests are deliberately narrow. They do not ask whether the market is large, the team is strong, or the product is elegant. They ask whether the company can survive the specific interval between permission and payment. The check makes that interval visible before the company spends the last of its cash.

Use the check before the money moves

For founders, run the check before setting a public launch date. If a test fails, fix the gap or delay the announcement. A delayed launch is easier to explain than a liquidation that follows a confident story.

An investor who accepts a license as the main evidence is underwriting the wrong asset. The asset is the funded path to first revenue. The capital check is the test that decides whether the company can reach it.