Engagement Configurator
Scope the engagement
you actually need.
Define the customer experience design and innovation engagement you want f/cx.ai to deliver — the objectives, the KPIs it will be measured on, the deliverables you want produced, how and where it runs, and when. Eight steps, roughly ten minutes, and you leave with a written engagement scope brief whether or not you send it to us.
Who you are, and what is actually going wrong
Who you are and what is actually going wrong. Nothing is filled in for you and nothing is assumed — the shape of the engagement comes out of the solutions you pick next and the commercial model each one carries, and it is confirmed with you at scoping.
To continue, this step needs your organization, name and work email, and a description of the customer experience challenge.
Who we would be working with
So the validated scope goes back to the right person.
This field is required.
This field is required.
This field is required.
This field is required.
This field is required.
This field is required.
This field is required.
This field is required.
The situation
Two short answers here shape everything that follows.
This field is required.
This field is required.
This field is required.
Which of the twenty-two solutions belong in this engagement
The full suite, grouped by area. Pick the solutions you want in scope — each one carries four named artifacts that travel through to the deliverables step and the brief. Most engagements are two to five. Nothing is pre-selected — each one has its own duration, commercial model, cadence and room, and the engagement is shaped around what you pick.
To continue, this step needs at least one solution in scope — from any of the three areas.
Pick only what you actually want scoped now. Anything you leave out stays available later, and the sequence the work compounds in is on the Solutions page.
01 · CX Strategy
0Everything downstream is cheaper when this is settled first.
02 · Design Studio
0A working studio, not a deck factory. Everything leaves tested and build-ready.
03 · Innovation Lab
0Every cycle ends in a decision: scale, iterate, or stop.
This field is required.
What this engagement has to achieve
Choose the objectives this engagement is accountable for, across customer experience design and innovation. Pick as many as genuinely apply, then add your own if something is missing. Three to six is usually the honest number.
To continue, this step needs at least one objective — selected from the lists, or one of your own.
Customer experience design objectives
0Innovation objectives
0Your own objectives
Anything the lists above do not cover.
This field is required.
The KPIs this engagement will be judged on
These are the measures we hold ourselves to — customer experience and innovation KPIs redefined around decisions rather than scores. Select the ones that matter, add a baseline and target where you know them, and define your own if a measure you use is not listed.
To continue, this step needs at least one success measure — selected, or a custom KPI.
If you do not know a baseline yet, leave it blank. Establishing honest baselines is itself part of the first phase of most engagements — and a metric with no agreed baseline is one nobody can be held to later.
Custom measures
A KPI your organization uses that is not on the list.
This field is required.
What you want produced
Every deliverable below is something f/cx.ai produces as working material, not a slideware artifact. Select the ones you want in scope, and define any additional deliverable you need.
To continue, this step needs at least one deliverable — selected, or one you define.
Carried by the solutions you selected
Every solution in scope brings its four named artifacts. These travel into the brief automatically — add anything else you want below.
Customer experience design deliverables
0Innovation deliverables
0Deliverables you want that are not listed
Describe it and we will scope it, or tell you honestly if it belongs somewhere else.
This field is required.
This field is required.
How the engagement runs, and what it depends on
The practical shape of delivery: onsite or remote, method and cadence, the dependencies that have to be true for the work to move, and the risks worth naming now rather than discovering in week four.
To continue, this step needs a delivery mode and at least one preferred method of delivery.
Where the work happens
This field is required.
This field is required.
Preferred method of delivery
0Select every method you want in the mix.
This field is required.
This field is required.
This field is required.
Dependencies
0What has to be true, or in place, for the work to move.
Risks
0Name them now. They are cheaper to design around than to discover.
Commercial and compliance constraints
This field is required.
When you would like to start, and what is driving that
A target start and the pressure behind it. We do not put a duration against an engagement before it is scoped — how long the work runs is set by scope and complexity, and confirmed with you at scoping rather than guessed at from a form.
To continue, this step needs a start date or approximate timing.
When would this start?
This field is required.
This field is required.
How long an engagement runs is set by scope and complexity, and we would rather agree it with you at scoping than guess it from a form. Tell us about phasing below if it matters.
This field is required.
What is driving the timing?
This field is required.
This field is required.
This field is required.
This field is required.
What you configure here is an input, not an agreement. f/cx.ai validates the scope against the objectives, measures and deliverables you have selected — and will tell you plainly if the duration and the ambition do not match. Nothing is priced, proposed or committed until that validation conversation has happened.
Anything else we should know before we scope this
Requests, constraints, concerns, prior attempts, internal politics, things that have already been tried and failed. The more context here, the more accurate the validated scope.
Nothing required here. Add whatever context helps — then continue.
This field is required.
This field is required.
This field is required.
This field is required.
How should we come back to you?
This field is required.
This field is required.
Your configuration is held in your own browser until you submit. Submitting opens your email client with the brief addressed to innovate@fractionalcx.ai — nothing is transmitted before you press send in your own mail application. A copy downloads to your machine at the same time.
Check the configuration, then send it to us
This is the complete engagement configuration. Review it, edit anything that needs changing, then submit — it opens your email client with the brief addressed to us, and downloads a copy for your own records.
Nothing required here. Add whatever context helps — then continue.
This configuration is a scoping input. f/cx.ai validates it before any proposal is confirmed — objectives against deliverables, deliverables against duration, and every KPI against whether it can actually be measured. Pricing is prepared only after the configuration is submitted and the scope has been validated with you. Nothing here creates an obligation on either side.
Your engagement configuration is ready to send
Your email client should have opened with the full scope brief addressed to innovate@fractionalcx.ai — check it over and hit send. A copy of the brief has also downloaded to your machine.
If your email client did not open, use the buttons below to download or copy the brief and send it however suits you.
We read every configuration personally and come back to confirm we have understood the scope, or to ask the questions that matter.
A working conversation to test the objectives against the deliverables, and the deliverables against the duration. We will push back where it is warranted.
Only after validation. A confirmed scope, a shape of engagement, and a price against it — never a number attached to an unvalidated brief.