Cord for Client Success

↳ One of your most highly requested features is here. With Cord for Client Success, not only can your users work together as a team, but your client-facing teams can also speak to users directly to provide account management or customer support in the same place.

Team-led Growth, via email

↳ Allow your users to invite their teams to your SaaS with engaging, easy-to-understand email invites. You're totally in control of the invite flows, so when your clients share a page, you can benefit from the growth.

↳ Email invites were key to 

Slack integration improvements

↳ Users can share messages or invite people to collaborate in your product via Slack. When a user gets a Slack with a link to an annotation or message in your product, clicking that will take them to exactly that annotation or message, open within your product, automatically. Hello, more Team-led Growth 👋

↳ We've even gotten special permission from Slack that lets messages come directly from your users rather than a bot. Because who wants to talk to a bot? ❌🤖

Bits and pieces 

 React to any message with whatever emoji your ❤️(or 💛💚🖤🧡) desires.

 When someone resolves a thread, a notification is sent to everyone following the thread’s inbox. You can also see that the thread is resolved in the thread itself.

 The Cord team is busy refreshing your collaborative features' look and feel– improved menu, simplified inbox, clearer threading, and more. Updates coming soon. 

Must read (or watch!): The Ultimate Build vs. Buy Framework

↳ To build or not to build (in-house)? That is the question that all SaaS product and engineering teams face when beefing up product features. So what’s best when?

Launch notes: Add smooth onboarding and top-notch service right inside your SaaS product

Updated email notifications

↳ Entice your user's teammates to join the convos happening in your tool. Users who are @mentioned get more context with screenshots, annotations, files, and previous messages in personalized and customizable emails.

↳ From there, users can reply via email or go directly into your tool, where they can sign up for an additional seat or use a view only seat (you decide!).

Direct links

↳ Your users can now join convos even faster to answer questions, get approvals and give their feedback. If a user gets an email or Slack message with a link to an annotation or message, clicking that will take them to exactly that annotation or message, open within your product, automatically.

Pinned annotations

↳ Give your users a birds-eye view of all the annotations so they can stay updated on all their team's conversations. Clicking on an annotation pin opens the relevant message so they can jump in where they're needed. All annotations can be hidden with a single click, too.

2022 roadmap

Get your API keys and adjust settings such as colors, logos, onboarding messages, and payment details

 Pick and choose the right features for your users

 Follow teammates' mouses (mice?) in real time

Launch notes: Add engaging email alerts plus annotation mode

What is your background, and how did you join Cord?

My background is in Graphic Design with a capital G&D. I finished studying design just before the idea of being a digital designer or product designer really exploded. In my first real job after graduating I was thrust into the world of digital design, and it was there that I really started to understand what UX was and how to apply design thinking to digital. Although graphic design and digital design are basically the same discipline, there are some key differences; you don't really need to bring 

 to digital design like you would with a brand, although this is something which I love to do and I think it ultimately makes things more interesting.

I was Digital Design Director at The Guardian, and I worked there for 6 years so a huge chunk of my career has been in the throws of editorial cycles. Editorial design, specifically digital editorial design will always be something which is close to my heart. It taught me so much, and made me a much better designer, it gives you the ability to think on your feet and turn things around very quickly, at a huge scale too so quality is always at the forefront of your mind.

The Guardian 200

What does design that "looks good and does good" mean to you? And how does that translate to your work at Cord?

Design is super subjective, what looks good to me, might look terrible to someone else. There are of course key principles which will always make a design look better; the basic underlying principles of alignment, scale, colour, type. For me it goes back to The Big Idea, if there is a great idea which is clearly communicated or clearly signposted which ultimately leads to a payoff of understanding this idea or easily being able to action something, that for me is where success is.

We can take taste out of the equation here and focus on the root of what we are trying to do. For Cord this mean two things: it means being smart in our communications, but it also means trying to find simplicity. Cord, and collaboration in general is a complex beast so we always have to strive to find simple, but not boring, ways to communicate this. This applies to our work on and outside of the product, whether it's solving one of the meaty problems that being a fully-integrated-collaboration-tool brings, or an animation which clearly brings these features to life.

Why is making software more collaborative important?

