Factsheets: 📈 Markets 🎯 Mandates 📋 Case Studies 📘 SOPs 🏛 Trade Bodies 🏙 Cities 🌍 Countries 🇮🇳 Indian States ⚓ Ports 🏛️ SEZs 🤝 Blocs 📜 FTAs 🛤 Corridors ⚙ Verticals 📦 Commodities 🧮 Tools ⚖️ Compare 🌐 Bilateral Hubs 📚 Library 🎓 Academy ✍️ Essays 📰 Blog 🔤 Lexicon ❓ FAQ 📡 Authority Sources ⚡ Daily Pulse 📰 Topic Briefs 📡 Google Signals 🧭 Scope Scape cron-refreshed
Live factsheets · cron-refreshed

All factsheets at a glance

Command center →
📈 Markets
554
global + India · commodities + indices + shares + crypto + FX
minute
🎯 Mandates
69
sell + buy · live
daily
📋 Case Studies
37
closed · anonymised
weekly
📘 SOPs
42
step-by-step playbooks
weekly
🏛 Trade Bodies
1,350
291 baseline + 1059 hand-curated
monthly
🏙 Cities
1,584
global atlas
daily
🌍 Countries
184
multilateral
weekly
🇮🇳 Indian States
37
state trade profiles
monthly
⚓ Ports
52
global maritime gateways
monthly
🏛️ SEZs
31
global SEZ profiles
monthly
🤝 Blocs
28
tracked
monthly
📜 FTAs
526
active or signed
monthly
🛤 Corridors
37
tracked
monthly
⚙ Verticals
50
sectoral
weekly
📦 Commodities
51
HS-coded intelligence
monthly
🧮 Tools
105
free utilities
monthly
⚖️ Compare
pairwise combinations
monthly
🌐 Bilateral Hubs
184
India × every country
weekly
📚 Library
140
interconnected
monthly
🎓 Academy
25
trade education
monthly
✍️ Essays
30
long-form analysis
monthly
📰 Blog
34
editorial
weekly
🔤 Lexicon
312
glossary terms
monthly
❓ FAQ
155
curated Q&A
monthly
📡 Authority Sources
140
curated · vetted
hourly
⚡ Daily Pulse
145
rolling 5,000 cap
hourly
📰 Topic Briefs
29
permanent archive
hourly
📡 Google Signals
Trends·News·Alerts
hourly
🧭 Scope Scape
61
11 scopes
hourly
Weekly factsheet · case-studies
Last refresh: 58 days ago
Next:
Case studies
37
closed · anonymised
Verticals
20+
covered

Trade Case Studies

1087 anonymised case studies from real India-EU, India-UAE, and global trade mandates — challenges faced, solutions applied, and key learnings for Indian exporters.

Clear
🚢

Logistics

2
India-EU Red SeaLogisticsRerouting Sep 2025

Indian Exporter Saves EUR 340,000 by Proactive Red Sea Rerouting Decision

The Challenge

In December 2023, Houthi attacks on Red Sea commercial shipping caused most shipping lines to announce diversion via Cape of Good Hope. An Ahmedabad textile exporter had EUR 2.8M of Christmas season g...

The Solution

AJG recommended immediate proactive rerouting for all vessels that had not yet entered the Red Sea. The exporter worked with their freight forwarder to divert 3 containers from a Dubai transshipment t...

The Outcome

Cape-rerouted containers: arrived EU ports 12-14 days late — EU buyers accepted the delay with written confirmation of force majeure notice. Red Sea containers: one arrived without incident; one was...

Key Learnings (4) ↓

