This week we onboarded the first businesses into Phase 1 of Flash Treasury.

It wasn’t a launch moment. No product theatrics. No big announcement energy.

It was kickoff calls and KYB - the structural layer that sits underneath everything else.

And that’s exactly why it mattered.

When you move from refining positioning to sitting across from real operators, the conversation shifts quickly. You stop talking about what the product could be and start talking about how money actually moves, how invoices are tracked, and how compliance really works in practice.

A few patterns emerged almost immediately.

1. The Conversation Was Operational, Not Ideological

None of the calls turned into debates about Lightning, custody philosophy, or Bitcoin mechanics.

The questions were practical:

  • How does settlement state update?
  • When does an invoice automatically mark as paid?
  • What are the ACH and card limits?
  • Can fees be passed through?
  • How does this integrate with QuickBooks?

That’s where the energy was.

It reinforced something we’ve been circling internally for months: Bitcoin treasury isn’t primarily a Bitcoin problem. It’s an accounting and compliance problem.

If it doesn’t fit into the way revenue is recorded, reconciled, and reported, it doesn’t matter how elegant the rails are.

The market isn’t asking for ideology. It’s asking for operational clarity.

2. Compliance Isn’t the Enemy - Opacity Is

KYB came up on every call. But not as resistance.

No one objected to verification itself. Everyone understands that if you’re operating in the US and touching revenue flows, there will be a compliance layer.

The frustration people described wasn’t about regulation. It was about black-box processes.

  • Being flagged without explanation.
  • Not understanding risk limits.
  • Not knowing why specific information was required.
  • Getting blocked and only finding out later.

For these onboarding calls, Jason from Polaris - our payments partner - joined live. Instead of uploading documents into a form and waiting, operators could ask questions in real time. Why is this required? What happens next? What does Maverick check for?

That completely changed the tone.

The difference between “upload documents and hope” and “talk to a human who explains what’s happening” is significant.

That’s an important lesson.

Trust in treasury infrastructure doesn’t come from eliminating compliance. It comes from making it transparent and navigable.

3. The Real Friction Is Quiet

The most revealing moments weren’t dramatic, they were mundane.

In one call, we talked about how ACH payments were tracked today - whether invoices automatically update once funds settle.

The answer was simple: “I just keep a mental note.”

They send about five invoices a month. When payments come in, they know. They don’t update the system immediately. At year-end, accounting forces everything back into alignment.

Nothing is broken. But nothing is clean either.

That’s the kind of friction that doesn’t show up in feature comparison tables. It doesn’t feel urgent. It just accumulates quietly over time.

When I asked what would make Phase 1 immediately useful, no one jumped to automated allocation rules or advanced treasury logic. The answers were simpler:

  • Knowing exactly what settled.
  • Knowing when it settled.
  • Having invoice state reflect reality automatically.
  • Reducing manual reconciliation later.

This is why we’re sequencing the rollout deliberately: visibility first. Control second. Automation later.

If you automate on top of unclear state, you just move confusion downstream.

4. Starting Small Is the Right Way to Start

Every business in this first phase is beginning with limited volume. One or two invoices. Controlled flow. Real usage, but measured. That’s intentional.

Treasury infrastructure isn’t something you flip on overnight. It needs to layer into existing workflows without breaking them. The signal isn’t the size of the first invoice. It’s the willingness to route actual revenue through a new system.

March invoices are already scheduled. That’s real.

5. The Cohort Model Is Doing Its Job

Even in this first phase, the cohort is diverse:

  • Bitcoin-native accountants.
  • Product teams thinking about embedded invoicing.
  • Agencies running recurring retainers.
  • Founders who care deeply about UX and compliance nuance.

Different businesses. Different workflows. What they share isn’t ideology. It’s a desire for operational clarity.

That’s the common denominator.

What Happens Next

KYB is complete or underway for the first group.
Next week we move into platform onboarding.

In March, the first invoices begin flowing. That’s when the next layer of signal will emerge: reporting structure, export formats, allocation controls, and eventually automation.

Treasury is the product. Payments are the rails.

Onboarding this first cohort didn’t challenge that thesis. If anything, it grounded it.

We’re expanding Phase 2 deliberately.

If you’re running a business in the U.S. and thinking seriously about integrating Bitcoin into your treasury - not as ideology, but as part of your operating system - we’d be glad to speak.

We’re building this alongside real operators, inside real workflows.

Reach out if that sounds relevant.