Puneet Mittal’s Quiet Bet: The Spreadsheet Era of Partnerships Is Ending

A partnership begins with optimism and very often ends up in a spreadsheet. Somewhere between the handshake and the renewal, two companies must decide which accounts overlap, who owns the next action, how a referral moves, which incentive applies, and whether anyone is looking at the same number. The vocabulary is warm - trust, alliance, ecosystem - while the machinery is gloriously unromantic.

Puneet Mittal has built a career around that machinery. He is the chief financial officer and chief operating officer of WorkSpan, the enterprise software company that makes partner operations less dependent on heroic memory and busy worksheets. His combined title is the clue. A CFO asks whether the motion makes economic sense. A COO asks whether people can run it again next Tuesday. In a partnership business, both questions arrive at once.

Mittal did not take the usual straight corridor to this particular corner office. His route ran through consumer finance, graduate classrooms, investment banks and an analytics startup. Each stop offered a different view of how companies turn intent into numbers - and how numbers turn back into decisions.

The education of an inside-out operator

At Capital One, Mittal held business manager and director roles. The setting mattered. Financial services train people to respect the small hinge on which a large door swings: a risk assumption, a cohort, a process exception, a number that looks tidy only because the mess has been pushed into another column.

He later earned a master’s degree from Stanford University and an MBA from the University of Chicago Booth School of Business. One institution is shorthand for the engineering culture of Silicon Valley; the other is famous for treating markets and management as arguments to be tested. Mittal’s later jobs would keep bringing those instincts together.

Credit Suisse and Morgan Stanley gave him the investment banker’s seat. At Citi, where he became a director in the technology investment banking group, he advised software companies on strategic alternatives and worked on transactions totaling more than $100 billion. Banking turns a company into a story told through forecasts, comparable businesses, risks and negotiated value. It also gives the adviser a view of many operating models without the luxury of living inside any one of them.

Then Mittal moved inside. At ThoughtSpot, the analytics software company, he became senior vice president of finance and strategy and handled finance, accounting, strategy and business operations. A transaction has a closing date. An operating company wakes up the morning after. Forecasts need owners, strategy needs a calendar, and growth needs enough control to remain understandable.

The banker sees the milestone. The operator sees the Tuesday morning after it.

A charming front stage, a complicated backstage

WorkSpan’s problem sits naturally at the end of that progression. Companies increasingly build, market and sell with cloud providers, service firms, software vendors and other partners. The customer may see a coherent solution. Backstage, the participating companies still have separate CRMs, approval chains, forecasts, definitions and anxieties about data.

The old method is familiar: email an account list, attach a spreadsheet, hold a call, update a portal, discover that the portal and CRM disagree, then schedule another call. It can work for a small program and a patient team. Scale turns patience into headcount.

WorkSpan’s answer is a network and set of applications for those cross-company workflows. It handles co-selling, joint planning, marketplace activity and partner data synchronization. The important word is cross-company. Ordinary business software assumes an organization can impose one process on its employees. A partnership platform must coordinate participants who keep their own incentives and authority.

That makes Mittal’s dual role unusually apt. Finance cares about attribution because executives must know what a partner motion produced. Operations cares because the attribution will be nonsense if sellers avoid the process or update it three weeks late. Data quality is partly a technical question and partly a question of whether the workflow respects how people already sell.

Capital for the long term

Mittal’s first prominent WorkSpan byline arrived in May 2020, when the company announced additional funding led by Mayfield, with Redline Capital, Microsoft’s M12, Nautilus and Knollwood participating. The timing was severe. Offices had closed, markets were unsettled, and partnership teams were learning in real time whether their processes could function without proximity.

His comment was measured. The financing, he said, would help drive growth and momentum as WorkSpan looked to “build the company for the long-term.” The sentence has the temperament of a finance operator: funding is not the achievement; it is time and capacity purchased for the work ahead.

