Co-Founder & Backend Engineer @TasksMind Engineer, Entrepreneur Ex @Capgemini Agartala, India 🇮🇳 → San Francisco, CA 🇺🇸
San Francisco, CA
Joined June 2011
- Tweets97
- Following198
- Followers69
- Likes291
Two parts of tasksmind answered the same question- which GitHub connection belongs to this team?
only a code comment kept their answers in sync.
This week we shipped one shared rule both use.
1
11
Our alert retry code had a blind spot.
After a few failed tries, we couldn't always tell if the alert had actually gone out.
So we stopped guessing. Now it gives up and reports it.
A rare false alarm beats a missed alert.
Would you pick loud or quiet?
2
2
21
Chiradeep Debnath retweeted
We just rebuilt @TasksMind .
New logo. New site. New everything.
→ tasksmind.com
We’re building the customer reliability platform for production bugs, backed by @forumventures , @nvidia Inception, and @RightSideCapVC .
When a customer reports a bug, tasksmind connects the dots across Slack, GitHub, logs, traces, and recent commits.
What broke.
Who reported it.
What changed.
Where the root cause lives.
And how to fix it.
Then tasksmind opens a safe PR for human approval and closes the loop with the customer.
Your team’s bug triage, done autonomously.
Mapped directly to customer retention.
Because at a startup, a production bug isn’t just an engineering problem.
It’s a customer trust problem.
Our mission hasn’t changed with the new brand:
Figure out how a bug turns into a lost customer, then build the AI engineer that stops it.
Check out the new tasksmind ↓
tasksmind.com
Made with ♥ in San Francisco.
Chiradeep Debnath retweeted
We’re launching @TasksMind .
When a customer reports a production bug, the problem is rarely just the bug.
The report sits in Slack.
Someone turns it into a ticket.
An engineer jumps between the codebase, logs, observability tools, and recent deploys trying to understand what happened.
Meanwhile, the customer waits.
We believe production bugs are not just engineering incidents.
They are retention events.
TasksMind starts with the original customer report, investigates the evidence across your engineering stack, identifies the likely root cause, and prepares a safe pull request for human review.
Nothing ships without an engineer.
Today, we’re opening TasksMind to a limited group of design partners.
Fix the bug. Keep the customer.
Every Slack thread contains context.
Every PR contains reasoning.
Every incident contains a lesson.
Most companies lose all three.
3
127
Chiradeep Debnath retweeted
Production bugs are not just engineering problems.
They are customer-retention events.
A customer reports an issue.
The team searches Slack, logs, Sentry, GitHub, and deploys.
Hours later, the bug may be fixed.
But the customer is still waiting.
The real problem is not just the bug.
It is everything that happens after.
Customer report → investigation → root cause → safe fix → customer follow-up
One context. One timeline. One workflow.
That is what we are building at @TasksMind.
Chiradeep Debnath retweeted
Hello, X. Time to reintroduce ourselves again as we reach 1K followers. Here's my team and what we are building. more at @TasksMind
Chiradeep Debnath retweeted
Hot take:
We don’t have an observability problem.
We have a context fragmentation problem.
Every engineering tool knows one piece of the story.
None of them know the whole story.
That’s why incident response still feels like detective work.
The next generation of engineering infrastructure won’t add another dashboard.
It’ll connect every signal into one context that humans and AI can reason over together.
The companies that solve this won’t just debug faster.
They’ll learn faster.
That’s the category we’re betting on.
Chiradeep Debnath retweeted
One thing I’ve noticed about startups:
The best product meetings rarely happen in meeting rooms.
They happen while walking to grab coffee.
On the bus back from an event.
Over late-night food.
Or while one person says,
“What if we’re solving the wrong problem?”
This photo wasn’t planned.
It was just two co-founders doing what we’ve been doing every day:
Talking to customers.
Debating ideas.
Challenging assumptions.
Trying to build something people genuinely need.
The best startups aren’t built in moments of certainty.
They’re built in thousands of small conversations that nobody else sees.
That’s the part of building I love the most. 🚀
There's something special about builders describing other builders.
No marketing.
No buzzwords.
Just the problem you're trying to solve.
4
74
Chiradeep Debnath retweeted
Five years ago, I landed in America with two suitcases and a student visa.
Today, I’m spending the Fourth of July in San Francisco, building a startup with my co-founders.
As America celebrates 250 years, I’ve been thinking about what this country has given me.
Not a shortcut.
An opportunity.
The opportunity to study computer science.
The opportunity to meet incredible people who challenged how I think.
The opportunity to go from an international student from Mumbai to building a company in San Francisco.
The journey hasn’t been easy.
There have been rejections, pivots, long nights, and plenty of moments where we questioned ourselves.
But every setback came with another lesson, another conversation, and another chance to keep building.
I’m incredibly grateful to my parents for believing in me, to my co-founders for taking this leap together, and to everyone who’s supported us along the way.
Five years ago, I came here to earn a degree.
Today, I’m chasing a much bigger dream.
Happy Fourth of July! 🇺🇸🚀
Chiradeep Debnath retweeted
Back in December 2025, I met @dianeemccormack at a holiday party while I was part of a founder residency.
At the time, I had nothing more than an idea.
No product.
No customers.
Just a lot of questions and the excitement of building something from scratch.
We became friends and stayed in touch.
A few months later, I walked into @Fondocom HQ, this time with my entire team.
That moment reminded me that startups aren’t just built through code or fundraising.
They’re built through relationships.
You never know which conversation will become a long-term connection, or who will be cheering you on months later.
So here’s a reminder to every founder:
Don’t go to events just to pitch your startup.
Go to meet interesting people. Stay curious. Build genuine relationships.
The startup may change.
The people you meet along the way often don’t.
Chiradeep Debnath retweeted
The biggest change we’ve made over the last few weeks wasn’t our product.
It was how we listen.
Every customer conversation has challenged an assumption we had. Some ideas got stronger. Others got thrown away completely.
Three things changed because of that:
1. We found our focus.
After dozens of conversations with engineering teams, we became obsessed with one problem that kept coming up. That’s where we’re going all in. No distractions. No “AI for everything.” Just solving one painful problem really well.
2. We redesigned our brand.
We wanted our identity to reflect what we’re building today, not the company we imagined months ago. Simpler. Clearer. More intentional.
3. We rebuilt our website from the ground up.
Not to look prettier, but to communicate our vision in seconds. If people don’t understand what you do, that’s on you, not them.
One lesson keeps repeating itself:
Your customers will often give you a better strategy than your own brainstorming sessions.
The hard part isn’t hearing the feedback.
It’s being willing to change because of it.
We’re still early, still learning, and still shipping every day. Excited to share what’s next.
Chiradeep Debnath retweeted
One thing I finally understand after moving to San Francisco:
Why founders drop out.
Not because school isn’t valuable.
Because building a company part-time and building one full-time are two completely different experiences.
When we were students, we’d work between classes, assignments, exams, and internships.
Now our only job is to understand customers.
And that changes everything.
This week, our team had one conversation that completely changed how we think about our company.
We started by asking how to make incident response better.
We left asking a different question:
“What actually makes a customer leave?”
It usually isn’t a single outage.
It’s when production bugs slowly chip away at trust.
A critical customer reports the same issue three times.
Support tickets keep reopening.
Engineering fixes what’s loudest instead of what’s most important.
A customer asks for something that doesn’t fit the roadmap, but they’re your biggest account. You hesitate. A competitor ships it first.
Customer gone.
That realization changed our direction.
We’re no longer thinking about incident response as the end goal.
We’re building customer retention infrastructure for production bugs.
Because bugs don’t just break systems.
They break customer confidence.
The biggest lesson from this week wasn’t technical.
Customer discovery isn’t something you do before building.
It is the building.
We’re heads down preparing for our closed beta.
Can’t wait to help teams save customer trust before it’s too late. – at San Francisco, CA
Chiradeep Debnath retweeted
Most AI SRE tools start from the alert.
We start from the customer.
Because for startups, a production bug is not just a reliability event.
It is a churn moment.
@TasksMind helps teams investigate, fix, and close the loop on customer-reported bugs before they lose trust.
Customer retention infrastructure for production bugs.
The dirty secret of on-call: most 2am pages aren't hard problems. They're easy problems wearing a scary costume.
A disk fills up. A cert expires. A bad deploy ships. The fix is usually one line.
We pay senior engineers six figures to be woken up and do five minutes of work badly because they're half asleep. That's the actual bug.
3
52
I deleted a feature we spent two weeks building this month.
It made our on-call agent faster, but it made it overconfident, and in production overconfident is dangerous. It started proposing clean, plausible fixes for the wrong root cause.
The kind a tired engineer would merge at 3am and regret at 9.
So it's gone. Speed isn't the metric. Being right, or honest about not being sure, is.
Building TasksMind has been a long lesson in that. I'm a cofounder and I write the backend, and the thing I'm proudest of isn't how smart the agent is. It's that it knows when to shut up and call a human.
Anyone else killed something good because it was subtly wrong for production?
1
3
53
Chiradeep Debnath retweeted
as an Indian founder, this one hits different.
watching @kunalb11 build CRED from an almost impossible idea into one of India’s most iconic companies, then step into leading WhatsApp globally, is insane.
trust, craft, distribution, ambition.
this is the kind of journey that makes you want to build harder.
It’s been a minute.
2015–2018
- Exited FreeCharge. Spent time learning and investing.
- Pondered about: Why can't trust be rewarded? Started with $1M of personal capital.
- Launched CRED to reward people for paying credit card bills on time.
2019–2025
- Built a system run by a team that values ownership, judgment, and craft.
- Grew from 0 to 17M members by aligning incentives with behaviour.
- Built several products during COVID lockdowns.
- Raised $900M+ from global investors. Did 4 ESOP buybacks.
- Made Indiranagar and IPL ads slightly more interesting.
- Received a full stack of regulatory licences.
- Lost 35 kilos.
- Scaled from 0 to ~$325M ( ~â‚ą3,200 crore) in annual revenue across payments, lending, insurance, commerce, wealth, and credit cards.
2026
- First profitable quarter (yet occasionally asked what our business model is)
- Raised another $900M from Meta in primary and secondary capital.
- Announcing our 5th ESOP buyback.
Today
CRED is ready for its next phase. I am stepping back and @miten steps in as interim CEO, partnered with an incredibly talented team. He has been heading strategy and finance and suffering me since 2020. I’m stepping away from the operating role and will continue as a shareholder. My commitment doesn’t change. Just the role.
Extremely grateful to our members, partners, regulators, and investors who made this possible. And to our board, Shailendra, Micky, Saurabh for their extraordinary conviction.
Team CRED, I’ll still expect you to be a 10x version of yourselves.
As for me, I’ll be joining Meta to lead WhatsApp globally.
Meta comes in as a minority investor in CRED. No access to member data.
While it’s come very far, the delta between WhatsApp today and its full potential is massive. I look forward to working with Mark, Chris, and the leadership across Meta for the next step in WhatsApp’s journey. Will, thank you for scaling something the world relies on quietly, and for making this transition smooth.
Onwards.