When a client buys a block of hours, both sides need to know how many are used and how many are left. Project settings decide which figure the client sees.
Once the client has accepted the quote or paid the invoice, one button in X7 creates a project: the lines become tasks and the document stays attached to the project. How it works on an invoice and a quote, and what carries over.
Intake templates define which project and which status a task gets when an order arrives from the web shop, or a request comes from web chat or a form. Source type, project, default status and field mapping in JSON — step by step.
An inbox request — an email, a web chat message, a submitted form or an order — becomes a project task from a single window: title, description, project, status and assignees.
What to settle before you close a project — hours, the invoice, client access — and how archiving differs from deleting. An archived project leaves the list while its tasks, comments and history stay.
Five views show the same tasks differently. Which view suits which kind of work: the daily board, the list for an overview, the table for bulk edits, the calendar for deadlines and the Gantt for stages.
Why a rate is not a salary divided by 160: counting billable hours, overheads and the profit you want. With a worked example and a reality check inside X7.
A working rhythm for a small team: a short Monday review, boards during the week, a Friday pass over hours and invoices. What to look at in X7 at each step.