About maykaTech
In 2014, two engineers left careers at companies where 'digital transformation' meant beautiful decks and stalled projects. They started maykaTech with one rule — never demo anything that isn't deployed — and hired only people who found that rule obvious.
Our story
Maya Krishnan was an engineering director watching a nine-figure transformation program produce governance committees instead of software. Adrian Kowalczyk was building trading systems where a bug was a headline and a millisecond was money. They met on a rescue project — she owned the budget, he owned the fix — and left with a shared conviction: the industry had normalized talking about software instead of shipping it.
maykaTech was their correction. Small senior teams. Working software every two weeks. Burn reports the client reads before asking. Twelve years later the company is 180+ people across four offices, but the operating system hasn't changed — including the founding rule about demos, which has now killed exactly four sales presentations and saved roughly four hundred projects.
We stayed private and bootstrapped by choice. No investor timeline has ever forced us to staff a project with juniors, chase billable hours, or say yes to work we couldn't do well.
By the numbers
The statistics we track internally and publish externally — same numbers, both places.
0+
Products shipped to production
0%
Client retention over three years
0+
Engineers, designers & architects
0
Countries with active clients
Milestones
The moments that shaped the company — including the accidents.
2014
Maya and Adrian start maykaTech with three engineers and a rule that still stands: never demo anything that isn't deployed.
2016
A stalled healthcare platform arrives eighteen months late. We ship it in seven — and inherit our modernization specialty by accident.
2018
Our first full data-center migration completes with zero downtime. The client's CFO frames the final AWS bill next to the old hosting invoice.
2020
London and Bengaluru open. Remote-first delivery becomes permanent — clients notice velocity went up, not down.
2023
After a year of internal tooling experiments, we formalize the AI practice around a rule that predates the hype: production or it doesn't count.
2026
180 people, 23 countries served, 96% client retention — and the same founding rule about demos.
Values
Every company lists values. Ours show up in code reviews, estimates, and the occasional lost deal.
The estimate that's too optimistic, the scope that's too big, the approach that isn't working — we surface it when it's cheap to fix, not when it's a crisis. Clients keep us around for this more than anything.
Quality lives in defaults: typed code, tested paths, reviewed changes, documented decisions. We don't rely on heroes because heroes burn out and take the knowledge with them.
Every design debate ends the same way — go watch someone use it. Observed behavior outranks the loudest opinion, including ours.
We work on systems that outlive engagements, teams, and sometimes companies. Writing things down is how we respect the person who inherits our work — often our future selves.
Leadership
Practice leads who still write code, review designs, and take the occasional 2 a.m. page.
Co-Founder & CEO
Former engineering director at a Fortune 100 retailer, Maya founded maykaTech in 2014 after watching too many consulting projects deliver slideware instead of software. She still reviews one client codebase a month to keep herself honest.
Co-Founder & CTO
Adrian spent a decade building trading infrastructure where a millisecond was money and a bug was a headline. He brought that discipline to maykaTech's engineering culture — and wrote the first version of our delivery playbook on a flight to a client rescue.
Head of AI Engineering
Sofia leads the practice that ships our LLM and machine learning systems. Previously a research engineer in applied NLP, she's known internally for the phrase 'show me the eval' — which has killed more bad AI ideas than any committee.
Principal Architect
David has led four of our largest monolith decompositions and still argues that half of them could have stayed monoliths. Clients request him by name for architecture reviews precisely because he'll tell them not to build things.
Web Platform Lead
Emma owns our web performance practice and the CI budgets that keep client sites fast long after launch. Her team's replatforms have survived three Black Fridays without a single degraded checkout.
Modernization Practice Lead
Rachel specializes in the systems everyone else is afraid of — twenty-year-old billing engines, undocumented mainframe jobs, and databases held together by one retiring engineer's memory. Her cutovers are famously, deliberately boring.
Global presence
Client teams are staffed for at least four hours of overlap with your core hours — wherever you are among our 23 countries.
USA
Headquarters
USA
Delivery Center
UK
European Operations
India
Engineering Hub
Thirty minutes with a practice lead — bring your hardest problem and we'll sketch an approach live. If we're not the right fit, we'll say so and point you somewhere better.