Rahul Mayekar and the art of keeping things in balance

Rahul Mayekar’s explanation of a finance company’s logo begins with objects that need no software update. There are stones, carefully balanced. There is an abacus, built for counting. There is a cairn, the modest pile of rocks that helps a traveler keep to a trail. Put them together and you have his account of Zeni’s identity: a business concerned with money, represented through balance and direction.

It is an unexpectedly tactile starting point for someone working in AI finance. The objects have weight. They can be touched. A stone will fall if its arrangement is wrong; an abacus asks someone to move the beads. In Mayekar’s telling, these references give the company a way to describe what it hopes to offer customers. Before the dashboard comes an idea about finding your bearings.

Mayekar is Zeni’s Vice President of Design and a founding member, based in Pune. His public work reaches across product, brand, marketing, and the environment where colleagues spend their days. Follow that work and the logo starts to look like a useful introduction to its author. He keeps returning to how separate parts fit together, and to the people responsible for the fit.

An abacus and a pile of stones

In August 2024, Mayekar described the company’s symbol through two commitments: balance and guidance. The stones bring the association with Zen. The abacus brings the history of precision in accounting. The cairn adds the idea of a marker placed deliberately so that somebody else can find the way.

A logo has very little room to make an argument. It must survive a small screen, a crowded page, and the distracted glance of someone with more urgent business. Mayekar’s explanation supplies the longer version: the company wants to help customers navigate their finances. The image carries a compact reminder of that intention.

“Life is all about balance.”

Rahul Mayekar, on Zeni’s identity

There is also an agreeable bit of friction in these references. Accounting suggests order; a pile of stones suggests the possibility of collapse. The attraction lies in the arrangement. For a designer, that is a productive image: elements can be ordinary on their own and still require care when brought together. Even a tranquil symbol has work to do.

The screen before the spreadsheet

Mayekar’s earlier career includes creative and web development at Reliance BIG Entertainment, and leadership of user experience and digital marketing at Dhingana. Those roles put him in the business of presenting digital experiences before his current work in finance. The responsibilities connect what a product does with how somebody encounters it.

That connection matters across very different kinds of software. An entertainment service asks a person to discover something they want. Financial software asks a person to understand something they need. Both require choices about emphasis, sequence, language, and attention. A designer has to decide what arrives first and what can wait.

Zeni’s company story begins with Swapnil and Snehal Shinde encountering slow bookkeeping while building earlier businesses. The company describes its evolution from AI software supported by experts to a broader AI platform for accounting work. Mayekar’s position places design inside that changing product context. The customer needs an experience that can accommodate the work without becoming another task to manage.

The practical interest in his career is this movement between contexts. A role in digital entertainment and a role in startup finance share a screen, but the person looking at it brings different expectations. The design brief changes with the stakes. A pleasant interface still has to give the right information its proper place.

A workplace that joins the brief

In August 2024, Zeni unveiled a new Pune office. Swapnil Shinde credited Mayekar and Mangesh Garud with building and executing its vision. Here was a design project measured in rooms and shared space, alongside the projects measured in screens.

Mayekar’s response put the team at the center of the explanation. He described an office intended to reflect the company’s culture, blend with nature, and support collaboration. He thanked Garud as a partner and acknowledged design, engineering, culture, and HR colleagues. His stated ambition extended to more spaces shaped for Zeni’s people.

A workplace gives a design leader a particularly candid audience. Colleagues have to use it repeatedly. They experience the decisions across an entire working day, rather than during a demonstration. An attractive room must also accommodate the ordinary demands of work: company, concentration, the conversation that runs longer than expected.

What makes the office episode revealing is its scale. Mayekar’s concern with an experience travels beyond a customer interface. It includes the surroundings of the people building that interface. The room becomes another place where an organization can make its intentions visible, and where those intentions meet daily use.

The people who make the pixels possible

In April 2025, Mayekar devoted a public appreciation to HR manager Chinmay Patil’s contribution to building Zeni’s design team. The language was full of Pune: misal, vada pav, tea, monsoon life. Recruiting received the sort of colorful treatment often reserved for a product launch.

His public voice is lively. The posts about colleagues arrive with emojis and affectionate nicknames, and his appreciation of Patil borrows comparisons from familiar local food. The effect is to give an organizational story a place and a tone. Pune appears as part of the telling, rather than merely as a location beneath a job title. That choice also leaves room for pleasure in the work. A discussion of hiring can sound like a conversation among colleagues who know the same city, its habits, and its jokes. The responsibilities remain serious; the prose allows the people involved to enjoy being recognized.

The point beneath the jokes was specific. Hiring had helped assemble the team. Mayekar also acknowledged Ritika Bajad’s leadership. His account widened the design story to include the people responsible for finding and supporting designers. A finished screen does not reveal the recruitment conversations that made its team possible.

He has made a similar point through a different form of appreciation. In a testimonial for designer Gopal Bhoi, Mayekar praised dependability during a difficult period with limited design resources, ownership of responsibilities, and readiness to help with additional work. His attention went to conduct under pressure, as well as to the result.

These are useful details because executive titles can make a career sound abstract. Here the concerns are recognizable: who follows through, who lends a hand, who helps the group keep moving. They suggest the qualities Mayekar chooses to recognize publicly. Reliability has no convenient thumbnail, which may be why it needs someone to write the caption.

“You follow through on your promises.”

Rahul Mayekar, addressing colleague Poonam Keny

In a response to Poonam Keny’s reflections on leadership, he connected keeping promises with trust and urged listening to teams. The comment fits beside the hiring appreciation and the designer testimonial. In each, the contribution is attached to a named person and a particular way of working.

A photograph with a long caption

A team photograph shared by Snehal Shinde in October 2024 offers another view of this habit. Mayekar supplied names for the people pictured and acknowledged collaborators who were absent. He described product, design, and marketing as working together to bring the company’s ideas into a customer experience.

The picture itself mixes a gathered group with smaller portraits beneath it. It makes a simple organizational fact visible: colleagues can contribute to the same work without standing in the same room. Mayekar’s accompanying account gives marketing a role in telling the product’s story, alongside product and design in shaping it.

A launch travels through all three. Someone has to decide what the product should do. Someone has to make its operation understandable. Someone has to explain why a customer should care. When those explanations disagree, the customer inherits the confusion. Mayekar’s emphasis on the partnership makes sense as an account of that shared responsibility.

Context enters the conversation

By July 2026, his public updates included Zeni MCP, which he described as connecting financial data with AI assistants so they could answer questions and analyze a business. He credited engineer Vishnu Prakash Bachu with building it. The announcement paired a customer-facing explanation with a person’s name.

The concern was context. A question about a business’s finances needs information about that business. Mayekar’s post placed the connection between data and assistant at the center of the story, giving readers a reason for the feature before asking them to care about the technical abbreviation.

For a design executive, that is an interesting extension of the brief. Financial information may be encountered through a conversation as well as a dashboard. The task of making it understandable remains. The interface changes; the need to orient the person using it persists.

The balance he keeps returning to

Mayekar’s public work offers several versions of the same practical question: how do people find their place in something complicated? A logo supplies a set of associations. An office gives colleagues an environment. A team photograph makes collaborators visible. A product announcement explains a connection that might otherwise remain technical.

The stones in his account of Zeni’s identity are a fitting image to return to. Each piece matters because of its position among the others. His profile takes shape in much the same way: through a product, a room, a recruiter, a colleague who keeps a promise. Look long enough at the finished arrangement and the people holding it together come into view.