Projects
Project delivery for MSPs and IT teams — scope, schedule, people, risk and billing on one record, from the signed Statement of Work to the final invoice.
How Solidlio helps
The quote becomes the project. The Statement of Work is drafted, sent and e-signed inside that project, and the signature is stamped into the PDF. Tasks, milestones, team allocations, risks and documents live on the same record, and billing milestones are attached to the delivery milestones they depend on — so approving a checkpoint and raising its invoice are two clicks in the same place, against the right account, in the right currency, with tax from the client’s own jurisdiction. Status reports are generated from the project’s live numbers and emailed to the client with one action.
Product manuals and all delivery playbooks are also published in the Knowledge Base for Sol retrieval.
Capabilities
| Capability | What it does |
|---|---|
| Quote-to-project | Turns an accepted quote into a project with its budget and client already set |
| Statement of Work | Draft, send, e-sign and version a SOW; the signed PDF embeds the signature block |
| Task board | Kanban and list views, subtasks, blocked-by dependencies, assignees and estimates |
| Milestone timeline | Delivery checkpoints with target dates, completion and reopening |
| Capacity planning | Allocate a share of someone’s week; the platform refuses commitments past 100% |
| Risk register | Risks scored likelihood × impact, with mitigation and contingency plans |
| Milestone billing | Approve a checkpoint and raise its invoice, tax-correct for the client’s jurisdiction |
| T&M invoicing | Sweep every uninvoiced time entry onto one invoice at a rate you set |
| Status reports | Generated from live project metrics, reviewed, then emailed to the client |
| Project templates | Reusable skeletons that create a project’s tasks, milestones and risks in one step |
| Document library | Per-project files, internal by default, shared to the client portal when you choose |
| AI assistance | Drafts SOWs and plans; Auto mode can materialize a validated plan and prepare unsent reports |
| Guided delivery | Ordered playbooks, evidence requirements, readiness and closure gates |
| Technical execution | Reviewed runbooks, bounded authorization, verification, rollback and recovery |
| RFP/RFI handoff | Resumable conversion from an awarded proposal into a scoped project |
Built for MSPs and their clients
An MSP runs projects for the clients it services. The client organization keeps control of what its provider can see.
| Organization | MSP | |
|---|---|---|
| Own projects | Creates and runs its own, invisible to the MSP if it chooses | Cannot see a project the client has hidden |
| MSP-run projects | Sees the project, its documents marked shared, and its reports | Creates, staffs, schedules and bills it |
| Statement of Work | Signs it — only the owning organization can accept or decline | Prepares, sends and versions it; cannot sign on the client’s behalf |
| Visibility | Sets Hidden, Summary Only or Full Access per project | Gets exactly that much, on every tab and every rollup |
| Entitlement | Independent orgs use their own plan | A managed client with no plan of its own inherits the MSP’s |
Visibility is enforced on every route, not just the list — including statistics, so an MSP’s portfolio numbers never include a project it is not allowed to see.
How it works
- The quote is accepted. Press Create project — title, description, client and total carry over, and the project opens in SOW drafting.
- Scope is written. Draft the Statement of Work by hand or generate a first pass with AI, then edit scope, objectives, deliverables, assumptions and commercial terms.
- The client signs. They open the SOW in their portal, type their name and signature, and accept. The acceptance name, timestamp and IP are recorded and the PDF is re-rendered with the signature block embedded.
- The project kicks off. Status becomes in progress, health resets to green, and the start date is stamped.
- Delivery runs. Tasks, milestones, risks, documents and team allocations are managed on the project. Logged time accumulates against it.
- The client is kept informed. A status report is generated from the project’s current task, milestone and time figures, reviewed, and sent.
- Money follows delivery. A billing milestone is approved and invoiced, or uninvoiced time is swept onto a single invoice. Closing the project records a summary in its activity trail.
Compliance and audit
- Signed scope is immutable. An accepted Statement of Work cannot be edited or revised — the platform refuses both, because revising in place would destroy the acceptance record. Changes to signed scope go through a change request.
- Acceptance is evidenced. Acceptor name, typed signature, timestamp, IP and the person’s account identity are stored on the SOW, and the generated PDF carries the signature block.
- Billing is one-way. A billing milestone cannot be edited or deleted once invoiced or paid.
- System actions are attributed. Automation posts to the project’s activity feed under a dedicated system identity, distinct from human comments, and repeats of the same finding on the same day are suppressed.
- Tenant isolation is enforced per route. Organization and customer callers are pinned to their own organization inside the service — not merely to the account — so one client’s project is never visible to another under the same MSP.
Integrations
- Quotes and invoicing — projects are created from accepted quotes, and project invoices are raised into the same billing ledger as the rest of the account, in the account’s currency with Canadian GST/PST/HST applied from the client organization’s province.
- Time tracking — time logged against a project feeds its rollups and is what T&M invoicing bills.
- Email and notifications — status reports are emailed to the client under the tenant’s own sender identity and branding, and project members are notified in-app.
- Change management — scope changes to signed work are raised as change requests against the project.
- Calendar — project tasks and milestones carry calendar events.
Plans and access
Availability depends on your plan, role and account permissions. Capacity limits and service terms apply. Compare current plans and integration requirements, or ask us about your setup.
Delivery work belongs on the same record as the money it earns.