The gift was a floppy drive. The missing accessory was a computer. Anand Krishnan was in eighth grade, and his father had supplied him with a puzzle that would occupy a summer: what, exactly, was inside this thing? His account of that early fascination has the charm of a very practical joke. A device designed to make information accessible had become an object of almost complete mystery.
It is a useful place to begin with the co-founder and CEO of thinkbridge. His working life has involved a succession of more expensive versions of that puzzle. A business acquires technology. The technology contains possibilities. Getting those possibilities out, and making them useful to the person who paid for them, turns out to require rather more than possession.
Krishnan now works with growing companies on custom business software, writes about AI and engineering, and hosts conversations under the name Meaningful Tech. The adjective is doing work. He has been asking the same unfashionably concrete question for years: what improves when this system arrives?
A factory before a software company
He grew up in India in an entrepreneurial family. His father ran several businesses, including a manufacturing operation that, Krishnan recalls, employed several thousand people at one point. He spent time around the business as a child. Programming arrived early, followed by software for work close to home: invoicing, inventory and job cards.
He studied mechanical engineering. The family connection to manufacturing made that choice fairly natural, even as he taught himself to program. His father encouraged him to learn how large corporations operated before running an enterprise himself. The educational detour lasted 18 years at IBM. Corporate life, it seems, had a longer syllabus than anticipated.
In 1998, he came to the United States for what was supposed to be a two-week client assignment through an IBM partner. He stayed. Later, people from his professional network began asking for help with companies they had started. Those relationships offered a route into working with smaller businesses, where he could apply experience accumulated inside a much larger one.
The friendship that kept making things
Another relationship reaches back further. Krishnan and Sai Ganesh met at college in Bangalore in 1992. They have continued to build businesses together. Their shared history includes an early nesting-algorithm project intended to reduce metal waste, a wonderfully specific introduction to the economics of software. The output mattered because less material went into the scrap pile.
Their later ventures include thinkbridge, ZTRIC and ZPQV. The last of these, launched in 2024, describes itself as an AI-first products studio for small and mid-sized businesses. Krishnan and Ganesh live in the United States, while its team works in India. The studio extends their interest in making useful software accessible to operators who have no wish to become developers.
A long partnership supplies a different kind of continuity from a product roadmap. Technologies change; a collaborator remembers why a problem interested you before the latest technology existed. In this case, the thread runs from cutting metal more economically to helping a business capture the rules by which it operates.
The software and the work part company
At thinkbridge, Krishnan’s subject is often the distance between a company’s official systems and its actual working day. The enterprise platform records one version of events. A spreadsheet contains the pricing exception. Somebody knows which customer needs a different approval. A perfectly respectable system can require a surprising amount of human improvisation.
One thinkbridge essay illustrates the problem with a manufacturing invoice. The order, pricing, shipment and credit exception travel through different tools and people. The final invoice can be correct while the process that produced it remains largely undocumented. The apparent success of the software depends on employees supplying the missing instructions.
That observation helps explain Krishnan’s recurring concern with ownership. Buying another application does little to preserve the knowledge that exists between applications. He wants operating rules, data and context to become part of systems a business controls. Otherwise, the company keeps paying people to remember the joins.
“I believe that technology should solve real problems and not invented ones.”
Anand Krishnan
His language generally returns to the people running the company. He writes for leaders who have bought ambitious promises and then acquired the additional responsibility of making them come true. There is an implied courtesy in his position: a business owner should be able to remain interested in the business.
The prototype has excellent manners
AI makes the distinction especially tempting to forget. A prototype appears quickly, responds politely and performs its demonstration. Krishnan’s May 2026 essay on vibe coding begins with a complaint he has heard in different technological eras: an executive makes something quickly and wonders why the engineering team needs longer to put it into the company’s systems.
The tools have changed from Excel to AI coding assistants. The executive’s impatience is familiar. Krishnan accepts the usefulness of rapid prototyping, then follows the work into review, testing, integration and deployment. The attractive first version has not answered every question the running business will ask.
His practical recommendation is to treat the weekend prototype as a specification. It can show engineers the workflow the operator wanted with unusual clarity. Asking it to become the production system immediately loads a different set of obligations onto an object built for demonstration. A sketch can explain a house very well. It still has a rather casual relationship with the rain.
Faster typing, more judgment
Two other essays carry his argument further. In The Rising Skill Premium, he contends that generating more code increases the importance of people who can evaluate it. A reviewer must understand the system, recognize defects and make decisions about material that arrived faster than it once did. Productivity at one stage can create pressure at the next.
This is his argument about the profession, rather than a promise that every team will experience the same result. It challenges a convenient managerial calculation: if code takes less time to produce, perhaps the organization needs proportionately fewer skilled engineers. Krishnan asks leaders to examine what happens to production reliability before making that leap.
In The Last Translator, he considers the identity of the developer. He began writing software in the floppy-disk era; he understands the attachment to the craft. Yet the engineers he values are also the ones who recognize an unnecessary feature, anticipate a design failure or save months by thinking carefully before building.
There is affection beneath the economic argument. He makes room for the pleasure of implementation while insisting that the durable contribution is judgment. The software profession, in this telling, has always contained work more valuable than its most visible activity. AI makes that work harder to overlook.
A remote company still needs a room
Krishnan applies a similarly deliberate approach to the organization around the software. Thinkbridge operates remotely, but its account of company life includes a gathering called Work from Work. Twice a year, the team assembles in Pune for a week together. The name is an agreeable small rebellion against the solemn vocabulary of workplace policy.
The purpose is to let colleagues learn things about one another that scheduled calls and formal reviews tend to miss. Krishnan has argued that a distributed organization must deliberately create that knowledge. Remote work offers flexibility; familiarity still needs occasions on which to develop.
The arrangement offers a concrete glimpse of his priorities as an operator. Outcomes matter, but the people responsible for them cannot be understood entirely through their deliverables. A company built around useful systems still has to make time for conversations that have no ticket number.
What happens after the demonstration
By October 2026, thinkbridge was reporting that its thinkOne delivery methodology had put a tenth enterprise application live. The company describes a sequence running from observing the business and modeling its processes through generation, validation, deployment and ongoing operation. It says clients own the resulting code, data model and business logic.
Those are company-reported milestones and terms, rather than a universal verdict on custom software. They nevertheless show where Krishnan is directing the enterprise: toward responsibility for a running system, with the business’s own operating knowledge captured inside it. The work continues after the first version looks convincing.
His public writing and podcasting offer another way to pursue the same ambition. Meaningful Tech discusses software alongside strategy, data and culture. The company’s leader keeps returning to the relationship between a technical decision and the daily life of the organization that must live with it.
The childhood floppy drive has acquired a fitting sequel. Krishnan is still interested in what the machinery contains. He now spends his time asking whether the people around it can get their work done. For a career in technology, it is a pleasingly human measure of progress.