EvolutionCo
ABSL GIFT City
UX Research, Competitor Benchmark, Strategic Recommendations, Personas, User Journeys & Information Architecture
Version
3.0
Research date
29 Jul 2026
{{ navTitle }}
No section title matches “{{ q }}”
Rows, themes, evidence cards and recommendations are still filtered by this term inside the report.
{{ n.k }} {{ n.label }}
Evidence legend
Source-derived observation
EvolutionCo assessment
EvolutionCo recommendation
Not publicly available
{{ printTabLabel }}
01 A Executive Research Summary

Direct GIFT City competitors solve parts of the investor journey well.

None combines persona identification, opportunity storytelling, contextual education, eligibility, product discovery, readiness and conversion into one adaptive experience.

{{ c.name }}
{{ c.mean }}
{{ c.badge }}
{{ c.verdict }}
{{ c.strong }}
{{ c.conf }}
Maturity at a glance
Mean qualitative score for each of five parameter groups. Adaptive experience is the weakest group for every brand reviewed.
{{ c.short }}
{{ r.g }}
{{ c.v }}
Methodology: EvolutionCo qualitative UX assessment based on the publicly accessible experience, 20 parameters on a 5-point scale. Not a mathematically weighted industry index.
Strategic gap
The category competes on information and process. Nobody competes on guidance.
Best-in-category strengths are split across six brands, none of which owns more than one stage well.
Personalisation scores 1.2 of 5 across the category — the widest unclaimed gap.
01 B Category Experience Model

The category runs a four-step information funnel. A first-time cross-border investor needs nine.

Observed today
Current category experience
{{ s.n }} {{ s.l }}
The visitor supplies all the context. The site supplies documents.
EvolutionCo recommendation
Desired adaptive experience
{{ s.n }} {{ s.l }}
Where each competitor is strongest
Each brand owns one part of the funnel. The category has no owner of the whole.
{{ s.brand }}
{{ s.owns }}
{{ s.note }}
Key insight
No single competitor currently owns the complete journey.
01 C Persona and Audience Architecture

Six segmentation dimensions are in play across the category. Not one competitor resolves more than three.

First-time versus experienced investor is the only dimension not addressed anywhere on any of the six public experiences. It is also the dimension that most determines whether a visitor understands what they are reading.

Dimension
{{ c.short }}
{{ r.d }}
{{ c.v }}
{{ l.k }} {{ l.l }}
Why these are not parallel homepage choices
Competitors place these dimensions side by side, which asks the visitor to compare four unrelated kinds of question at once.
{{ k.kind }}
{{ k.pair }}
{{ k.note }}
EvolutionCo recommendation · previewed here, detailed in Tab 02B
{{ h.l }}
{{ h.arrow }}
01 D Competitor Maturity Scorecard

Twenty parameters, six brands, one qualitative scale.

Competitors
Parameter group
Scale · hover for methodology
{{ s.n }} {{ s.l }}
Competitor UX maturity heatmap
Rows flagged in red are parameters where the whole category scores below 2.5 — the weak spots ABSL can claim.
{{ c.short }}
{{ r.label }}
{{ c.v }}
{{ r.flag }}
Overall UX maturity, ranked
Mean qualitative score across all 20 parameters. DSP and PPFAS lead on different halves of the funnel.
{{ r.name }}
{{ r.val }}
Weakest parameters across the category
The six lowest category means. These are the parameters where category-leading is cheapest to achieve.
{{ r.p }}
{{ r.val }}
Category mean of six brands, 5-point scale.
Best in category, parameter by parameter
The leading brand and its score for each parameter. No brand leads more than a third of the list.
{{ r.p }} {{ r.top }} · {{ r.max }}
01 E Competitor Deep Dives
{{ deepName }}
{{ deepUrl }}
Strategic verdict · EvolutionCo assessment
{{ deepVerdict }}
{{ deepConf }}
{{ r.k }}
{{ r.v }}
Strongest sections
{{ s }}
Limitations
{{ s }}
Applicable cue for ABSL
{{ deepCue }}
What ABSL should improve beyond
{{ deepBeyond }}
Parameter profile
{{ s.p }}
{{ s.v }}
Pages and exact sections referenced
{{ r.p }}
{{ r.u }}
{{ r.s }}
{{ r.c }}
01 F Content and Communication Benchmark

