Map
Define the current workflow, evidence, owner and operating constraint.
OPERATING SINCE2006LETTERBOX COVERAGESYDNEYDIGITAL SERVICEAU + NZCALL TRACKINGFROM $99/MOENQUIRY REVIEWSENIOR TEAMISO 27001PLATFORMOPERATING SINCE2006LETTERBOX COVERAGESYDNEYDIGITAL SERVICEAU + NZCALL TRACKINGFROM $99/MOENQUIRY REVIEWSENIOR TEAMISO 27001PLATFORM
GibsonFamily-Owned Sydney Lead Engine · Since 2006
Internal Gibson operation
Demand Reactivation Engine
A controlled reactivation workflow that starts with an existing dormant database, confirms eligibility and message controls, then records replies and agreed outcomes. It is not a promise that every list is contactable or that every campaign will produce the same result.
Last reviewed 2 August 2026 · By Albert Triolo, Founder and Managing Director
Current public statusControlled Gibson pilot and current service pattern
Evidence boundary
The pilot is a small, prior-relationship cohort. It does not forecast another database, sector, contactability rate or commercial outcome.
What is confirmed
Facts this entry can support.
- 01The published Gibson pilot used 130 existing contacts.
- 02The verified record shows 35 confirmed jobs and $9,415 in total value.
- 03The service is now scoped from data readiness, consent evidence, cohort, message, reply ownership and reporting.
How a similar problem proceeds
Evidence to decision, without assuming AI is the answer.
Compare
Check process, rule, integration and AI options against the same decision.
Bound
Set representative cases, human controls, unacceptable failures and stop conditions.
Decide
Stop, improve, test further or separately scope production from the evidence.
Questions before using this example
Status and fit, answered directly.
What is the current public status of Demand Reactivation Engine?
Controlled Gibson pilot and current service pattern. The pilot is a small, prior-relationship cohort. It does not forecast another database, sector, contactability rate or commercial outcome.
What does Demand Reactivation Engine show?
A controlled reactivation workflow that starts with an existing dormant database, confirms eligibility and message controls, then records replies and agreed outcomes. It is not a promise that every list is contactable or that every campaign will produce the same result.
Can this example predict the outcome of another build?
No. A future workflow has its own evidence, systems, users, risks, human controls, acceptance tests and production decision. This entry supports a capability discussion only within the stated evidence boundary.
What information should go into a workflow brief?
Describe the current process, the constraint, affected users, systems involved, available evidence, unacceptable failures, required human decisions and the outcome that would justify a bounded test.
Related register entries
Next decision
Do not copy the example. Scope the operating problem.
Review the AI Consulting method, then send the current process, evidence and controls if a bounded workflow decision is still useful.