Skip to main content

Linnoedge

Linnoedge
Back to Works
Works — Platform Development

The professionals were there.
People just couldn't find them.

A search & consultation platform connecting people with licensed professionals

Web Platform Marketplace Search Real-time Chat Content CMS End-to-end build
30+ screens
designed and built across
user, professional & admin
6 core features
search, booking, Q&A, chat,
reviews, article CMS
~5 months
from kickoff to
Phase 1 launch
Context

Finding the right professional shouldn't be this hard.

When someone has a question that really needs a professional, the hard part usually isn't the question itself. It's finding the right person to ask — and knowing whether to trust them.

Licensed professionals are out there. But for an ordinary person, the path to reaching one is scattered across word of mouth, directory sites that barely explain anything, and a first phone call that feels like a leap. On the other side, professionals who would happily take on the right cases have no simple way to be found by the people who need them.

The client wanted to close that gap with a single platform: search for a professional, ask a question in the open, consult privately, read up first, and decide with some basis. Not a directory with contact details bolted on — a place where finding, asking, and choosing all happen in one flow.

The professionals were there. People just couldn't find them.

Challenge

It looked like a directory. It wasn't.

The brief arrived as something close to "a search site for professionals." Simple enough on the surface.

Two very different people had to feel at home in the same product: someone anxious, looking for help they can trust — and a professional deciding whether this platform is worth their time.

The moment you take both seriously, a "directory" isn't enough. A worried first-time user needs to search, read, ask in the open, and message privately before they commit. A professional needs a profile worth being judged on, a clean way to field questions, and reviews that mean something. Those are two products sharing one system — and the architecture had to be designed for that from the start, not patched on later. We also had to keep Phase 1 deliberately focused, so the core loop — find, ask, consult — could be proven before anything heavier was layered on.

Craft

The decisions behind the build

Linnoedge handled the whole thing — requirements definition, design, architecture, implementation, testing, and delivery. Not a slice of it. All of it — thirty-plus screens, two public roles, and an admin console.

We started before a line of code, by aligning on what we were actually building. A completed-image video, a requirements document, and a WBS gave the client something concrete to react to — so "is this what you meant?" got answered in week one, not at acceptance testing. Weekly check-ins, with the work tracked openly in a shared board, kept everyone looking at the same reality.

Honestly, the hardest part wasn't the code — it was the distance. The work sat several layers down a contracting chain, and the people who actually knew what the product should be were not the people we talked to every day. That gap is where projects quietly go wrong: a requirement everyone assumed was obvious, never said out loud, surfacing only at acceptance. So we over-communicated on purpose — the completed-image video, the written spec, the WBS, the open board — not to look organized, but to surface every silent assumption early, before it turned into rework.

Two roles, one system

General users and professionals see different things, but draw on the same data. We designed the account model so each role gets a tailored experience — search and consultation for users, profile and inbound questions for professionals — within a single Laravel codebase, not two parallel apps to keep in sync. The public Q&A board and private real-time chat run on the same identity and permission layer, so a message is always tied to the right person, in the right context. Behind both, an admin console handles moderation — Q&A, reviews, users, and professionals — from one dashboard.

Search that answers a real question

The point of search here isn't "return a list." It's "help an anxious person narrow down to someone they can approach." Region-based filtering, readable profiles, and reviews were built to work together, so the result of a search is a decision the user feels okay about — not just more options to sort through.

A small Phase 1, on purpose

Phase 1 was deliberately scoped. Get the core loop right — search, read, ask, consult — prove it works, and only then layer on the heavier pieces: scheduled paid consultations, the admin tooling, the rest. Shipping a focused first phase beats shipping a bloated one that never gets used.

For general users

Find a professional
by area, then decide

Users search by region and browse profiles that actually explain who each professional is. Filters narrow the field; review scores add a second signal. The goal of every search is the same — turn "I don't know who to ask" into "I'll reach out to this person."

Ask & consult

Ask in the open,
or talk in private

Two ways to reach a professional. A public Q&A board lets anyone ask a question and read past answers — useful before you've decided who to approach. The public board stays open to read before you commit; private chat — and booking a scheduled consultation — carry the conversation forward when you're ready.

Read & choose

Learn first,
then judge with a basis

A managed library of professional articles — organised by category and filterable — lets users get oriented before they ever reach out. Reviews of professionals add the social signal that a plain directory lacks. Together they turn a cold search into an informed choice. Professionals, in turn, get a profile and a body of work worth being found for.

Change

Before → After

BeforeAfter
Finding a professionalWord of mouth, thin directory listingsRegion search with readable profiles
First contactA cold phone call, all or nothingPublic Q&A, private chat, and scheduled consultations
Deciding who to trustNo signal beyond a nameArticles to learn from, reviews to weigh
For the professionalHard to be found by the right peopleA profile and inbox built to be discovered

Phase 1 was delivered and accepted, with the core experience working as intended. The platform was built to grow — the next phase has somewhere solid to stand on.

Linnoedge

Requirements, design, build, test & delivery

Process

How the project ran

1
Kickoff
Align scope & team
Faces, roles, and how we'd work — settled up front.
2
Define
Requirements
A completed-image video, a written spec, and a WBS to react to.
3
Build
Design & development
Both roles built around one system, tracked in the open.
4
Test
Acceptance testing
Client feedback worked through, item by item.
5
Ship
Delivery
Phase 1 delivered and accepted.
Tech Stack

Technologies used

PHP Laravel MySQL Redis Laravel Echo (WebSockets) Laravel Scout (Search) Blade Docker

Building a platform with two sides?

Let's talk about your version of this.

30 minutes. No cost. Comes with a written next-step summary.