01 / FOUNDER
Knowlly
Where I build with ownership. Products, AI systems, experiments and the hard decisions that come with turning an idea into something people can actually use.
PRODUCT · AI · EXECUTION
Work / 002
Founder. Enterprise AI leader. Software engineer. Product builder.
Strategy is useful when it ships.
My work sits between vision and implementation: deciding what is worth building, designing the system, then getting close enough to the code and product to make it real.
The work, in three modes
Build the company. Lead the transformation. Stay an engineer.
02 / ENTERPRISE
Deloitte Innovation Hub
As a Senior Manager, I work across AI, data and innovation — shaping opportunities, building teams and helping move emerging technology from interesting demo to credible enterprise capability.
AI · DATA · INNOVATION
03 / ENGINEER
Still close to the machine.
Architecture, prototypes, agents, APIs, mobile apps, cloud systems and the occasional late-night rabbit hole. Leadership did not replace engineering; it made the engineering problems bigger.
ARCHITECTURE · CODE · SYSTEMS
Knowlly × Microsoft / GITEX
Building agents on Copilot, in public.
At GITEX, Knowlly showcased its Copilot Agentic Team experience as a Microsoft VIP partner — a working example of how multi-agent systems can move from architecture diagrams into real business workflows.
What I actually build
01
Agentic systems.
Multi-agent workflows, orchestration, human-in-the-loop patterns, interoperability and the architecture needed to move beyond a chatbot with a fancy label.
→02
AI platforms that can scale.
Reusable foundations for turning business use cases into prototypes, then prototypes into something with a credible path toward production.
→03
Products and demos.
Fast enough to learn, polished enough to communicate the idea, and engineered well enough that the next step is not a complete rewrite.
→04
Teams that can build without me.
The real scale test. Architecture, standards, mentoring and enough structure for good people to move faster without creating dependency on one person.
→How I judge the work
Less theatre. More useful systems.
01
Time to proof.
How quickly can we turn an assumption into something testable?
02
Path to production.
A prototype matters more when its architecture does not trap us there.
03
Interoperability.
I prefer systems that plug into the world rather than demanding the world move into them.
04
Real adoption.
The final metric is not how impressive the architecture diagram looks. It is whether people use the thing.
Selected areas of practice
AI agents + multi-agent architecture
01Enterprise AI strategy + operating models
02Product engineering + rapid prototyping
03Cloud, APIs + modern application architecture
04Mobile + web product development
05Technical leadership + team building
06The rule
I prefer shipped things to slideware.
Not because slides are useless. Because eventually the diagram has to become a system, the strategy has to become a product, and someone has to build it.