How Calescence ships faster by running every project on Slate

The challenge

Calescence was growing fast, and the way the team worked hadn’t kept up. Engineering tracked work in one tool, product planned in another, and leadership pieced together status from a patchwork of docs and weekly check-ins. Nothing lived in one place.

The cost wasn’t obvious at first. It showed up as small delays, work that slipped between teams, and the quiet overhead of asking around to find out what was actually happening.

We were spending far more time coordinating the work than actually doing it. Every team had its own system, and none of them talked to each other.

Elliot Vale - Director of Product, Calescence

For a security company shipping on tight timelines, that friction was starting to matter. The team needed one place to run everything, not another tool to add to the pile.

Why Slate

Calescence moved to Slate to bring planning, engineering, and project tracking under one roof.

Slate was the first tool that didn't force us to choose between structure and speed. It just fit naturally into how we already worked, without asking us to change everything.

The appeal was that Slate didn’t try to replace how the team thought. Engineering kept its fast, issue-driven workflow. Product got the planning views it needed. And for the first time, leadership could see the whole picture without asking anyone for an update.

Setup took an afternoon, not a quarter. The team imported existing work through the Slate API, connected their repositories, and had every active project visible in one workspace by the end of the first day.

How they use it

Today, every project at Calescence runs on Slate from start to finish.

Engineering plans each cycle directly in Slate, breaking work into issues that link back to the larger initiatives on the roadmap. When a build ships, the deployment status flows straight into the workspace, so anyone can see what’s live without leaving the tool.

The whole company finally works from the same single source of truth. When something changes, everyone sees it at the same time.

Product uses Slate to connect day-to-day work to longer-term goals. Instead of plans living in a separate document that slowly goes stale, every initiative ties directly to the issues moving it forward. Nothing drifts out of sync.

The security team, which lives under constant time pressure, uses Slate to triage incoming work and route it to the right people fast. What used to be a scramble across channels is now a single, ordered queue.

What changed

The clearest change was visibility. Status updates that used to take a meeting now take a glance.

We got rid of three standing meetings in the very first month. The information was already in Slate, so there was simply nothing left to report.

Work stopped slipping between teams, because there were no longer gaps between tools for it to slip through. Handoffs that once required a conversation now happen inside the same system, with full context attached.

And the coordination overhead that had been quietly slowing everything down mostly disappeared. The team went back to spending its time on the work itself.

The result

Six months in, Slate is where Calescence runs.

Projects move faster because everyone is working from the same information. Leadership has a clear, live view of the company without interrupting anyone to get it. And the engineering team, freed from the busywork of coordinating across tools, ships on shorter cycles than before.

Slate didn't just organize our work. It gave us back all the time we were quietly losing to keeping everything in sync across teams.

For a company built on cutting through noise to find what matters, Slate does the same thing for how they work. It takes everything happening across the company and puts it in one clear place, so the team can focus on what they do best.