BetaQuesto sito e la piattaforma che c’è dietro sono in beta test.

← Tutti i settori

Project delivery

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

Con che cosa si apre lo spazio di lavoro

projectstimesheetstaffingexpensesclient-portalworkflowsokr

Più il nucleo che ogni spazio di lavoro porta con sé — support, notifications, documents, analytics — perché un tenant senza documenti, senza notifiche e senza analisi non è un prodotto più piccolo: è un prodotto rotto.

Che cosa ti permette di fare dall’inizio alla fine

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. (richiede il modulo recruiting, che questo settore non attiva di 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. (richiede il modulo recruiting, che questo settore non attiva di 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. (richiede il modulo contractor-portal, che questo settore non attiva di 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. (richiede il modulo onboarding, che questo settore non attiva di 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. (richiede il modulo invoicing, che questo settore non attiva di 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. (richiede il modulo invoicing, che questo settore non attiva di 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. (richiede il modulo crm, che questo settore non attiva di 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. (richiede il modulo crm, che questo settore non attiva di 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. (richiede il modulo quotes, che questo settore non attiva di 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.

Guardala con dei dati dentro

Uno spazio configurato per project delivery, popolato e tuo. Per 15 giorni è una sandbox, poi continua sul piano gratuito — lo stesso spazio, con dentro quello che ci hai messo.

Aprine uno