How a Trusted Employee Can Walk Out and Open a Competing Business
Most businesses do not lose customers, pricing intelligence, or competitive advantage the day an employee resigns. They lose them years earlier by failing to define ownership, protect confidential information, and document critical business relationships.
The resignation email arrives on a Tuesday. It is polite, professional, and entirely expected ,good people move on. The handover is smooth. The farewell drinks are warm.
Then, six weeks later, a long-standing client mentions almost as an aside that your former employee has been in touch. With a similar service. At a sharper price. Using a pitch that sounds remarkably familiar.
No stolen laptop. No dramatic midnight download. No obvious paper trail. Just a business that looks like yours , built by someone who spent years with your company.
This is not a hypothetical. It is the commercial reality at the centre of Sonani Industries Pvt. Ltd. v. Prime Diamond Tech.
In that dispute, a former employee went on to establish a competing operation in the same specialised industry. The question before the court was not simply whether the employee had done something wrong. The deeper question ,the one that exposed a gap every business should recognise ,was: what had the company done to protect itself before the employee ever walked out?
Had Sonani clearly defined what information was confidential? Had it documented who owned the client relationships? Had it established, in writing and in practice, that its pricing models, technical processes, and commercial intelligence belonged to the company ,and not to the person who had been given access to them?
This article is not a legal case summary. It is a practical prompt for every founder, HR leader, and management team: ask these questions now, while there is still time to answer them properly.
What Made Sonani Industries Vulnerable: The Risk Hidden in Everyday Business Operations
Sonani Industries operated in a specialised market ,one where commercial relationships, pricing structures, and technical processes were built up over years and formed the core of its competitive advantage.
When Prime Diamond Tech entered that same market ,founded by, or associated with, individuals who had previously worked within Sonani's orbit ,the questions raised were predictable: where did that knowledge come from? How much of it was built from personal skill and industry experience, and how much of it was built from Sonani's own commercial intelligence?
That distinction ,between what an employee earns through effort and what an employer builds and owns ,sits at the heart of every post-employment dispute. And it is almost never resolved cleanly.
A Well-Placed Employee Has Access to the Full Commercial Playbook
Think about what a senior employee inside a business like Sonani would typically have access to. Not just one or two pieces of information ,the full picture:
Which clients were buying, on what terms, and at what price
When client contracts were due for renewal and how sensitive each client was to price changes
Which competitors had been beaten in pitches, and what arguments worked
Which internal processes made delivery faster or cheaper than rivals
Which relationships were fragile and which were locked in
None of that knowledge disappears when the employee submits their resignation. It travels with them, in their memory, their habits, and their professional instincts.
The real question in the Sonani dispute was not whether the former employee possessed this knowledge. They clearly did. The question was whether Sonani had ever established ,in writing, in practice, and in culture ,that this knowledge belonged to the company and carried ongoing obligations after departure.
Why Most Businesses Wait Too Long
Confidential business information extends beyond general knowledge and includes valuable assets created or developed through company resources and investment, such as client lists, pricing models, proprietary processes, and operational know-how. In practice, the distinction between an employee’s personal knowledge and the company’s confidential information is often blurred.
A salesperson may struggle to separate insights gained through experience from information provided by the company, just as a technical lead may find it difficult to distinguish personal expertise from company-developed systems. For this reason, the responsibility for defining and protecting confidential information rests with the company, which must clearly identify, document, control access to, and consistently treat sensitive information as confidential in its day-to-day operations.
The Structural Risk: One Employee Becomes the Whole Relationship
Many smaller and mid‑sized businesses allow a single person to become the client’s entire relationship. The client stops thinking of the company as the supplier and starts thinking of the person.
When that person leaves and returns as a competitor, the company does not just risk losing a contract. It risks discovering that, in the client’s mind, the relationship never really belonged to the company at all.
Shared account visibility, documented client interactions, and structured relationship management are not bureaucracy. They are evidence that the relationship belongs to the business, not to one individual.
The Four Documentation Failures That Decide Most Post-Employment Disputes
When a dispute like Sonani v. Prime Diamond Tech reaches the point of litigation, the court's inquiry moves quickly from what the former employee did to what the company documented ,and when. Four failures appear repeatedly in these cases.
Failure 1: No Employment Agreement, or One That Does Not Reflect the Actual Business
A clause that says "the employee must keep confidential information confidential" without defining what confidential information means in this specific business is a clause that will be argued over. A generic template downloaded from the internet and never adapted to the company's actual operations is not a shield ,it is an invitation to a dispute.
What does your business actually treat as sensitive? Client pricing? Vendor terms? Technical processes? Delivery workflows? Internal sales data? These need to be named, not implied.
Failure 2: No Clear Statement of Who Owns What
Founders typically assume that anything created during employment belongs to the company. Employees sometimes hold a different view ,that relationships they personally built, or knowledge they personally developed, have a personal dimension.
These assumptions are never tested until the employment ends. If the employment agreement does not clearly state that all work product, client intelligence, and commercial know-how developed during employment belongs to the company, that gap becomes the first thing a departing employee's lawyers will exploit.
Failure 3: Confidentiality Treated as a One-Time Formality, Not an Ongoing Practice
A confidentiality clause signed on the first day of employment, never referred to again, never reinforced through access controls or document handling, creates a much weaker legal position than a business that actively treats confidentiality as a daily practice.
In Sonani's situation, the ability to show that confidential information was consistently marked, controlled, and handled with care would materially strengthen the argument that the departing employee knew ,or should have known ,that certain knowledge was proprietary and protected.
Failure 4: No Audit Trail of Who Accessed What
If a dispute is filed, the company will need to demonstrate what information the former employee had access to and when. Without access logs, system records, or documented briefings, this becomes a matter of assertion ,and assertions without evidence are difficult to sustain in court.
Who had access to the pricing database? Who was present in client negotiations? Who received the internal strategy documents? If these records do not exist, the company cannot prove misuse even when misuse is obvious.
Where Legitimate Competition Ends and Unfair Competition Begins
Before drawing conclusions about what went wrong in the Sonani situation, it is worth being precise about something: not every employee who leaves to start a competing business has done something wrong. The law permits competition. It does not permit unfair competition.
The boundary between the two is not always clear ,but it is where every dispute of this kind is ultimately decided.
What a Former Employee Is Allowed to Take
A former employee can take their skills ,the negotiation techniques they have refined, the technical expertise they have developed, the industry relationships they have built through their own effort and reputation. These belong to the person and always will.
They can take general knowledge of how a market works ,typical price ranges, common client concerns, industry norms. This is background knowledge, not proprietary information.
They can compete with their former employer. They can approach former colleagues. In many cases, they can even approach clients ,unless a valid and proportionate restriction prevents it.
What They Cannot Take
They cannot take confidential information that belongs to the business ,client lists compiled at company expense, pricing models developed through internal investment, technical processes that represent the company's proprietary know-how.
They cannot use a business relationship that was built using company resources, company reputation, and company time as if it were a personal asset.
They cannot compete in a way that is built on appropriating the employer's commercial intelligence rather than developing their own.
The central question in Sonani v. Prime Diamond Tech was precisely this: was Prime Diamond Tech built on its founders' own ingenuity and legitimately acquired skill ,or was it built, in material part, on Sonani's accumulated commercial intelligence? That question cannot be answered without the documentation that Sonani either had or did not have before the dispute arose.
Five Things Every Business Should Do Before the Next Resignation Letter Arrives
The Sonani dispute is a familiar scenario dressed in specific facts. Most founders will recognise elements of their own business in it. The response is straightforward, even if the work is not.
1. Do Not Give Sensitive Access Before the Employment Agreement Is Signed
Client pricing, internal strategy, technical documentation, and vendor terms should not be shared until a proper employment agreement, not just an offer letter, is executed.
2. Write Confidentiality Clauses That Reflect Your Business
Name what is confidential: client records, pricing data, delivery processes, technical systems, supplier relationships. Generic language protects generically. Specific language protects specifically.
3. Make Confidentiality a Practice, Not Just a Signature
Mark sensitive documents. Use role‑based access so people see only what they need. Brief employees when they receive particularly sensitive access. Create a paper trail that shows the company treated this information as protected.
4. Ensure Client Relationships Are Owned by the Company
No single employee should be the sole keeper of a strategically important client. Maintain shared records of client history and status. Introduce clients to more than one person. Use structured handovers so relationships clearly sit with the company.
5. Take the Exit Process Seriously
A structured exit is not an accusation. It is discipline. On every departure, confirm confidentiality obligations, retrieve devices and credentials, and document handover of clients and projects. Do this consistently, not just when a resignation feels suspicious.
The Sonani Lesson: Protect the Business Before You Need the Protection
Sonani Industries v. Prime Diamond Tech is, at its core, a story about timing. Not the timing of the resignation, or the timing of the competing company's launch, or even the timing of the first client approach.
The timing that mattered was years earlier ,the moment when the company should have documented what it owned, what was confidential, and what it expected of the people it trusted with that knowledge.
Companies that lose disputes like this are rarely the ones whose employees behaved the worst. They are the ones who waited too long to define the rules ,and found themselves arguing about those rules in a legal proceeding that could have been avoided entirely.
Employment agreements are not HR formalities. Confidentiality practices are not compliance theatre. Exit processes are not bureaucratic rituals. They are the infrastructure of a business that knows what it owns and is prepared to defend it.