Step 01
Analyse the asset
Upload the creative you intend to defend. Add tags immediately so it is retrievable later.
User Guide
Quick Start
Use this sequence for reviews, pitches, and client rooms. It keeps the read consistent across teams.
Step 01
Upload the creative you intend to defend. Add tags immediately so it is retrievable later.
Step 02
Quality Gate → Intelligence → Mechanics → Psychology → Stress Lab → Market Pulse → Decision Log.
Step 03
Once the team aligns, export a dossier designed for decks, internal reviews, and client conversation.
Decompiler Tabs
Each tab is a different lens. Use them in sequence so your rationale builds from execution → meaning → decision.
The source workspace for the creative you are analysing. Confirm you are looking at the correct execution before you interpret any outputs.
Example
Example: Before review, tag “Client: Nike”, “Market: AU”, “Format: 9:16”, then export once the team agrees the asset is final.
A first-pass integrity check. Quality Gate isolates execution risks that can sabotage performance regardless of strategy (legibility, hierarchy clarity, format survivability).
Example
Example: If the CTA is low-contrast or near platform UI chrome, adjust contrast/placement first, then rerun the read.
The strategic layer: how the creative is positioned, what it signals, and what it implies about category pressure and differentiation.
Example
Example: “Restraint + visual isolation signals premium status; do not add density that breaks the status read.”
Structural decomposition of how the ad works: hierarchy, pacing, contrast control, and attention routing.
Example
Example: If the product locks attention but the CTA is peripheral, restructure the hierarchy so the CTA inherits attention after recognition.
The behavioural layer: what the asset asks the viewer to feel, believe, and do — and which levers it uses to produce that shift.
Example
Example: “Authority tone + restrained palette builds trust; playful copy may undermine credibility.”
The context layer: where the asset lives, who is likely viewing it, and what surrounding cues shape interpretation.
Example
Example: If a route reads as premium internally but looks like commodity content in-feed, tighten distinctiveness signals and spacing.
A constraint-first view of what the asset cannot violate: safe zones, legibility thresholds, and structural limits across formats.
Example
Example: When converting 9:16 to 4:5, preserve hierarchy so the conversion mechanism still holds.
A blueprint-level trace of the creative’s construction: how layers stack, what’s doing what, and where the pattern holds or leaks.
Example
Example: Keep identity cue and hero framing stable, but test copy compression and CTA prominence.
A stress-test layer for decision confidence. Pressure-test variables and predict where confidence breaks under review, risk, or uncertainty.
Example
Example: If “copy compression” is flagged, test shorter variants that preserve the core promise while reducing density.
Competitive context and market pressure signals. Market Pulse helps you interpret the route against saturation, novelty conditions, and timing.
Example
Example: If saturation is high, remove generic category cues and tighten distinctiveness signals.
The final decision record: what you are choosing, why you are choosing it, and what gets tested next — designed to prevent circular review loops.
Example
Example: “Hold: gaze direction. Test: CTA prominence. Change: supporting copy compression.”
Navigation Areas
These areas support real workflows: retrieval, comparison, packaging, and governance.
The Decompiler is the operating interface. Analyse assets, move through tabs in order, and export dossiers designed for review rooms.
Example
Example: Treat the Decompiler like a pre-meeting protocol: upload → run tabs → export → present.
Upload the creative and trigger the analysis. This is the start point for every workflow.
Example
Example: If you need a fresh run, upload a revised version so it hashes differently.
Vault is the memory system. It stores analyses so they can be retrieved, compared, and reused instead of re-created.
Example
Example: Before pitch, pull three past category reads from Vault to identify stable persuasion patterns.
Pulse is route comparison. It is built for moments when two directions are contested and you need clear deltas.
Example
Example: Compare incumbent vs challenger routes to decide whether to iterate the current pattern or pivot.
Market Pulse also exists as a standalone area for competitive and context signals across your work.
Example
Example: If category fatigue is rising, plan a distinctiveness-focused variant set early.
Boards group analyses into curated sets for delivery, comparison, or internal review.
Example
Example: Build a board with five category exemplars + your preferred route read for pitch review.
Configure agency identity and output controls. This is where you set the system to feel like your team.
Example
Example: Use white-labeling for client-facing exports to reduce “tool output” feel and increase trust.
Invite operators and assign access. Seats keep collaboration clean and accountability clear.
Example
Example: Add a producer seat for export + delivery responsibility, and keep billing access limited to owners.
Usage depends on your subscription plan and the volume of analyses your team runs. Higher plans unlock deeper workflows and larger operating capacity.
Example
Example: If you run frequent comparisons, choose a plan that supports higher-volume workflows.
Export
Exports are designed to travel: decks, internal reviews, and client conversation.
Export after the team aligns on what holds, what changes, and what gets tested next.
Use the tab sequence so the dossier reads like a decision narrative, not a screenshot dump.
Lead with Decision Log, then show the evidence chain (Mechanics → Psychology → Market Pulse).
Troubleshooting
Most issues are workflow-related, not failures.
Deduplication may have returned the existing analysis for an identical upload. Check Vault and confirm asset versioning.
Refresh and check Vault. Results can complete before the UI updates. If it persists, try a revised asset version.
Review the full tab sequence first. Check Agency Settings for identity/output controls that affect export styling.
Use Vault retrieval first (avoid reruns). If your workflow requires higher volume or white-labeling, see Pricing.
Support
If you still need help, include the asset id (or Vault link), the page URL, and what you expected to see.