Why We Went Quiet — And What Happens Now
For the past several months, we've been in what I'll generously call stealth mode. Less generously: we went quiet, turned inward, and built. Here's why.
If you’ve been following this series, you’ve read about how we think about transparency, ownership, and the kind of people we choose to build with. All of that is foundational. But foundations exist to support something — and it’s time to talk about what.
For the past several months, we’ve been in what I’ll generously call stealth mode. Less generously: we went quiet, turned inward, and built.
Here’s why.
The Temptation of “Ship It”
We could have launched something months ago. The pressure to ship is real — especially in a market where AI-powered tools are proliferating weekly and every consultancy is racing to offer something with “intelligent” in the name.
But we’d watched enough companies rush products to market and spend the next two years apologizing for the architecture. In payments and cybersecurity, the cost of a bad foundation isn’t technical debt — it’s client data at risk, compliance exposure, and the kind of trust damage you don’t recover from.
So we made a decision that felt counterintuitive at the time: we slowed down.
What “Getting the Roots Right” Actually Means
When we talk about investing in foundations, we’re not being vague to sound strategic. We’re talking about specific decisions.
Security infrastructure first. Before we put a single client’s data through any new system, we needed to be confident in how that data moves, where it rests, who can access it, and what happens when something goes wrong. Not “we’ll harden it later” confident. Actually confident. The kind of confident where you’d put your own financial data through it without hesitation.
Architecture for portability. Everything we’ve said about ownership and data portability applies to what we build, too. If we’re going to tell clients they own their stack, the products we create need to honour that from the first line of code. That means open standards, documented APIs, and export capability that isn’t an afterthought bolted on before launch.
AI with guardrails. The current AI landscape is flooded with tools that are impressive in demos and unpredictable in production. We’ve invested heavily in understanding where AI delivers genuine value in our domains — payment analytics, security assessment, operational efficiency — and where it introduces risk that isn’t worth the capability. Not everything needs to be “AI-powered.” Some things need to be reliable.
What This Means for the Businesses We Serve
We work with merchants processing meaningful volume who deserve to understand their economics. We work with nonprofits protecting donor data on tight budgets. We work with organizations building digital infrastructure they’ll depend on for years.
These aren’t audiences that benefit from us moving fast and breaking things. They benefit from us moving deliberately and building things that last.
What’s coming will help more businesses navigate cost-effective payments, make smarter digital lifecycle decisions, and keep more of what they earn. The specifics will roll out over the coming months — and when they do, you’ll be able to evaluate them against every principle we’ve outlined in this series.
The Accountability Part
In our first post, we talked about inviting scrutiny rather than asking for trust. That applies here too.
When we launch new products and capabilities, we’re going to show you how they work. Not just the polished demo — the architecture, the data flow, the pricing model, and the trade-offs we made. If we’ve built something that genuinely serves the businesses using it, that transparency will be a competitive advantage. If we haven’t, we’d rather know now than later.
The Nugget: “The cost of a bad foundation isn’t technical debt — it’s client data at risk, compliance exposure, and the kind of trust damage you don’t recover from.”
We’ve spent months making sure the roots are solid. Now it’s time to see what grows.
We can’t wait to show you what’s next.
Hatim Zavery is the founder of Telos One, a Canadian consultancy specializing in payment processing, cybersecurity, and web development.