He Helped Build the Startup, Then Lost His Access Overnight: Inside a Co-Founder Split That Turned Friendship Into a Fight

After months spent developing partnerships, handling customers, and helping Reticket find a new business model, one co-founder says he was abruptly pushed out. His account is a cautionary tale about trust, power, and the paperwork founders put off until it’s too late.

A startup can survive a product setback, a difficult launch, or a business model that needs to change. A co-founder relationship can be harder to repair.

In a personal account published on November 16, 2026, a former Reticket co-founder describes how a friendship of several years turned into a bitter business separation. He says he joined the ticketing startup without a signed equity agreement, helped build its partnerships and operations, and was eventually removed from the company’s administrative systems after a dispute with his co-founder.

His story is one side of a conflict. The other co-founder may have a different account, and the claims described here have not been independently verified. But the details raise familiar questions for startup founders: What happens when roles are unclear? How should disagreements be handled? And what risks do people take when they rely on friendship instead of signed agreements?

From trusted friends to startup co-founders

The former co-founder says Aniket Chaudhary invited him to join Reticket in 2025. He was initially unsure about the idea, but says their longstanding friendship made him comfortable joining the venture.

According to his account, Chaudhary first offered him a 5% stake. They discussed the offer, and he says they settled on 20%. He describes their roles as complementary: Chaudhary had built the product, while he expected to focus on growth, marketing, partnerships, and operations once the platform launched.

Before launch, he says he asked to formalize their arrangement in writing. Drafts were exchanged, but the agreement was never signed. He recalls being told that the venture was being treated more as two friends building something together than as a formal business partnership.

He agreed to move forward. Looking back, he calls that decision a major mistake.

The account does not establish what legal rights either person held. It does show how an informal understanding can leave founders with sharply different expectations about ownership, authority, and what happens if the partnership ends.

A legal setback forced a new business model

Image

Reticket launched in March 2026, according to the post. Shortly afterward, the founders received a legal notice from District, the former co-founder says. He says they responded together, but that ticket resale, the company’s core idea, became difficult to pursue.

The setback could have ended the project. Instead, he says, he began exploring a second way to bring tickets onto the platform: partnerships with event organizers.

The proposed model was straightforward. Reticket could obtain ticket inventory directly from organizers, offer it to customers, and generate activity while the founders continued working on peer-to-peer resale.

He says it took months to understand how ticket distribution worked, contact organizers, negotiate deals, and establish partnerships. He also says those relationships helped the company continue operating until peer-to-peer resale returned in July 2026.

According to his account, the partnership model brought in users, revenue, industry connections, and credibility. He says the company reached about ₹20 lakh in gross merchandise value and 5,000 users over six months, with nearly 90% of GMV coming from the organizer-partnership model he had developed.

Those figures are claims in his post and have not been independently confirmed. His account says the two founders disagreed about what the numbers meant: he viewed the partnerships as a valuable growth engine, while Chaudhary questioned whether the model was helping Reticket and whether it deserved continued focus.

Operational frustrations added to the strain

Image

The former co-founder says he handled operations, organizer relationships, customer support, and Reticket’s WhatsApp community. He describes being in daily contact with customers and having a close view of what buyers wanted and which events were gaining interest.

Meanwhile, he says, Chaudhary handled technology while also working full-time at Constantinople. The former co-founder felt some basic operational needs were going unmet.

One example was collecting customers’ delivery addresses. He says he repeatedly asked for a website feature that would let customers submit addresses directly. Without it, he was manually requesting the information over WhatsApp. He says the request remained outstanding for months.

He also says he asked several times for access to the codebase so he could make small improvements or submit basic code changes himself. According to his account, Chaudhary refused.

That dispute went beyond a delayed feature. For one founder, code access may have been a matter of control and responsibility. For the other, granting access may have raised technical, security, or governance concerns. The account provides the former co-founder’s view, but not the reasoning from the other side.

The gap between their expectations appears to have widened: one founder wanted to move faster on operations and experiments; the other retained control over the product and its technical direction.

A disagreement over an independent tool became a breaking point

Image

In September, the former co-founder says he noticed repeated requests for tickets in the WhatsApp community. Customers were looking for events the platform did not yet have, and he worried that useful demand information was disappearing in the chat.

He says he asked for a feature that would let people submit ticket requests. When no product change followed, he built a small tool himself using Claude and hosted it on Cloudflare. It allowed people to request tickets or list tickets not supported on Reticket.

He says he imagined it as a community tool to reduce WhatsApp back-and-forth, not as a replacement for the company’s product. He also acknowledges that some aspects of the tool could have been handled better.

According to his account, Chaudhary objected, saying the tool could divert traffic from Reticket and asking him to shut it down. The former co-founder says he took it down after they discussed their concerns and agreed that a similar feature could eventually be built into Reticket.

He believed the disagreement had been resolved. The next day, he says, Chaudhary sent him a list of 13 reasons he was no longer considered a fit for the company and called to say they should part ways.

