When I asked Swapnika Nag what it was like to build a startup with her husband, I expected a conversation about boundaries. What emerged was a masterclass in trust, profitable growth, decision-making, and building a small team with serious leverage.
Swapnika is the Founder and CEO of Periskope and PerisClaw. Periskope automates WhatsApp operations for more than 5,000 businesses across 100 countries. PerisClaw is an AI executive assistant that runs on your own WhatsApp number. An IIT alumna and former McKinsey consultant, she builds both companies with her husband and co-founder, Bharat.
On Dilse Omni Talks, her answers were refreshingly practical. No perfect work-life balance story. No fundraising-as-success narrative. Just an honest account of what works, what gets messy, and what they are still learning.
Table of Contents
1. A Life Partner and a Co-Founder Need Similar Qualities
2. Flexibility Does Not Automatically Mean Switching Off
3. Agree on the Business You Want Before Debating Growth
4. Marriage Does Not Teach You How to Disagree as Founders
5. The Consulting Edge: Learn Fast, Move Fast, Deliver Value
6. AI Changes the Economics of Both Consulting and Startups
7. Networks, Visibility, and Trust Are Different Things
8. Choose Tools for the Work, and Leave Room for Joy
1. A Life Partner and a Co-Founder Need Similar Qualities
Swapnika and Bharat met during their undergraduate years at IIT. Their careers followed similar paths: he went to IIM Ahmedabad and Bain; she went to IIM Bangalore and McKinsey. Eventually, they started building together.
Her argument for working with a spouse was simple. The qualities you want in a co-founder overlap considerably with those you want in a life partner:
Trust: Can you rely on this person when things become difficult?
Respect for judgment: Can you accept a decision you would not have made yourself?
Comfort with uncertainty: Do you approach risk in compatible ways?
Financial alignment: Do you agree on the trade-offs worth making?
The benefit becomes tangible when life changes. During pregnancy and the early months of raising their son, Swapnika could step back while Bharat increased his involvement. They could redistribute responsibilities dynamically because they understood both the business and the family context.
My takeaway: the advantage is not merely knowing each other well. It is being able to adapt together.
2. Flexibility Does Not Automatically Mean Switching Off
When Swapnika described taking vacations without coordinating two employers’ leave policies, I asked the obvious question: what happens when both founders are away?
The answer was wonderfully honest. Their laptops go with them. Fewer meetings can make a vacation a surprisingly productive period for focused work. As I put it, sometimes you are simply changing the location of work.
“We never switch off.”
Swapnika Nag
They tried the familiar rules: no work conversations at dinner, clear shutdown times. Those rules did not stick. Business remains part of family conversation, to the point that they joke their son’s first word might be something server-related.
I would not turn that into universal advice. What mattered was her candour. Do not confuse flexibility with rest, and do not assume someone else’s boundaries will work for your relationship.
3. Agree on the Business You Want Before Debating Growth
One of Swapnika and Bharat’s strongest points of alignment was profitability. Neither wanted to build an unprofitable technology business.
Swapnika shared that Periskope had been profitable from its first year. They raised a small initial round involving mentors, partners, and friends, then chose not to raise further. Funding remained an option, but not a badge of achievement.
That distinction stayed with me: capital should serve the business, not validate the founder.
It also explains why co-founder alignment matters beyond getting along. If one person wants sustainable growth and the other wants growth at any cost, every major decision can reopen the same disagreement.
A Co-Founder Alignment Framework
I would organise the lessons from their experience into this simple sequence. This is my synthesis, rather than a named framework Swapnika presented:
Shared principles: Agree on profitability, risk, and the purpose of raising capital.
Clear ownership: Decide who has the final call in each domain.
Open disagreement: Challenge the decision without making every challenge personal.
Committed execution: Once the accountable person decides, move forward together.
4. Marriage Does Not Teach You How to Disagree as Founders
When I asked about the downside, Swapnika identified something easy to overlook: knowing how to argue as a couple does not mean knowing how to disagree as co-founders.
Emotions do not disappear because a discussion concerns technology or pricing. Their solution is not to eliminate disagreement, but to make decision rights clear.
Technology: Bharat has the final call.
Customers, sales, and discounts: Swapnika has the final call.
Product and design: They work together.
Both can challenge the other. Neither needs to win every argument.
“He does the building, I do the selling.”
Swapnika Nag
That sentence sounds casual, but underneath it is an important operating discipline: shared commitment does not require shared final authority on every decision.
5. The Consulting Edge: Learn Fast, Move Fast, Deliver Value
Swapnika spent about five years at McKinsey, while Bharat spent a similar period at Bain. I wanted to understand what actually transferred into entrepreneurship.
Her answer had three parts.
First, learn unfamiliar subjects quickly. She recalled using a flight to Australia to get up to speed on medtech and local procurement. Founders face the same expectation. You cannot permanently avoid marketing because you consider yourself a technology person.
Second, work at pace. The first version of Periskope took three days; an early version of PerisClaw took a few weeks. Consulting had trained them to make progress within short windows.
Third, deliver outcomes. Swapnika pushed back against the idea that consulting is only presentations and gyan. Her experience of outcome-linked work shaped how they supported early customers: helping build useful systems, not simply handing over a tool.
The Problem-Solving Loop
Her team’s working style offers a practical framework:
Problem → Hypothesis → Proposed solution → Experiment → Results
If email deliverability drops, the discussion should include likely causes, possible fixes, and an experiment already underway. The founder becomes a thinking partner rather than the destination for every unresolved problem.
She also believes founders should understand work before delegating it. Between them, she and Bharat can perform the functions their team runs.
Would she recommend consulting to her younger self? Yes, for a year or two before building. But she was equally clear that it was stressful and that she wanted to get her hands dirty.
6. AI Changes the Economics of Both Consulting and Startups
Swapnika’s view of AI in consulting was more optimistic than a straightforward job-replacement story. Smaller teams can handle research and analysis, reducing delivery costs. Clients may expect lower fees, but firms can also serve mid-market businesses previously priced out of consulting.
Her own company reflects that leverage. At the time of our conversation, the team had 12 people, and staying small was intentional. Swapnika herself ran roughly 10 to 12 AI agents.
Content research: Running 500 prompts weekly to assess visibility, competitors, and content gaps.
Social listening: Tracking relevant conversations on Reddit and X and drafting responses.
Prospecting: Finding businesses in specific markets and assembling contact information.
Development: Supporting coding workflows.
Quick approvals happen on WhatsApp; team interactions also happen on Slack. For social responses, she described approving drafts before agents publish them. That distinction matters: automation can accelerate execution while keeping human judgment involved.
For more on that approach, I have explored turning WhatsApp into an AI executive assistant.
7. Networks, Visibility, and Trust Are Different Things
Swapnika called the McKinsey alumni network her most valuable takeaway from the firm. Its value extended beyond customers and introductions. During her parents’ cancer treatment, the community helped her find specialist care and secure an appointment quickly.
She acknowledged the privilege of that access. I added that networks involve both giving and receiving. Their ecosystem includes businesses that buy from Periskope and businesses whose services Periskope uses.
Our discussion of LinkedIn added another dimension. Swapnika described using an agent to work through an old backlog of access requests. We also questioned our platform biases: a technology-heavy Reddit or X feed is not necessarily representative of the wider market.
I shared my own identity mix-up, where search results used my photograph alongside information about a Tata executive with a similar name. The resulting LinkedIn post attracted more than 250,000 impressions and media attention.
It was amusing, but the underlying lesson was serious: visibility is not the same as accurate identity.
Swapnika connected this to voice cloning. She had established family code words for critical requests because a familiar-sounding voice asking for money may not be genuine.
8. Choose Tools for the Work, and Leave Room for Joy
Although their business uses Google Cloud, Gemini, and Google Workspace, Swapnika is not loyal to one AI model. Her selection criteria are practical: usable output, acceptable latency, and sufficient capability for the task. Repetitive work does not always need the most capable model.
That is also the principle behind choosing the right AI platform for your business: start with the work, not the brand.
Her remote-first setup gives the family flexibility about where to live. Hyderabad appealed as a possible balance, while pollution, traffic, family proximity, schools, and airport access shaped the discussion.
And not everything needs to become a productivity exercise. Swapnika reads murder mysteries, including Keigo Higashino, and business stories such as Focus: The ASML Way and The World for Sale for enjoyment.
She enjoys the Dwarkesh Podcast and Amit Varma’s The Seen and the Unseen. After listening, she sometimes uses live AI conversation to test how an idea applies to her business. I shared my own NotebookLM research habit and how studying podcast mechanics helps me ask crisper questions.
My biggest learning was that durable entrepreneurship combines clear principles with adaptable methods. Align on the business. Clarify who decides. Learn quickly. Use AI where it earns its place. And allow curiosity to exist without demanding an immediate return.
I am Saurabh Agrawal and we come with a new episode on Dilse omni talks every fortnight and cover different aspect of omnichannel with amazing speakers.

