Key Learnings

  1. Proactive rerouting via Cape of Good Hope was the correct decision when Red Sea risk was elevated — the 10-14 day delay was manageable; cargo loss would have been catastrophic
  2. War risk insurance (Institute War Clauses) must be in place BEFORE entering a high-risk zone — it cannot be obtained after the vessel has entered the Red Sea or Gulf of Aden
  3. Force majeure notice to EU buyers should be sent as soon as rerouting is confirmed — buyers are far more sympathetic to documented supply chain disruption than to unexplained delay
  4. Check your marine insurance policy'\2 war risk geographical scope — some policies automatically include Red Sea as a war risk zone once it is listed on the Lloyd'\2 Joint War Committee list
India-Germany ATA CarnetHannover MesseGermany Jun 2025

ATA Carnet Saves Indian Engineering Manufacturer INR 18 Lakh in Duties for Hannover Messe

The Challenge

A Kolhapur-based engineering machinery manufacturer planned to display 4 machine tools (total value INR 2.4 crore) at Hannover Messe. Without ATA Carnet, temporary import into Germany would require: t...

The Solution

AJG facilitated ATA Carnet application through FICCI India (an ATA Carnet issuing body). Carnet covered 4 machines, 12 demonstration components, and 200 technical brochures. Carnet validity: 12 months...

The Outcome

Total customs formality time at Frankfurt: 2 hours. Duties avoided: approximately EUR 225,000 (7.5% duty on EUR 3M CIF value). VAT avoided: EUR 570,000 (19% VAT on EUR 3M). ATA Carnet cost: INR 18,000...

Key Learnings (4) ↓

Key Learnings

  1. ATA Carnet is the only practical mechanism for taking machinery and equipment to EU trade fairs — without it, the customs formalities are impossibly slow for trade fair logistics
  2. FICCI, CII, ASSOCHAM, and PHD Chamber of Commerce are ATA Carnet issuing bodies in India — apply 3-4 weeks before the exhibition date
  3. ATA Carnet covers goods for temporary import — the goods MUST return to India — any goods sold from the exhibition stand must be cleared through normal import procedures
  4. Hannover Messe EEPC India Pavilion organises group ATA Carnet assistance for Indian machinery exhibitors — contact EEPC India 6 months before the exhibition

Submit a mandate and let AJG apply these learnings to your trade challenge

Commission-only. No upfront fee. Both principals represented.

Submit a Mandate → Ask the Principals

Totality lens · 32 points to ponder · 16 user POV + 16 developer POV · this institutional hub

User POV — for the practitioner navigating the Case Studies institutional hub

Eight dimensions

1 · Possibility

A case-studies hub that publishes structured anonymised post-mortems on completed deals — what the structure was, what the timeline was, what the friction-points were, and what the outcome was — replaces the marketing-led "client success story" with an analytical surface. The possibility opens when the hub is honest about failures and partial-successes alongside wins, which most case-study libraries are not. Practitioners learn faster from honest post-mortems than from polished success narratives.

2 · Plausibility

Plausibility is bounded by counterparty consent. Real case studies require the parties involved to agree to publication, even anonymised. We default to anonymising on principal-by-mandate basis; some deals stay in private archive because counterparties decline. The visible hub is therefore a curated subset of the deal book, but the curation is consent-driven not selection-bias.

3 · Probability

On a six-month horizon, case-study-led search is high-quality, low-volume — researchers compiling case-libraries, students learning the craft, professionals diligence-checking the platform. The probability of converting case-study readers into platform users is high; case studies are the highest trust-building surface we publish.

4 · What works

What works is structured five-section format: situation, structure, timeline, friction-points, outcome. Each section is two to four paragraphs. Visitors absorb a case in five minutes. What works less well is over-narration; case-study readers are professionals scanning for transferable patterns, not seeking entertainment. We strip narrative flourish out of revisions.

5 · What doesn't work

What does not work is sanitising failures. A case study where everything went smoothly is unbelievable to professional readers and useless for learning. We deliberately publish the friction-section even when the outcome was successful — what almost broke the deal, what the work-around was, what we would do differently. The honesty is the value.

6 · Common pitfall

