Squid connects your backlog, architecture, sprints, code and delivery rules, and guides every story from the first idea to production, with an assistant that knows your work. Built for teams outgrowing ClickUp.
Set up and find an organisation · Sign in and manage your own account
Every story is checked against the rules of your delivery manual. Ready is computed, never ticked — and the gate says what holds it.
Lanes per person, a timer on every task, and stories that move along the board as their steps are ticked.
Every step from idea to production — who acts, which rules check it, what evidence it leaves.
What finished, what moved, who is blocked and whether the sprint will land — ready to paste into chat.
Work shaped by readiness, architecture and delivery rules.
Set up and find an organisation · Sign in and manage your own account
Every step, decision and evidence trail in one place.
Momentum, blockers and quality from the work recorded today.
Each part of Squid does one job well — and they all share one brain, so nothing has to be copied from place to place.
Every rule from your delivery manual, checked on every story. Nobody ticks a box.
Time lands on the work it belongs to, and the board moves as steps are ticked.
Assigned, mentioned, unlocked — the moment it happens, with no feed to watch.
A test case per criterion; a pass needs a green run, checked against the real one.
Skills scored from real code reviews, a ladder with the next step in view.
Discover, refinement, decisions and evidence arrive as change sets to read and accept. Gates stay a person’s call.
An assistant that knows the page you are on. It checks, explains and suggests; you decide.
Repositories in Squid. Work goes on a branch named for it, then into dev, stage and main, one pull request at a time.
Calls inside Squid, from the calendar, in a window that floats while you keep working.
An assistant that knows Squid and your work. Ask it anything: it explains, checks, says what comes next, and rewrites a line when you ask. It never changes anything by itself. You decide and you save.
It runs the rules and the gates on a story, a feature or a decision, and says plainly what holds it back and how to fix it.
From the page you are on and what is waiting on you: one next step, then the few after it.
Any gate, rule, lens or feature in Squid, in plain words, with where it comes from.
A story, a criterion or a requirement, reworded to read well and pass the rules, as a suggestion you can use.
Not yet. Two rules hold it:
Given the address already belongs to the team, when the invite is sent, then it is refused and the sender is told why.
The modules, who owns which data, the standards and the decisions — the map everything is built against.
Ready is computed, not ticked. Evidence is checked, not pasted.
Squid is opening to a few teams at a time. Leave your email and tell us what you use today.