Content is organised around internal document categories, not around the questions investors actually ask.

Content-theme coverage heatmap
Twenty investor-facing themes coded from public pages. Misconceptions, fund-versus-direct and currency risk are the thinnest.
{{ c.short }}
{{ r.t }}
{{ c.v }}
{{ l.k }} {{ l.l }}
Most underserved investor questions
Coverage index out of 24 across the six brands, where strong coverage scores 4 and no coverage scores 0.
{{ r.t }}
{{ r.val }}
EvolutionCo recommendation
Put a user-question layer above the content taxonomy
One investor question resolves into seven internal content elements. Competitors publish the elements and leave the question unanswered.
User question
“Why should I invest internationally?”
Internal content elements it needs
{{ e }}
01 G Education, Guidance and Conversion

The funnel breaks at Identify Route and Prepare — exactly where an uncertain investor abandons.

Journey-stage heatmap
Nine stages of the first-time-investor journey, coded per brand from public pages.
{{ c.short }}
{{ r.s }}
{{ c.v }}
Education-to-conversion flow, per brand
Read each row left to right as one continuous journey. Gaps in the middle of a row are where the visitor is left to work it out alone.
{{ s }}
{{ r.short }}
{{ c.v }}
First-time-investor confidence model
Five confidence layers a first-time cross-border investor must clear before acting.
{{ c.short }}
{{ r.l }}
{{ r.d }}
{{ c.v }}
Key insight
No competitor visibly links all five confidence layers into one adaptive journey.
01 H Personalisation Benchmark

Nine of nineteen capabilities are not observed on any of the six sites.

Capability
{{ c.short }}
{{ r.c }}
{{ c.v }}
{{ r.noneLabel }}
{{ l.k }} {{ l.l }}
Key conclusion
No reviewed public competitor currently provides a homepage or content journey dynamically adapted to location, relationship status, investor knowledge and declared intent.
Disclaimer
Authenticated portals may contain capabilities that are not publicly visible. This benchmark assesses only the unauthenticated experience accessible on 29 July 2026.
01 I Evidence Gallery

Eighteen evidence cards, each reading category cue, observed limitation, ABSL opportunity.

No screenshot has been fabricated. Each card specifies the exact page, section and crop required, so the production pack can be captured against a fixed brief. Select a card to open its capture specification and annotation.

{{ s.b }} — {{ s.s }}
{{ s.s }}
{{ s.b }} {{ s.rec }}
{{ s.p }}
{{ s.w }}
{{ s.l }}
View source ↗
01 J Category Gaps and Strategic White Space

Everything the category has built is table stakes. Everything it has not built is high value.

White-space opportunity map
Horizontal: current adoption across the six competitors. Vertical: potential user and business value, EvolutionCo assessment. The top-left quadrant is unclaimed.
User & business value →
Strategic white space
Table stakes
{{ w.n }}
Low adoptionCategory adoption →High adoption
Key
{{ w.n }} {{ w.l }}
Category strengths — parity, not advantage
{{ s }}
Category gaps — where ABSL can lead
{{ s }}
ABSL opportunity · strategic white space
ABSL can become the clearest, most adaptive digital guide for understanding and accessing cross-border investment opportunities through GIFT City.
02 A Strategic North Star

ABSL GIFT City should not simply be a place to find GIFT City funds.

It should be the clearest digital guide to understanding and accessing cross-border investment opportunities through India.

Proposed experience model
Eight beats, in order. Each one is a decision the visitor makes, not a page we publish.
{{ s.n }} {{ s.l }}
Three strategic objectives
Every recommendation in this tab serves one of these three.
{{ o.t }}
{{ o.d }}
Competitor category model
Publish, then wait to be asked
Information, product, process, login. The visitor supplies the context, the intent and the interpretation. The site supplies documents and a form.
EvolutionCo proposed ABSL model
Identify, then adapt, then act
The site resolves who is reading, adapts the story and the depth, shows only plausibly available products, and prepares the visitor for a specific next action.
02 B Proposed Persona Architecture

Five sequential questions, each one narrowing the next. Nothing is asked twice.