A common pitfall is publishing too soon after a deal closes. Recent deals are too easily de-anonymised because the counterparty pool was small and timing-distinctive. We default to a 12-month gap between deal-close and case-study-publish, which protects anonymity at the cost of recency. Readers tolerate the gap when they understand the rationale.

7 · Counter-intuitive insight

Counter-intuitively, the most-shared case studies are often the partial-success ones, not the clean-wins. Practitioners share what they can learn from; clean-wins teach less than "we got 70 percent of what we wanted, here is why we did not get the other 30 percent." The schema does not weight by cleanness; we publish across the win-spectrum.

8 · Highest-leverage move

The highest-leverage move is the cross-case pattern-extraction: across the published cases, what friction-points recur most often, what structural patterns succeed most often, what timeline-shapes correlate with outcomes? The pattern-extraction is editorial (algorithmic clustering would miss the nuance) but the underlying data is structured enough that it is tractable to do. Patterns become their own mini-essays linked from individual cases.

Eight user intents

9 · Who gains most

For practitioners learning the trade-deal craft, principals diligence-checking the platform before engaging, students researching practical trade structures, and the case-study-curious sub-group who consume them as professional reading. The schema is built to serve all four — practitioners read for transferable patterns, principals read for evidence-of-competence, students read for pedagogy, and the curious read for the same reason people read post-mortems generally.

10 · Irreducible essence

They want honest five-section structure with the friction-section preserved. Not the polished marketing version. Most platforms publish the polished version because it is safer; we publish the friction version because it is more useful. The schema enforces the structure so even authors who would soften reality cannot sneak it through.

11 · Optimal timing

When they are diligence-evaluating the platform (principals), studying the craft (practitioners + students), or researching adjacent-deal-types for their own work. Editorial freshness matters less here than depth — a one-year-old case study with the friction-section preserved beats a six-month-old sanitised one.

12 · Where (sub-areas)

Where they read it: 70 percent desktop because case studies are sit-down reading. The mobile design preserves the five-section structure with section-by-section navigation. Cases run 1,500-3,000 words each so we surface a TL;DR on mobile and gate the full read behind expand.

13 · Why misunderstood

Because case studies are the highest-trust content type a platform like ours can publish. Marketing copy is universally mistrusted; case studies are universally read. The asymmetry is huge and we lean into it by being more rigorous (structured + honest + anonymised) than the typical case-study library.

14 · Highest-leverage sub-paths

Which case-pattern dominates per audience: structural-complexity cases for the practitioner, timeline-friction cases for the principal evaluating engagement-tempo, pricing-friction cases for the negotiator, regulatory-friction cases for the compliance-leaning reader. The hub tags cases by primary friction-pattern so readers can filter.

15 · Whose advice to trust

Whose perspective is the case told from: usually the principal who ran the deal, occasionally the counterparty (with their consent), rarely the broker (we discourage broker-narration because broker-incentives diverge from principal-incentives). The schema labels the narrator-perspective explicitly so readers know whose lens they are reading through.

16 · How to proceed differently

How they consume: enter via cross-case pattern essay or specific case URL, read the five sections, jump to a related case via the friction-pattern tag, exit at a methodology page or a vertical hub. The funnel is depth-first not breadth-first; readers go deep into one or two cases per session rather than scanning many.

Developer POV — for the architect, maintainer, future contributor to this hub

Eight dev dimensions

17 · Data architecture

Data architecture: per-case record with five-section payload (situation, structure, timeline, friction, outcome) + metadata (deal-type, vertical, geography-pair, counterparty-anonymisation-level, publish-date, narrator-perspective, friction-pattern-tags, related-cases). The pattern-extraction layer reads across all cases and produces clusters, surfaced as cross-case essays.

18 · Schema markup

Schema markup: each case-study emits as Article with articleSection mapping to the five sections, plus specific properties for deal-type and friction-pattern-tags. Anonymisation status emits as a custom Property; readers see "anonymised at counterparty consent" prominently. JSON-LD identifier "ajg:case::{slug}".

