Hey there, We just wrapped up our first build cycle of 2026, and what a cycle it was. We successfully submitted the CIF-NL subsidy proposal. Established our content strategy and finally set up proper marketing and sales systems. Most significantly, we built the first core of our proprietary software.
Looking at everything that came together these past six weeks, I'm realising that money, team, and tech have now fully aligned. Not gradually over the year, but specifically now, in this cycle. After twelve months of building Askara, we can finally do what we envisioned from the very beginning.
Let me tell you how the OpenClaw craze plays into that.
Timing the Waves
Working in six-week cycles has an underappreciated benefit when building in a landscape that shifts as rapidly as AI does. When something like OpenClaw drops and the internet loses its mind, we don't have to decide immediately whether to chase it. There's natural space within the cycle to observe, to let the initial frenzy settle, to assess whether what emerged is signal or noise. And if it turns out to be signal, we can shape our next cycles around it.
That's exactly what happened these past weeks. OpenClaw exploded with all the accompanied chaos. People exposing their entire digital lives to the whole world, breathless commentary about everything changing overnight. I watched from a distance at first, letting it play out. But as the noise subsided, something substantial remained. Something that marks a genuine inflection point in how we experience AI.
The Gap That Closed
A year ago, I had a presumption for how this could work. Write your methodology in plain language. Give an agent access to the right tools. Let it figure out how to execute. I genuinely believed we could make it work by describing the steps in a system prompt and letting an n8n agent node handle the rest.
Reality was humbling. Making an agentic flow work predictably takes significantly more than good instructions. Luckily Ritwik dove into this with passion, engineering solutions that actually work for our launching customer. While he was deep in that technical work, Simon and I had space to focus on everything else a real business requires.
But here's what shifted with MCP servers and SKILL.md files: the methodology can now become the capability directly. This isn't incremental improvement. It's a fundamental change in the relationship between human expertise and machine execution.
I've spent years developing compliance knowledge, refining frameworks through client work.
Previously, translating that expertise into software required engineering effort at every step. With SKILL.md files, we can write our methodology in structured Markdown, and that text itself becomes what the agent knows how to do. No translation layer. Our graph database handles the structured compliance data while the agent handles the reasoning.
Claude is furthest along in implementing these patterns, which is why we've been prototyping there. But Claude remains a cloud service, which creates constraints for compliance work where client data needs careful handling.
OpenClaw being open source opens a different path. The architecture we've been developing can run on infrastructure we control. The security work ahead is real: hardening the implementation, ensuring proper isolation, validating that data stays where it should. But that work doesn't diminish what this represents. The barrier between methodology and capability has fundamentally shifted. What required months of engineering translation a year ago can now be expressed directly.
This is exactly what I envisioned a year ago. The difference is that now we have a team and the budget to actually build it.
The Preparation We Didn't Know We Needed
Looking back at the past year, certain periods felt frustrating in the moment. Before the Accelerator, we were scrambling through small assignments that seemed more like distractions than contributions to our core product. With just me part-time and Simon, we didn't have enough hands for everything a real business requires.
But that wasn't wasted time. Building a strong team foundation takes months of coordinated effort. You can't rush trust. If we'd chased rapid growth earlier, we would have been chasing something that eventually would have caught up with us anyway.
And it wasn't just our internal organisation that needed this time. After the successful implementation at our launching customer at the end of 2025, I received exciting news last week. There's potential for a Qwello-wide rollout across all their European branches. About seven different EU countries.
The timing feels almost designed. Just as our tech has matured, the opportunity to deploy at scale arrives.
Where We Stand
What strikes me most is how these inflection points aligned. OpenClaw marking a fundamental shift in how AI can be experienced. Askara reaching the internal readiness to actually build on that shift. Our launching customer maturing into expansion-ready territory. None of this was orchestrated, yet all of it converged in the same moment.
I've learned to pay attention when internal and external experiences synchronise like this. It's a sign you're tapped into something larger than your own planning. The flow of things moving together, carrying you toward what wants to emerge.
The part-time structure, the breathing room it created, allowed us to respond to developments thoughtfully rather than reactively. To watch OpenClaw unfold and understand what it actually means before committing resources. To let our team and customer relationships mature at their natural pace.
Standing here at the end of this first cycle of the year, what I feel is something grounded. The readiness of a team that did the work, built the foundations, and can now move with genuine confidence.
The inflection point isn't the destination. It's where the real building begins.
With care, Ben