About SAQ
SAQ is inspired by "sak", the Norwegian word for a ticket, and is read the same way: [saːk], with a long a. The idea behind SAQ is to gather project work, support, time tracking, and billing around the ticket.
How is SAQ put together?
Do not run a helpdesk, a project tool, and a timesheet and glue them together. Run one connected system. A ticket is the unit of work. A project is where a team and its clients collaborate. A client is who the work is for and who is billed. A time entry is a line of work on a ticket. Email, boards with tickets in columns by state, the filterable ticket list, search, and the API are different doors onto the same ticket page.
Which features are included?
-
Ticket management
Support requests, bugs, and project tasks in one system, each with a workflow, priorities, labels, links, and attachments.
-
Project management and boards
Projects, boards, parent tickets as epics and milestones, dependencies, and a My work page. Nothing you have to configure for weeks.
-
Client collaboration
Clients follow their own tickets by magic link at no cost. Every comment is written for a role: shared with the client, internal to the project, or staff only.
-
Time tracking and timesheets
Log time on the ticket you are working on. A weekly grid, reports, and periods that close permanently, so the basis for an invoice can be verified long after it was sent.
-
Billing, rate cards, and time banks
Rate cards per client, paid, free, or retainer-covered work per ticket kind, and a client timesheet as PDF, HTML, and CSV.
-
Email inbox
Connect your Microsoft 365 or IMAP mailbox. Incoming mail becomes a ticket, and every reply from either side lands in that same conversation.
-
API and AI agents
A REST API and an MCP endpoint with the same permissions as the app, so Claude Code, Cursor, or your own scripts can work in SAQ.
What else is in every workspace?
- Full-text search across the tickets and comments you may read
- A command palette and keyboard shortcuts
- Email notifications you can set to everything, mentions and assignments only, or off
- Configurable workflow states, ticket kinds, priorities, and labels
- Attachments on tickets and comments, scanned before they are served
- Reports by person, project, ticket, client, category, and billing outcome
- A ticket id prefix of your choosing, like ACME-184, that stays stable in email subjects and commit messages
- Manual GitHub links from a ticket to a commit or pull request
- Norwegian and English, chosen per person, per client, and per workspace
- Light and dark themes, following the device by default
- WCAG 2.2 AA accessibility, checked automatically in every release
- Workspace export as a complete package, and self-service deletion
FAQ
Common questions about SAQ
Is SAQ a helpdesk or a project management tool?
Both, deliberately. A support request and a project task are the same ticket type with a different kind. That is what lets a support ticket become project work without being re-created somewhere else, and lets time logged on either be billed the same way.
Do I need to configure a lot before starting?
No. A new workspace ships with a workflow (backlog, to do, in progress, review, done), kinds (planning, implementation, bug, support), priorities, and consultant categories. You rename or add to them under Settings. Rate cards and time banks are only needed when you want billing.
Which features are not in SAQ?
Invoices, VAT documents, and accounting integrations (SAQ produces the timesheet, your accounting system invoices it). SLAs and service-level timers. Gantt charts and resource planning. A CRM. GitHub automation beyond manual links. Invoicing, accounting, and CRM are deliberately left to the systems you already use. The rest are not there yet, though they may come later.
See whether SAQ fits your team
Workspaces are set up by us, not by a signup form. Tell us how your team works and we set one up, with a 30-day trial. Already invited? Log in.