19 · Internal linking

Internal linking: cases hub → individual case URLs → friction-pattern essays → vertical hub for the case sector → corridor hub for the case geography. Each case carries a "similar cases" rail computed from friction-pattern overlap + geography overlap. Cross-content injector surfaces methodology nodes that the case demonstrates.

20 · Page-speed posture

Page-speed posture: case content is text-heavy (1,500-3,000 words per case). We render server-side with no client-side dependencies; total weight under 70 KB compressed. The cross-case pattern essays are the heavier surface but still text-only. PageSpeed-100-v7 layer applies; sticky-section-nav is CSS-only.

21 · Mobile UX

Mobile UX: case TL;DR at top with section-jump navigation. Each section expands inline or in a full-screen modal at user choice. Sticky section-progress indicator shows reading progress. All tap targets 48 px.

22 · Accessibility

Accessibility: cases use proper article semantics with section landmarks. Screen readers traverse in document order with section-jump as alternative. Friction-pattern tags are role=link with descriptive aria-labels. Reading-progress indicator is aria-live to announce section transitions.

23 · SEO saturation

SEO saturation: each case has unique H1 (anonymised case title), meta-description naming the friction-pattern and outcome, FAQPage with the four most-asked questions about the case structure, BreadcrumbList. Cross-case pattern essays get HowTo + Article schema. Speakable on the TL;DR.

24 · Extensibility

Extensibility: friction-pattern tag taxonomy is editorial-curated and grows organically as new patterns emerge from new cases. Section structure is fixed (five sections) for consistency across the library. Adding new metadata (e.g. deal-stage-where-friction-appeared) is a schema extension that backfills cleanly.

Eight dev intents

25 · Maintainer audience

For the developer maintaining this library, the most editorially-sensitive part is the anonymisation review. A case that de-anonymises by accident (because too many distinguishing details accumulated across the five sections) is a counterparty-trust-breach. The review-checklist at admin/case-review.php enforces the deindentification rules.

26 · Architectural commitment

What changes when cases publish: data/cases-data.php gains a new record; the friction-pattern-tag index updates; the cross-case pattern essays pre-renders refresh on the next cron. The publish process is intentionally manual through admin/case-publish.php to keep the editorial gate prominent.

27 · Refresh cadence

When the cron runs: weekly at 05:00 UTC on Sundays for the cross-case pattern-essay regeneration. Cases publish on editorial cadence (typically 1-2 per month), not on cron. The pattern-essays update with every new case publish but the visible regeneration is weekly to keep load even.

28 · File map

Where files live: data/cases-data.php (the case registry), data/case-friction-patterns.php (the tag taxonomy), includes/case-template.php (renderer), shared/case-pattern-extraction.php (the cross-case pattern engine). Hub at /case-studies.php; individual cases at /case-studies/{slug}/.

29 · Existence rationale

Why structured five-section format: because unstructured case content drifts. Authors over time begin to write more narrative, less analysis, less honesty. The structure is a discipline-forcing constraint that keeps the library readable and useful even as the contributor pool widens.

30 · Highest-leverage extension

Which renderer: includes/case-template.php emits the TL;DR + five sections + friction-pattern tags + similar-cases rail + narrator-perspective badge. Accepts $case_slug. Echoes directly. Idempotent.

31 · Authoritative sources

Whose responsibility: case authoring is editorial (currently shared with sector-specialist contributors). Anonymisation review is editorial gate. Pattern-extraction essays are editorial-with-data-assist. Schema validity enforced by pre-flight.

32 · Maintenance procedure

How to publish a new case: (1) author the five sections under the structure; (2) submit through admin/case-intake.php with anonymisation level; (3) editorial review triggers de-anonymisation check; (4) on approval, case-publish.php writes to data/cases-data.php and triggers pattern-essay refresh. Total: about a week from author-draft to publish.

