From Brand Manager to Startup Founder: Why I Co-Founded PitchNDA

A creative director I had worked with for years called me one evening, frustrated and a little defeated. She had pitched a campaign concept to a prospective client in an informal meeting — no contract, no NDA, just a conversation. Six weeks later, she saw a version of her concept running on billboards across Mumbai, executed by a different agency. The client had taken her idea and handed it to their incumbent partner.

She had no recourse. No paper trail. No proof that the idea had originated with her. And no practical way to have prevented it.

That conversation was one of several that crystallised the problem I would eventually build a company around. But the path from recognising a problem to actually founding a startup was neither linear nor rational. It was messy, terrifying, and — in ways I did not expect — the most educating experience of my career.

The Problem Space

The gig economy was accelerating rapidly by 2016. Freelancers, independent consultants, small agencies, and creative professionals were pitching more work to more clients through more channels than ever before. The volume of unsecured idea exchange was enormous.

Here was the fundamental tension: to win work, you had to share your ideas. But sharing your ideas without protection meant anyone could take them. The traditional solution — a Non-Disclosure Agreement — was theoretically available but practically useless for most independent professionals. NDAs required legal knowledge to draft, created friction in early-stage conversations (nobody wants to start a potential client relationship by asking them to sign a legal document), and were expensive to enforce even if they existed.

I started counting. In my own network of creative professionals, brand managers, and consultants, I found that fewer than 10% used any form of IP protection when sharing ideas in pitch contexts. The remaining 90% were operating on trust alone. And as the gig economy grew more competitive and more transactional, that trust was increasingly misplaced.

The insight was not that NDAs were valuable — everyone knew that. The insight was that the existing NDA process was fundamentally incompatible with how modern creative professionals actually worked. They needed protection that was embedded in their workflow, not bolted on top of it.

The Emotional and Financial Calculus

I want to be honest about what it felt like to consider leaving a successful brand management career to start something from scratch. By 2016, I had spent several years working on major FMCG campaigns and million-dollar brand launches at some of the best agencies in India. I had a clear career trajectory. I had stability. I had the kind of professional identity that made my parents comfortable at family gatherings.

Walking away from that was not a moment of inspiration. It was a slow negotiation with fear.

The financial calculus was straightforward and sobering. I had enough savings to sustain myself for roughly 12 months without income. The opportunity cost of leaving a salaried role was real and quantifiable. If PitchNDA failed — and most startups fail — I would re-enter the job market having “lost” two to three years of career progression in a competitive industry.

The emotional calculus was harder to quantify. There was the fear of failure, obviously. But there was also a subtler fear: the fear of discovering that I was not capable of building something from nothing. In agency and brand management, I had always operated within structures. Someone else had built the company, established the client relationships, created the processes. My job was to excel within those structures. Founding a company meant building the structure itself, and I genuinely did not know if I could do that.

What tipped the balance was not a grand epiphany. It was a pragmatic assessment: the problem was real, the market was growing, and my specific background — sitting at the intersection of creative industries and business — gave me a perspective on the problem that most technologists lacked. If not me, who? And if not now, when?

Defining the Product Vision

PitchNDA’s core proposition was embedding NDA-level protection directly into the file-sharing workflow. Instead of asking a client to sign a separate legal document before you shared your pitch deck, you would share the deck through PitchNDA, and the platform would automatically generate and attach a legally structured NDA to the shared file. The recipient could view the content, but the act of accessing it constituted acknowledgment of the NDA terms.

This was not a trivial technical or legal challenge. We needed to ensure that the auto-generated NDAs were legally sound across multiple jurisdictions. We needed to build a file-sharing experience that was frictionless enough that users would actually adopt it instead of just emailing their decks as attachments. And we needed to price it accessibly for freelancers and small agencies who were our primary target market.

My co-founder and I spent the first three months purely on problem definition and validation. We interviewed 40+ creative professionals — freelance designers, independent consultants, small agency founders, filmmakers, musicians — and mapped their existing workflows for sharing creative work.

Three patterns emerged consistently:

Pattern 1: Protection was desired but perceived as impractical. Every single person we spoke to had either experienced idea theft or knew someone who had. They all wanted protection. But the effort required to implement it — drafting an NDA, getting it reviewed, having it signed — was seen as prohibitively cumbersome for the volume of pitches they were making.

Pattern 2: The moment of maximum vulnerability was the initial pitch. Once a project was won and contracts were signed, IP protection was typically included. But the initial pitch — the moment when you shared your best thinking to win the work — was almost always unprotected. This was where the leakage happened.

Pattern 3: Trust eroded with scale. Professionals who worked with a small number of long-term clients felt relatively safe. But as they scaled — taking on more clients, working through platforms, engaging with unfamiliar contacts — trust became unreliable. The gig economy was inherently a trust-erosion engine.

