A consultancy usually sells its wisdom by the hour. The client buys the answer, the team moves on, and somewhere a slide deck begins a dignified retirement in a shared drive. Rajeev Kumar chose a more stubborn model. When the same problem kept returning, his company tried to turn the answer into software.
That decision explains much of Mirketa, the California technology company Kumar founded in 2003 and now leads as chief executive and chief product officer. It implements enterprise platforms, untangles integrations and manages cloud systems. It also builds products: tools that route leads, find duplicate records, distribute reports, forecast sales and support specialized workflows. Advice goes in. Reusable intellectual property comes out.
The arrangement suits a founder trained to notice the machinery beneath a business. Kumar studied electrical engineering at an Indian Institute of Technology, then earned an MBA in information systems from IIM Lucknow. His early American career passed through Charles Schwab, Washington Mutual, Wells Fargo and Blue Shield of California. The titles changed from business analyst to project manager to vice president and director. The underlying job remained recognizable: find where a large organization gets stuck, then make its people and systems move together.
An education in friction
At Wells Fargo, Kumar served as vice president of operational excellence. His remit included leading Agile coaches as an eBusiness group moved away from waterfall delivery. Later, at Blue Shield of California, he worked on another Agile transformation: assessing process, people, systems and culture, then defining the future state. These were not glamorous assignments. Transformation work happens amid dependencies, competing incentives and the diplomatic art of persuading a meeting that it may not need three more meetings.
An informal Mirketa portrait, kept at its native resolution.
Kumar carried a useful suspicion from those rooms: a good team can still fail. He made that the subject of a short case-study collection, Tales of (Good Teams') Failures. The premise is pleasantly inconvenient. Bright people with records of success can miss an expected result because the system around them is vague, brittle or poorly governed. Talent is not a spell. It needs clear ownership, honest feedback and a process that lets reality arrive before the deadline.
His public recommendations add texture to the systems thinker. Former colleagues describe an Agile champion, a strong negotiator and a good listener. One colleague credited him with thinking through client solutions quickly while maintaining a motivating culture. Another connected him directly to a large organizational change program. These are third-party descriptions, but they rhyme with the company Kumar built: process-conscious, client-facing and unusually willing to make “fun” one of its stated values.
“AI should feel like a natural extension of your team, not another tool to manage.”
The product hidden inside the project
Mirketa began as a business and IT consulting firm. Its center of gravity eventually settled around Salesforce, with NetSuite, ServiceNow, Oracle and integration work broadening the practice. But Kumar's product title matters as much as his CEO title. Round Robin Distributor automates the routing of leads and cases. Duplicate Search and Merge addresses dirty CRM records. eCourier schedules and distributes Salesforce reports. Finacast tackles financial and sales forecasting. Elixir packages a set of industry workflows on the Salesforce platform.
Each product has the air of a consultant's recurring headache made concrete. Routing sounds trivial until territories, capacity and service levels collide. Duplicate data sounds cosmetic until several versions of a donor or customer produce several versions of the truth. Forecasting sounds like a spreadsheet until a sales leader asks which assumptions made the number wobble. The product opportunity appears where the annoying exception becomes a pattern.
The Mirketa loop
A simplified editorial model of the services-to-software pattern visible in Mirketa's portfolio.
That loop has been running for years. In 2017, Mirketa released Delphi, a Salesforce-native sales forecasting application that used machine learning to learn from historical data. Kumar's explanation at the time was plain: existing approaches were too simplistic for clients. He was discussing applied machine learning before enterprise AI acquired its present wardrobe of agents, copilots and breathless keynote demos.
The current vocabulary has changed, but the practical instinct has not. Mirketa now talks about AI-assisted documentation, predictive donor engagement, workflow automation and intelligent orchestration. Kumar's best line on the subject is also a product test: AI should feel like an extension of the team, not an extra tool that demands care and feeding. It should enter the workflow where the work already happens.
Selected milestones, shown by progression rather than duration.
A company on two clocks
Mirketa operates between Dublin, California, and Noida, India. One clock follows customers and enterprise sales. The other follows delivery teams and product engineering. Distributed companies love to describe themselves as seamless. Time zones retain a sense of humor about that claim. Kumar's answer appears in the company's working language: transparent delivery, two-week sprints, client focus and explicit ownership.
There is a warmer clue in the company scrapbook. In 2025, Mirketa posted about a delayed Holi celebration after Kumar flew in from the United States. The Noida office filled with color, laughter and the sort of photographs that make corporate headshots look tragically underdressed. It is a small story, but leadership is often legible in small stories. Kumar speaks the dialect of governance and process; he also turns up for the festival.
Culture, in his telling, is operational too. In a Forbes India company feature, Kumar called hiring the most important decision and emphasized selecting for technical and nontechnical attributes without compromise. Mirketa's workplace materials pair that selectiveness with flexibility, learning and recognition. The company was named an Inc. Best Workplaces honoree in 2022. The tidy lesson is that rigor and warmth are not rival management theories. A useful operating system has room for both.
Teaching the seam
In September 2022, Kumar addressed several hundred students at IIM Raipur about careers in business and technology consulting. His own résumé was an apt syllabus. Consulting lives at a seam: technology on one side, incentives and behavior on the other. The person who can translate across that seam becomes valuable long before becoming senior.
Kumar's route also resists a fashionable myth about founders: that the useful years begin at incorporation. His analyst work taught him to model a problem. Project management taught him dependencies. Operational excellence taught him to inspect a system. Transformation work taught him that a process diagram cannot persuade a human being. Mirketa gave those lessons somewhere to compound.
The company has earned recognition along the way, including a 2024 NetSuite Alliance Partner Spotlight Award for consumer-goods work. Yet the more revealing achievement is structural. Mirketa has kept services and products under one roof. Services keep the company close to awkward, current problems. Products force it to express what it has learned in repeatable form. One side supplies reality; the other refuses to forget it.
There is an advisory strand to Kumar's career as well. Consumer51 lists him among its advisors and notes his earlier leadership work across major financial and service organizations. Advising is an unsurprising side role for someone whose main occupation is translation. It asks for pattern recognition without the luxury of owning every decision. The advisor has to see the shape of the problem, make the useful part legible and then let another team carry it forward.
His six published LinkedIn articles offer the same habit in miniature. The subjects range from predicting Salesforce project success to recognizing a client's partner award and, most recently, the architecture required to add AI to older applications. The topics have moved with the market. The questions underneath have stayed steady: what makes an implementation work, where does responsibility sit, and how can a technical choice survive contact with an actual organization?
A project solves the client's Tuesday. A product tries to make next Tuesday easier too.
What comes next
Kumar's recent public work points toward an AI-first version of the same model. In 2026, he wrote about the architectural demands of adding AI to legacy and SaaS applications. Mirketa announced a Salesforce-native donor-management accelerator using prediction, content generation and agent orchestration. In another update, Kumar praised a team that moved a nonprofit from an older Salesforce package to Nonprofit Cloud in six weeks under a hard cutoff. The technology varies. The fixation on the working system remains.
That fixation protects the story from becoming a parade of buzzwords. Kumar's career began around enterprise constraints, where every shiny idea eventually meets data quality, governance, security, adoption and somebody's unmovable quarterly deadline. His aspiration is visible in what Mirketa now builds: automation that participates in work instead of hovering above it.
There are louder ways to describe a technology company. Kumar's way is more useful. Listen for the problem that repeats. Solve it with the client. Preserve the lesson. Improve the system around the team. Then, if the calendar permits, fly across an ocean and arrive in time for the colors.