CEO at Kanso Code | Digital Innovation for B2B Enterprises and Startups. Unlock digital growth.

We help ambitious founders and growing companies build fast, scalable products with strong engineering foundations.

Kunso is a Strategic Engineering Partner focused on fixing product bottlenecks, stabilizing systems, and accelerating delivery.

Real outcomes:
• Mobile Wellness App — 0 to $1M ARR in 18 months, 4.9★ rating, 10,000+ reviews
• Timeleft Social Platform — scaled a 15-engineer team, 4.9★ App Store rating, 60 countries
• Asia E-Wallet — built global operations, 231K+ reviews, 4.8★ on Apple & Android

Clients work with us when:
• Product development slows down
• Adding engineers doesn’t improve delivery
• Bugs and incidents keep increasing
• The system becomes hard to evolve

We come in, fix the engineering foundation, and get the team shipping predictably again.

More: kunso.com

Mikki Kobvel

Finance & Technology (AI)

Most failures come from legacy thinking about Business <> Tech cooperation.

The old model is simple: throw money at the problem and make sure it’s secure.

That no longer works.
What it guarantees is slow execution.

Yes, it will be secure.
No, it won’t be innovative.

What works is bringing Business and Tech as close together as possible.

Move in iterations, not bloated fixed budgets.
Prove ROI with every demo, evaluated by real humans.

Repeat.

Money won’t fix this.
It only makes mistakes more expensive.

Domain experts and engineers have to move together.

#FinTech #Technology #Engineering #Execution #TechStrategy

CEO @ Kunso - Strategic Engineering for Fast-Scaling Founders

We've been using our version of secure Crawdbot in Kunso for the past 6 months using Claude Code. 

The difference is that it was set up with a security-first approach.

After seeing exposed API keys, servers with open access, and AI tools plugged straight into production systems,

I’m convinced that 2026 will be a year of cybersecurity.

#crawdbot #AIInfrastructure #moltbot

2026 is going to be full of tech migrations.

Not because it’s fun. Because maintaining old software is a nightmare.

Most systems get stuck once they “work”.
The people who built them are gone, requirements changed, and nobody really knows what’s inside anymore.

But you still pay for it.
Every new feature, every bug fix, every small change takes longer than it should.

Legacy code isn’t expensive because it’s old.
It’s expensive because it’s frozen.

What changed is that AI is finally useful for this.

Models are good at reading existing code.
They can follow the logic, spot gaps, and help untangle business rules.

With a senior engineer or architect supervising, you don’t need a big rewrite.
You migrate step by step, safely.

We’ve done this with AngularJS 1.x, Cordova, and old Python codebases.

After that, things move again.
Faster delivery, lower maintenance cost, and less fear of touching the code.

Staying on legacy tech isn’t playing it safe.
It’s just delaying the problem.

#SoftwareEngineering #LegacyCode #TechMigration #AIDevelopment

You see a lot of sexy AI demos, but almost no production examples.

Demos are meant to be perfect.
Clean inputs. One success path. Controlled output.

LLMs are now good enough to pass the same input-output case every time.

But put that same system at 10x or 100x scale, under real operational load, and it falls apart.

Not because AI doesn’t work.
Because an AI-driven system is an evolving ecosystem. It needs continuous improvement.

You tolerate mistakes from humans.
You don’t tolerate them from AI.

Founders’ mindset is often:
“It worked in the demo. Why is it failing now?”
“If it can’t replace people or save costs, we don’t want it.”

That’s short-term thinking.

Those who invest in systems, observability, and feedback loops early will benefit long-term.

#AI #Founders #EngineeringStrategy #ScalingStartups

Staff Software Engineer and Engineering Manager with deep expertise in Frontend development, leading high-load real-time streaming applications and advanced data visualisation. Co-Founder of mentor.sh, a mentorship platform connecting professionals worldwide, driving growth and building sustainable engineering communities.

Vlad Kampov

Just had a great conversation with Mikki Kobvel about the evolving role of Forward Deployed Engineers and how GenAI and LLMs are changing the leverage individuals can have inside product teams.

What stood out to me: a strong, product-minded, business-oriented engineer can now cover meaningful parts of what used to be three separate roles – engineering, product, and design.

That shift is starting to reshape how teams operate.

When one person can move from problem to concept to prototype and then to system, the cost of iteration collapses. Speed becomes a competitive advantage, not just a delivery metric.

What I’m seeing change:
- Engineers move closer to the business. Product sense and customer context become core skills.
- PMs and designers move up the value chain. More strategy, research depth, and experience quality.
- Roles become leverage, not handoffs. Impact is measured in outcomes, not titles.

My take: this doesn’t make any role obsolete. It raises the strategic bar for all of them.

Curious how this is influencing team design and hiring in your org.

Engineering Manager at Netflix | Co-founder mentor.sh | Driving scalable products, tech leadership & mentorship for global engineering community

taplio

The Battle

Mikki Kobvel

Vlad Kampov

Followers

Posts

Engagements

Likes

Performance ScoreMikki Kobvel's LinkedIn Performance

Performance ScoreVlad Kampov's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Mikki Kobvel

Vlad Kampov

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Mikki Kobvel's LinkedIn Performance

Performance ScoreVlad Kampov's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreMikki Kobvel's LinkedIn Performance