← Blog
CompanyMay 1, 2025·5 min read

From CONNCT to SLEDS: A Rebrand Story

How we evolved from task-exchange between AI agents to shared context as the core value proposition, and why the name SLEDS captures the vision.

S
SLEDS Team

For the first few months, we were called CONNCT. The product was focused on AI-to-AI task exchange — letting Claude hand off work to ChatGPT, or having Cursor request design assets from a Figma AI agent. It was technically interesting and nobody needed it.

The Pivot

The pivot happened when we noticed something unexpected in our early testing. Users weren't interested in task exchange. They were interested in context sharing. The most popular feature wasn't "send this task to another AI" — it was "let my other AI tools know about this conversation."

We'd built a pipeline for moving tasks between AI agents, and people were using it as a context bus. The signal was clear: the value wasn't in task orchestration. It was in shared memory.

Why SLEDS

The name SLEDS came from the acronym: Shared Layer for Every Digital Space. But it also captured something about the product philosophy. Sleds move across terrain. They connect points. They carry things from one place to another. That's what the product does — it carries context across the landscape of your AI tools.

The winter/alpine branding followed naturally. Frost as the AI personality. Snowflake iconography. The blue color palette. It gave us a distinct identity in a market full of generic SaaS brands with abstract gradient logos.

What Changed Technically

The rebrand wasn't just cosmetic. We restructured the entire data model. CONNCT was built around "tasks" — discrete units of work passed between tools. SLEDS is built around "threads" — persistent context containers with observation histories. This change unlocked everything that came after: Pulse briefings, semantic search, automatic linking, and eventually Frost Dispatch.

Lessons

The biggest lesson was humility about what users actually need. We came in with a vision of AI agents collaborating on complex workflows. Users wanted something much simpler: "Make my Claude session know what I did in ChatGPT yesterday." Starting from that simple need and building outward has been far more productive than starting from a grand vision and building downward.

← Previous
From Solo to Team: How Context Scaling Works
Next →
Why We're Building SLEDS

Ready to try shared AI memory?

Free to start. Connect your AI tools in minutes.

Get Started Free →
sleds — Shared AI memory for teams