THE LATEST
27 OCT 2026 · JP BHATT LISTED FOR ORACLE AI WORLD MEETINGS · LAS VEGAS, OCT 25-28

People / The business of software quality

JP Bhatt built a business around the bugs you never see

Before ImpactQA, JP Bhatt ran an SAT training business in Arizona. His career since has joined two ambitions: making enterprise software dependable and opening doors for the engineers who test it.

Advertisement

Before he was selling software testing, Jyoti Prasad Bhatt ran an SAT training company in Scottsdale, Arizona. It is a pleasing wrinkle in the résumé of a founder now occupied with enterprise systems and artificial intelligence. Preparing students for an examination and preparing software for release have a certain family resemblance: both involve discovering, preferably in advance, where confidence exceeds competence. Bhatt has made a career in the space between the two.

Known professionally as JP, he is the founder and CEO of ImpactQA, a software testing and quality engineering business with an international customer base. His work concerns the machinery beneath the screen: whether applications behave correctly, whether connected systems exchange the right information, and whether a release is ready for the people expected to rely on it. These are unglamorous questions until an application supplies a glamorous failure.

His first engineering discipline was mechanical. He studied at Motilal Nehru National Institute of Technology in Allahabad, with his education dated 1996 to 2000. His professional career began at Polaris Software Labs. Later assignments involved clients including American Express, Toyota and JPMorgan Chase. The geography widened too, across India, the United States and Europe. Before he employed people to examine other companies’ systems, he had spent years working inside that world.

A customer’s view of the supplier

There is a particular education in being the person who receives an outsourced service. Promises arrive neatly arranged; the work arrives with rather more personality. Bhatt’s approach to ImpactQA grew partly from experience on the customer’s side of that arrangement. He brought a concern for how a testing supplier fits the actual business asking for help.

That preference appears in the company’s operating principles: engagements adapted to the client, teams that can change size, clear commercial arrangements and continuity of ownership. Such details are less photogenic than a product launch. They also determine whether the relationship survives the second project. A customer buying testing is buying evidence and judgment, along with the hours required to produce them.

ImpactQA took shape in the early 2010s. Bhatt’s own career biographies place his founding move in 2012. He chose a specialist testing business, with automation, performance and consulting among its activities. The choice gave him a defined problem to pursue. Software could acquire new features indefinitely; someone would still have to establish whether those features worked together.

A business that must pass its own test

A testing company has an awkward obligation: it sells confidence while being judged on the care of its own work. Bhatt has expressed the commercial consequence with unusual directness. His description of quality leaves little room for the comforting fiction that a supplier’s reputation will excuse its next mistake.

“Companies like us cease to exist, if we don’t maintain the quality of our offerings.”

JP Bhatt, on the economics of quality

The sentence is rather brisk for corporate prose. It makes quality a condition of staying in business. In his account, cost discipline belongs beside it. Customers have budgets as well as expectations, and a specialist supplier has to respect both. A beautiful testing strategy that cannot be sustained commercially has a short and expensive life.

His ambition also included creating employment. When he discussed the company’s purpose in 2020, jobs were part of the explanation for starting it. That gives the founder’s story a second measure of progress. The service must win customers; the business must also create work for the people who deliver it. Growth becomes a responsibility with names attached.

Backing another team’s homework

Bhatt’s involvement in cybersecurity startup Kratikal puts him on another side of the entrepreneurial table. A January 2017 funding announcement named him among the participants in its $500,000 seed round, alongside technology executives Praveen Dubey and Amajit Gupta. The amount belonged to the round as a whole. It should not be mistaken for his individual investment.

He was also a customer of Kratikal and spoke positively about working with its team. That connection is telling without requiring a grand theory of his investment style. Here was a founder backing people whose work he had encountered as a client. The relationship crossed a familiar boundary: the person paying for a service could also help finance the company providing it.

Kratikal’s founders came from the same engineering institution associated with Bhatt’s own education. The connection places the investment within a recognisable professional network of technical work, customers and alumni. It is one of the more concrete ways his career extends beyond the company whose name usually accompanies his own.

ImpactQA photo collage showing JP Bhatt with colleagues and industry contacts at meetings and events
Out of the test lab. Bhatt and the ImpactQA team in the company’s collection of meetings, events and a few well-earned group photographs. Photo: ImpactQA.

From people doing tests to people building tools

