Vertical CRM shape
The module set is far more tailored than a generic pipeline board and gives the case study a concrete industry angle.
Logistics and CRM/overview5 screens
FreightWorld CRM
Freight CRM spanning accounts, leads, opportunities, quotations, rates, business gained, finance, feedback, and AI insights.
Screen walkthrough
A fuller gallery for the product story.
This gallery shows progression, not just a single hero frame. Use it to talk through navigation depth, records, analytics, and workflow context during a call.
/overview
Screen 01
Primary interface capture used for the listing card and story lead.
Overview
This product is broad in the right way. It combines classic CRM primitives with logistics-specific flows such as rates and SLAs, handovers, quotations, visit planning, and business gained, which makes the product useful for telling a story about vertical software rather than a generic CRM clone.
Strongest story angle
Tell this as a commercial operations platform for freight teams where sales, service planning, and handover data live together.
Observable modules
AccountsContactsLeadsOpportunitiesVisit PlansEngagementsQuotationsRates and SLAsBusiness GainedAI Insights
Why this one works
Three angles worth carrying into the final write-up.
Commercial-to-delivery flow
Quotations, handovers, finance, and feedback suggest a system designed to carry work beyond lead capture.
Reporting and runbooks
The visible runbooks and reports help position the product as an operations system with process discipline baked in.
Motion outline
This sequence can still become a short teaser.
- 01
Open on the CRM overview with a freight-focused title card.
- 02
Highlight the path from accounts and leads into quotations, rates, and handover.
- 03
End on AI insights and reports to show management visibility on top of sales execution.
Next publishing pass
The structure is now cleaner: better screenshots, stronger conversion paths, and shared page chrome that behaves correctly. The next layer is adding repository-backed build notes and verified outcome data.
Still worth adding
- 1. Verified repository context for stack and architecture notes.
- 2. Approved proof points to replace generic performance language.
- 3. Short teaser renders once the repository evidence is in place.