We plan to bring eChai across 100 cities in India. It starts with eChai Startup Demo Day on 26 September, all in person. 14 cities confirmed, 1093 founders registered. Any city that reaches 20 interested founders is on too. See your city

Founder Notes

Jatin Chaudhary on eChai Founder Notes

More Founder Notes

  • Sumit Karanji Sumit Karanji Dermatouch 2h

    Every D2C consumer brand panel ends at the same question.

    How do you start a D2C, how do you control Meta & Shipping spends, how do you build trust and retention.

    Last night at GVFL, eChai Ventures ran the Ahmedabad edition of Building Consumer and D2C Brands. Riddhi Sharma, Mompreneur of BabyOrgano, Shweta Patel from @fashionfloorindia and me on the panel.

    My answer has not changed in three years, Online makes you findable. But don't stop your business on one channel.

    A D2C brand can buy its first 10,000 customers. Almost nobody buys their next 100,000 the same way. At some point the CAC stops making sense and you need to deep-dive what channels work, who is you real customer, why are they buying and what's their feedback on your product.

    Riddhi spoke about building trust which took her 5 years, Shweta spoke about building an initial group of power user/community to kick start the business, although Dermatouch did all of that with our product efficacy, results and without having to do what both of them did, key takeaway here is that not all business models are similar.

    Find the one which suits your customers the most, and double down.

    What I keep noticing about folks in echai Ahmedabad rooms is that nobody has a mask. People ask what they actually want to know.

    Thanks Jatin Chaudhary for putting founders in a room and getting out of the way. -:)

    Originally on LinkedIn →

  • Vivek Trivedi Vivek Trivedi Clozzet 3h

    Had a great time at eChai’s “Building Consumer & D2C Brands – Ahmedabad Edition”!

    it was amazing to connect with fellow founders, exchange ideas, and learn from the incredible D2C ecosystem being built in Ahmedabad.

    Always exciting to be part of conversations that shape the next generation of consumer brands.

    Originally on LinkedIn →

  • Curated from X →

    Anthropic's developer account posted this on 17 September, and the problem it is aimed at is one anybody running several Claude Code sessions at once already knows: you decide what each one works on, repeat the same background at the start of each, and check back to see which finished or needs an answer. In a project that coordinating moves to Claude. One long-running conversation takes what you send, a bug report, a stack trace, a list of tasks, and starts a thread for each piece of work or hands it to the thread already working in that area. Each thread is a cloud session with its own context window, on its own branch, opening a pull request when the work calls for one and reporting back when it finishes, and every new thread starts with the project's repositories, instructions and memory, so a rule stated once, such as which branch to target, reaches all of them. An Overview pane lists which threads finished, which pull requests are ready for review and which thread is waiting on your answer, which is the concrete form of the line about it keeping going when you leave. The examples in Anthropic's own docs are a lint config brought across every service, one service's stream of bugs and review requests pasted in as they arrive, a migration bigger than one session, and a folder of contracts or a support-ticket export you keep asking new questions of. The limits are stated just as plainly. Threads work on GitHub repositories and uploaded files, not on anything only your machine can reach, so a local database or a device emulator still means a local session; it is on Pro and Max and not yet on Team or Enterprise; a project uses the same plan limits and uses them faster, with a ceiling of 200 new threads a day; and the name is a redesign of the Projects that already existed in the claude.ai chat, which grouped conversations and reference files without threads or a coordinator. In the replies they add that it reaches Pro and Max users who already run cloud sessions and have not used Projects first, earlier Projects users a little later so existing ones move over cleanly, and that support for local workflows is coming very soon. A good deal of what is built on eChai, this site included, is built in Claude Code, so this is the next thing a lot of founders here will be running their week through.

    ClaudeDevs ClaudeDevs 17h

    Today we're rolling out Projects in Claude Code on desktop and web.

    A project is one conversation with Claude. It splits the work into threads itself, runs them as parallel cloud sessions, passes context between them, and keeps going when you leave.

    In beta for select users.

Every note →

eChai Partner Brands The partnership →