Skip to content

B2B industrial

Anthro Office Systems

A B2B furniture site mapped to how procurement actually buys: a persona router, on-page spec sheets, a working workspace estimator, architect downloads, installed projects, and a minimal RFQ.

Demo build
/10-anthro-office-systems/
Orivian contribution
Full website built from zero — self-initiated, no client commission.
Site audience
Facilities managers, architects, and procurement teams fitting out offices
Pages
6 pages in the build
The Anthro Office Systems homepage: a green headline "First. And still the strongest." beside a specification panel on a white technical layout.
Demo build · /10-anthro-office-systems/ · captured September 2026

The context

What this website is for.

An office furniture manufacturer selling to facilities managers, architects, and procurement teams — readers who scan specs, self-qualify, and distrust adjectives.

The research rule on this build: if you cannot prove it, you cannot sell it. Spec tables live on the page, CAD availability is treated as most of the sale, and every page ends in one of two actions.

What the site has to do

  • Put specifications on the page instead of behind a download form.
  • Let a buyer estimate a workspace and get a budget range without a call.
  • Give architects CAD and BIM files as a first-class path.
  • Map products to the environments they are bought for.
  • Keep the RFQ form short enough that a procurement officer will finish it.

Scope

What the build covered.

Structure, content, design, and build for the whole site — the parts a visitor can see and use.

  • Homepage with persona-based routing
  • Product pages with on-page spec sheets
  • Working workspace estimator
  • Architect asset center
  • Installed work with project scopes
  • Request-for-quote form

Related services

How this translates to your project.

These are self-initiated demo builds. No client commissioned them; brands are fictional or fictionalized, and prices, hours, and metrics inside the demos are labeled indicative.

Planning a clearer, more useful website?

Describe what you are building and what needs to be clearer. The conversation starts with the problem, not with a package.

Remote · Direct · No pressure to choose the biggest package