I'm a
I'm designing for

oi.fi

Oiva Isännöinti — dense service homepage when nothing can be deprioritized

Whole site· Other· resources Some· Established

Screenshot of oi.fi

Why it works

Great example for those massive service sites that have literally hundreds of semi-important links and pages and when the client's web project team doesn't have the ability or will to imply that some departments are more important than others, so we need to link to so many things on the front page. Oiva's public homepage surfaces resident tasks (documents, move-in, renovation notice, fault report, sauna booking, and more) alongside board/offer CTAs without pretending one path owns the page.

What I'd steal

A front page that honestly carries many equal-weight service links when the org will not rank departments; keep resident self-serve actions visible without burying the "compete our property management" path.

What I'd never do

Forcing a single "primary" department hierarchy the client team will not stand behind — on sites like this the honest dense link set is the brief.

For assistants / Brush

{
  "id": "oi-site",
  "title": "Oiva Isännöinti — dense service homepage when nothing can be deprioritized",
  "domain": "oi.fi",
  "url": "https://oi.fi/",
  "anchor": null,
  "kind": "site",
  "sectionType": "whole-site",
  "industry": [
    "other"
  ],
  "clientProblems": [
    "buried-next-step",
    "unclear-offer"
  ],
  "buyerGoals": [
    "conversion",
    "enterprise-ready"
  ],
  "resources": {
    "overall": "some"
  },
  "companyStage": "established",
  "verdict": "approved",
  "added": "2026-11-02",
  "lastChecked": "2026-11-02",
  "screenshot": "/images/entries/oi-site.webp",
  "example": false,
  "tags": [],
  "whyItWorks": "Great example for those massive service sites that have literally hundreds of semi-important links and pages and when the client's web project team doesn't have the ability or will to imply that some departments are more important than others, so we need to link to so many things on the front page. Oiva's public homepage surfaces resident tasks (documents, move-in, renovation notice, fault report, sauna booking, and more) alongside board/offer CTAs without pretending one path owns the page.\n",
  "whatIdSteal": "A front page that honestly carries many equal-weight service links when the org will not rank departments; keep resident self-serve actions visible without burying the \"compete our property management\" path.\n",
  "whatIdNeverDo": "Forcing a single \"primary\" department hierarchy the client team will not stand behind — on sites like this the honest dense link set is the brief.\n"
}

entries.json · llms.txt