Understanding numbers as a technical co-founder

I came to Bloccpay as an engineer. For most of my career, the numbers I cared about were the ones a build prints: tests passed, pages loaded, errors in the logs. They were for the team, and nobody outside it needed to hear them.

Co-founding a company changed who the numbers are for. Programme applications, partners, investors and other founders all ask some version of the same question: how is it going? The answer they want fits in one line. Ours is that Bloccpay has processed more than $500,000 in payroll and invoice payments since the private beta began in 2024.

I can say that line with confidence because I know what sits under it. That turned out to be the part of the job I did not expect: being the person who can walk from the sentence down to the records, and back up again.

What a payment is, to the system

To a business owner, paying someone is one action. To the system, it is a sequence. A payroll run is created, reviewed and approved. Each person’s payment is sent over stablecoin rails, lands in a bank account or a wallet, and leaves a pay slip behind. An invoice follows a similar path, starting from a payment link the client opens, and ends with a receipt.

At any moment some payments are waiting for approval, some are on their way, and some have arrived. Now and then one fails and has to be dealt with. The $500,000 counts the ones that arrived. A payroll that was drafted and never approved is not money that moved.

A payment that had to be retried was still owed once, so it should count once. That is not a rule I can apply at the end of a quarter. It has to hold in the code from the first day, because if a retry could send money twice, the number would be wrong and, worse, someone would have been paid twice. Most of the care that keeps the figure honest is the same care that keeps the product safe.

Three numbers that look alike

A payments company has more than one number with a dollar sign in front of it, and they are easy to blur.

Payments processed is the money that moved through Bloccpay to the people who were owed it. It belongs to our customers and their teams. It tells you whether the product is being trusted with real payroll.

Revenue is what the company keeps: the fees. It is a much smaller number, and it is the one that says whether Bloccpay is a business. A fee is recorded as its own entry, apart from the payment it came with, so the two are never added together by accident.

Money given to the company is a third thing. In June 2026 Bloccpay received a Stellar Community Fund award of $100,000 worth of XLM. It is a grant. It is not in the payments figure, and it is not revenue.

When “processed” gets retold as “made”, or a grant gets added to volume, a company sounds bigger and becomes harder to trust. Keeping the three apart in the build is what lets me keep them apart when I talk.

Where the number starts

Bloccpay was founded in 2022. The first years were research and customer discovery, with no product yet to process anything. The payments figure starts in 2024, when operations and the private beta began. Private beta means a limited group of customers using the product while we keep building it. A number from that stage is early, real use, and I would rather it be read that way than stretched.

Why it is a human number

Every dollar in that figure was owed to someone: a salary at the end of a month, an invoice a freelancer sent and then waited on. Bloccpay exists because of a payday that took three steps and two intermediaries and still lost money on the rate. So when I look at $500,000, I do not see volume first. I see paydays that arrived, with a pay slip to show for them.

That is the bridge I try to hold as a technical co-founder. The business needs a clear number it can say out loud. The build has to make sure that number means exactly what we say it means. Most days those are the same job.