Skip to content

Project story · Community services platform

MentorNet

Making a community exchange platform searchable and understandable.

MentorNet gave a community a structured place to publish needs, offer services, search activity, and understand the exchange model behind the platform.

MentorNet community platform with publication search and service categories

From the Runnable archive

The interface reflects the project’s era. The story focuses on the business and product decisions that still matter.

Sector
Community services
Product
Multi-user platform
Scope
Search · Publishing · Accounts

The context

MentorNet

A service-exchange community has a different challenge from a conventional directory. People need to understand the model, describe what they offer or need, find relevant activity, and participate through an account.

MentorNet translated those community rules into a navigable platform with publication search, service categories, member access, and clear routes into contributing or asking for help.

What Runnable delivered

Making a community exchange platform searchable and understandable.

01

Structured publication search

Keyword, category, and location filters helped members move from a broad community to relevant activity.

02

Community publishing model

Needs and service offers were organised as content that people could browse, understand, and act on.

03

Member and account journeys

Account access, participation guidance, and community navigation supported the platform beyond anonymous browsing.

What shaped the work

How a searchable community platform organised service exchanges, requests, categories, and member activity.

  1. 01

    Search before browsing

    A multi-sided platform becomes useful when people can narrow activity to their own need.

  2. 02

    Make the model visible

    The exchange mechanism and community vocabulary have to be understandable before participation.

  3. 03

    Design for contribution

    Publishing and account journeys matter as much as the public content people discover.

What carried forward

Custom software succeeds when the rules become clear actions.

Platforms often begin as a set of organisational concepts: members, categories, requests, offers, regions, and exchange rules. The interface has to turn those concepts into a path a new person can follow.

That remains a core Runnable approach to custom software: learn the operating model first, then make each role and next action visible in the product.

Have something in mind?

Let’s turn it into the next useful thing.

Bring the problem, the rough idea, or the current system. We will help define a practical next step.

Start a conversation