// PODCAST

Retail Tech Pivot: From Self-Checkout to POS and an Amazon Exit | Abhinav Pathak, Perpule

Perpule co-founder Abhinav Pathak explains how poor retention forced a pivot from self-checkout to retail POS, how to land large retail clients, and why he chose to sell to Amazon.
Abhinav Pathak, Perpule on The Builders Club Startup Founders Podcast
Advertisement

Growing orders, growing stores and a retention chart that looked like a warning light. That was Perpule’s first big lesson.

Co-founder Abhinav Pathak joined The Builders Club to walk through a pivot from self-checkout to retail billing systems, the enterprise sales grind, and the decision to sell to Amazon.

What can founders learn from a retail tech pivot? Abhinav Pathak’s core thesis

Abhinav’s central point is that headline growth can hide a broken business. Perpule’s self-checkout app scaled by orders and stores, but customer retention was poor, and the cause was inaccurate store inventory, prices and promotions caused by legacy billing systems.

The team fixed the root cause. It moved from a B2B2C app to a pure B2B point-of-sale product that retailers could run on modern hardware, where retention was strong and switching costs were high.

  • Watch retention early. Rising orders can mask churn, so check cohort retention from the start.
  • Fix the layer underneath. The self-checkout idea needed accurate store data first.
  • Zero to one is persistence. Landing a first large customer took months of repeated pitches.
  • Do not over-customise. Building too much for one big client cost eight to nine months.

How did Perpule start with self-checkout?

Abhinav studied at NIT Surathkal, where meeting entrepreneur seniors made startups feel relatable, and later worked at Goldman Sachs. He met his co-founders there and through college, and they chose retail because it is large and technologically behind.

Perpule began with a self-checkout app for offline stores, as online giants threatened physical retail. Landing the first customer, Hypercity, took about three months of pitching to 30 to 40 brands, five or six times each. The pilot went live in late 2016 with a few stores.

Why did retention expose the real problem?

As the app reached around a hundred stores, roughly 10 to 12 percent of store transactions ran through it. Yet retention was weak: about 25 to 30 percent in month one and only a few percent after five or six months.

The team made some 500 customer calls and found customers liked the experience but lost trust when prices, promotions or inventory in the app were wrong. Stores updated items in their systems late, so the data was wrong.

  • Customers will try a new experience, but grocery buyers expect price accuracy.
  • Retailers already knew their systems were weak and encouraged the team to solve it.
  • Abhinav says the team lost several months before checking retention.

How did the pivot to retail POS work?

The conclusion was that experiences like self-checkout or hyperlocal delivery would not scale until the store’s billing system was modernised. Many retailers ran billing software that was 10 to 20 years old and not built for cloud integration.

In 2018 Perpule became a B2B company building point-of-sale systems for large-format retailers, and raised a Series A.

  1. Build a billing app that runs on the Android card-payment machines that stores already own, which cut hardware costs.
  2. Win the same early customers back with the mobile version.
  3. Add a desktop solution when retailers asked for it, then scale to thousands of stores.
  4. Take the product to Southeast Asia and the Middle East.

Why are enterprise sales cycles so long?

Abhinav described sales cycles of about three months and deployment of three to four months. Store teams resisted change, so Perpule set up learning and customer-success teams, including messaging-based training for cashiers. The upside is retention: he said they never lost a customer in the POS business.

What mistakes should enterprise startups avoid?

Abhinav said that early-stage product and sales grow faster than technology, so technical debt is a sign of growth. The answer is a strong team and a willingness to launch before the product is perfect.

His biggest regret was over-customising for one very large retailer for eight to nine months, because the work was not reusable. The company was raising money and felt it could not say no.

  • Keep a focused product team separate from sales.
  • Talk to other founders, who have often faced the same demand from big clients.
  • Do not get emotional about one customer: look at the business as a whole.

Why did Perpule sell to Amazon?

Abhinav said the team never set out to sell. Retail is a slow market, and the pandemic halved their volumes, so growth at venture pace was uncertain.

Acting on what was right for customers, employees and investors, and with relationships built with corporate development teams since 2018, they sold to Amazon. He stayed on to lead small and medium business technology there, citing Amazon’s process-driven culture as a learning opportunity.

Further reading and sources

Frequently asked questions

How do you know when to pivot a startup?

Look at the metrics that reflect real value, such as retention, not just growth in orders or stores. Perpule pivoted after customer calls showed the underlying problem was outside its control and would block scale.

How do startups win their first large enterprise customer?

Expect persistence to matter more than polish. Abhinav’s team pitched dozens of brands several times each before one agreed to a pilot, then built credibility from that proof.

Why should startups avoid heavy customisation for one client?

