Grid Labs by Nischhal SubbaGrid Labs by Nischhal Subba

Grid Labs

Portfolio project
Nischhal Subba
Grid Labs is a hosting and infrastructure website. I worked on its commercial hierarchy, plan presentation, domain-search affordance and static frontend.
A prospective customer needs to understand which service fits and how plans differ. The challenge was putting those decisions ahead of the full specification list.

What shaped the design

Plan attributes need consistent labels, units and billing periods.
Stacked cards make direct comparison harder on narrow screens.
A static site must be clear about what its actions actually provide.
THE DESIGN CHALLENGE

How can a hosting buyer compare plans without carrying every specification in memory?

I focused the page on choosing a service, comparing its plans and understanding what happens after the next action.
01 / Keep plan differences in a stable order

Keep plan differences in a stable order

Equivalent plan details need the same labels, order and units. That lets someone compare the differences instead of remembering where each attribute appeared on the previous card.
Technical detail still has a place, but the attributes that change the choice deserve more attention. Current prices and commercial terms belong with the service owner; the historical site is used here to discuss the pattern.
Giving every specification equal weight makes the information harder to compare.
02 / Help comparison survive a narrow layout

Help comparison survive a narrow layout

Stacking cards preserves their content, but it makes comparison depend more on memory. Repeated attribute labels help someone connect the same detail across plans.
I would review a narrow layout with two plans that differ in one important way. If finding that difference depends on remembering an offscreen card, the comparison needs more support.
A layout can fit the screen while still making the decision harder.
03 / Make the next step honest

Make the next step honest

The domain-search field suggests a useful task, but the website in this case is a static implementation. Its destination and response need to match that scope.
The same applies to purchase actions. The page can help someone understand a plan without implying that account creation, billing and provisioning are all part of the demonstrated work.
An attractive action needs a clear destination and an accurate promise.
Open image ↗
Grid Labs public implementation, independently captured on 5 November 2026. The legacy demo retains its placeholder copy and sample claims; these are not measured outcomes. Earlier portfolio artwork is shown separately.
A commercial website and static frontend, with the focus on service hierarchy, plan comparison and maintainable page structure.

Outcomes and next steps

The work makes the plan-comparison decisions visible. It does not establish a live hosting-management, billing or provisioning service.

What I would test next

Ask a buyer to choose between adjacent plans and explain which specification drove that choice.
Repeat the comparison on a narrow screen with longer plan labels; preserve units and distinctions without requiring horizontal page scrolling.

What I learned

The label and unit beside a number are part of the comparison. Consistent detail often helps more than another highlighted specification.

About the screens

Historical design material and a dated public static-site reference. Offers may be out of date; domain lookup, billing and provisioning were not verified.

Related work and reading

RELATED EXPLORATION

Website UX and implementation

RELATED EXPLORATION

Website evaluation checklist

RELATED EXPLORATION

Technical product storytelling

Earlier portfolio artwork

Earlier owner-supplied portfolio artwork, preserved separately from the independently captured public implementation.
Earlier owner-supplied website capture; placeholder copy belongs to the source design.
NEXT FILE / YOUR PRODUCT Let’s talk

0 likes · 0 views · Nov 7, 2026

Grid Labs hosting site and static frontend: plan comparison, commercial hierarchy and domain search affordance to make plan differences clear.

Tags