Project Overview
Arbor — Concept Build: B2B Expert Marketplace
Arbor is an internal H Product Studio concept build — a design and architecture exercise, not client work. The brand and all screens are fictional.
It works through a two-sided B2B marketplace: growth-stage companies on one side, independent senior consultants — strategy, finance, growth — on the other.
The framing question is a practical one: companies want senior-level expertise faster and cheaper than a full-time executive hire, so what would the platform need to own? Discovery, matching, contracts, and payment orchestration — the concept maps all four. None of it represents live operations.
The imagined buyer is a seed-to-Series-C team pulling in outside expertise for fundraising, market entry, RevOps, due diligence, or hard product calls.
Concept Questions Explored
Every services marketplace risks decaying into a thin directory. The build treats trust signals, expert positioning, and operational workflow as one design problem instead of three afterthoughts.
Premium expert positioning (illustrative direction)
What earns high consultant rates on a platform? Deep profiles, case metrics, credentials, and an editorial brand register — deliberately unlike a commodity talent site. Illustrative direction only.
Multiple acquisition paths
Homepage, expertise pages, industry pages, consultant profiles, and use-case landings all function as entry points — and each had to land a visitor without losing the thread.
Marketplace operations as one system
Matching is the easy part. Contracts, messaging, dashboards, role switching, project posting, and payments have to feel like one operating product, or both sides churn.
Concept Approach
Arbor sits deliberately between premium consulting-firm branding and modern SaaS product design — an editorial-tech register. Every design decision here is exploratory.
Authority-first information architecture
Each surface — expertise page, industry page, use-case landing, consultant profile — is built as its own acquisition channel with a distinct buyer intent behind it.
Marketplace product system (conceptual)
Public marketing routes, application flows, and dashboard environments connect as layers of one system rather than a pile of screens. Structure only, no delivered implementation.
Controlled premium visual language
Warm off-whites, serif-led type, mono labels, and a restrained violet accent aim for an interface that reads serious and considered — zero startup noise.
Speculative Platform Architecture
One route architecture carries three very different jobs: public acquisition, transactional marketplace workflow, and role-based dashboards. This is the conceptual map, not a shipped system.
Key Product Modules (Concept)
Public Marketplace Layer (concept)
The front door: introduce the model, build trust fast, and route visitors toward consultants, expertise areas, industries, and use cases. Illustrative screens only.
Acquisition by Expertise
High-value needs become dedicated landing pages, so a buyer searching for one specific kind of help lands on exactly that page.
Operational Marketplace Flows (sketched)
Both sides of the network get real workflow: companies post projects, consultants apply through an onboarding and verification path, and execution surfaces carry the engagement.
App Shell and Retention Layer (concept screens)
Dashboards and workspaces are what keep a marketplace from being just a lead form — the concept sketches the delivery side too. No live data, no real consultants.
Design System Direction
Visually the study balances premium advisory branding against structured SaaS usability. All design tokens shown belong to the study, not a live product.
Prototype Stack Used to Assemble This Study
Concept Direction
The direction Arbor lands on is closer to an operating system for expert engagements than to a commodity freelancer marketplace.
On paper, it joins acquisition pages, profile credibility, marketplace operations, and dashboard tooling into a single structured platform direction.
It also sets up the harder downstream questions — matching logic, contract-flow integrations, payout orchestration, SEO expansion across expertise and industry clusters — all of which would be validated in a real engagement.
Concept-build note: this study is a speculative H Product Studio exploration. The Arbor name, screens, consultant profiles, testimonials, metrics, and third-party services shown are illustrative. Nothing on this page represents a delivered product, a real user base, or an active service.
Arbor Concept Screens (Illustrative)
Interested in a Similar Marketplace Build?
If a two-sided marketplace is your actual product direction, this is the scale of thinking we bring into a scoped engagement. This page itself is a concept build, not a productized offer.