Software businesses depend on reuse. Abhinav spent months building features for a single large retailer that no other customer could use, so he now recommends a dedicated product team to decide what is built.

Conclusion

Abhinav Pathak’s journey shows that the right metric can save a company: retention told Perpule that a growing product was not yet a good one. The fix lay beneath the app, in the store’s core systems.

Check your cohort retention this week, and if it is weak, make customer calls before you add more growth spend.

Want more conversations like this? Join The Builders Club, our community of 35,000+ founders and CXOs, and explore more episodes of the Startup Founders Podcast.

Never miss an episode

Join 35,000+ founders and CXOs in The Builders Club community.

Join the Community
Advertisement
Advertisement
Facebook
X
LinkedIn

Why the Self-Serve PLG Playbook Fails with Indian Enterprise CXOs (And the High-Touch Assisted Model That Actually Wins)

Self-serve PLG works when the user is also the buyer. In Indian enterprises, they almost never are. A product-led funnel can get your tool into a team’s hands, but it rarely gets a CXO to sign. The model that wins is a high-touch, assisted motion that uses product usage as proof, not as the whole sales strategy. Here is why the standard playbook stalls in India’s large organisations, and what to run instead. Why does the self-serve PLG playbook fail with Indian enterprise CXOs? Product-led growth, as described by pioneers such as OpenView, assumes that users discover, try and adopt the product themselves, and that revenue follows usage. That assumption holds for tools with low risk, low price and individual buyers. Enterprise buying in India breaks all three conditions at once. The user is not the buyer. An analyst may love your tool. The budget sits with a CIO, CFO or business head who has never opened it. Risk is organisational. A CXO signs against security, vendor-continuity and reputational risk, none of which a free trial answers. Trust is personal. Decisions often move on credibility, references and conversations with someone they respect, not on a sign-up flow. Does a free trial or freemium plan ever work in Indian enterprises? It can work for teams, departments and SMB-sized units, where one manager has a card or small discretionary budget. It rarely scales to the top accounts without a human who turns usage into a business case. What does the high-touch assisted model actually look like? Assisted does not mean old-fashioned. It means every stage of the product experience is paired with a person who removes a specific obstacle. Stage Pure self-serve PLG Assisted model for Indian enterprises Discovery Organic search, product trial Warm introduction, peer room, referral Evaluation Self-guided trial Guided pilot with named success criteria Decision User upgrades with a card Business case built for the CXO and the committee Contracting Click-through terms Negotiated MSA, security review, procurement Expansion In-app prompts Account lead plans rollout across divisions How do you turn product usage into a signed enterprise contract? Use the product as the evidence, and a person as the translator. A practical sequence: Find your champion. Identify the user who gets the most value and ask them to explain the problem in their own words. Quantify the result. Convert usage into time saved, errors avoided or revenue influenced, in a one-page summary the CXO can read in two minutes. Map the buying committee. Ask your champion who else must say yes: IT, security, finance, legal, and the business owner. Run an executive conversation. A founder or senior lead speaks to the CXO about outcomes and risk, not features. Offer a scoped commitment. A defined pilot or first-division rollout with clear exit and expansion terms reduces perceived risk. When should you still invest in self-serve? Do not abandon it. Use self-serve as the top of the funnel and as a signal engine. Track which accounts have several active users, which teams invite colleagues, and which admins explore security settings. Those are the accounts your sales team should call first. Think of it as product-qualified leads feeding a human-led close. Many global companies now run exactly this hybrid, and it fits Indian enterprise buying better than a pure self-serve approach. FAQ Is PLG dead for B2B SaaS in India? No. PLG is useful for building awareness, usage data and champions inside accounts. It fails as the only motion for large enterprises, where committees, security reviews and relationships decide the contract. A hybrid model works better. What is a product-qualified lead (PQL)? A PQL is an account or user whose in-product behaviour suggests buying intent, such as multiple active teammates or admin-level exploration. Sales teams use PQLs to prioritise who to approach with a human conversation. How many people does an assisted enterprise sale need? It depends on deal size, but you typically need one senior owner for the relationship, one technical resource for security and integration questions, and a customer success lead after signing. Founders often cover the first two roles in early deals. Conclusion PLG gets you into the room, but it does not get a CXO to sign. In Indian enterprises, winning sales pair product evidence with human trust: a champion, a business case, a guided pilot and a senior conversation. Building an assisted enterprise motion? Meet founders and CXOs who have done it at The Builders Club, and bring your toughest sales question to our next roundtable. Join The Builders Club. About the author: Sohail Khan is Founder and Director of The Builders Club, a professional community of 35,000+ founders and CXOs across India, UAE, Singapore and the US.

Read More »