ferent.aiEngagements
Coming soon This page describes a product we are building, not one you can buy today. Portfolio and the platform ship now.
Services delivery · in development

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.

Tell us what it has to handle See the shared platform
The record it is being built on
Engagement the customer commitment
Phase a stage of it
Milestone a date that matters
Deliverable the thing handed over
Task the work under it
Alongside it, the commercial spine
Estimate versioned, so scope change is visible
Change order what moved, and who agreed
Time entry where the hours went
Margin what is left
No screenshots on this page. Engagements is not running yet, and every capture on this site is a real one.

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.

Plan the work

Phases, milestones, deliverables and tasks with real dependencies, plus risks and issues the client can see.

Estimate and re-estimate

A configurable estimation model with versioned estimates, so a scope change will produce a change order instead of an argument.

Deliver the work

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.

Report to the client

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 engines they run on are already live.

Engagement completes Project CSAT fires Health moves in Portfolio
Engagement completes Source event Delivery bonus is calculated

One trigger, two engines, two products touched, and no integration to maintain. This is what shipping Engagements onto the same record buys.

Capabilities

What Engagements is scoped to do.

The plan, the people, the money, and what the client can see. Fifteen capabilities, none of them shipping yet.

Plan
Projects and phases
Structure that survives a replan
Milestones
Dated, owned and reported against
Tasks and dependencies
Real sequencing, with dependencies
Deliverables
What was promised, and its acceptance state
Scope
Estimation model
Configurable to your own estimating method
Estimate versions
What you quoted, and what changed since
Change orders
Scope movement recorded as commercial fact
Risks and issues
Raised in the project, visible to the client
Staff
Resource assignments
Who is committed, and until when
Capacity
The forward view before you sell the next one
Time entries
Captured against the work they belong to
Margin and cost
Project economics as the project runs
Show
Status reports
Sent without anyone assembling them
Project CSAT
Fires on completion, feeds the health score
Delivery incentives
The same engine that calculates CS bonuses today

Sixty-five endpoints in a single deep module · the closest comparison is Rocketlane, reached from the customer record

Request a demo

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.

One form for every product

Tell us which product you are here for and the session is set up around it before we meet.

Request a demo