The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
I developed Movam to bring customer ordering, merchant fulfilment, rider dispatch, and platform administration into one application.
I built the backend with Laravel and REST APIs, alongside Vue.js and TypeScript dashboards for customers, merchants, riders, and administrators.
Key features include:
Product browsing, cart, checkout, and order management.
Paystack payment integration, wallets, and OTP-verified withdrawals.
Dispatch logic that assigns deliveries to nearby available riders.
Mapbox integration for location services and delivery-distance calculations.
WebSocket events for order status and rider location updates.
Merchant product management and administrative reporting.
The project demonstrates my ability to translate business workflows into connected interfaces, backend services, and third-party integrations.
Tools: PHP, Laravel, Vue.js, TypeScript, Tailwind CSS, Pinia, Laravel Sanctum, Laravel Reverb, Paystack, and Mapbox.
Combining ordering, fulfilment and dispatch in one app probably trims a lot of manual steps. Laravel APIs feeding Vue TypeScript dashboards keep the data moving smoothly across customers, merchants and riders.
Exactly, that was the goal with Movam. Connecting ordering, fulfilment, and dispatch gives customers, merchants, and riders a shared view of each order, with less back-and-forth between them. The interesting challenge was making each dashboard useful for that person’s role while...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Leads pre-qualified before a human touched them.
Every one scored and routed the moment they finished chatting, not after someone got around to it.
→ Curious what this looks like for your site? Message me.
Having the lead score appear instantly after chat ends removes the waiting gap before a rep can act.
The bot once scored “just browsing” as hot.
Early scoring leaned too hard on page visits alone someone reading the pricing page out of curiosity got flagged as ready to buy. Rebuilt the scoring around actual answers, not just clicks.
→ A page visit is curiosity. An answer is intent. They're not the same signal.
Switching the model to weight answers over page views really separates curiosity from intent, so you catch the buyers before they slip through.
How a visitor becomes a scored lead in one chat:
1. A few natural questions instead of a form
2. Intent scored from the answers, not just the page they landed on
3. Hot leads routed to sales instantly, cold ones nurtured automatically
→ Want this running on your site? Happy to walk through it.
Swapping the form for a quick chat that scores intent really cuts the friction before a lead hits sales. Instant routing of hot leads while the rest get nurtured is a solid flow