We've all seen how Figma has revolutionised the way that design teams work, and it's done this on a scale which I'm sure even Figma are surprised by. This one tool has unified the design process by understanding the process and the pitfalls. Before Figma we had large files which needed to be shared, tools like WeTransfer and Dropbox do an OK job of this, but it's a slow process with many moving parts, files get lost, emails get missed, feedback follows, more emails, and more files. 

What Figma managed to do was to remove the need for final_final_really_final.pdf and combined the design process, with file sharing and communication all in one place. We believe that these same pitfalls and challenges apply to other disciplines, other sectors and other products; no one works in just one tool anymore, your working day is spread out hopping from one place to another, and this complexity will only continue to grow. What Cord is doing is working on ways to 

help people collaborate better both across and within these tools.

Figma's growth

What does it take to get collaboration right, from a design perspective?

Put simply, a lot. Collaboration is inherently complex because the audience is everybody and anyone on a team. Anyone in any role at anytime should be able to jump into a tool do the thing they need to do with as little barriers as possible. The collaboration layer is there to facilitate this; it can't get in the way of their primary role, but it should enhance their ability to do their task. But this looks different in different teams and in different products. We've learnt that it's very difficult to design a one-size fits all approach because there are always nuances to the way people want to work. But what we've also learnt is that some of the basic building blocks for collaboration do fit, most, if not all ways that people work. 

The design challenges are also unique; we have to think about how these building blocks will looks inside other peoples products which means that we often have to think about ubiquity and what an amorphic experience looks like. But there is a tension here as we also need a brand that both stands alone and explains what Cord is. We are always working towards striking a balance between a universally applicable product experience and a recognisable brand.

Where do you look for inspiration? And how does that appear in Cord's features?

For me, it depends what hat I am wearing. With my brand design hat on I get most inspiration from words and the way people communicate. Often my ideas come from writing something first, I love the interplay between what something says and what something looks like; not everything needs to said and not everything needs to be seen, they play off of each other and can create a magically satisfying way of communicating.

I also get very inspired by movement. In my minds eye I always see my designs as things with the potential to move, and shift and change form, and therefore change in meaning.

Inspiration from words, the way people communicate and movement

How does the design team work together now? How are you hoping to grow the design team?

It may not be surprising that we spend most of our time in Figma; the collaboration company that loves collaboration. Whilst Cord as a business is still very much in its infancy, our brand language and design system is quite mature in comparison. We are a small team and we work very closely together across the brand communications and the product, one informs the other– for us they are symbiotic. We love to get the most out of our design team; healthy critique and open communication are key to this. We have total freedom to think of ideas and propose new things but if we think it's not right we're not going to shy away from discarding this and moving onto the next thing. This critique and feedback comes from across the business as we're a close-nit group, and so far this has been a super easy and productive way for us to test our ideas.

We want to build a team of doers, people who are not afraid to get stuck in and help shape our product and brand language as we grow. Currently we have a team with a wide variety of skills from brand design to front-end development, product design to strategy; our work touches almost every surface of Cord's business. We are still small, so it's the moment for people to shape something from not quite the ground up but certainly close to.

We are actually looking for a product designer to join the Cord team so if this sounds good to you head over to our jobs page and 

Get to know our design philosophy with a quick Q&A with Ben, our brand designer. 

Design stories: Ben Longden

, a major design platform for UX teams to design, manage and handoff projects, recently added in-app collaboration abilities for their users. This implementation was one for the (Sketch)books as the biggest upgrade to the tool since launching in 2010.

 puts the need for real-time, in-app collaboration best:

“We know that the design process is fundamentally collaborative. Whether you’re bouncing ideas around with other design colleagues or working with developers to turn pixels into code, a design cannot exist in a vacuum.”


 And SaaS tools will need to implement similar in-app functionalities, or they’ll fall behind.

Slapping together a commenting feature or emoji reactions won’t help you win– it takes a quality user experience to work. Luckily, Sketch summarized their entire process in their 

 so the industry can be both impressed and inspired. Here’s the gist – and what you can learn from them about collaboration for your own product.

How Sketch rolled out their high-quality collaboration experience

Sketch doesn’t do research carelessly. They created an entire business arm dedicated to engaging with customers for user research.

Sketch’s two-part research for the collaboration project included discovery research and usability testing.

Discovery research was about solving the problems with real-time collaboration – but what exactly were they? To find out, this team dove into what their own customers thought about collaborative editing, including concerns and pain points.