v207.1 cross-Crucible synthesis · Case Studies

Case Studies in the cross-Crucible framework

Case studies are the empirical validation of the cross-Crucible framework. Every actual cross-border decision AJG's mandates have closed touches at minimum 4-7 of the 22 Crucibles — an Indian-pharma-to-EU mandate threads Cost + Knowledge (regulatory: EU MDR + EMA + national RVAs) + Visa (regulatory affairs leads + EU on-site presence) + Business (EU subsidiary structuring) + Economics (EUR/INR hedging) + Travel (FDA + EMA inspection visits). A UK-founder-to-Portugal-residency mandate threads Visa + Tax (now stratified post-NHR-to-IFICI) + Live + Business (Portuguese entity vs UK-only with Portuguese-tax-residency) + Family (international schooling + healthcare). The case studies on this page are anonymised; the underlying decision-pattern is the empirical anchor for the framework. The cross-references below decode the most-frequent multi-Crucible decision-patterns observed across AJG's mandate-pipeline.

Connect to Crucibles

Decide atlas → Where case-studies' multi-Crucible decision-patterns become structured trade-off matrices applicable to new mandates. Decide Crucible converts the empirical case-pattern (what we've seen work and fail) into reusable decision-frameworks (what to consider, in what order, against what alternatives).
Knowledge atlas → Where case-studies' regulatory-friction findings get codified into long-form deep-dives — when a CBAM-compliant supply-chain restructuring case revealed an unexpected interaction with REACH chemicals registration, that interaction goes into Knowledge Crucible as a permanent reference rather than living only in the closed-mandate file.
Cost atlas → Case-studies regularly surprise on cost — a "low-cost" jurisdiction often has hidden friction-costs that exceed sticker-price savings (banking-account-opening time · regulatory-licence backlogs · skill-shortage premiums · currency-volatility hedging cost). Cost Crucible accumulates these case-revealed friction-costs into a richer-than-sticker-price comparison.
Visa atlas → Case-studies on actual residency outcomes deepen the Visa Crucible's analytical framework — published government-timelines often differ from real applicant experience by 30-100%, and this case-anchored real-world data informs the Crucible's "expected timeline" guidance vs the "official timeline" cited in regulator portals.
Business atlas → Case-studies on actual structuring outcomes — when a Mauritius-holding-company structure failed to deliver expected India-DTAA benefits because of GAAR (General Anti-Avoidance Rules) interpretation, the case feeds Business Crucible's GAAR-risk-adjusted analysis of holding-company structures.
Economics atlas → Case-studies on currency-hedging + macro-shock impact — INR-EUR volatility during 2022-23 European energy crisis surfaced previously-untested mandate dependencies; case-anchored data informs Economics Crucible's currency-shock contingency framing for forward mandates.
Live atlas → Case-studies on actual relocated-family experience — international-schooling availability + healthcare-quality + community-fit determines whether a "successful" residency-route mandate closes for the principal but fails for the family. Live Crucible accumulates these family-fit findings.
Travel atlas → Case-studies on cross-border travel friction — passport-strength outbound + visa requirements inbound + transit complications. Real travel patterns from closed mandates feed Travel Crucible's practical-mobility analysis vs theoretical-passport-strength rankings.

Related cross-Crucible decision lists

Sources: AJG closed-mandate case archive 2018-26 (anonymised per professional confidentiality · published with case-principals' explicit consent) · UK Companies House public filings · Indian MCA public filings · EU Official Journal regulatory publications · WTO RTA Database · Henley Passport Index Q1 2026 · Coface country risk · all data points cross-verified against open-source-intelligence (OSINT) public records before publication

PhiloJain Music
Loading…

Explore

Explore the AJG knowledge graph

Every page in the AJG platform cross-links to these primary entities. Click any pill to explore that branch of the knowledge graph.

All hubs · 80 surfaces · click to expand ↓