MOXIE STUDIO / EVALUATION 01
Primary Channel
Handoff Fixtures
Twelve synthetic observations for missing contacts, conflicting sources and preservation. For implementers who need a clear, repeatable handoff test, not another attribution claim.
Free evaluation sample. Not live-CRM validation.
Expected results apply only to the declared example policy. AI-assisted original fixtures; no customer data, vendor affiliation or measured time-savings claim.
One declared policy. Twelve edge cases.
Freeze channel at creation. Preserve populated opportunity source. Otherwise use a single distinct creation-contact source; use Unknown for no usable source and needs_decision for conflict. Blank original source stays blank.
| ID | Observation | Channel / association | Why this result |
|---|
| S01 | Paid inbound | Paid
associated | Creation contact supplies Paid. |
|---|
| S02 | Event inbound | Event
associated | Creation contact supplies Event. |
|---|
| S03 | Manual outbound | Outbound
missing | Explicit opportunity source wins even without a contact. |
|---|
| S04 | Import without contact | Unknown
missing | No source at creation; Unknown is explicit, not blank. |
|---|
| S05 | Contact without source | Unknown
associated | Associated does not imply a usable source. |
|---|
| S06 | Preserve populated source | Referral
associated | Existing opportunity source wins; preserve Referral. |
|---|
| S07 | Opportunity/contact conflict | Paid
associated | Explicit Paid wins over contact Event. |
|---|
| S08 | Conflicting contacts | needs_decision
multiple | Conflicting creation contacts require a policy decision. |
|---|
| S09 | Late association | Unknown
late | No contact at creation. Late Paid must not backfill frozen channel. |
|---|
| S10 | Re-enrollment | Event
associated | Second enrollment preserves original Event and frozen Event channel. |
|---|
| S11 | Source changed after handoff | Event
associated | Contact changed Event to Paid after handoff; frozen channel remains Event. |
|---|
| S12 | Duplicate import replay | Paid
associated | Replay same opportunity key; retain one output row and Paid source. |
|---|
Before using the comparison
- Agree the creation boundary and source precedence. If policy is unresolved, record a decision instead of guessing.
- Map four unique observed headers in rule-map.json. Version any changed policy and expectations together; JSON descriptions do not execute rules.
- Stage lifecycle cases using synthetic inputs only. These CSV files are specifications, not vendor import templates.
- Run the passing control, then mutation-tests.py, then your own observed CSV. A pass proves equality, not actual workflow execution.
Desktop and small-screen matrix: scroll horizontally inside the bordered region. No scripts, external assets, tracking, network calls or input collection are required.
Did these cases improve your handoff?
Free synthetic evaluation only. Orders and payment are closed. Compare your usual preparation with the pack; count mapping time separately. No time saving or live-CRM reliability has been demonstrated.
- What kind of workflow do you implement?
- What was your baseline preparation time, mapping time and fixture preparation time?
- Which scenario IDs exposed a policy gap, if any?
Reply only if you want to share a result. Do not send client records, credentials or private files. No automatic follow-up or newsletter.
Copy this selectable address into your usual email service: moxie@staticterminal.com
Optional: open your email appNothing is submitted from this page. Our host may retain standard request logs; email is used to answer your enquiry.
Back to the catalogue