Second came usability testing, which ensured that the solutions to these problems were efficient, user-friendly, and the best possible approach.

After discovery and testing, Sketch Labs had a better idea of how their users work together and solutions to their needs. For example, their research unveiled common concerns around file-sharing, which led Sketch to create a new way for saving files directly in the Workspace.

Sketch created a new way for saving directly in the Workspace.

It’s clear the Sketch team has incredible research, product, and development teams who put in the time and effort needed to do this right.

If you want to skip some of these steps, an out-of-the-box solution like 

Building vs. buying collaborative features

If you have an in-house research lab, months to pull together users for discovery and testing, and engineering time to spare on developing features that's aren't the core functionality of your product, then you could probably handle a Sketch type of rollout in-house. The truth is, most start-ups and scale-ups don’t. Enter: an out-of-the-box solution.

Cord empowers SaaS vendors to add months of research-level collaboration to their product in a few days.

There’s no need to reinvent the wheel when you get similar functionalities to what Sketch carefully developed, starting with just a single line of Javascript.

Cord offers native collaboration for your tool such as:

Visual or Google-Docs-esque text annotations for any part of your software

A messaging API that provides in-context customer support

Integrations with tools your users are already using, like Jira, Slack, Asana, and more

Live cursors so your users can feel togetherness in real time

 so users will still feel cozy in your tool

See how Typeform created a collaborative experience powered by Cord

No matter the route you take, we wish you the delight Nativ got to experience with Sketch’s rollout:

“For me, one of the most rewarding moments of the whole process was seeing our participants’ reactions when they experienced collaboration — and saw their teammates’ cursors — for the first time.”

Get the best version of your product without the heavy lifting. See how Cord can level up your native SaaS tool collaboration features in days at 

How Sketch added collaboration & what other SaaS can learn from it

Collaboration just got more customizable

↳ Collaboration via Cord perfectly matches your brand's look and feel. Partners get complete customization of the collaborative features, including colors and the copy/design of onboarding messages. We've also added the ability to fully design the button and embed it in your UX.

↳ Coming soon: More fine-grained control over the comments feed – from fonts, colors, to its placement inside your product.

Anonymous animals don't increase engagement, this will

↳ As much as we love the anonymous wombats that appear in Google Docs, seeing teammates' profile pictures will encourage more engagement from your users. Make your product more of a hub for teams with our face pile upgrades.

Slack integration for your tool

↳ Your users Slackin' away: sending screenshots and links from your product to get feedback or ask for approvals. Embedded collaboration allows anyone to share message threads and annotations (with screenshots!) directly to Slack.

↳ We've even gotten special permission from Slack that lets messages come directly from your users rather than a bot. Because who wants to talk to a bot?

UI updates: All the small (important) things

↳ We refine your users' collaboration experience so you don't have to. We obsess over UI details to get teams working together in seconds (without help center articles or how-tos). We've improved how the inbox and button work to make it crystal clear when and how many notifications you have.

Coming in early 2022

: Reply to Cord messages directly via branded email notifications

: Keep all annotations floating on the screen for easier access

 Follow teammates' mouses (mice?) in real time

 Set up your features faster with a simple log in

Launch notes: Match your product's look & feel

Collaboration-first companies will be the ones who scale the fastest. We’ve seen it time and time again – Figma, Notion, Canva and Airtable are the most notable examples. SaaS tools that put collaboration at their core, instead of as an afterthought, will win in this new era of software.

Collaborative products are better for businesses, users and their teams – so why doesn’t every product have a collaboration experience as smooth as Figma’s? Well, they are trying.

Teams are scrambling to build multiplayer tools, only to discover how hard it is, and often disappointing users. It makes sense – as more teams go remote and rely on tools like Slack and Loom, users hold incredibly high standards of what 

Product teams are discovering the market-winning benefits of adding collaboration but are struggling to deliver an experience that aligns with the standards they hold for their core experience. That’s where Cord comes in.

Product managers save their teams months of research, design, development, testing and iterating 

get ahead of the collaboration game by partnering with Cord.

Typeform becomes a market leader by adding collaboration

 is, by nature, a user-friendly software tool that prioritizes an intuitive interface (they’re called “people-friendly forms and surveys” for a reason). Their users’ top feature request was a way to work with teammates on a typeform. We were delighted when a member of their team discovered Cord by using it in another tool.

