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 · verticals

Verticals · 50 Sectoral

Weekly-refreshed factsheet of 50 sectoral verticals across 97 HS chapters and GATS services.

Last refresh: 58 days ago
Next:
Verticals
50
sectoral
HS chapters
97
covered
GATS services
12+
sectors
See also: Countries Tools Trade Bodies
Vertical taxonomy

Sectoral regulator landscapes — 66 verticals

AJG's vertical taxonomy spans HS chapters (goods) and GATS/CPC services. Each vertical has a hub page surfacing its primary regulator across all jurisdictions tracked. Total: 66 verticals · 974 regulator cells · 85 countries.

Verticals
66
Total cells
974
Countries
85
Families
9
📅 Updated 2026-06-23MultilateralWCAG-AAA

Chemicals & Pharma · 6 verticals

Electronics · 2 verticals

Energy · 2 verticals

Food & Agriculture · 8 verticals

Metals · 4 verticals

Minerals · 2 verticals

Other Manufacturing · 21 verticals

Services · 18 verticals

Textiles · 3 verticals

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

User POV — for the practitioner navigating the Verticals institutional hub

Eight dimensions

1 · Possibility

A verticals hub that maps every commercially significant sector — from agro-commodities and pharmaceuticals through textiles, chemicals, electronics, and luxury goods — onto a single comparable schema lets a reader cross-reference sector × country × FTA × corridor in one navigation move. The possibility opens when sectors stop being marketing pages and start being analytical surfaces with regulation, tariff, logistics, and counterparty data attached. A user comparing the pharmaceutical opportunity in Vietnam against the textile opportunity in Bangladesh should not need two different mental models; the verticals hub gives them one.

2 · Plausibility

Plausibility is bounded by sector heterogeneity. A vertical like cement is small-volume and capital-heavy; a vertical like apparel is high-volume and labor-heavy. The schema must be elastic enough to surface the right metrics per sector — capacity utilisation matters for cement, lead-time matters for apparel, cold-chain integrity matters for pharma. We solve this with sector-specific lens overlays on top of the canonical hub schema, rather than forcing every vertical into the same metric template.

3 · Probability

On a six-month horizon, vertical-led search is dominated by mid-market firms researching adjacent-vertical entries and consultants compiling one-off sector reports. The probability that the hub captures both audiences is high precisely because both want the same underlying data assembled differently — the firm wants their entry-decision question answered, the consultant wants the data to repackage. The hub serves both by being assembly-friendly: paragraphs are quotable, tables are exportable, links are deep.

4 · What works

What works is anchoring each vertical to its HS-chapter core plus its primary cross-vertical adjacencies. Pharma is HS 30 but pharma logistics overlap with chemicals (HS 28-29) and packaging (HS 39, 48). Treating verticals as graph nodes with weighted edges to other verticals lets readers walk the adjacency map — a pharma founder researching Indian APIs naturally clicks through to chemicals, then logistics, then trade finance. The graph-walk pattern is what produces five-page sessions on what would otherwise be one-page lookups.

5 · What doesn't work

What does not work is treating verticals as flat lists. The early version had verticals A-Z; visitors landed on the hub, scanned 50+ entries, and bounced. The fix was hierarchical browsing — top-level by broad sector (industrials, agro, services), second level by HS-chapter cluster, third level by sub-vertical specialty. Visitors land on a level that matches their mental model and drill down or pivot from there.

6 · Common pitfall

A common pitfall is conflating verticals with HS chapters. HS chapters are tariff classifications; verticals are commercial categories. Cement is HS 25.23 but the cement vertical also includes ready-mix, equipment, and clinker logistics — multiple HS lines that share a commercial logic. The schema decouples vertical from HS and links them through a many-to-many mapping, which is messier to maintain but matches how trade actually happens.

7 · Counter-intuitive insight

Counter-intuitively, the highest-engagement verticals are not the largest by trade volume. Specialty chemicals attracts more session depth than bulk agriculturals despite lower trade volumes because specialty chemicals decisions are higher-margin and the reader rewards depth more. We allocate editorial deepening accordingly: specialty verticals get the rich treatment, commodity verticals get the data-heavy treatment.

8 · Highest-leverage move

