Project · Services
Every job as a board, a timeline and a budget.
See the work the way you think about it.
Board
Tasks by stage. Drag one to Review and its owner knows.
See the work the way you think about it.
Tasks by stage. Drag one to Review and its owner knows.
This is the room.
One project, opened: its board, its budget, its client and its next milestone, with the hours and the visits that have already been logged against it reading in from the apps beside it.
The things a project needs, none of them bolted on.
And it takes the shape of your business: your fields, your stages, your documents.
Milestones
A date the client is promised, tied to the tasks that deliver it, and to the invoice that can only go out once it is hit.
Budget and cost
The budget from the quote, the cost from the hours and the parts, the margin that follows both without a spreadsheet.
Subtasks and dependencies
Break a task down, or make one wait for another, and the timeline knows.
Documents on the record
The plan, the site photos, the signed worksheet, on the project, not in a drive folder named after it.
Templates
A refit, a maintenance contract, a website build: each starts from the tasks and the milestones the last one taught you.
Recurring tasks
The monthly check, the quarterly review, created on schedule and assigned to whoever holds the contract that month.
Your project, shaped for you. And for someone nothing like you.
A project is an object you own, not a template you fill. Its fields, its stages, its milestones and the document it produces at the end are yours to set, and two businesses that both say "project" mean two different things.
An installer
A project is a site with phases. It carries the site address and access code, the phases (survey, delivery, fit-out, sign-off) as stages, the client's sign-off as a milestone that gates the final invoice, and the site photos as documents.
A consultancy
A project is an engagement with workstreams. It carries the statement of work, the workstreams as stages with a lead each, the retainer hours against hours logged, and the monthly steering report as the document it produces.
What comes in, and what goes out.
A project is created when a quote is accepted, and it carries the quote's scope and budget with it. From then on it collects: the people Planning places on it, the hours Timesheets logs against it, the interventions Field Service completes for it, the tickets Helpdesk opens on it. And it produces the one thing the client is waiting for: an invoice whose lines are those hours and those visits, without a re-key.
Your project, your fields.
A refit needs a site address and a client sign-off flag. A maintenance contract needs a renewal date and an SLA. A website build needs a launch date and a staging URL. The project object is yours: add the field, make it calculate, make it required, and every view, every filter and every report picks it up.
What a project connects
Each one reads the same record. Start with the one you are missing.
The project tool you would otherwise buy is the wrong shape.
It is good at tasks. It has never heard of your quote, your hours, your van or your invoice.
Tasks, board, timeline
- A spreadsheet
- Some
- A project tool
- Yes
- A suite module
- Yes
- Enobase
- Yes, and every other view
The quote it came from
- A spreadsheet
- No
- A project tool
- No
- A suite module
- Sometimes, via a connector
- Enobase
- Yes, it created the project
Hours logged on the task
- A spreadsheet
- No
- A project tool
- On a higher plan, or an add-on
- A suite module
- Yes
- Enobase
- Yes, natively
The invoice reads from it
- A spreadsheet
- No
- A project tool
- Exported to your accountant's tool
- A suite module
- Yes, in their format
- Enobase
- Yes, in yours, over Peppol
The client sees their slice
- A spreadsheet
- A shared file
- A project tool
- A guest seat
- A suite module
- Rarely
- Enobase
- Yes, field by field
Your own fields on the project
- A spreadsheet
- Yes, uncontrolled
- A project tool
- Custom fields, limited
- A suite module
- With a developer
- Enobase
- Yes, calculated ones too
Time to live
- A spreadsheet
- A day
- A project tool
- A week
- A suite module
- Months
- Enobase
- One to two weeks
| What you need | A spreadsheet | A project tool | A suite module | Enobase |
|---|---|---|---|---|
| Tasks, board, timeline | Some | Yes | Yes | Yes, and every other view |
| The quote it came from | No | No | Sometimes, via a connector | Yes, it created the project |
| Hours logged on the task | No | On a higher plan, or an add-on | Yes | Yes, natively |
| The invoice reads from it | No | Exported to your accountant's tool | Yes, in their format | Yes, in yours, over Peppol |
| The client sees their slice | A shared file | A guest seat | Rarely | Yes, field by field |
| Your own fields on the project | Yes, uncontrolled | Custom fields, limited | With a developer | Yes, calculated ones too |
| Time to live | A day | A week | Months | One to two weeks |
Questions about Project
Yes. It is a complete project tool on its own: board, timeline, calendar, list, milestones, documents, templates. The connections to Quotes, Timesheets and Invoicing are there when you turn those apps on, not before.