Nachum Kligman @Kligman - Twitter Profile

the best decision I made this year was to connect my entire business to claude the tech stack that makes it possible: > linear: we use this for project and product management. used to be just for PMs, designers, and engineers. now everyone on the support team has access via MCP > unblocked: added it to slack and it gathers context of every conversation happening there. connected to github so it understands our code. connected to Linear so it knows what engineers are building. it has a full 360 of the business. > fellow: records every single meeting with full transcriptions and summaries. > claude: ties it all together. for almost all queries, I just go straight to claude. for example, last week, I asked claude: "what's the status of the podcast feature rollout?" it read the engineering slack channel, pulled the relevant linear tickets, checked which PRs had merged, read through all the relevant meeting transcripts, and gave me a status update with timeline + blockers in 30 seconds I would have easily spent a couple hours doing that manually there's just so much transparency through the business by connecting all of these different applications through claude if anything ever goes sideways (a spike in support tickets, a regression, a customer issue) I can just ask claude what's going on and it picks up context from a slack channel I don't even have access to, surfaces the ticket that was created, tells me which engineer is working on it and when it's shipping. unfathomably exciting time to build dope shit

denk_tweets's tweet photo. the best decision I made this year was to connect my entire business to claude

the tech stack that makes it possible:

> linear: we use this for project and product management. used to be just for PMs, designers, and engineers. now everyone on the support team has access via MCP

> unblocked: added it to slack and it gathers context of every conversation happening there. connected to github so it understands our code. connected to Linear so it knows what engineers are building. it has a full 360 of the business.

> fellow: records every single meeting with full transcriptions and summaries.

> claude: ties it all together. for almost all queries, I just go straight to claude.

for example, last week, I asked claude: "what's the status of the podcast feature rollout?"

it read the engineering slack channel, pulled the relevant linear tickets, checked which PRs had merged, read through all the relevant meeting transcripts, and gave me a status update with timeline + blockers in 30 seconds

I would have easily spent a couple hours doing that manually

there's just so much transparency through the business by connecting all of these different applications through claude

if anything ever goes sideways (a spike in support tickets, a regression, a customer issue) I can just ask claude what's going on and it picks up context from a slack channel I don't even have access to, surfaces the ticket that was created, tells me which engineer is working on it and when it's shipping.

unfathomably exciting time to build dope shit

21

182

9

248

17K

0

91

Nachum Kligman

@Kligman

about 1 month ago

@EliLebowicz @LevTahorMusic Good stuff 😂

0

1

0

32

Nachum Kligman

@Kligman

Who to follow

Last Seen Users on Sotwe

Trends for you

Most Popular Users