These patterns gave us confidence that the problem was real and the timing was right.

Building the MVP

Our MVP was deliberately minimal. The first version of PitchNDA did three things: it allowed you to upload a file, it auto-generated an NDA based on configurable parameters, and it created a secure sharing link that bundled the file with the NDA. That was it. No analytics, no collaboration features, no integrations.

We built it in roughly four months. My co-founder led the engineering, and I led everything else: product definition, user research, positioning, early marketing, and business development.

The most important decision we made during the MVP phase was what not to build. Every user interview surfaced feature requests — “Can it watermark documents?” “Can it track who viewed what?” “Can it integrate with Google Drive?” — and the temptation to build all of it was strong. We resisted. The MVP needed to validate a single hypothesis: would creative professionals change their sharing behaviour if protection was embedded and frictionless?

The answer, based on our first 200 users, was a cautious yes. Adoption was strongest among freelancers who were actively pitching — people sharing five or more decks per month. For them, the time cost of using PitchNDA versus email was negligible, and the protection value was immediate and tangible.

Early-Stage User Interviews

I conducted roughly 15 in-depth user interviews during the first six months post-launch. These were not surveys or feedback forms. They were 45-to-60-minute conversations where I watched users interact with the product and asked them to narrate their thought process in real time.

Three findings reshaped our roadmap:

Finding 1: The NDA language scared some recipients. Several users reported that clients had pushed back on receiving files wrapped in legal language. The NDA, while protective for the sender, created friction for the recipient. We responded by developing “soft” NDA formats — language that established confidentiality expectations without the adversarial tone of a traditional NDA.

Finding 2: Users wanted visibility into recipient behaviour. Did the client open the file? Did they download it? How long did they spend on it? This was not just about security — it was about sales intelligence. Users wanted to know if their pitch was being taken seriously. This insight eventually led to our analytics layer.

Finding 3: The value proposition shifted with the user segment. Freelancers valued protection. Small agencies valued professionalism — sending a pitch through PitchNDA signalled that you were serious and established. Larger companies valued compliance — they needed audit trails for regulatory reasons. Same product, three different value propositions.

This last finding was particularly important because it informed our pricing and positioning strategy. We could not be everything to everyone, but we could lead with one segment and expand.

What I Learned About Product Vision

Setting product vision for PitchNDA was fundamentally different from brand strategy in FMCG. In brand management, the product already existed — my job was to position and communicate it. In a startup, the product was a hypothesis that needed to be validated, iterated, and sometimes completely rethought.

The hardest lesson was learning to hold the vision loosely. I had a clear picture of what PitchNDA should eventually become: a comprehensive IP protection platform for the creative economy. But the path from MVP to that vision was not a straight line. It was a series of experiments, pivots, and uncomfortable conversations with users who told me, in various polite and impolite ways, that what I had built was not quite what they needed.

The discipline of prioritisation — deciding what to build next when everything seems urgent — was something I later sharpened significantly at Y Combinator Startup School. But the initial instinct came from FMCG. In brand management, you constantly face the tension between what the brand wants to say and what the consumer wants to hear. In product management, the equivalent tension is between what you want to build and what users actually need. The resolution is the same in both cases: start with the user.

The Co-Founder Relationship

I want to touch briefly on the co-founder dynamic, because it is one of the least discussed and most critical aspects of startup building. Finding a co-founder is often compared to finding a spouse, and the analogy is apt. You need complementary skills, aligned values, compatible working styles, and the ability to disagree productively.

My co-founder brought the technical expertise I lacked. I brought the market understanding, the user empathy, and the business development instinct. On paper, the fit was excellent. In practice, making it work required constant communication, explicit role definition, and a shared commitment to the mission that superseded individual ego.

The most valuable thing I learned about co-founder relationships is that they require maintenance. Not crisis management — maintenance. Regular check-ins about direction, honest conversations about what is and is not working, and proactive alignment on priorities before they become conflicts.

Looking Forward

Leaving brand management to co-found PitchNDA was the scariest professional decision I have made. It was also the most consequential. Not because PitchNDA became a unicorn — it did not — but because the experience fundamentally changed how I think about problems, products, and my own capabilities.

The recognition that followed — being named among Top 25 WEQ Anita.B startups, Top 200 Niti Aayog women-driven startups — was gratifying. But the real value was the education. I learned more about product, about users, about myself in three years of building PitchNDA than in the preceding years of brand management combined.

If you are a brand manager or marketing professional sitting on a problem you believe you can solve, and the question in your head is “should I leave to build it?” — I cannot tell you yes or no. What I can tell you is this: the skills you have are more transferable than you think, the fear you feel is normal, and the worst-case scenario is rarely as bad as your anxiety makes it seem. You will not know if you can build something until you try. And trying, even if it does not work out, is its own kind of success.