Projects

Projects are where delivery happens. Break work into milestones and tasks, tie deliverables to sign-off and payment, track issues and feedback, and keep budget and timeline visible to everyone — including your client.

• Milestone projects — tie deliverables to sign-off; clients approve and payment can flow.
• Task management — subtasks, dependencies, estimates, and time tracking in one place.
• Rich document editor — proposals, SOWs, and contracts, versioned and signed in-platform.
• Real-time collaboration — comments, mentions, and live updates so everyone sees the same version.
• Project intelligence — AI flags scope creep and surfaces blocked tasks.
• Client view — a clean, read-only project view for clients, no extra license needed.

A project's work is organized as a tree of milestones and tasks. Milestones are the major phases or deliverable checkpoints; tasks are the granular work beneath them. Each milestone shows live task counts and completion so progress is always accurate — not a stale number someone forgot to update.

A milestone's progress counts its deliverables (approved or paid counts as done), falling back to its tasks when it has none, and a completed milestone is never shown as overdue. Assign work to team members, set due dates, and change status inline from the milestone tree. See Tasks & Mission Control for the day-to-day workflow.

A project opens on Milestones & Deliverables; Notes is the second tab, a running thread where you can @mention people — they are notified and land on the note.

Every project has an Issues tab for tracking bugs and problems, and a Feedback tab for client and stakeholder input. Both support priorities, status workflows, file attachments, and comments.

The project detail view keeps budget, timeline, team, and attachments always visible alongside the work. You can reserve a share of the budget and time for issues and feedback so unplanned work does not silently eat your margin.

For owners and managers the budget card shows the total budget, the company's cost, what is available for development, how much is already assigned to deliverables (and of that, how much is paid), and what is left to assign. Every deliverable's payout counts against the budget from the moment it is assigned, not only once it is paid.

When you win a deal in the CRM, Create Project from Deal starts delivery with the budget worked out for you:

• Project budget = deal value − Profit (20% by default, or a flat amount) − Company Cost (30% by default; tools and licensing) − Infra & Third-party Costs.
• The Budget Breakdown shows the result before you create it, and creation is refused if the deductions exceed the deal value.
• A deal has one project; the link keeps revenue, scope and the client relationship together in your reports.

Suggested budgets then help managers split the money: each milestone gets a share in proportion to its price on the deal (an advance payment gets none) and shows what is left or over; within a milestone, deliverables are suggested amounts by their estimated hours. A payout more than 5% above its suggestion is flagged. Suggestions are advice — the budget cap is what is enforced.

A deliverable's payout is worked out for you — the assignee's hourly rate × the delivery hours — plus an optional on-time bonus. Salaried staff are not paid per deliverable: their deliverables show Salaried — no per-deliverable pay, and delivering on time adds to their efficiency instead.

Approving a deliverable pays it into the assignee's earnings wallet when they have one. When they don't — or you paid them some other way — Mark as paid on the approved deliverable records it, with an optional note such as a bank reference. The owner, the person who assigned it, or a project manager can do this.

In Mission Control → Deliverables, switch between Assigned to me, Assigned to others and Everyone; the choice is remembered in your browser.