Thanks to the leadership of Tyze Whorton, Typeform’s group product manager, we rolled out what he called a “Google Doc experience, and then some” to over 120,000 Typeform users in just a few weeks, creating the best form collaboration tool on the market.

Some amazing investors trust us to make this a reality for even more tools

 last year after leading a product team at Facebook, advising founders and CPOs of $1B+ startups and mentoring newer startups with Techstars. I witnessed firsthand the stark contrast between Facebook’s suite of connected internal tools and the disjointed nature of B2B SaaS tools newer startups rely on.

My co-founder, Jackson, an early engineer at Facebook, and I knew we couldn’t change this space alone. We looked for the best designers, engineers, and product craftspeople to start working on transforming web products into collaborative, multiplayer experiences. We’re proud to have gone from not having a single line of code in May 2020 to signing partnership deals with 9-figure companies just over a year later.

, our team can forge ahead with connecting more tools and websites to a collaborative, communication-first team environment. All our partners need is a line of Javascript for Cord’s API to save years of development time, improve customer experience, and level up their products.

This is exactly why the Cord team puts all of our energy into crafting the 

best features for all types of collaboration

 like real-time (e.g., co-browsing, live video) and async (e.g., annotations, integrations with task managers, screen recordings).

This all drives what we’re calling team-led growth.

The next big shift in SaaS: Team-led growth

There’s a lot of talk about product-led growth. This was the remedy for over-relying on salespeople to sell software. It highlights how important self-service and trial periods are for products.

But, product-led is missing the secret sauce of the fastest-growing products we see today (again, think Figma, Notion, and Airtable). What do these products have in common? They’re collaborative and grow within teams.

Figma reached 4 million users in 4 years and decimated Adobe, Invision and Sketch to become the dominant prototyping design app – in major part thanks to its built-in collaboration.

Team-led growth happens organically as users invite their teammates from Slack, Google, Teams, and task managers to work together inside a tool like Typeform.

Team-led growth makes your product stickier in organizations

When selling software for teams, a product has to stick with more than just one person. Network buy-in reigns when a product is collaborative, shareable, and has baked-in communication. Try ripping out months, or years, of messages from a team’s vice president to analyst, out of a team’s workflow.

Plus, users spend more time in sticky, collaborative products. Imagine a world without context switching and app toggling just to complete one task. Cord lets your users do just that — stay in the trenches (aka 

) without the Asana-to-Slack-to-your-product dance.

Better collaboration and efficient workflows make for better products. We will continue to see that welcoming a user’s team into a tool leads to better sales value, seat expansion and retention. We know our partnership with Typeform is just the beginning.

Cord is fueling team-led growth for companies like Typeform with our latest $17.5M round

Annotations got even better

↳ First, we gave your users pins to drop annotations on any part of your tool. Now, they can highlight text and create Google Docs-style comments too! Welcome your users' teams into your product by allowing them to leave feedback, ask questions, or get approval quickly and clearly.

Resolve threads in your tool

↳ Users can now resolve threads in the collaboration sidebar. That way, when a team finishes a project, or ships a campaign, teammates can declutter their workspace. Not to worry, though, they'll still be able to refer back to resolved threads by scrolling down to "Resolved threads" towards the bottom of the sidebar.

Attention: Product people

, add the best collaborative features natively in your product, all with a single line of Javascript.

 doing just that – giving their 120,000+ users the ability to work together directly inside Typeform. We're using our $17.5 million fundraise to make this a reality for even more tools (yours included!).

API updates for the builders

→ Sidebar open and closed events. You can now tell if a user has the sidebar open or closed, as well as the width of the sidebar. That way, you can adjust the UI accordingly and offer the smoothest experience for your users. 

→ Better tools for single-page-app developers. We've given you more control over when the sidebar appears to give single page apps user-friendly collaborative features. 

→ Segment integration. You can now get a real-time events stream for analytics with our Segment integration to understand your user's full journey: when they send messages, use annotations, or mention and invite their teammates, as a few examples.

Launch notes: Add the Google Docs experience to your product – and then some

Heads up: On October 4th, I’m going to be presenting a workshop at Product Drive, entitled “

Team-led Growth and the Rise of Multi-Player Collaborative SaaS

