I started with hardware. The work grew into brands, physical spaces, communities and digital systems. The thread is the same: making an idea work in the real world.
These chapters connect hardware, Zo House, communities and the products I build. Step inside the Whitefield living room or explore the complete story below.
Approximately 2020–2022 / Brand strategy · Operations · Sales
From assembling a vehicle to building distribution.
A friend starting White Carbon Motors asked me to help build it into a company. I came in as a hardware nerd. We began with one vehicle brought as a kit and assembled it ourselves. My role grew into brand strategy, operations and sales: the “everything guy.”
First 100-vehicle Bangalore deal
7 flagship showrooms
iACE facilities & incubation
GT5 · White Carbon Motors specification sheetSourceRead the story
The first vehicle
At the beginning, the work was hands-on: taking the kit we had brought in and building the vehicle ourselves. That is the starting point of this chapter, before franchise distribution or a showroom network existed.
Building a route to market
I built a franchise-led distribution system and closed our first 100-vehicle deal in Bangalore. The business grew to seven flagship showrooms. Brand strategy, sales and operations sat together in my role because getting the product into customers’ hands required all three.
The iACE arrangement
We established a knowledge-transfer incubation MoU with iACE. As I describe the arrangement, WCM would share its two-wheeler expertise if Maruti pursued that category; in return, we could use iACE facilities as a home base, including equipment and training. This was an incubation relationship, not a claim that Maruti launched a two-wheeler programme.
What came next
As White Carbon matured, I moved on to Zo World. The lesson I carried was simple: grit can go a long way. My WorkMob interview documents my brand and business-development role; iACE’s incubation material provides the institutional context.
Personal scope and outcomes are my account. External records below document the project and, where named, my role; they are not independent verification of every result.
From 2022 / Brand creation · Physical builds · Community leadership
Building Zo House from the ground up.
When I joined Zo, the Founder NFT membership already existed. Zo House did not. I took ownership of both: turning a membership into somewhere people could actually live, meet and build, and creating the house’s brand, concept and culture.
Koramangala penthouse
Whitefield clubhouse
San Francisco house
Whitefield · original project render · WTFxZo 3D collectionSourceRead the story
Koramangala: making the first house real
The first Bangalore chapter meant turning a penthouse into an operating house. My scope crossed the physical setup, team, membership and programming. The public launch was on 24 December 2022; the event record lists me, as Samuraizan, among its cohosts.
Whitefield: building the place I lived in
The next chapter was a villa and its evolution into a clubhouse. I worked with designers and project teams on the physical build while shaping the experience around it. I lived there, so the spaces I helped create were also the spaces I used every day. This website recreates that living room.
San Francisco: taking the house abroad
I went to San Francisco to set up and run the house. That put the physical space, daily operations and community programming in the same remit. The local context changed; my responsibility still ran from making the place work to giving people a reason to gather there.
The product included the people
Founder Members, public gatherings and residential programmes were part of the house itself. I led teams, vendors and partnerships as the work grew. My contribution was the whole experience: brand, space, community and delivery. Designers, builders, partners and the house team contributed to making it real.
See the house beyond this portfolio
Zo House’s website shows the brand today. The Economic Times house-anniversary feature identifies me as Zo House BLR director and documents the rooms, shared spaces and residency activity. It is an independent view of the environment we built.
Personal scope and outcomes are my account. External records below document the project and, where named, my role; they are not independent verification of every result.
From 2022 / Product ownership · Community monetisation
Turning Founder membership into a lived experience.
I inherited ownership of an already-launched Founder NFT membership. Alongside building Zo House, I worked on the membership as the commercial product for the community: connecting paid access to physical spaces, gatherings and an ongoing relationship with members.
Existing NFT → owned product
Physical access & programming
Member onboarding & support
The community, together · Zo House collectionRead the story
What the membership offered
Historical Zo membership pages describe 24/7 house access, curated events, a gated community and member benefits. Those were the published offers of that period. They explain what the product was selling: access to a place and the people and activity inside it.
What I owned
I owned the membership lane alongside the house, rather than treating the token and the venue as separate products. My remit connected the community relationship, the offering and its delivery through the spaces and programmes we were building.
Making access usable
The Koramangala and Whitefield house guides named me as the purchase and wallet-support contact. That meant a member had a person to come to when moving from buying or holding the membership to using it. This practical layer mattered as much as the promise on the membership page.
What I value in the outcome
The stories I want to preserve are the relationships formed, ideas seeded and memories members took away. I am not presenting token supply or network-wide member counts as my sales results. The linked membership record lets you inspect the actual offer.
Personal scope and outcomes are my account. External records below document the project and, where named, my role; they are not independent verification of every result.
Across my Zo House years / Event concepts · Brand partnerships · Team leadership
500+ events. From the idea to the room.
I led the events lane end to end. Most concepts started with me or were developed with partners and brands. As the programme grew, I managed teams, vendors and partnerships to deliver it, not just the logistics after someone else had set the brief.
500+ events across my work
Bangalore · SF · Dubai
Social, technical & creative formats
A full Degen Lounge session · SF collectionRead the story
A launch, a summit and a house party
The archive includes the Zo House BLR launch on 24 December 2022, Memecoin Summit in San Francisco and Habibi House Party in Dubai. Each public listing names me as a cohost. These give visitors specific events to inspect, alongside my broader account of leading the programme.
Designing more than one kind of gathering
The SF Memecoin Summit agenda brought together onboarding, an AI hackathon, a panel, trading, poker and a party. Sunday Sundowners offered a recurring social format, with public and Founder Member entry options. The format changed according to who we wanted in the room and what they would do together.
Residencies: enough time to make something
Zo House hosted programmes with different audiences and durations. Crosschain Clubhouse was a two-week Solana/Wormhole builder residency; Manifest brought artists, creators and developers together for five weeks. The Residency Bangalore names Zo House as its primary partner and venue. These were collaborations, with their own programme teams and contributors.
My responsibility as the programme grew
I worked across the initial concept, partner and brand conversations, format, planning and delivery leadership. Teams and vendors handled parts of the execution under that direction. The portfolio will grow with individual event stories, while the public archive already provides named examples to explore.
More formats, the same instinct
DUH was a hardware hackathon; DeFi Mania brought four chains into one hacker house. Alongside the five-week Manifest residency and Zozalu’s accelerated-living direction, these explored different ways for people to live, make and learn together.
Personal scope and outcomes are my account. External records below document the project and, where named, my role; they are not independent verification of every result.
Started late 2025 / Solo build · Product · Systems architecture
Building a digital identity for a distributed community.
After the Zo House chapter, I wanted a way to mobilise the community beyond a physical house. I built Passport myself, starting with open-source identity and developing it toward Zostel’s main identity system. The product connects a person’s identity with what they do in the community.
Login, profile & public identity
Quests, referrals & tribes
Journey, stamps & participation
Read the story
Getting someone into the system
The work includes authentication, onboarding, profiles and avatars. The first visit and the returning visit need different flows: establish identity, collect what is missing, unlock the experience and let someone return to their existing account.
Giving identity somewhere to go
The frontend brings together quests, referrals, tribes and a Passport journey. A person can discover an activity, participate, invite someone and see that participation attached to their profile. A public Passport gives that identity a shareable surface.
Connecting Zo and Zostel
The architecture connects Zostel identity with the Zo-owned Passport experience. Onboarding, referral and unlock behaviour belong to that product layer. This is the kind of systems work I moved toward: one identity crossing several interfaces without losing the person’s context.
Explore the product and its technical history
Open zo.xyz to see the public product. The linked zopassport package is a separate public artifact listing me as a verified maintainer and the Zo World Team as author. It documents authentication, profiles, avatars and wallet features; it is not a claim that I solely authored every earlier Zo SDK.
Personal scope and outcomes are my account. External records below document the project and, where named, my role; they are not independent verification of every result.
Started early 2026 / End-to-end build · Restaurant workflows
From a guest’s table to the kitchen and back.
While at Zo House, I built the restaurant app end to end, with a few builder bounties accelerating parts of the work. The system covers the customer’s order, the kitchen’s workload and the operating tools around both. Cafe Zomad is the current product surface linked here.
Table → menu → order
Kitchen, stock & meal plans
Credits, payments & nutrition
Read the story
The guest’s order
Guests choose a property and table, browse or search the menu, inspect dietary information and ingredients, add items to a cart and leave kitchen notes. Checkout connects to account and payment flows. Order history includes status, with edits or cancellations for eligible unpaid orders.
The team behind the meal
The operator app includes a kitchen board, menu and order management, inventory and meal-plan tools. These are distinct working surfaces: the guest chooses food, the kitchen sees what needs preparing, and the operator manages the information that makes both possible.
Food credits and payment
The cart can apply available food credits and calculate the remaining payment. Order and wallet flows need to account for changes and cancellations, while statements separate issued or revoked credit from property-level spending. The work extends beyond putting a payment button on a menu.
Bio Hack: a record of what you eat
The consumer app also contains nutrition information, meal history and daily goals. That gives the same order data a second use: helping a guest understand their food choices over time. The source includes these capabilities; availability depends on the connected menu and order data.
Personal scope and outcomes are my account. External records below document the project and, where named, my role; they are not independent verification of every result.
An ongoing practice / Founder advice · Product · Operating systems
Advising on the whole business around a product.
My role has gradually grown from the person doing everything into a systems architect and founder advisor. At Fancall, I advise founder Akash Chaudhary across product, growth and the operating model behind a platform connecting fans, creators and brands.
Fancall · Akash Chaudhary
Fan, creator & brand journeys
Advice and product decisions
Read the story
The product problem
A creator platform has several connected experiences. A fan needs to find someone and have a successful interaction. A creator needs a workable way to participate. A brand needs a clear commercial offer. Advice about one side has to consider what changes for the others.
What my advisory work covers
My work has covered customer journeys, creator availability, product structure, commercial conversion and growth measurement. I examine where the promise to a customer depends on a process, a product decision or a person taking responsibility.
What I bring from building
White Carbon taught me to connect product, distribution and operations. Zo House put brand, spaces and community in the same remit. Building Passport and restaurant software brought that experience into digital architecture. Those are the practical perspectives I bring to a founder’s decisions.
What this case study claims
This is an advisory relationship, not a claim that I founded Fancall or built its entire product. The public link shows the business itself. Specific adopted recommendations and their outcomes will be added as publishable examples are agreed.
Personal scope and outcomes are my account. External records below document the project and, where named, my role; they are not independent verification of every result.
Active development / Website engineering · Maps · Product integration
Turning Aga’s travel recommendations into usable guides.
I am developing Aga Guides with Aga: a travel website where her recommendations become destination guides and maps people can use while planning a trip or exploring a place. The linked Cloudflare site is our working review preview.
Destination discovery
Guides & interactive maps
Account & commerce integration
Read the story
Find a trip, then find a place
The site combines a globe and destination catalogue with search and interest filters. Inside a guide, recommendations connect to place details and map actions. The intended experience is concrete: choose a destination, inspect a recommended place and find your way there.
The supporting travel tools
The build also contains saved lists, route tools, a travel passport and stamps. These support discovery and keeping a record of a trip. They are parts of the developing product, rather than separate promises of a finished club or active community.
What I am building underneath
The app uses Next.js, Supabase, Mapbox and Shopify. My work connects the interface, destination data, map experience and access/commerce integrations. I also moved the review deployment from Vercel to Cloudflare so we could keep sharing the developed product.
Where the project stands
The preview is available for review and demonstration. It is not presented here as an accepted public commerce launch: normal-customer purchase-to-access testing still needs completion. Open the preview to see the actual build rather than a concept rendering.
Personal scope and outcomes are my account. External records below document the project and, where named, my role; they are not independent verification of every result.
Notes from an unfinished journey / Ashwin Panicker / Samurai
Different mediums. The same instinct.
From Gandhinagar and Canada to vehicles, Zo House and software: I keep finding ways to understand how things work, bring good people together and make something happen.
Curiosity → agency → world building
People, places and systems
Still becoming
Poker and philosophy · Zo House collectionRead the story
First, find out how it works.
I took apart toys and electronics because I wanted to understand them. A Nintendo 64 at seven opened another world. Samurai started as my gamer tag, from Samurai Jack. At school I was the person behind the annual days and extracurriculars: the everything guy.
Learn the system behind the thing.
Operations management led to SAP, warehouse work at Kuehne+Nagel and inventory allocation at Canadian Tire. Later I learned beside entrepreneurs: convenience stores, flipping cars, a dollar store that failed and a pizza store that made money. I wanted agency and impact, not a career I could already see the ending of.
Build the world around the product.
At White Carbon, helping a friend meant working across the vehicle, brand, operations and sales. At Zo House it became a whole environment: space, people, membership, gatherings and culture. The founders gave me freedom and the team helped make it real. “Zo House was an expression of my best self.”
Make the next thing possible.
The same instinct now goes into Passport, restaurant systems, Aga Guides and advising founders. AI changed the speed at which I can build. The medium changes; the work still means understanding what people need, bringing the right pieces together and making it happen.
The everything guy
At White Carbon I worked across brand strategy, operations and sales. At Zo House it became the brand, physical spaces, community, membership and events. I did not experience those as separate careers. They were different parts of making something real.
What I want to remember
Some outcomes are a deal or a working product. Others are an idea seeded, people meeting, or a core memory made in a house. This journal will make room for those individual stories instead of forcing every experience into a numerical achievement.
Room for playful experiments
Lollypop Labs, duh.zo and duh.v2 were side quests alongside the larger projects: playful visual work, a smart-wearable idea and hardware hackathon experiments. Music is another part of the same curiosity. At Zo House, access to the console drew me into DJing; I am still preparing my first set, drawn to hypnotic melodic house.
Personal scope and outcomes are my account. External records below document the project and, where named, my role; they are not independent verification of every result.