Recognition followed the company’s development. In September 2020, Bhatt’s acceptance into Forbes Technology Council was announced. In 2023, ImpactQA was classified as a Major Contender in Everest Group’s assessment of quality engineering specialist services. The latter was a company assessment, a useful distinction in a founder profile where every corporate milestone can otherwise acquire the appearance of a personal medal.

There was product work alongside the service business. In June 2023, ImpactQA announced FALCON, a low-code test automation platform. Its proposed audience included users with different levels of technical experience, using a visual interface and prebuilt components to construct tests. The underlying ambition was practical: make more testing work repeatable without requiring every user to build everything from scratch.

By October 2025, Bhatt was discussing NeX-AI with Sachin Sangle, ImpactQA’s vice president of engineering, in a company podcast. Their subject was testing energy and commodity trading systems, including difficult tax rules and access permissions. These are the sorts of details that can make a tidy demonstration look positively innocent. Real businesses bring exceptions, inherited configurations and users who quite reasonably expect yesterday’s work to survive tomorrow’s update.

The conversation covered generating tests from requirements and maintaining automation as applications change. It shows where Bhatt is directing attention: towards tools that help testing teams prepare and adapt their work. The promised efficiencies remain product claims. The interesting career development is the move from delivering testing expertise to packaging parts of that expertise into software.

The enterprise has a long memory

A partnership with Tricentis, begun in 2022, offers a concrete picture of the company’s enterprise work. An account published in January 2026 describes ImpactQA supporting an unnamed oil and gas company’s SAP S/4HANA implementation. The customer had fragmented legacy systems, regional rollouts and limited visibility into testing. A new digital core still had to accommodate a business already in motion.

The work brought together test management, automation and analysis of which processes a change might affect. The account reported more than 30 percent savings in test management costs for that engagement. This is a specific customer result, rather than a universal promise. Its appeal is easy to understand: spend less time repeating unnecessary checks while keeping a clearer account of what has been examined.

For Bhatt, whose earlier experience included large financial and manufacturing clients, this is familiar territory in a newer form. Enterprise technology has a long memory. Old decisions persist in interfaces, workflows and configurations, often after their authors have moved on. Testing has to negotiate that accumulated history before anyone can enjoy the elegance of the replacement.

One engagement, one reported result>30%

Savings in test management costs during an oil and gas company’s SAP transformation.

ImpactQA + Tricentis · Customer account published January 2026

October’s calendar, the same old question

By October 2026, the company was advertising meetings with Bhatt at Oracle AI World in Las Vegas. The agenda included cloud updates, migrations, integrations, security and AI assurance. Those subjects describe a founder still working around the consequences of change. Each new capability arrives beside the question of what it might disturb.

A company podcast published on October 23 returned to reliability in commodity and energy trading systems. Its discussion ranged across upgrades and the connections between trading, scheduling, settlement and accounting. There is a satisfying lack of glamour in that list. Money and operations depend on such handoffs, and a mistake need not be visually impressive to be expensive.

Bhatt’s public writing has travelled beyond testing terminology too. His LinkedIn articles include a March 2025 piece titled The Dark Underbelly of Commodity Trading, and earlier writing on agile methods and QA’s place in DevOps. The subjects suggest a professional conversation that keeps returning to how technical decisions meet business consequences. His trade may involve bugs; his audience also has balance sheets.

Five to ten seats at the next table

At MNNIT’s Global Alumni Convention in 2025, Bhatt made a commitment that brings the story back to engineering education: placements for five to ten students annually. The institution recorded the pledge as part of its alumni gathering. It was a promise about opportunities, with a number small enough to picture as actual people entering a workplace.

That undertaking sits beside the earlier ambition to create jobs. A founder’s public life tends to collect abstractions: transformation, scale, innovation. An offer to recruit students has a more useful shape. It connects a company’s needs with the point at which a young engineer is trying to turn a qualification into a first professional chance.

The route from a mechanical engineering course to an Arizona training business and then to enterprise testing is hardly a straight line. What holds it together is work concerned with readiness: a student facing an examination, a system approaching release, an engineering graduate looking for an opening. It is an editorial reading of his choices, rather than a slogan he has supplied.

Bhatt has built his business around work most users will never notice when it succeeds. Somewhere, an update behaves, a transaction completes and a colleague gets on with the day. There is little applause in that outcome. There is, however, a customer who can keep working, and perhaps another engineer being hired to make the next release equally uneventful.

A promise back to campus · 2025
5-10

MNNIT students offered placements annually in Bhatt’s alumni convention pledge.

Keep the conversation going