Two years later, WorkSpan raised a $30 million Series C led by Insight Partners, with Mayfield and M12 participating. Mittal’s LinkedIn reaction was considerably less formal: “Excited to share the news about our Series C raise!!” The double exclamation marks are a tiny but useful reminder that a balance sheet can contain an emotional event.

In March 2025, WorkSpan announced a Series D round, with the amount undisclosed, to continue product development and expansion around AI-powered partnerships. The company’s language has evolved from ecosystem management toward AI teammates and automated workflows. The operating question has not changed much: can software remove clerical effort while leaving judgment, trust and negotiation with the humans?

“At WorkSpan, our Ecosystem Business Summits are annual highlights for me.”Puneet Mittal, January 2024

The social life of a systems thinker

There is another side to Mittal’s public work that keeps the software story honest. He has hosted and promoted WorkSpan’s ecosystem summits, including conversations with partner leaders from Microsoft, MongoDB, AWS, Boston Consulting Group and other companies. In January 2024 he called the annual summits personal highlights.

This is more than event enthusiasm. Partner operations cannot be solved solely with a cleaner interface. Companies need common definitions, expectations and habits. A summit is the analogue companion to a digital platform: get practitioners into one conversation, let them compare what breaks, and carry the useful language back to their own organizations.

Mittal’s public style in these moments is concise. When a partner leader announced a session with him on planning for partner-led growth in 2025, Mittal replied, “Rohan B. looking forward to this.” No manifesto. No victory lap. Five words, a name, and the meeting placed on the calendar.

That economy suits his career. He has spent years around the gap between the elaborate story a company tells and the ordinary system required to make it true. Capital One taught scale. The banks taught strategic consequence. ThoughtSpot taught the inside of a growing software business. WorkSpan gives those lessons a peculiar, useful target: the space between companies.

Four questions hiding inside one alliance

Read Mittal’s career as a practical checklist and four questions emerge. First: is the opportunity real? A banker learns to test the story against evidence. Second: is the process repeatable? An operator knows that a result produced by one gifted employee at midnight is not yet a system. Third: can the economics be explained? A CFO must connect activity to an outcome without giving every helpful touch the entire credit. Fourth: will the participants actually use the process? A polished diagram is decorative if a seller sees it as one more place to type.

Those questions travel well beyond partnership software. They apply to any project crossing departments, incentives or legal entities. Begin with the shared outcome, name the information each participant needs, decide who owns the next action, and make the evidence visible to everyone entitled to see it. Then remove any field, meeting or approval that exists only because the previous system was awkward. It is less a grand theory than a way to stop complexity from charging rent.

The finance instinct is particularly useful here because collaboration can become a refuge for pleasant ambiguity. Everyone influenced the deal; nobody sourced it. Everyone supports the program; nobody owns Friday’s update. A number forces a definition. A workflow forces a handoff. Neither guarantees wisdom, but both make disagreement specific enough to resolve.

The operations instinct supplies the necessary counterweight. Measurement can become its own bureaucracy. If recording a partner-assisted opportunity takes longer than making the introduction, the system has confused the receipt with the meal. Mittal’s combined mandate puts both failure modes on one desk: vague value on one side, burdensome proof on the other. The useful middle is evidence gathered as a natural by-product of work.

The quiet bet

Partnerships will remain human because the point is complementary judgment. A cloud provider sees distribution. A software company sees a specialized problem. A service partner sees implementation. The customer wants the pieces to arrive as one answer. No database can manufacture the initial reason these parties should trust one another.

But trust should not be asked to do clerical labor. It should not reconcile duplicate opportunities, chase referral updates or remember which incentive expires on Friday. Those tasks can become shared infrastructure. When they do, the people get to spend more time on the part that actually requires people.

This is Mittal’s quiet bet at WorkSpan. The partner economy does not need less humanity. It needs fewer occasions to waste it. Somewhere, a spreadsheet with six owners and a heroic color legend has just felt a chill.