{{ s.n }}
{{ s.k }}
{{ o }}
Resulting principal journeys
Five questions produce six journeys — a governable number of content and CTA variants.
{{ j }}
Why not parallel homepage options
Parallel choices multiply. Sequential questions divide.
Four parallel dimensions offer sixteen combinations and no guidance. Asking role first removes half the site immediately; asking location next removes half again.
Parallel options presented at once 16
Questions asked in sequence 5
Journeys the site must support 6
02 C Content and Storytelling Model

One communication sequence. Three voices. The same nine beats told differently per persona.

{{ s.n }} {{ s.l }}
Narrative track
{{ t.a }}
{{ i }}
02 D Experience Recommendation Pillars

Thirty recommendations, eight pillars, one governable structure.

{{ p.n }}
{{ p.t }}
{{ p.prio }}
Strategic objective
{{ p.obj }}
Benchmark cue
{{ p.cue }}
Category gap
{{ p.gap }}
EvolutionCo recommendation
{{ p.rec }}
User objective
{{ p.u }}
Business objective
{{ p.b }}
{{ p.recs }}
Primary pages: {{ p.pages }}
02 E Feature Catalogue · R01–R30
Pillar
Status
{{ r.id }}
{{ r.n }}
{{ r.pillar }}
{{ r.status }}
{{ r.s }}
User objective
{{ r.u }}
Business objective
{{ r.b }}
Pages {{ r.pages }} Differentiation {{ r.diff }}
Research basis
{{ r.basis }}
User problem
{{ r.prob }}
Primary interaction
{{ r.int }}
Required content
{{ r.cont }}
Dependency
{{ r.dep }}
Relevant personas
{{ r.per }}
Supporting pages: {{ r.supPages }}
02 F In-Scope Page Map · 14 pages

Five unique templates and nine adaptations carry all thirty recommendations.

Recommendation-to-page matrix
The first column is frozen. Filter by pillar or status above in the Feature Catalogue to reduce the rows.
Recommendation
{{ p }}
{{ r.id }} {{ r.n }}
{{ c.v }}
Primary application
Supporting application
Future-ready
Not applicable
Recommendation load per page
Primary applications in navy, supporting in light blue. Home and the master PDP carry the most.
{{ p.id }}
{{ p.n }}
{{ p.t }}
{{ p.c }} + {{ p.s }}
02 G Page-by-Page Strategic Summary
{{ pgId }}
{{ pgName }}
{{ pgType }}
Strategic purpose
{{ pgPurpose }}
Primary personas
{{ pgPer }}
Content narrative
{{ pgNar }}
User objective
{{ pgU }}
Business objective
{{ pgB }}
Conversion role
{{ pgConv }}
Primary recommendations
{{ r.id }} {{ r.n }}
Supporting recommendations
{{ r.id }}
02 H User and Business Objective Map

Every recommendation answers a user objective and a business objective. No numeric ROI is claimed.

User objectives
Bar length shows how many recommendations serve each objective.
{{ o.o }}
{{ o.recs }}
Business objectives
Differentiation from direct competitors is served by five recommendations.
{{ o.o }}
{{ o.recs }}
02 I Personalisation and Adaptive Experience

The same homepage, five ways. Select a persona to see what changes.

{{ variantName }}
{{ r.k }}
{{ r.v }}
Stated constraint
Personalisation should adapt content, education, preparation and CTA logic. It must not provide unregulated product recommendations, tax advice or suitability decisions.
02 J Prioritisation and Roadmap

All {{ totalRecs }} catalogued recommendations split {{ coreCount }} Core, {{ diffCount }} Differentiators, {{ futCount }} Future-ready.

Bands below are generated from the R01–R30 catalogue in 02E, so these counts always match the status filter there. The Future-ready card also lists five architectural provisions that are not catalogue items — they need design headroom now, not delivery.

{{ b.t }}
{{ b.sub }} · {{ b.count }} recommendations
{{ i.id }} {{ i.n }}
Plus 5 architectural provisions
Not catalogue recommendations — capabilities the architecture should not preclude.
{{ e }}
Impact versus effort
Vertical: combined user and business value. Horizontal: design, content and technology effort. Both axes are EvolutionCo qualitative assessments, not financial estimates.
User & business value →
Do first
Prototype and stage
Fill in
Defer
{{ s.id }}
Lower effortDesign, content & technology effort →Higher effort
Core
Differentiator
Future-ready
No financial benefit or numeric ROI is assigned. Effort and value are relative, not absolute.
03 A Persona and Journey Overview

