HQ: the workspace we built for ourselves.
We were drowning in Basecamp threads, Asana columns, Slack DMs, and email. So we built one fast workspace that holds everything — and now we offer it to other teams who've had the same enough.
- Product: All-in-one team workspace — tickets, projects, conversations, ops
- Built for: Small-to-mid teams (5–100) who've outgrown spreadsheets and Slack threads but don't want enterprise PM bloat
- Origin: Built by Stacksy, for Stacksy. We use it every day. Now sold externally at aychkyoo.com
- Differentiator: One opinionated place that holds the whole picture — not a stack of tabs
The problem we kept hitting (in our own team)
Stacksy is a small team that ships a lot. We tried the usual stack — Basecamp for client work, Asana for internal projects, Slack for conversations, email for the slow stuff, Linear for engineering, Notion for docs, plus the spreadsheet that nobody admits is the actual source of truth.
Each tool was excellent at its narrow job. The problem was the gaps between them. A client conversation in Basecamp would reference an Asana task that was actually being worked on in Linear, with the doc in Notion that nobody could find, and the decision happening in a Slack DM that wasn't searchable in any of those places.
The cost wasn't any one tool. The cost was the constant context-switching, the things that fell through the cracks, and the rising "where does this live?" question every time anyone joined or returned.
What we built instead
HQ holds tickets, projects, conversations, and team ops in one workspace. It's opinionated about what it does and what it doesn't.
- Tickets — for inbound requests (customer support, internal asks, anything that needs a response). Threaded, assignable, with proper state machines.
- Projects — for work that has shape: tasks, milestones, owners, deadlines. Not a kanban graveyard; a real project structure.
- Conversations — async threaded discussions that don't evaporate the way Slack does. Searchable, durable, ownable.
- Team ops — the lightweight tracking that every team needs but nobody wants a dedicated tool for: who's out, what's shipping this week, what's blocked.
One workspace. One search. One source of truth.
The design principles
- Fast. Page transitions in <100ms. Keyboard-first navigation. No loading spinners for actions that should be instant.
- Opinionated. We don't support 50 different workflows. We support the way most small teams actually work — and we make that way feel natural.
- Searchable. The conversations, the tickets, the project notes — all in one index. You find things by remembering anything about them, not by remembering which tool you used.
- Multi-tenant from day one. Built so each customer has their own isolated workspace, with shared infrastructure underneath. We use this ourselves to run Stacksy AND host the platform.
- Honest pricing. Per-workspace, not per-seat. Adding the 50th teammate doesn't change the bill.
Who it's for
- Small consultancies and agencies running 5–30 clients at once
- SaaS teams wanting one place for support tickets, product work, and team ops
- NFP operations teams coordinating programs, volunteers, and grant deliverables
- Anyone who's tried Basecamp + Asana + Slack + Notion + email and concluded the gaps cost more than any one tool saves
The "we use it ourselves" loop
HQ is the system we run Stacksy on. Every customer ticket comes into HQ. Every project we work on lives in HQ. Every conversation we have asynchronously happens in HQ. We don't use Slack or Asana or Linear or Notion. Just HQ and email.
This isn't a marketing line — it's a forcing function. Every annoyance we hit is one we feel. Every missing feature is one we feel. Every performance regression is one we feel. The product gets better fast because we're also the most demanding customer.
What this tells you about how Stacksy works
HQ is what happens when we look at a problem space and conclude none of the existing tools are designed for the team we actually have. Building it was a multi-year commitment — but we needed it to exist, so we made it exist.
If your operations have the same shape — too complex for spreadsheets and Slack, too specific for the off-the-shelf enterprise stack — that's the kind of work we're built for. Sometimes the answer is "use HQ." Sometimes it's "build something custom that fits exactly how you work." Both paths run through the same conversation.
- Custom software vs SaaS — when each one wins
- When SaaS stops scaling — 7 signs
- Visit HQ at aychkyoo.com →