The former co-founder says he asked to discuss the concerns rather than jump straight to separation. He says he was willing to address each point, but believed Chaudhary had already made up his mind.

Access was removed before he could respond

Image

The account’s most painful moment came immediately after that call. The former co-founder says that before he had time to fully review the list or respond, his administrative access to company systems began disappearing.

He says the experience made him feel less like a co-founder and more like an employee who could be dismissed without discussion. He also says his name was removed from Reticket’s website.

One of the 13 reasons, as he quotes it, concerned deleting a message from the WhatsApp community using administrator rights without first informing Chaudhary. The former co-founder says he believed the message was irrelevant to the group and says he privately informed Chaudhary after removing it. He accepts that he could have handled the situation differently, but viewed it as a small disagreement that should have been discussed when it happened.

The larger issue, in his telling, was a lack of timely communication. He says concerns accumulated without being raised as they arose, then appeared all at once as the basis for ending the partnership.

A founder breakup can involve legitimate concerns about conduct, access, security, or decision-making. But when there is no written agreement defining roles and exit procedures, even routine disagreements can turn into disputes about who has authority and what each person is owed.

A separation became a negotiation

After losing access, the former co-founder says he took control of Reticket’s Instagram and WhatsApp accounts. He acknowledges that he does not consider this a good decision. He says he felt cornered because he had no signed equity agreement, no access to the codebase, and had suddenly lost control over the product and channels he had helped develop.

He says the two later tried to negotiate a settlement. He proposed receiving 50% of profits for the financial year and keeping the WhatsApp community he says he had built and managed. His account says he did not want to take the codebase or shut Reticket down; he wanted compensation for his work and a way to move on.

He says the initial offer was ₹25,000. Later discussions, he claims, included different conditions and disagreements about what had been agreed verbally. He says the pair eventually worked out a separation, including a transition for the WhatsApp community.

The post also says their settlement included restrictions on public statements. The former co-founder writes that he understood publishing his account could put his profit share at risk. That makes the post more consequential, but it also makes the written settlement especially important to understanding the situation. The post does not provide the full agreement, and readers should not assume its terms or legal effect from his description alone.

The final incident that prompted the post

The former co-founder says he continued helping former Reticket customers who contacted him on his personal WhatsApp, even after leaving the company. He says he answered questions and directed people to the right place because he still felt responsible for customers he had personally assisted.

On November 16, he says, he was removed from the company’s new WhatsApp community. Around the same time, a public message was posted about removing scammers from the group. He explicitly says he is not claiming that Chaudhary directly called him a scammer, but says the timing and context left him feeling humiliated.

He says Chaudhary told him he had been removed because he contacted someone in the group to ask whether they worked with Reticket. The former co-founder says he would have left if asked, and felt the removal could have been handled privately.

That incident, he says, ended nearly two months of silence and prompted him to publish his account.

A personal story with a business lesson

The former co-founder does not present himself as blameless. He says he made mistakes, lost his temper, and tried experiments that could have been handled better. He also says he expects Chaudhary may have his own account of the events.

That acknowledgment matters. A founder dispute is rarely understood fully from a single post, especially when the parties disagree about decisions, authority, and what they discussed verbally. Still, the account offers a clear warning for anyone building a company with a friend: good intentions do not replace a written agreement.

Founders should document the basics before a venture becomes valuable or conflict appears:

  • Ownership: What percentage does each person own, and when does it vest?
  • Roles: Who is responsible for product, technology, sales, operations, and customer support?
  • Decision-making: Which decisions require agreement, and who has authority over day-to-day work?
  • Access: Who controls code repositories, domains, social accounts, payment systems, and customer data?
  • Departure: What happens if a founder leaves or the partnership ends?
  • Compensation and work: How will contributions, expenses, and unpaid work be handled?
  • Disputes: What process will the founders use to resolve disagreements before they become public or personal?

These points need qualified legal advice and signed documents suited to the company and jurisdiction. A friendly conversation or exchanged draft can help clarify expectations, but it is not a substitute for finalizing the agreement.

The hardest loss may not be the company

The former co-founder closes his post by saying he hopes Reticket succeeds. He remembers the first customers, the first organizer partnership, and the momentum the team found after facing a legal setback. What he says hurts most is not simply losing his role, but losing a friendship and wondering whether he was ever regarded as an equal partner.

That is the emotional core of the story. Startups can make founders feel that trust is enough, particularly when the people involved have known each other for years. But when money, control, and responsibility enter the picture, assumptions can become fault lines.

The account leaves open what the other co-founder would say and how the dispute might look with both perspectives. Its central lesson, though, is difficult to miss: agree on ownership, roles, access, and exit terms while the relationship is still strong. Put it in writing, sign it, and make sure everyone understands what they are agreeing to.

Friendship may be the reason people start building together. Clear agreements help them survive when building together stops.

Leave a Reply

Your email address will not be published. Required fields are marked *