Five tools, one conversation: why small teams lose the thread

Picture a team of eight deciding whether to take on a new client.

It starts in a chat thread. Someone forwards the client's email to two people, who reply from their inboxes. A quick call settles the price. Nobody writes it down, so a week later two people remember two different numbers, and the person who joined on Monday has no idea any of it happened.

Nobody did anything wrong. The conversation just went through four places, and none of them holds the whole story.

Why small teams feel this more

Large companies have people whose job is to keep track: project managers, assistants, a wiki someone actually maintains. A team of 2 to 20 usually doesn't.

Small teams also move fast and wear several hats. The same person is in sales calls, client email and product chat on the same afternoon. Every switch between tools is a chance for a detail to stay behind.

And small teams grow. The founding three remember why things are the way they are. Person number nine doesn't, and has nowhere to look.

What it costs

The cost rarely shows up as one big failure. It's small and constant:

• Asking the same question twice because the answer is buried in someone's inbox.
• Decisions being reopened because nobody can find where they were made.
• New people taking weeks to understand context the team could have handed over.
• Clients getting slightly different answers from different people.

Each one is minor. Together they're a lot of the friction people describe as "we're busy".

Habits that help, whatever you use

You don't need new software to make this better.

Pick a home for decisions. Agree on one place where a decision is considered made. A pinned message, a shared doc, a channel. If it isn't there, it isn't decided.

Close the loop after calls. Two or three lines after any meeting that changed something: what was decided, who's doing what. Post it where the conversation started.

Bring email into the open. When a client email affects the team, share the gist in the team space rather than forwarding it to a few people.

Name threads after outcomes. "Acme proposal: price agreed at the call" is easier to find later than "re: re: quick question".

Write for the next hire. Every so often, ask whether someone joining tomorrow could follow what happened. If not, add the missing line.

Why we're building Gliddi

These habits work, but they rely on people remembering to do extra steps at the busiest moments. We think the tools should carry more of that weight.

That's the idea behind Gliddi: make work coherent again by keeping a team's conversations together, starting with communication. It's built for founders and teams of 2 to 20, and product data stays in the EU. If that sounds useful, you can join early access.