Nischhal Raj Subba
Software studio brand + website

Hamro Idea

A service website designed in the browser as much as in the design file.

Role
Design + development
Year
2025
Product
Software studio brand + website
Users
Prospective clients evaluating a Nepal-based software studio
Hamro Idea product design case study
The product problem

The first job was making the offer easier to understand.

Prospective clients need to know what the studio does, whether the work is relevant and where to go next. The redesign therefore began with positioning and information architecture rather than a visual refresh. It also had to survive real content, responsive constraints and future service pages.

My contribution. I worked across positioning, information architecture, visual design, responsive UI, reusable sections, conversion paths, semantic markup and front-end implementation.

Key decisions

Where the design judgment mattered.

Decision

Organize around client intent

Service structure follows the questions prospective clients are likely to ask rather than internal company terminology.

Decision

Use the browser as a design tool

Real content lengths, breakpoints and implementation constraints become feedback during design instead of after handoff.

Decision

Treat semantics as part of craft

Heading structure, accessible markup and search readability are considered during composition, not as post-launch cleanup.

Project evidence

Screens, shipped material and public references.

The artifacts sit inside the story because proof is more useful next to the decision it supports than in a ceremonial section at the end.

Hamro Idea website homepage showing dark blue service-business hero section
Hamro Idea website homepage showing dark blue service-business hero section
LinkedInGitHub
Experience model

A service journey from fit to proof to contact

The finished system is easier to extend because the content structure, responsive behavior and front-end patterns were designed together. The case is also a useful example of my preference for staying close to implementation.

  1. 01

    Positioning establishes relevance.

  2. 02

    Service architecture helps visitors find the right capability.

  3. 03

    Project proof gives the offer credibility.

  4. 04

    Contextual calls to action turn evaluation into conversation.

What this work demonstrates

A clearer offer with less distance between design and build

The finished system is easier to extend because the content structure, responsive behavior and front-end patterns were designed together. The case is also a useful example of my preference for staying close to implementation.

End-to-end ownershipDesign-to-code executionService information architecture