.” It’s shaping up to be a terrific event with an impressive speaker list, and a little while ago I chatted with Emilia Korczyńska - Head of Marketing at 

 and one of the organizers - about my topic. You can watch the video of that discussion 

In our lives, we've gone from buying gigantic servers and moving, organizing, and sending files around to using cloud software, where the app and the data are one. We can already see the next huge shift to how software works on the horizon. As we’ve started to see, early adopters must replace incumbents – or protect their lead – before they become the Siebel CRM (a once undisputed king) that gave way to Salesforce and HubSpot.

Living through the last quarter century has been unique. We've enjoyed a rare opportunity to see a few platform shifts up close and get a deep sense of how these disruptions unfold. I vividly remember the last on-prem server I saw. In the startups I worked at 15-20 years ago, buying servers was a rite of passage before your first investment round. All companies had to have a “server room” (which sometimes was just a big, noisy box under my desk.)

All of a sudden in 2007, we started using S3 and EC2, Amazon’s earliest cloud offerings. And just like that – It was gone from the life of startups in no more than 2 years. This shift took years more for old incumbent companies – some of which still have on-prem servers to this day. But for startups, the swiftness of adoption was palpable.

This isn't the only shift cloud brought on from 2008 forward. All these startups built from scratch on the cloud had a new thing in common: There were no more files.

Some of us may not even remember saving files. We don’t even consider that our account software, games, CMss – they all had files somewhere that you had to remember to save, organize in folders and back up. The data that these tools work on is no longer your responsibility – it’s baked into the software itself.

Managing this data separately from the software was full of friction and overhead. Cloud made files redundant, to the advantage of both users not having to mess with it, always having the latest available to their entire org, easily located as they were integrated inside the app; and to the benefit of the vendors who had stickier products, easier deployments, less version/backwards compatibility hell, more measurability of use, etc. Data became inseparable from the apps.

That's what Sketch and Adobe must’ve felt as Figma became the dominant UX design app.

The next huge revolution in cloud-based, fileless SaaS

Here at Cord we think there's another huge revolution coming in cloud-based, fileless SaaS. It's the final frontier, the one thing that's still clunky and inefficient like carrying files around. And that's bringing in your team, partners and clients into the tool where you work.

Making tools multi-player and collaborative is so powerful that it's an irresistible force for both users and vendors. And it's already happened: That palpable, sudden switch is what Sketch and Adobe must’ve felt as Figma became the dominant UX design app in major part thanks to their collaboration.

It’s quite clear why: The thing we for the most part didn’t integrate into our software yet is the social layer. Collaboration – who you work with, what did they say and do in the app, what are they working on now – it all gets handled inefficiently in other software, with copying and pasting of links and screenshots to communicate in a way that’s unmapped to where you work on and increases your cognitive overhead when you try to remember where was there a discussion relating to this item. People prefer to collaborate in line when they are given an integrated, performant, expressive way to do so, as you can see in Google Docs or Figma. And vendors see this change coming, and the first to adopt a high quality collaboration solution will accrue the advantage from user adoption, seat expansion and retention as teams and organizations get enmeshed deeper in their tools.

Those who adapt quickly – thrive. The second – survive. The rest …

So what's a vendor to do? Building all of these capabilities by yourself is tough work, both from engineering and from a product and design perspective – just like continuing to buy and maintain servers under the desk for new startups, is complete folly. It’s a job better done well for customers and vendors by a specialist that invests in the research, the infra, brings in the specialist talent and spreads the costs of developing the cutting edge, best-in-class collaboration capability across many vendors that embed this.

 to reap the benefits of team-led growth inside your product.

Why is collaboration eating software?

Building apps – internal tools or otherwise – is 

 together with your teammates when code is involved is easier said than done. Taking screenshots, adding annotations, sending a flurry of Slack messages, and then adding Jira tickets is 


In this post, we’ll walk through how to use 

 (a fast way of building internal tools used by DoorDash, Warner Bros, Peloton and more) with 

. Cord lets you add comments, annotations, and guides directly in your favorite apps – so you can talk with your team in the apps you’re working in. Cord also 

 (Jira, Asana, Monday, etc.) so you can create and manage tickets without leaving your app.

Save time by building internal apps with Retool and Cord

Here’s a few suggestions for how teams use Retool and Cord to build better internal tools without all the back and forth.

