The modules are joined up. That is the product.

Most platforms for consulting firms are a folder of tools that happen to share a login. This one keeps the arrows: a staffing gap becomes an opening, a hire writes a consultant and an onboarding, those hours reach an invoice. Configure it below, walk the paths, and send a real lead through it before you give us an address.

Start a workspace Try it first

Set up for what you do

A workspace opens with the modules its work needs, not with the whole catalogue. This is not a mock-up of that choice — it is the same catalog the provisioning reads, so what you pick here is what gets built.

Every module the platform has, which is the right choice for looking around and the wrong one for working in.

The workspace opens with 0 modules

The outlined ones are the core every workspace carries — documents, notifications, analytics, support. A tenant without them is not a smaller product, it is a broken one.

What that lets you finish

From a gap on a project to somebody working on it — stops short: needs staffing, recruiting, contractor-portal, onboarding, timesheet.
From work done to money received — stops short: needs timesheet, projects, invoicing.
From a stranger on the website to a signed quote — stops short: needs crm, quotes, projects.

Nothing here is locked. A module left out of a vertical is one you have not asked for yet, not one you have to change plan to get.

Start a workspace

Each one has a page of its own: Consulting firm, Sales organisation, Project delivery, Compliance and governance, People operations, Reporting and insight.

How the work moves

Every step below is a record in the demo workspace, and every arrow between them is a foreign key rather than a convention somebody remembers to follow.

From a gap on a project to somebody working on it

We need a person. What does the platform actually do about it?

1. staffing
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. recruiting
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.
3. recruiting
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.
4. contractor-portal
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.
5. onboarding
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.
6. timesheet
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

How do hours turn into an invoice without somebody retyping them?

1. timesheet
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. projects
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. invoicing
The invoice is generated from those hours
Line items come from the approved entries. Nothing is retyped, so nothing can disagree.
4. invoicing
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.

From a stranger on the website to a signed quote

What happens to an enquiry after somebody submits the form?

1. crm
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.
2. crm
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.
3. quotes
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.
4. projects
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.

Send one through, right now

Lead capture is the one journey that starts outside the product — a stranger filling a form on your website. So it is the one you can run yourself, without an account. This form posts to the same public endpoint a customer embeds on their own site, and the lead lands in a CRM with its source and status already set.

Read this before you type.

What you send goes into a shared demo workspace that anyone reading this page can also write to. Treat it as public.
So please do not enter real personal data — a made-up name and an address you do not mind publishing demonstrate it exactly as well.
The demo workspace is reseeded periodically, and what you submit is deleted with it.
Nothing is emailed to anybody. Demo workspaces cannot send email, SMS or e-invoices at all, which is enforced on the server rather than left to the interface.

Start a demo workspace

Yours this time, not the shared sandbox: your own tenant, seeded with a believable dataset, for 14 days — with a lead form of its own, its own token, and the embed snippet to put it on your site. It cannot send email, SMS or e-invoices, and the REST API is switched off in it: a demo should be able to show you everything without being able to reach anyone.