From tasksto a teamthat ships.
Say what needs doing. Span puts it on the right person's list, in their hours, and keeps everyone looking at the same thing: what is on now, and what is next.
How it works
One loop. Five screens. Nothing to configure.
- 01
Capture
Type it. An idea, a bug, a task, a “we should”. One box, on every screen, in plain English.
- 02
Decide
A lead names a person, or a team and Span picks. That is the whole approval process.
- 03
Place
Span books it inside that person's hours and timezone, before the deadline. No accept step: it is on their list. Not today, or send it back with a note, if the placement is wrong.
- 04
Do
Each person's Today is a list: what is on now, then the order they will do the rest. Drag to change your mind. Tags land at the top in red.
- 05
Reflect
A lead's Today adds the team as output: done this week, on now, queued. Never hours or spare capacity, because a lead who sees room fills it.
The list is the product
Every person sets when they work, once, on first open. Span places work inside those hours, in that timezone, and shows the result as a list, not a calendar. The calendar exists for the one day a week you need to reshuffle.
Calendars you can actually see
Everyone in a workspace can see everyone's calendar. Hide the details of yours and teammates still see you as busy, so nobody double-books you. Belong to two companies? Your commitments in one show up grey in the other, never with a title.
Updates where the work is
Post an update on the task. Type @ and tag someone: a thirty-minute review lands pinned at the top of their list, linked back, and Today shows a red number until it is dealt with. No channels, no feed, no bell.
Who it is for
Teams of one to about twenty who would rather work than manage a tool.
Span was built inside a live-ops game studio, where the last thing anyone needs at 2am is to fiddle with software. It works for a founder running two companies, for testers who never open Settings, and for one person keeping their own week straight.
It is not a Kanban board, a wiki, or a chat app. It does one thing: gets the right work onto the right calendar and keeps it visible. Your data is yours: one click exports the whole workspace as JSON, and the owner can delete it.
Open it, invite your team, type the first task.
Ten seconds to set your hours. Nothing else to configure.