This week I had a conversation that crystallized everything we've been building toward.
I was speaking with a podcast host who regularly interviews institutional players about Bitcoin treasury operations. When I asked how most companies actually handle Bitcoin treasury, the answer was better than any market research we could have commissioned:
"Honestly most are still pretty ad-hoc. A CFO gets conviction, they buy, it lives in a spreadsheet, and the 'process' is whatever the finance team improvises until an auditor asks a hard question."
They continued: "The gap I keep seeing is that companies want to know what a mature process looks like before they buy, not after. So the demand is really on the governance template and board-ready reporting side more than anything at the custody or execution layer."
That single insight validated months of positioning work and operator conversations. It also explained something we'd been observing in our design partner cohort.
What Our Cohort Is Actually Teaching Us
We're approaching the point where the first invoices will begin flowing next week, which means we've been deep in onboarding conversations with early partner businesses.
The pattern has been consistent: these operators already handle both Bitcoin and payments at small scale, manually. They're not struggling with the mechanics of buying Bitcoin or accepting payments. They're struggling with what comes after: how to systematize it, how to report on it, and how to build repeatable processes around it.
One conversation this week reinforced this perfectly. A treasury-focused operator described complex payment flows: receiving fiat, converting automatically into Bitcoin, and paying out through Lightning. The technical execution isn't the blocker, it's building the operational framework that makes the process sustainable and auditable.
That's exactly what we see at the institutional level as well. Bitcoin sits in an organizational middle ground, not equity, not cash, not a bond, so approval chains and reporting require custom work. Recent accounting updates cleaned up the GAAP side, but the internal reporting problem remains largely unsolved.
The Infrastructure That Enables Governance
This week we completed several foundational pieces: revenue insights rebuilt with API-aligned data, invoice payment notifications for both billers and clients, and batch FX quote endpoints to handle rate limiting.
These might sound like incremental product updates, but they're actually governance infrastructure. When a CFO needs to explain Bitcoin treasury decisions to a board, they need cost basis tracking, unrealized exposure visibility, and custody concentration reporting. That data has to come from somewhere reliable.
A key payment integration is nearly complete after resolving backend authentication issues. Once that's live, we can begin integrating custodial buy/sell functionality that will complete the treasury infrastructure stack.
Each piece builds toward the same goal: giving operators the systematic, auditable processes they need to move from ad-hoc Bitcoin accumulation to mature treasury operations.
What Comes Next
Next week we'll see the first invoices flowing, which moves us from infrastructure to operational proof. Several early partner businesses are ready to begin issuing invoices as soon as the final payment rails are confirmed.
But the bigger milestone is template development. Based on everything we're learning from these early operators, we're building toward governance templates and board-ready reporting that companies can implement before they buy, not after.
That's the category we're actually creating: treasury automation built on systematic processes, not just payment rails.
We're onboarding a small cohort of businesses building Bitcoin treasury operations. The focus is on operators who understand that buying Bitcoin is the easy part - governance, reporting, and repeatability are what actually matter.