SKIP TO CONTENT
5SHIRY
START A PROJECT
  • LIVE
  • CLIENT / SELECTED WORK
  • NSH-01
  • Real estate

Nushin Real Estate

An agent-brand platform for a Berkshire Hathaway HomeServices salesperson in Northern California.

nushinrealestate.comSTATIC CAPTURE — PREVIEW UNAVAILABLE
Nushin Real Estate homepage as it renders on a desktop browser, captured from the live site
PREVIEW UNAVAILABLEOPEN LIVE SITE ↗

Real desktop capture of nushinrealestate.com, taken . This site sends security headers that prevent embedding. Open it directly instead.

ROLE
UI/UX · Frontend · Backend · Admin
OWNERSHIP
Client project
SYSTEM
Agent site, listings, communities, admin portal
STATUS
Live
01 / OVERVIEW

A personal-brand platform for Karim Nushin, a licensed California salesperson operating under Berkshire Hathaway HomeServices Elite Real Estate. The site has to satisfy two audiences at once: buyers, and the sellers deciding who to trust with a listing.

Client work. The brokerage brand sits alongside the agent’s own, and the design had to respect both without letting either disappear.

02 / PROBLEM

Agent websites usually inherit a brokerage template, so every agent in the region looks identical and the one thing that actually sells — the individual — is reduced to a headshot in a sidebar.

Structurally, they also funnel everyone into one path. A buyer browsing communities and a seller weighing an appraisal need different information, different proof, and a different first click.

03 / SOLUTION

A cinematic property-led entry that puts the agent in front of the visitor immediately, then splits into separate buyer and seller journeys. Listings, communities, and a newsletter carry the ongoing relationship; an admin portal keeps it all editable.

  • Full-bleed property hero with agent identity card
  • Separate Buyers and Sellers journeys
  • Community and neighbourhood pages
  • Listings with search and enquiry handling
  • Blog and newsletter for ongoing contact
  • Admin portal for listings and content
04 / MY ROLE

Client work, held to the same standard.

Different ownership, identical process. The admin side matters as much as the front.

UI/UX

Two journeys designed separately, then reconciled into one navigation that does not overwhelm a first-time visitor.

BRAND HANDLING

Brokerage identity and agent identity in one header, with a clear hierarchy so neither cancels the other out.

FRONTEND

Full-bleed property imagery, responsive at every breakpoint, fast on a phone in a driveway.

BACKEND + DATABASE

Listings, communities, posts, and enquiries as structured data rather than hand-built pages.

SEARCH + DISCOVERY

Community-first browsing, because buyers choose an area before they choose a house.

ADMIN PORTAL

The agent updates listings, communities, and posts without calling me. That was a requirement, not a nice-to-have.

05 / TWO JOURNEYS

Buyers and sellers want opposite things.

Most agent sites put everyone through one funnel. Splitting the entry point at the top was the single highest-leverage structural decision on this project.

BuyersBROWSE FIRST

A buyer is not ready to talk. They want to look, narrow down an area, and understand what their money buys before they identify themselves.

  1. Enter through a property or a community
  2. Browse listings and neighbourhood detail
  3. Save interest, subscribe to the newsletter
  4. Contact when they are actually ready
SellersPROOF FIRST

A seller is interviewing the agent. They need evidence, process, and a person — fast — before they will hand over a listing.

  1. Land on credibility: agent, brokerage, licence
  2. Understand the selling process end to end
  3. See comparable local activity
  4. Book a direct conversation
06 / SYSTEM INSPECTION

For the technical reader.

STACKNSH-01
FRONTEND
Next.js · React · responsive imagery
BACKEND
Node · Postgres · listings and content models
ADMIN
Custom portal — listings, communities, posts, enquiries
INTEGRATIONS
Email delivery · newsletter · enquiry routing
INFRASTRUCTURE
Vercel · managed Postgres · CDN imagery
07 / PROCESS EVIDENCE

Only the parts worth showing.

Marked slots below — drop in real screens, admin captures, or diagrams and this section carries the case study on its own.

DROP: journey map
P01Journey splitThe structural decision the whole site rests on: two entry paths, one navigation.
DROP: header explorations
P02Identity cardHow agent and brokerage coexist in one header without a hierarchy fight.
DROP: community page comps
P03Community pagesBuyers choose an area first, so the area page is a first-class destination.
DROP: admin portal capture
P04Admin portalThe agent edits listings and posts directly. No developer in the loop.
08 / OUTCOME

The agent runs the site himself — listings, communities, and posts go up without a developer, and buyer and seller enquiries arrive already separated.

Published performance figures are being measured properly before they go on this page. When there are numbers worth defending they will appear here — sourced and dated.

OPERATIONAL STATUS
Deployment
Live
Content updates
Agent-managed
Enquiry separation
Buyer / seller
Published metrics
Client-held
OPEN THE LIVE SITE ↗
09 / NEXT

Need a platform your team can actually run?

The front end is the part people see. The admin behind it is the part that decides whether the site stays current.

START A PROJECT ↗OPEN LIVE SITE

5SHIRY · NSH-01 · CLIENT / SELECTED WORK/work/nushin-real-estate