Abin S.
Founder's Associate
SUMMARY OF EXPERIENCE
• 2.5+ years of experience across founder's office and category management roles, with direct exposure to P&L ownership, cross-functional execution, and operational system-building from the ground up.
• Spent ~2 years as Chief of Staff at Thevasa (founder's office), where he ran two manufacturing units on a JIT model, co-owned P&L tracking, and built Excel dashboards that cut MIS creation time by 50% and improved operational efficiency by 80%.
• At Urban Company, he owned daily category operations for Delhi NCR, where he reduced M1 partner churn by 32%, improved customer satisfaction by 27%, and cut approval turnaround time by 40%, largely through SOPs, data tracking, and cross-team coordination with product and tech.
👍 What we loved about them
• Structured thinking under pressure: When faced with the missing data scenario, he didn't freeze or default to "I'll wait for the data." He immediately thought about what proxy data was available and how to calculate an estimate, which showed us that he can keep things moving when things aren't perfect. He also instinctively moved from identifying a problem to asking "how do we make sure this doesn't happen again?" Whether it was setting up real-time data entry, using Fathom for meeting notes, or building dashboards, we found him to consistently thinks in systems, not just one-off fixes.
• Tries to understand the why: In the discovery call, Abin shared a situation where two sets of data were contradicting each other in front of the founder, and people were starting to point fingers. Instead of just defending his own numbers, he took the time to understand why the other person had presented wrong data, figured out it was fear-driven (the employee was scared of being shouted at for showing a bad number), and then mediated between them. He solved the human problem underneath the data problem, and did it without making anyone look bad in the process.
• A people's person: He's genuinely good with people at every level, whether that's managing tailors on a shop floor, navigating a frustrated founder, or mediating between team members; this came through consistently across both interviews.
ℹ️ Things to be aware of
• He's available to join immediately.
• He left Urban Company because the category he was running wasn't profitable, and with the IPO underway, it felt like the writing was on the wall in terms of where the business's priorities lay. Coming from Thevasa, where he had real ownership and founder proximity, a single-category role in a large organisation was always going to feel limiting after a while. This opportunity is clearly a return to the kind of environment he thrives in — close to the founder, broad scope, and problems that actually need solving.
• He has strong hands-on data skills – he's comfortable with SQL, Excel dashboards, and building reporting systems from scratch rather than inheriting them.
• His understanding of the steel industry is directionally correct but fairly surface-level. He got the broad strokes right (e.g. raw materials, refining, distribution), but some of the detail was a bit loose (e.g. mixing up players and processes). That said, he was upfront about this and clearly did his homework before the interview, so there's appetite to learn.
💁♀️ Where he may need support
-
Although he lacks extensive experience with LinkedIn and Bing ads, his proficiency in Google ads suggests a high adaptability to new platforms.
👩💻 Technical interview performance
Objective
This candidate was invited to a 60-minute follow-up interview to assess their technical capabilities in more detail. During this interview, we assessed their critical-thinking skills, technical expertise, and overall conversational skills.
Technical abilities
• Structured problem-solving and analytical thinking [8/10]: When Abin was walked us through the furnace utilisation discrepancy, he went beyond just flagging that the numbers seemed off; he immediately started thinking about how to verify it, what data to pull, and who to speak to on the ground. He also broke down the cost-per-tonne question sensibly, drilling from the macro level (which unit?) down to the micro (which product? which cost line?), rather than jumping straight to a solution. What also stood out to us was his comfort with ambiguity. When asked how he'd present a finding he wasn't 100% certain about, he suggested triangulating with the plant manager before going to the founder, showing us he's aware of the difference between a hunch and a backed hypothesis.
• Operational systems and process design [8.5/10]: This is probably where Abin is most credible, and it comes through naturally rather than feeling rehearsed. During his Thevasa experience, he built dashboards, ran JIT manufacturing, managed vendor timelines, and designed onboarding workflows. So when he talks about setting up data pipelines or fixing meeting structures, we could tell he had practical experience to back this. His answer on the WhatsApp notes problem was a good example of this – he correctly identified what the current system was capturing (the founder's MVP thoughts) and what it was missing (distributed action items and accountability). From there, he moved logically into a solution, i.e. Fathom for transcription, review and edit, then automated email to all attendees, which is a clean, low-friction fix that doesn't require everyone to change behaviour dramatically. He also brought up pre-meeting prep as a way to make meetings more decision-ready.
• Stakeholder management and communication [8.5/10]: Abin clearly has a way with people, which feels genuine. His approach to handling resistance (e.g. showing people how a new system makes their own life easier rather than just telling them to do it) reflects someone who's actually had those conversations before and knows that logic alone doesn't change behaviour. His comfort with blue-collar workers and shop-floor teams is also worth noting, because a lot of people in this type of role struggle to bridge that gap. He was also thoughtful about how to manage the "you're just a kid" dynamic when engaging with plant heads. Rather than projecting authority he doesn't have, he'd lean on curiosity and collaborative framing, asking whether his ideas are feasible, incorporating ground-level pushback, and presenting conclusions as a team effort.
• Founder's associate readiness [8/10]: What this comes down to is: can he actually be a founder's right hand, not just a smart operator? And from both the interviews, we think the answer is yes, with a few caveats. He understands the core of the role (i.e. taking ownership of firefighting so the founder can think longer-term) and he articulated it in a way that felt genuine. He's also clear-eyed about what he needs from a founder (open dialogue, willingness to share context) and what would make the relationship hard (a blame-first reaction to bad news), which shows a level of self-awareness that's useful in a role built on trust. In particular, the Thevasa experience as Chief of Staff is directly relevant here. He's been in the founder's orbit, co-owned P&L decisions, managed cross-functional execution, and built systems from scratch.
Areas of growth
• Right now he's very good at breaking things down but less practised at stepping back and offering a pointed view. As a Founder's Associate, there'll be moments where the founder doesn't just want an analysis; they want a recommendation. Building the confidence to offer one clearly, even with uncertainty, is something he should actively work on.