The microsite supports six primary personas through three role-based branches and one connected conversion architecture.

Classification is sequential, not parallel: role, then location, then new or existing, then confidence. The investment route is derived from those answers — it is never a homepage card the visitor has to decode.

{{ m.v }}
{{ m.l }}
Six primary personas
{{ roleQuote }}
{{ roleNote }}
{{ p.id }}
{{ p.br }}
{{ p.s }}
{{ p.cls }}
{{ p.need }}
{{ p.route }}
Converts on: {{ p.prim }}
Persona → narrative → pages → CTA strategy → conversion
One line per persona. The narrative is the homepage promise, not a campaign strapline.
{{ r.id }} {{ r.s }}
{{ r.nar }}
{{ r.pages }}
{{ r.cta }} Secondary: {{ r.cta2 }}
{{ r.conv }}
Universal acquisition journey
{{ s.n }} {{ s.l }}
Content sequence inside those stages
{{ s.n }} {{ s.l }}
Supporting states — not primary personas
These are filters, tags and variants applied to the six personas. They do not receive persona cards of their own.
{{ s }}
Persona archetypes are behavioural and contextual. No demographic data, photography or fictional biography is used.
03 B Classification and Routing Logic

Five stages, asked in order, and only when the answer is not already known.

This is a decision framework, not five mandatory questions. Confirm important assumptions; do not repeatedly ask what is already known.

{{ s.k }} {{ s.n }}
{{ o }}
Why this question is asked
{{ s.why }}
Derived routes {{ r }}
Test the routing logic
Answer as a visitor would. The route, narrative, starting page and CTAs are outputs.
01 Role
02 Location
03 New / Existing
04 Knowledge / confidence
Persona
{{ routePer }} · {{ routePerShort }}
{{ routePerName }}
Derived route
{{ routeRoute }}
Homepage narrative
“{{ routeNar }}”
Content mode
{{ routeMode }}
Recommended starting page
{{ routeStart }}
Primary CTA
{{ routePrim }}
Assisted CTA
{{ routeAssist }}
Questions that can be skipped
{{ s }}
{{ routeWaiting }}
03 C Persona Profiles

Each persona changes the narrative, the depth, the product order and the conversion — not the page count.

{{ perId }} · {{ perBr }}
{{ perName }}
{{ perNeed }}
Relevant route
{{ perRoute }}
Primary conversion
{{ perPrim }}
Role
{{ perRole }}
Location
{{ perLoc }}
Relationship
{{ perRel }}
Knowledge / confidence
{{ perKnow }}
Motivations
{{ m }}
Primary questions and concerns
{{ m }}
Content depth and products
{{ perMode }}
{{ perProds }}
Entry points
{{ e }}
Priority content
{{ m }}
Key features
{{ m }}
Primary pages
{{ p }}
Variants and states
{{ v }}
Alternative conversions
{{ m }}
Assisted support
{{ m }}
Business opportunity
{{ perBiz }}
Experience risks
{{ m }}
What changes for this persona?
The page set stays the same. These eight things adapt.
{{ c.a }}
{{ c.v }}
Primary conversion
{{ perConv.prim }}
Secondary and assisted
{{ perConv.sec }}
{{ perConv.assist }}
Dependency and confirmation
{{ perConv.dep }}
{{ perConv.conf }}
03 D End-to-End Journey Explorer

Six journeys. Every one ends in a named outcome, not a vague conversion.

Journey
Journey view
Product type
Journey status
Phase
{{ jFilterNote }}
{{ viewNote }}
{{ jId }} · {{ jPerName }}
{{ jName }}
Entry: {{ jEntry }}
Product
{{ jProd }}
Status
{{ jDirect }}
Journey ends at
{{ jEnd }}
Flow
{{ f.l }}
{{ s.i }} {{ s.s }}
{{ f.k }}
{{ f.v }}
Stage detail · {{ drJ }}
Stage {{ drN }} — {{ drS }}
{{ r.k }}
{{ r.v }}
Alternative outcomes
{{ a }}
Failure states and recovery
{{ f.f }}
{{ f.r }}
03 E Page and Screen Flow

