← All verticals

Project delivery

Running the work: projects, tasks, allocation and client visibility.

What the workspace opens with

projectstimesheetstaffingexpensesclient-portalworkflowsokr

Plus the core every workspace carries — support, notifications, documents, analytics — because a tenant with no documents, no notifications and no analytics is not a smaller product, it is a broken one.

What that lets you do end to end

From a gap on a project to somebody working on it

  1. A project reports a gap — A staffing request names the role, the skills and the dates. Until somebody is allocated it sits in the capacity view as an unmet need, not as a note in a spreadsheet.
  2. The gap becomes an opening — The opening remembers the request it came from, so the pipeline is answerable to the project that asked. Candidates carry their consent date and a retention deadline from the moment they are created. (needs the recruiting module, which this vertical does not enable by default)
  3. Interviews, kept separate — Each interviewer files their own evaluation. A split panel is shown as a split panel rather than averaged into a number that hides the disagreement. (needs the recruiting module, which this vertical does not enable by default)
  4. The hire becomes a person on the payroll — Marking a candidate hired writes the consultant record. The database refuses the state otherwise: an application cannot claim a hire that produced nobody. (needs the contractor-portal module, which this vertical does not enable by default)
  5. And an onboarding that already exists — The same action instantiates a checklist from a template, one row per item, with due dates counted from the start date rather than from today. (needs the onboarding module, which this vertical does not enable by default)
  6. Then the hours start arriving — The new consultant files time against the project that raised the request. The loop closes where it opened.

From work done to money received

  1. Hours are approved, not just entered — An entry passes an internal approval, and — where the contract says so — a client approval through a tokenised link that needs no account.
  2. The project knows what it has burned — Budget burn is computed from the approved hours, and crossing 80% or 100% raises a digest rather than being noticed at the end of the quarter.
  3. The invoice is generated from those hours — Line items come from the approved entries. Nothing is retyped, so nothing can disagree. (needs the invoicing module, which this vertical does not enable by default)
  4. And transmitted where the law requires it — Italian e-invoicing goes to the SDI with its receipts tracked as states, not as an email somebody remembers sending. (needs the invoicing module, which this vertical does not enable by default)

From a stranger on the website to a signed quote

  1. The enquiry becomes a lead — A web form writes a lead directly into the pipeline, carrying what the visitor said and where they came from — not an inbox nobody works from. (needs the crm module, which this vertical does not enable by default)
  2. The lead becomes an opportunity — Stages are configured per tenant, and the forecast weights each deal by the probability of the stage it is in and its close date. (needs the crm module, which this vertical does not enable by default)
  3. The opportunity becomes a quote — Line items priced from a price book, an approval when the margin drops below the threshold, and a share link the client can open without an account. (needs the quotes module, which this vertical does not enable by default)
  4. And a won quote becomes a project — With the tasks, milestones and budget the quote implied — which is the moment the first journey on this page can start again.

See it with data in it

A demo workspace set up for project delivery, seeded and yours for 14 days.

Start one