Write onboarding guides directly in the app. 

Onboard new members of your team by creating annotations and comments with Cord. Attach relevant files to document how the internal tool works, right inside the tool. This is a lot easier than outdated walkthroughs lost in Confluence or Coda. Plus, teammates can @mention you if they have a question and you can chat directly in Retool– almost like sharing your screen on Zoom, without having to sit through another video call.

Create tasks that will automatically appear in Jira or Asana. 

Anytime you write a comment using Cord, whether it’s to 

 or change a dropdown to a search input, you can make it an Asana or Jira task so it fits right into your workflow (and it will actually get done!).

Write onboarding guides directly in the Retool app with Cord.

Create tasks that will automatically appear in Jira or Asana with Cord.

Your internal ops team can log edge cases and leave a record of the conversation. 

The users of your app can record edge cases and leave notes about what was decided inside Retool to increase efficiency and speed up onboarding for new team members who may run into the same issue.

Add Cord to your browser to start collaborating in Retool

Cord is a Chrome extension that you can activate on SaaS tool or website. Install Cord in a few quick 

2. Sign-in with Slack (Or, sign-up to be notified when we add Google and Microsoft Teams support)

3. Complete onboarding: Watch a 30 second video, install the extension from the Chrome store, and import relevant Slack messages by adding the Cord Slackbot

Complete Cord onboarding

5. Then, go directly to your Retool app and start annotating with your team!

Go directly to your Retool app and start annotating with your team!

If you don’t have a Retool account yet, you can sign up on 

Build together in Retool with Cord comments and annotations

People already realize the power of collaboration.

Just think of the tools you’re working with daily: SaaS products like Google Docs, Figma, and Pitch have already added collaboration elements to their platforms (hello, Anonymous Muskrat 👀). Software companies know people want it — that’s why they gradually add chat abilities to their products, but it’s usually at a cost.

SaaS products like Google Docs, Figma, and Pitch have already added collaboration elements to their platforms.

“This creates sub-par and inconsistent collaboration experience for the end-user,” said Nimrod. Notes go in separate inboxes, feedback gets lost, teammates cry in frustration.

The way we use multiple tools is way clunkier than it needs to be.

But as it stands, it’s unavoidable – you have to use them all to get your work done.

 working in Mailchimp may grab copy from Google Docs, designs from Figma, and feedback from Slack to create a campaign back in Mailchimp. We don’t need work to be this excessive.

You already use a lot of apps, and it’s time to connect them for a streamlined workflow. 

One inbox. One notification to check. Many sighs of relief.

“Switching costs” aren’t in your budget.

The average small business uses over 100 different apps

, and Matt shares that Capiche’s four-person team uses over a dozen tools.

Think of all the lost energy, time and brainpower it takes to switch from coding/designing/writing to chatting apps, then back to coding/designing/writing, at least a dozen times per day.

“Every time we switch, we’re losing seconds of our time." 

, you can stay in the context of what you’re working on to stay in deep work mode.

Cord’s long-term value = streamlined collaboration
Immediate relief = eliminating clunky interactions

Nimrod has an extensive engineering background, specifically surrounding chat, productivity, and community (aka peopleware). His tenure as a PM at Facebook inspired much of the vision for Cord.

When Facebook’s development teams kept running duplicate analyses, Nimrod knew the overlap was wasting valuable resources and time. They built a way for related data conversations to integrate across an expansive suite of internal tools.

Launch notes: Add smooth onboarding and top-notch service right inside your SaaS product

Launch notes: Add engaging email alerts plus annotation mode

Design stories: Ben Longden

How Sketch added collaboration & what other SaaS can learn from it

Launch notes: Match your product's look & feel

Cord is fueling team-led growth for companies like Typeform with our latest $17.5M round

Launch notes: Add the Google Docs experience to your product – and then some

Why is collaboration eating software?

Build together in Retool with Cord comments and annotations

The future of collaboration is here, but we need a mindset shift

State of Project Management in 2021 Report Reveals How Companies Use Task Managers

Work with your team directly in HubSpot with this add-on

Heal your love-hate relationship with Mailchimp with this add-on

In flow and in context: How to unlock that 10x productivity for your team

How in-app collaboration is changing the way we work

Cord + Slack = Collaborative magic ✨

Add comments and annotate inside any tool you use at work, get updates in Slack