A first engagement with a defined end.
Most firms ask you to commit to a programme before you know whether they can deliver. These three engagements are the other way around. Fixed scope, fixed duration, and an artefact you keep whatever you decide next.
Three ways to start.
Each one answers a question you cannot currently answer. Pick the one that matches the question you are being asked.
Salesforce Health Check
An independent review of an existing Salesforce org across configuration, data, automation, integrations, security and adoption. You receive a written report, a prioritised remediation backlog and a live readout with the people who own the platform.
Agentforce Pilot
One real workflow, built on Salesforce Agentforce in a sandbox and measured against a scored scenario set. The engagement ends in a go or no-go recommendation supported by evidence rather than a demonstration.
AI Workflow Sprint
A short engagement that puts a small number of automations into production on the systems you already run. No Salesforce dependency. The code, the runbook and the accuracy baseline are handed to you at the end.
Choose on the question,
not the technology.
The three engagements overlap very little. In most cases the right one is obvious within a few minutes of conversation.
| Engagement | Choose it when | Duration | What you hold at the end |
|---|---|---|---|
| Salesforce Health Check | You have an established Salesforce org and no current, independent view of its condition or risk. | Two to three weeks | Assessment report, prioritised remediation backlog and a 90 day plan. |
| Agentforce Pilot | You are being asked to justify Agentforce, and you need evidence from your own data rather than a vendor demonstration. | Four to six weeks | A working agent in a sandbox, scored evaluation results and a go or no-go recommendation. |
| AI Workflow Sprint | Manual handling is consuming your team, and the automation ideas have never cleared the backlog. | Three to four weeks | Two to four automations running in production, with a runbook and an accuracy baseline. |
Engagements are quoted individually. We scope and price after the first conversation, not before it.
The same three commitments,
whichever one you take.
Written down before it starts
Every offer has a fixed scope, a fixed duration and a defined deliverable, agreed in writing before work begins.
- Named inclusions and exclusions
- A date the engagement ends
- No open-ended discovery
The engineers who do the work
You are scoped by the people who will deliver. There is no separate presales team and no handover to a junior bench.
- Senior Salesforce and AI engineers
- Direct access throughout
- Melbourne based, dual-region delivery
Something you keep
Each engagement ends with an artefact you own and can act on with us, with another partner, or on your own.
- Documents, code and access handed over
- Findings written to be actioned
- No obligation to continue
From first call to handover.
The sequence is the same for all three. It is short on purpose, because the point of an entry engagement is to find out quickly whether we are the right firm for the larger work.
- 01
Conversation
Thirty to forty five minutes with an engineer. You describe the situation, we say plainly whether one of these offers fits, whether something else does, or whether you do not need us at all.
- 02
Scope in writing
We send the scope, the assumptions, the access we need from you and the dates. Nothing starts until you have read it and agreed to it.
- 03
Delivery
A named engineer runs the engagement with a weekly checkpoint. Findings are shared as they emerge, so nothing in the final readout is a surprise.
- 04
Readout and decision
We present the work to the people who own the outcome, hand over everything produced, and set out the options. Continuing with us is one of them, not the default.
Not sure which one applies?
Describe the situation in a couple of sentences. We will tell you which engagement fits, or that none of them do.