Skip to content
2025In developmentProduct design, architecture, development

TeamLink

Coordination software for teams that hate coordination software

−66%

Status meetings in pilot

0

Manual weekly reports

The problem

Where it started

Small teams drown in tools built for large organisations. Project platforms assume a full-time administrator; chat tools bury decisions in scrollback. What small teams actually need — who is doing what, by when, and what changed — gets scattered across five apps.

The solution

What got built

TeamLink strips team coordination to those three questions. One shared view of commitments, an activity stream that summarises instead of streams, and AI that drafts status updates from what already happened, so nobody writes Monday reports. The design principle: every feature must remove a meeting, or it doesn't ship.

The impact

What changed

In pilot use, weekly status meetings dropped from three to one, and the AI-drafted summaries proved accurate enough that teams stopped writing manual reports entirely.

Technology
Next.jsTypeScriptPostgreSQLClaude APITailwind CSS
Lessons learned
  1. 1

    The hardest part of team software is what you refuse to add.

  2. 2

    AI summaries succeed when they cite their sources — trust comes from traceability.

  3. 3

    Pilot with a real team early; imagined users are always too patient.