OBox — Pakistan
Custom CRM & Operations Platform for OBox
- On-site, two weeks
- Discovery
- Embedded build pod
- Team
- Laravel · Filament · MySQL
- Tech stack
- Live in production
- Status
Project details
The Challenge
OBox is a Karachi-based business solutions company whose internal operations had outgrown the patchwork of spreadsheets, shared inboxes and ad-hoc tools that had carried them from early days to active growth. The familiar pattern: customer information lived in three places, none of them authoritative; the sales pipeline was a tab in a shared Google Sheet; task ownership was a function of who had seen the most recent WhatsApp message. None of this was unworkable — but all of it was a brake on the team scaling.
The brief was a custom internal platform that consolidated the operational reality of the business into one place: customer pipeline, task management, internal workflows, and the reporting the leadership needed to actually see how the business was performing. Not Salesforce, not HubSpot — a tool shaped exactly like how OBox runs.
Our Approach
We started the engagement with two weeks of on-the-ground discovery — sitting with the sales team, watching how leads actually moved through the pipeline, mapping the small decisions and exceptions that any generic CRM would have hidden. The build that came out of that discovery is opinionated about OBox's workflow rather than generic.
The platform is a Laravel monolith with Filament powering the back-office surface and a focused operational front end for the sales and ops teams. Core capabilities:
- Customer pipeline — single record per customer, with the full history of interactions, documents, and the deal stages that map to OBox's actual sales motion.
- Task management — tasks attached to customer records, assigned with clear ownership, with SLAs and reminders so nothing falls through.
- Workflow automation — the small repetitive sequences that previously ate the team's time — assigning a new lead, sending a follow-up reminder, raising an internal task when a deal moves stage — automated.
- Reporting — leadership dashboards on pipeline health, team load, and conversion, built on the same data model the team works in every day rather than on a parallel BI extract.
One important call: the platform is the system of record. Where it integrates with external tools (email, document storage, the team's communication tools), the integrations are deliberately one-way enough that nobody can be tempted to treat the external tool as the source of truth. The phrase we kept repeating was "one record, one place."
Stack: Laravel · PHP 8 · Filament · MySQL · Redis, with queue workers for the workflow-automation layer.
The Outcome
The platform is live and is the day-to-day operational surface for OBox's team. The qualitative difference is the one any team feels when the spreadsheets go away: handoffs are clean, ownership is unambiguous, and leadership can see what's happening without asking three people for status. The reporting tier in particular has changed how the team runs its weekly business review.
The engagement continues — new workflows and integrations ship as the business evolves, and the platform has become the kind of internal infrastructure that the team would feel acutely if it were taken away.
Capabilities used
Services that powered this project
Next project
PAKGrocers — Karachi, Pakistan