02 / Business Websites

Project Meridian

Concept Project

A logistics business website concept that turns a complex service offer into a clear journey from discovery to a structured first brief.

Current record state

Authentic concept case study / verified interface evidence

Production-rendered interfaces and documented technical checks support the implemented journey. No operating logistics or commercial outcomes are claimed.

Project Meridian concept homepage with logistics route graphics, service pathways and a visible concept disclosure — Production-rendered concept interface. Project Meridian is an independent design and engineering project, not an operating logistics company.

01 / Business context

Turning a complex logistics offer into a clear first journey.

Meridian explores how a B2B logistics website could move from service discovery to a structured first brief without pretending to quote, track or operate a real shipment.

The concept is written for decision-makers assessing freight coordination, warehousing and fulfilment, or distribution support. They need to describe an operating requirement—not browse consumer parcel products.

The project objective is to reduce ambiguity before a first commercial conversation. That intended benefit has not been measured, and Meridian has no customers, shipments, locations, traffic, enquiries or commercial results.

Diagram showing a business website connecting service discovery, trust and fit assessment to a structured brief — Design explanation: the website is treated as part of the commercial journey, not as a passive company profile.

The information hierarchy answers six practical questions

01
What does the service cover?
02
Which operating situations might fit?
03
What information is needed?
04
What happens after the brief?
05
What remains illustrative?
06
What will the concept do with submitted data?

02 / Website system

Specific service pathways carry the trust work.

The navigation progresses from discovery to evaluation and action. Trust comes from clear service language, a visible process, explicit boundaries and a coherent interface—not fabricated scale, logos or testimonials.

Project Meridian freight coordination service detail page with service scope, route diagram and enquiry actions — **Service discovery**Freight coordination is presented as a distinct pathway with its own scope, operating questions and next action.

Project Meridian process page showing a staged logistics planning and handoff sequence — **Process and trust**A staged process explains how a requirement could move from brief to planning and handoff without claiming an active logistics operation.

03 / Qualified brief

Progressive questions prepare a more useful first conversation.

The implemented six-step brief collects service choice, business context, operating requirements, the current problem, desired outcome, contact details and consent before a grouped review.

Six-step qualification flow from service selection and business context through operating requirements, priorities, contact details and review — Implemented capability: a six-step sequence with grouped review. Its effect on completion or lead quality has not been measured.

Initial Project Meridian logistics brief step asking the visitor to choose a service pathway — **A small first decision**The first step asks for a relevant service pathway before the form requests detailed operating context.

Grouped Project Meridian logistics brief review populated with clearly synthetic example details — **Review before submission**The review capture uses synthetic example data. It demonstrates grouping and correction—not a real enquiry or customer.

04 / Evidence and decisions

The proof is technical, responsive and bounded.

The supplied evidence supports an implemented interface and local verification record. It does not support production operations, field performance or commercial outcomes.

Formatting and analysis

Prettier, ESLint and strict TypeScript passed.

Unit and component checks

45 tests passed across 13 files.

Production-browser checks

13 Playwright checks passed; one capture-only check was skipped by default.

Production build

The reviewed build generated 24 routes.

Earlier local, unthrottled observations recorded mobile LCP at 584 ms with CLS 0 and desktop LCP at 700 ms with CLS 0. These are laboratory observations—not field Core Web Vitals, a production service level or evidence of conversion improvement.

The reviewed dependency graph retained one documented moderate Next.js-to-PostCSS advisory path. It was accepted after reachability analysis; the source package does not describe the graph as audit-clean.

Narrow Project Meridian interface with a persistent concept disclosure and responsive single-column layout — **Responsive honesty**The interface reflows for narrow screens while the concept disclosure and author attribution remain visible.

Decisions and trade-offs

A structured brief instead of a generic lead form

The six-step sequence keeps the first choice small, then collects the operating detail needed for a more useful later conversation.

Trade-off: The journey asks for more attention than a short contact form. Its value is a product hypothesis, not a measured conversion result.

Operational diagrams instead of logistics clichés

Routes, nodes, handoffs and planning grids explain coordination without stock freight photography, fake maps or invented scale.

Trade-off: Code-native graphics stay lightweight and editable, but deliberately avoid photographic realism.

Inactive side effects in the concept

A valid brief is acknowledged honestly while persistence, email and CRM remain off. The concept cannot imply operational follow-up.

Trade-off: A provider-independent MongoDB adapter is prepared but has not received a credentialed staging integration test.

What this project demonstrates

Translating a commercial problem into information architecture, a conversion journey, responsive interfaces, a validated full-stack form flow, security-conscious boundaries, accessibility behaviour, search planning, automated tests and implementation documentation.

Related service

Have a related business problem?

This record is transparent about its current evidence. Your project can begin with the problem you are trying to solve.

Discuss a project Explore Business Websites