Designed for: Development agencies and studios that already organize client delivery in Linear.
The situation
A client asks for a new invoice export. The request arrives during a call, gets copied into a task, and leads to follow-up messages asking when it will be ready.
A concrete example
A client requests a CSV export of paid invoices, including a date range and the columns their finance team needs.
Illustrative workflow, not a customer case study.
How the workflow fits together
- The client submits the request in their portal with the desired outcome and relevant context.
- The request becomes an issue associated with their Linear Customer and enters your triage.
- Your team reviews the scope, asks for clarification and agrees priority with the client.
- The client checks the portal for progress and replies on the request when they have more information.
What to prepare
Map each pilot client to the correct Linear Customer. Review project and status visibility, visible labels and shared comments, who reviews new requests and how you will agree any additional scope.
What to agree with the client
A submitted request is an intake item. Agree estimates, scope and delivery dates through your normal process before treating it as committed work.
What to check in a pilot
- The request reaches the correct Customer and triage queue.
- The client can find the request and its status.
- Unrelated requests stay out of view, and shared comments are suitable for the client.
Use the first-portal checklist to test the complete flow, or review the Linear connection and permissions.
Related workflow: Track client bug reports.