Expertise is more valuable when it comes with context.
The hardest technology problems are rarely just technology problems. They sit at the intersection of software, business transactions, operational realities, customer expectations, economics, and risk.
Punditry is built around people who develop depth across those boundaries. We call them Pundits.
A Pundit does not approach a problem with a preferred technology, architecture pattern, or delivery model.
They first understand the business the system supports, the transactions that matter, the constraints that have accumulated, and the consequences of getting the decision wrong.
They then determine what actually needs to change.
Technology consulting should understand more than technology.
This is the belief that led to the creation of Punditry — a consultancy built to solve what conventional consulting overlooks.
“Why did the people behind Punditry believe another kind of technology consultancy needed to exist?”
Punditry was started after years of building and modernizing mission-critical systems at the intersection of commerce, payments, and transactions. We saw a pattern.
Projects didn't fail because of technology. They failed because the solutions didn't fit the business, the operations, or the real world constraints. We believed clients deserved partners who could connect engineering depth with functional-domain understanding to solve the right problems, not just deliver software.
The name Punditry comes from the word Pundit — someone who combines knowledge, insight, and judgment to guide smart decisions. Inside our company, a Pundit is an engineer who thinks beyond code, understands the business, and takes ownership of outcomes.
We built Punditry to create long-term relationships based on trust, transparency, and results that matter. We choose to work on problems where we can add true value — and we choose not to be everything to everyone.
We exist to bring context, clarity, and conviction to complex technology decisions.
What Is
a Pundit?
Deep expertise in technology.
Equal curiosity about the business it serves.
Great software engineering requires technical depth. But when software becomes critical to a business, technical depth alone is not enough.
A Pundit develops an understanding of both the engineering discipline and the functional world surrounding the system.
The objective is not to turn technologists into business generalists. It is to develop specialists who understand enough of the whole system to make better technology decisions.
A Pundit connects technical depth with functional understanding to design, build, and evolve systems that drive real business outcomes.
Understand before changing.
We first understand why the system became what it is before deciding what should change.
HOW PUNDITS
THINK
Context before prescription.
We believe difficult systems deserve deliberate thinking.
That leads to a few principles that shape how we approach our work.
These principles help us understand complex systems deeply, make better decisions, and deliver outcomes that last.
Preserve before replacing.
We preserve what continues to serve the business and focus change where it creates meaningful advantage.
Business outcome before architectural fashion.
The right solution is the one that improves the business's ability to grow, operate, respond, and change while managing risk and cost.
Look at the whole transaction.
We follow the complete business transaction rather than optimizing individual technical components in isolation.
Challenge the obvious answer.
Understanding the underlying problem often changes the solution.
Leave the client with more capability.
Good consulting should leave behind stronger systems, clearer architecture, better operational knowledge, and greater confidence inside the client's organization.
The People Behind Punditry
Expertise comes from individual journeys.
Punditry's point of view is shaped by the people who make up the firm. Each Pundit brings a different combination of technology experience, functional-domain understanding, operating experience, and lessons learned from systems that have succeeded—and systems that have been difficult.
Rather than traditional corporate biographies, these stories explain how each person's experiences shaped the way they think about technology today.
Poulamy Ghosal
Co Founder, CTO
Poulamy is responsible for the architectural correctness and technical execution of Punditry’s work. She partners with businesses to identify where technology can improve efficiency and return on capital, then translates those opportunities into systems that can perform reliably in production. Her architecture experience spans generations—from AS/400 and COBOL systems to distributed cloud-native platforms and AI agents. That breadth shapes a core belief: understanding how systems evolved is often the best starting point for deciding how they should evolve next.
Vamseedhar Yerukala
Co Founder, COO
Vamsee’s expertise is people. He believes successful technology is ultimately built by capable, motivated people working in the right environment. Drawing on years of experience identifying and building engineering talent across fintech, commerce, and technology organizations, he helps Punditry create teams where expertise, ownership, and motivation reinforce each other. His focus is ensuring the people behind the technology are positioned to do exceptional work.
Kuldip Chakraborty
Co Founder, CEO
KC works at the intersection of business strategy, enterprise architecture, and revenue-critical transaction platforms. He helps organizations shape technology strategy, prioritize modernization roadmaps, and make architecture decisions around business risk, scale, and return. At Punditry, he also leads the development of reusable IP and frameworks designed to help clients execute faster and reduce the cost and uncertainty of solving complex technology problems.
Expertise across
generations of
technology.
We've worked through enough technology cycles to know the difference between change and progress.
Punditry's experience spans seven generations of enterprise technology. Why does that matter? Because most business-critical environments are not greenfield. They contain multiple generations of technology that have to coexist.
Our role is to understand where each generation still provides value, where it creates constraints, and how the platform should evolve.
Mainframes
Long-lived transaction systems
Java
Enterprise application platforms
Modern Apps
JavaScript, Node.js & Python
Distributed
Event-driven architectures
Cloud
AWS & cloud-native platforms
Data
Operational intelligence systems
AI + Agents
AI and agentic applications
Technology expertise becomes more powerful when you understand what the transaction means.
Commerce and payment systems have their own language, operating realities, and failure modes.
These concepts cannot be treated simply as fields moving through software. They represent business processes, money movement, customer commitments, and operational responsibilities.
The deeper the understanding of that context, the better the technology decision.
TRANSACTION & DOMAIN VOCABULARY WE OPERATE IN
Usually when the easy answer isn't good enough.
Clients tend to bring us into situations where several concerns collide and traditional software consulting falls short.
The system is critical, but difficult to change.
Growth is good, but increasingly expensive to support.
The obvious technical answer carries too much business risk.
Multiple systems or partners are involved and nobody owns the entire problem.
A major architecture decision needs to be made with incomplete information.
An incident has exposed weaknesses that cannot simply be patched over.
A promising AI opportunity needs to become a controlled production capability rather than a prototype.
These situations benefit from people who can move between the business conversation and the technology conversation without treating them as separate worlds.
Bring us into the problem, not just the implementation.
The most productive Punditry engagements start before somebody has already decided exactly what must be built. We work with founders, executives, technology leaders, architects, product teams, operations teams, and domain specialists to understand the situation from multiple perspectives.
Advise
Clarify technical strategy, evaluate architecture options, and assess business risk.
Architect
Design resilient systems, transaction models, and evolution roadmaps.
Build
Execute critical platform capabilities, integrations, and high-performance components.
Pivot & Direct
Help an existing technology team reset direction and rebuild execution velocity.
What remains constant is accountability for the quality of the thinking behind the solution.
Specialization requires knowing what you are not trying to become.
We are most valuable when the problem is important enough that understanding what should be done is as important as doing it well.
Punditry is not built around supplying technology capacity.
We are not trying to be the largest team in the room.
We do not believe every legacy system needs replacing.
We do not introduce technology because it is fashionable.
We do not treat AI as a mandatory ingredient in every solution.
And we do not measure success by how much software we create.
Better decisions. Stronger systems. More options for the business.
A successful engagement should leave the client able to do something they could not confidently do before:
Handle substantially more customers.
Introduce a new revenue stream.
Integrate another part of the ecosystem.
Recover from failures more gracefully.
Understand transaction behavior sooner.
Operate at lower marginal cost.
Modernize without creating unnecessary disruption.
Introduce AI without surrendering control.
Or simply make an important technology decision with greater confidence.
That is ultimately what Punditry exists to provide.