Delivery that will start from the customer.
Engagements is being built. It will pick up when the deal closes and run the work in front of the client: phases, deliverables, change orders and margin. Because it starts from the same customer record as Portfolio, how an onboarding went will show up in that account’s health score rather than sitting in a separate delivery tool.
It will hold the whole engagement, and what it costs.
Scope moves and dates slip. Someone has to say so before the invoice does. The design brief for Engagements is to keep the money side of a project next to the plan for it.
Phases, milestones, deliverables and tasks with real dependencies, plus risks and issues the client can see.
A configurable estimation model with versioned estimates, so a scope change will produce a change order instead of an argument.
Who is on it, what they have capacity for, where the hours went, and what the margin is doing while the work is still in flight rather than after it.
Status reports the client does not have to ask for. A shared client portal is planned as a platform capability, serving both products rather than just this one.
Where it meets Portfolio.
A completed engagement will tell you two things at once: how the customer feels about the work, and who should be credited for it. Both flows below need Engagements to ship. The question engine behind the first is already live; the incentive engine behind the second is on the roadmap.
One trigger, two engines, two products touched, and no integration to maintain. This is what shipping Engagements onto the same record buys.
What Engagements is scoped to do.
The plan, the people, the money, and what the client can see. None of it is shipping yet.
Your team will lay the work out as phases, milestones, tasks and deliverables, with the dependencies between them and an acceptance state on each deliverable.
You will configure the estimating model and every estimate will be versioned, so a scope change produces a change order. Risks and issues will be visible to the client.
Who is on the work, their capacity, the hours, and the margin while the project runs.
Status reports the client will not have to ask for, a project survey that moves the health score, and delivery credit through the incentive engine, which is also on the roadmap.
Tell us what your delivery has to handle.
The onboarding that slipped twice and grew a scope change nobody logged. We cannot demo Engagements yet, but describing that job now is how it gets built right. Forty-five minutes.
Tell us which product you are here for and the session is set up around it before we meet.
Request a demo