Every journey resolves inside the confirmed fourteen pages, plus named external boundaries.

Filter the matrix
Persona / page
{{ c.id }}
{{ r.id }} {{ r.s }}
{{ c.v }}
{{ l.k }} {{ l.l }}
Page names: P01 Home · P02 Product Listing · P03 Product Detail 1 (Master) · P04 Investor Centre · P05 Why GIFT City — NRI / Global · P06–P10 Product Detail 2–6 · P11 Our Company · P12 Our Team · P13 Contact Us · P14 Why GIFT City — Distributor.
Page sequence — {{ jId }} {{ jName }}
Screen order for the journey selected in 03D. Change the journey there and this sequence follows.
{{ p.st }}
{{ p.n }}
External boundaries
The microsite designs the handoff. It does not own what happens beyond it.
{{ e.n }}
{{ e.s }}
{{ e.r }}
03 G Channel and Assistance Strategy

What can be completed here, what continues elsewhere, and what is not yet in scope.

WhatsApp, the AI guide, live chat, video consultation, QR continuation and advanced cross-channel continuity are labelled Separate Scope / Future-Ready Capability. They are not confirmed current-scope deliverables.

Task / channel
{{ c.n }}
{{ c.s }}
{{ r.t }}
{{ c.v }}
{{ l.l }}
AI-assisted GIFT City guide
R29 · Separate scope
A governed guide that explains and navigates. It never recommends, assesses suitability or confirms eligibility.
Allowed
{{ a }}
Prohibited
{{ a }}
Escalation logic
{{ e.l }}
WhatsApp continuation
Separate scope · operational validation required
Suitable use cases
{{ u }}
Illustrative prefilled message
“{{ waMsg }}”
Guardrails
{{ g }}
{{ c.n }}
{{ c.s }}
{{ u }}
03 H Conversion, Failure and Recovery

Ten conversion types. Every failure state has a definite recovery action.

ID
Conversion
Dependency
Confirmation state
{{ c.id }}
{{ c.n }}
{{ c.dep }}
{{ c.conf }}
Persona conversion map
{{ m.id }} · {{ m.s }}
Primary
{{ m.prim }}
Secondary
{{ m.sec }}
Assisted fallback
{{ m.assist }}
Conversion point
{{ m.page }}
{{ m.dep }}
{{ m.conf }}
CTA orchestration
Select a context to see the CTA set. Retail transacts; AIF and restricted products are enquiry-led.
User and product context
Primary
Secondary
Assisted
{{ r.ctx }}
{{ r.prim }}
{{ r.sec }}
{{ r.assist }}
Failure and recovery explorer
{{ f.f }}
{{ f.w }}
Recovery
{{ x }}
Owner: {{ f.own }}
Defined journey endings
{{ o }}
04 Information Architecture

How is the microsite organised?

Review how pages, content and key journeys are grouped so users can easily find the information and actions relevant to them.

For client review
Please review whether the proposed page grouping, navigation structure and page hierarchy are clear and complete.
{{ iaScopeLine }}
{{ iaCrumb }}
{{ iaSelName }}
Why a user would visit
{{ iaSelWhy }}
Main action
{{ iaSelAction }}
Intended audience
{{ iaSelAudience }}
Feedback required {{ iaSelFb }}
{{ r.count }}
Use the chevrons to expand or collapse a section · click any page or section to see its details.
{{ iaZoomPct }}
Scroll to move around · use +/− to zoom · click any page or section to see its details.
Evidence
Sources & Availability

Every competitor observation in this report is tied to a public page and a named on-page section, captured 29 July 2026. Where a page could not be retrieved, confidence is stated explicitly.

{{ g.name }}
{{ s.title }}
{{ s.url }}
Section: {{ s.section }}
Supports: {{ s.supports }}
{{ s.status }}
{{ lbBrand }} · {{ lbDate }}
{{ lbSection }}
{{ lbPage }}
Screenshot pending capture
No screenshot has been fabricated. The crop below is specified for capture during production of the client pack.
Required crop: {{ lbSection }}
{{ lbUrl }}
Category cue
{{ lbWorks }}
Observed limitation
{{ lbLimit }}
Opportunity for ABSL
{{ lbRel }}
{{ lbRec }}