Selected EWD work

The work behind the visible result.

5 project dossiers connecting business context, content, design, development, search, and conversion decisions.

5Selected stories · honest evidence labels

How to read the work

A portfolio shows taste. A case study should show judgement.

Each story starts with the job and constraint, names the delivered system, and separates visible work from claims that require deeper measurement context.

Context before screenshots.

Decisions before claims · outcomes labelled with limits

01Contextrecord →
02Constraintrecord →
03Optionsrecord →
04Decisionrecord →
05Buildrecord →
06Evidencelabel ✓

Case 01 · Personal brand · Hospitality

Shloke Chhabra

Turn an established culinary reputation into a focused digital experience that makes private-chef services understandable and enquiries easy to begin.

Visible project scope

✓Personal positioning and service hierarchy
✓Story-led responsive website
✓Clear booking and enquiry journey

Evidence shown here

Approved interface and project context. Quantitative performance is not claimed without a publishable baseline, timeframe, source, and attribution note.

Case 02 · International ecommerce · Gifting

Nippon Florist

Balance gifting intent, product selection, local expectations, and delivery information for customers ordering flowers across borders.

Visible project scope

✓Localised shopping journey
✓Fast product discovery
✓Delivery confidence and purchase clarity

Evidence shown here

Approved interface and project context. Quantitative performance is not claimed without a publishable baseline, timeframe, source, and attribution note.

Case 03 · B2B · Pharmaceutical manufacturing

Innova Captab

Present products, manufacturing capabilities, technical credibility, and corporate information clearly to very different stakeholder groups.

Visible project scope

✓B2B information architecture
✓Capability and product content system
✓Credible responsive interface

Evidence shown here

Approved interface and project context. Quantitative performance is not claimed without a publishable baseline, timeframe, source, and attribution note.

Case 04 · Heritage · Content discovery

Heritage Temples of India

Make a growing body of cultural stories easy to explore without flattening the character, context, and visual richness of each place.

Visible project scope

✓Story-led content architecture
✓Search and browse journeys
✓Flexible publishing system

Evidence shown here

Approved interface and project context. Quantitative performance is not claimed without a publishable baseline, timeframe, source, and attribution note.

Case 05 · Fine jewellery · Ecommerce

NIMORAA

Translate a premium product story into a storefront that supports discovery, trust, product understanding, and confident purchase decisions.

Visible project scope

✓Premium commerce interface
✓Product discovery and merchandising
✓Responsive purchase journey

Evidence shown here

Approved interface and project context. Quantitative performance is not claimed without a publishable baseline, timeframe, source, and attribution note.

What every case records

The useful details live between the brief and the screenshot.

A reusable evidence standard makes different projects easier to compare without pretending they share the same metric.

Business context

What the organisation offers, who decides, and what the digital experience needed to change.

Constraint

The commercial, content, UX, technical, operational, or measurement problem addressed.

Approach

The alternatives considered and why the selected direction fit the real requirements.

Implementation

What was written, designed, developed, integrated, migrated, and verified.

Evidence

Available qualitative or quantitative outcomes with timeframe, source, and attribution context.

Next work

What remained outside scope, could not be verified, or became the next useful priority.

Case study FAQs

Questions about relevance, results, and confidentiality.

Can I see a project similar to mine?

Share the industry, customer journey, platform, content shape, and required functionality. We can point to the closest public example or explain relevant experience without pretending two projects are identical.

Why are there no dramatic percentage claims here?

A responsible result needs the metric definition, baseline, timeframe, source, concurrent work, and attribution limits. This page shows approved interfaces and project decisions; quantitative evidence is added only when that context can be published.

Can our project remain confidential?

Yes. Publication, attribution, screenshots, results, and the level of detail are agreed with the client. Confidentiality does not change how the work itself is documented and handed over.

Find the relevant evidence

Tell us the project shape—not just the industry label.

Share the customer journey, platform, content, functionality, and commercial goal. We will identify the closest useful work or explain the gap directly.

Discuss a similar project