The highest-leverage move is the vertical-comparator: pick any two verticals, see them side-by-side on regulatory complexity, tariff exposure, logistics-intensity, capital-intensity, and ecosystem maturity. It costs near-zero to compute (the data is already keyed on vertical) and unlocks adjacent-vertical entry decisions, which is the question mid-market firms most often arrive with.

Eight user intents

9 · Who gains most

For mid-market exporters and importers entering a new sector, consultants compiling sector reports for clients, founders evaluating adjacent-vertical opportunities, investors screening sector-rotation hypotheses, government trade-promotion officers researching outbound priorities, and the sector-curious sub-group of any of the above. The schema is built so all six audiences read the same hub differently — the exporter sees tariff first, the consultant sees data quality first, the founder sees entry barriers first.

10 · Irreducible essence

They want a sector view that respects their decision context. Not "the textile industry is large and growing" but "Indian cotton textiles to Vietnam: 5% MFN duty, ASEAN-India FTA reduces to 3%, RCEP not yet operative for India, lead time 12-18 days via Chennai-HCMC, three corridor options ranked by cost." That paragraph is what the schema produces, repeated for every commercially relevant origin-destination-vertical triple.

11 · Optimal timing

When they have committed to entering a sector and are validating origin-destination-product-pathway combinations. Earlier in funnel they read sector overviews; later in funnel they engage trade lawyers. The verticals hub is the bridge artifact — analytical enough to support a real entry decision, accessible enough to read in one sitting.

12 · Where (sub-areas)

Where they read it: 70 percent desktop because vertical research is a sit-down task that benefits from multi-tab comparison. The mobile design surfaces the headline tariff + lead-time numbers and pushes the deeper schema into expandable cards. We do not optimise the hub for thumb-zone navigation because the audience is overwhelmingly at a desk.

13 · Why misunderstood

Because vertical research is poorly served. Industry association sites are membership-recruitment marketing. Government trade portals are authoritative but unreadable. Generic business-news sites are surface-level. The verticals hub sits in the empty middle: structured enough to be analytical, written enough to be readable, sourced enough to be defensible.

14 · Highest-leverage sub-paths

Which sub-lens dominates per audience: tariff for the exporter-importer, regulatory for the founder, logistics for the supply-chain manager, ecosystem-maturity for the investor, capital-intensity for the financier. The hub surfaces a "lens of the moment" hint based on the entry path — readers arriving via tariff search see tariff data first.

15 · Whose advice to trust

Whose decision-shape drives the hub layout: most often a small team rather than a single individual. The export-decision is a CFO-CEO conversation; the entry-decision is a CEO-board conversation. We render at two levels: an executive summary appropriate for a board pack and a deep-dive appropriate for the analyst building the pack.

16 · How to proceed differently

How they navigate: enter via vertical search ("indian pharmaceutical exports vietnam"), drill into the sub-vertical (API vs finished dosage), pivot to corridor-detail, end at trade-body lookup. The funnel is wider than the cities funnel because vertical research has more legitimate exit-points (a corridor page, a country page, a trade body) but each exit deepens the session rather than ending it.

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

Eight dev dimensions

17 · Data architecture

Data architecture: 50+ verticals, each with HS-chapter mapping (many-to-many), regulatory-overlay (per country), tariff-overlay (per FTA-pair), logistics-profile (corridors + lead-times), and cross-vertical adjacencies (weighted graph). Sources: HS schedules from government tariff portals, regulatory data from sectoral regulators, ground-sourced from our trade-body partner network. The graph adjacency is hand-curated; the per-cell data is cron-refreshed.

18 · Schema markup

Schema markup: each vertical hub emits as Service with serviceType matching the sector, plus an ItemList of sub-verticals. Industry-classification emits as DefinedTerm with inDefinedTermSet pointing at the HS-chapter taxonomy. Cross-vertical adjacencies emit as relatedLink. JSON-LD identifier "ajg:vertical::{slug}" so cross-references resolve cleanly.

19 · Internal linking

Internal linking: verticals hub fans down to 50+ vertical detail pages, across to country-vertical cross-pages (for major exporting/importing countries), and up to the trade-body registry for the relevant industry associations. Each vertical detail page carries a "see also" rail of adjacent verticals computed from the weighted graph. Cross-content injector matches vertical-related library nodes.

20 · Page-speed posture

