MapleJockey: demo and next pilot
17 November 2026 | Private working materials
Five-minute demo
0:00–0:45: Find the job. Open MapleJockey_Canadian_Tools_and_Migration.html. Search for a familiar source tool such as HubSpot, Mailchimp or Dropbox, then filter by sector. Explain that these are evaluation candidates, not a market-share ranking or complete inventory.
0:45–1:45: Read the Canadian connection. Open one entry. Compare Canadian connection, ownership and jurisdiction, residency, support and administrator access, key control and portability. Open a dated source. Explain that supplier declarations are not live observations. Show an Unknown and the evidence needed to resolve it.
1:45–3:15: Follow a migration guide. Open the relevant guide. Identify the exact objects in scope, the features left behind, preflight conditions, validation checks and rollback. The guides are desk-reviewed; no source or target vendor account has been migrated during this increment.
3:15–4:15: Substantiate the decision. Open the companion MapleJockey_Assessment.html from the package. Review the existing internal case and its three evidence-linked findings. A catalogue entry supplies questions and public evidence. The customer assessment still needs the exact tenant, contract, source, date and scope.
4:15–5:00: Show the proof boundary. Export a directory JSON or readable report. Review the packaged test report. The earlier restoration of the Internal reporting application is a separate bounded exercise. It is not proof that any of these vendor migrations has succeeded. End on one scoped migration rehearsal, with no production cutover yet implied.
Interview additions for migration demand
Use these alongside the existing pilot interview guide. Record answers without contacting anyone as part of this build.
- Which specific tools and plans support this workload today? Which integrations would break if one were removed?
- What is the trigger: procurement, control of sensitive information, contract renewal, cost, recovery or dissatisfaction? What is the decision date?
- Which Canadian connection actually matters to the buyer: ownership, contracting entity, locations, access restrictions, skills, support, economic benefit or something else?
- What must transfer: records, relationships, messages, files, versions, permissions, consent history, automations, reports, audit events or secrets?
- Which functions would make a Canadian candidate unacceptable even if residency were better?
- Who owns source administration, data classification, contract interpretation, destination approval and rollback?
- Which evidence is available now? Which claims depend on a supplier response, paid plan or confidential contract?
- Can the first rehearsal use synthetic or explicitly approved non-sensitive records? Define a bounded sample and a meaningful user task.
- What count, hash, permission, functional and recovery results are required for acceptance? Who signs off?
- What work would the buyer pay for: a decision pack, a rehearsal, an assisted cutover or recurring change checks? Record a real budget and procurement route rather than treating interest as willingness to pay.
First pilot selection
Prefer a contact-only CRM rehearsal or a non-sensitive file subset. The selected route must have accessible source export and destination import functions, a reversible test space, a named owner and no new spend without approval. Avoid making a credential migration or controlled defence document set the first real-data experiment.
The pilot gate requires:
- Exact source/target products, plans, accounts and regions.
- Data classification and explicit authority for the scoped access and transfer.
- A field or file manifest and a written list of deliberately excluded objects.
- A protected original export and a rollback owner.
- Quantified completeness checks plus user-level functional and permission checks.
- Agreed elapsed-time target, acceptable losses and stop conditions.
- A dated result distinguishing passed, failed, excluded and untested checks.
What must be decided later
The contracting/IP entity remains open for external work. Public publication, external recruitment, purchases and production changes remain separate decisions. Existing price and budget figures are hypotheses, not approved expenditure. None of those decisions is required to inspect this private prototype or refine the research catalogue.