Page-speed posture: the verticals hub is one of the heaviest pages on the site by data density. We virtualise the 50+ vertical cards via intersection-observer (initial 12 visible + lazy load) which holds first-paint under 800 ms. Detail pages are normal size; the cross-vertical comparator is the one heavy surface and is loaded only on /verticals/compare/. PageSpeed-100-v7 layer applies elsewhere.

21 · Mobile UX

Mobile UX: hub collapses 4-column card grid to 1-column. Hierarchical browse switches from accordion-tree to drill-down stack. Detail pages keep their executive-summary-first layout because the audience is desktop-heavy but not desktop-only. Tap targets all 48 px per SO #100.

22 · Accessibility

Accessibility: verticals hub uses proper landmark structure with role=navigation on the browse hierarchy. Each vertical card has aria-label combining vertical name + HS chapter + headline metric. Hierarchical browse is keyboard-navigable with arrow keys traversing the tree. Color encoding (regulatory complexity gradient) supplemented with text bands.

23 · SEO saturation

SEO saturation: each vertical detail page has unique H1 (vertical name + tagline), unique meta-description naming the standout metric for that vertical, FAQPage with the four most-asked vertical-entry questions, BreadcrumbList. The verticals hub itself emits ItemList of all 50+ verticals. Cross-pages (vertical × country) get their own schema. Speakable on summaries.

24 · Extensibility

Extensibility: adding a new vertical is a registry append + populating the schema for that vertical (regulation, tariff, logistics, adjacencies). Adding a new sub-vertical inside an existing vertical is similar but cheaper. The schema accommodates arbitrary additional cross-vertical edges so the adjacency graph can be densified without code change.

Eight dev intents

25 · Maintainer audience

For the developer maintaining this hub, the most demanding part is the cross-vertical adjacency graph. It is hand-curated because no algorithm reliably captures industrial logic — pharma-to-chemicals is obvious, but pharma-to-logistics-cold-chain-to-aviation-cargo is non-obvious and requires sector knowledge. The graph lives at data/shared/vertical-adjacencies.php as an explicit edge list with weights.

26 · Architectural commitment

What changes when verticals data updates: data/shared/verticals-master.php holds the canonical 50+ vertical records. Per-vertical regulatory + tariff + logistics overlays live in data/shared/vertical-{slug}/*.php. The cron rebuilds the cross-vertical adjacency-walk cache nightly; the master itself is editorial-driven.

27 · Refresh cadence

When the cron runs: weekly at 04:30 UTC on Sundays for the per-vertical regulatory + tariff sweep. Monthly at 04:30 UTC on the 1st for the cross-vertical adjacency-walk recompute. The walk is O(N²) over 50 verticals so the monthly cadence is conservative; we could weekly if we add more verticals.

28 · File map

Where files live: data/shared/verticals-master.php (the registry), data/shared/vertical-adjacencies.php (the edge graph), data/shared/vertical-{slug}/ (per-vertical overlay folder). Renderer at includes/vertical-template.php; hub at /verticals/index.php; comparator at /verticals/compare/.

29 · Existence rationale

Why hand-curated adjacency graph: because algorithmic adjacency (e.g. cosine similarity over HS-code patterns) misses the industrial-logic nuances that matter for entry-decision research. A reader looking at pharma needs the dotted lines to logistics, packaging, and cold-chain explicitly drawn — not because they share HS codes but because they share decision-relevant constraints. We pay the curation cost.

30 · Highest-leverage extension

Which renderer: includes/vertical-template.php emits the executive summary + tariff overlay + regulatory overlay + logistics profile + adjacency rail. Accepts $vertical_slug. Echoes directly. Idempotent like all entity templates.

31 · Authoritative sources

Whose responsibility: master registry curation is editorial (currently Vinod with sector-specialist contributors). Per-vertical overlay data is cron-driven from public sources + ground-sourced corrections. Adjacency graph maintenance is editorial. Schema validity enforced by pre-flight.

32 · Maintenance procedure

How to add a new vertical: (1) declare in verticals-master.php with HS-chapter mapping; (2) populate per-vertical overlay folder with regulatory, tariff, logistics records; (3) add adjacency edges to the graph; (4) verify via admin/verticals-coverage.php that all four overlay sections are populated; (5) verify hub render. Total: variable, often two days because new-vertical research takes time and the schema is intentionally rich.

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 ↓