Amaanullah Khan - PHP & Laravel Developer | Karachi, Pakistan

Amaanullah Khan

PHP & Laravel Developer

Also: Flutter mobile apps

Karachi, Pakistan
4.8 ★ Google Rating 17 verified client reviews

PHP & Laravel developer in Karachi - custom CRM, SaaS & enterprise web apps for global clients.

Download CV

Ticketing CRM - Advanced Job & Vendor Management Portal

Client Field Operations Client (Confidential)
Category CRM & Enterprise Systems
Duration 5+ months
Status

Project Overview

The Business Problem

Field operations teams were managing jobs, vendor assignments, SLA deadlines, and payment approvals across email threads, spreadsheets, and disconnected tools. Managers had no single source of truth — status updates were delayed, vendor context was lost, and missed deadlines were discovered too late to recover.

The business needed one enterprise portal where jobs move through defined stages, vendors are matched and assigned efficiently, SLAs trigger automatic escalations, and every conversation stays attached to the correct job record for audit and dispute resolution.

Solution Overview

I built the Laravel backend for a Ticketing CRM Portal that connects the full job lifecycle — from discovery and vendor alignment through completion and payment approval. Operations teams, vendors, and administrators each get role-based views with the data they need and nothing they should not see.

The system replaces email-chain chaos with structured workflows: every job has a status pipeline, assigned vendors, SLA timers, threaded contextual chat, and approval gates managers can action from one dashboard.

Architecture & Key Modules

Job lifecycle pipeline. Configurable stages from intake through vendor assignment, work in progress, review, and closure — with status history and timestamps.
Vendor matching module. AJAX-powered search with filters for skills, region, availability, and historical performance — shortlisting vendors in seconds instead of manual database lookups.
SLA orchestration engine. Cron-driven deadline checks with automated priority badges and escalation triggers as milestones approach — reducing missed deadlines before they happen.
Contextual threaded chat. Conversations scoped by job ID and vendor ID, permanently linked to the ticket — full audit trail for payment and dispute resolution.
Payment approval workflow. Role-based approval gates so managers verify vendor work and context before releasing payments — no more approving requests with missing information.
Admin oversight dashboard. Aggregated views for operations leads: overdue jobs, SLA breaches, vendor workload, and pipeline bottlenecks in one place.

My Role

On this enterprise operations project, I designed the database schema, built the SLA engine, vendor matching logic, approval workflows, and contextual chat integration. My focus was backend architecture and business logic — ensuring the system handles real operational load with clean permission boundaries.

Results

Operations teams gained a 70% reduction in missed SLA milestones, faster first-time-right vendor assignments, and tamper-proof conversation history tied to every job. The portal became the daily workspace for field operations — not a side tool. Related services: custom CRM development and business process automation.

Ready to achieve similar results?

Let's discuss how we can build a similar high-performance solution for your business.

Discuss a Similar Operations Portal

Strategic Execution & Challenges

SLA Orchestration Without Manual Escalation

The Challenge

Multi-stage job deadlines across discovery, vendor alignment, and payments were tracked manually — missed milestones were caught too late.

Strategic Solution

I built a cron-driven SLA engine with automated priority status updates and dashboard badges triggered as deadlines approach.

Impact / Result

70% reduction in missed milestones and instant visibility for tasks requiring immediate manager intervention.

Contextual Chat Linked to Jobs & Vendors

The Challenge

Email threads made it impossible to verify approval context — conversations were disconnected from specific jobs and vendor records.

Strategic Solution

I integrated threaded chat scoped by job_id and vendor_id directly in the job view, with attachments stored on the ticket record.

Impact / Result

Tamper-proof audit trail for payment approvals and faster dispute resolution with full conversation context.

Intelligent Vendor-Job Matching

The Challenge

Finding suitable vendors by skills, region, and availability across a large database was slow and inconsistent when done manually.

Strategic Solution

I developed an AJAX vendor matching module with paginated filters and performance history — shortlisting vendors in seconds.

Impact / Result

Improved first-time-right vendor assignments and reduced navigation time for operations teams handling high job volume.

Technology Stack

Laravel PHP 8+ MySQL AJAX Cron/SLA Engine RBAC REST APIs

What This Project Proves

Enterprise operations do not need another generic project management tool — they need software shaped around their vendor network, SLA rules, and approval chain. This ticketing CRM shows how a Custom CRM Laravel build replaces fragmented workflows with one auditable system.

If your team still runs jobs through email and spreadsheets, a portal like this cuts friction fast. Contact me to discuss a similar field service or vendor management system.

Impact & Performance

70% reduction in missed SLA milestones Efficiency & Performance improvement
Faster vendor-job matching & audit-ready workflows Growth Potential & Scalability Boost

Project Technical FAQ

What does this ticketing CRM manage?

Jobs, vendor assignments, SLA deadlines, status pipelines, contextual chat, and payment approvals — the full field operations lifecycle in one portal.

How does SLA tracking work?

A cron-based SLA engine monitors job stage deadlines and triggers automated priority updates and dashboard alerts as milestones approach — before breaches occur.

Is vendor communication auditable?

Yes. Chat is scoped by job and vendor ID and stored permanently on the ticket — managers see full context for every approval and dispute.

What stack was used for this portal?

Laravel and PHP 8+ with MySQL, AJAX for vendor search, cron jobs for SLA checks, and RBAC for role-based views across operations, vendors, and admin.

Who is this type of system built for?

Field service companies, facilities management, logistics coordinators, and any business that assigns external vendors to jobs with SLA and payment accountability.
Select Solution Type
Custom CRM / HRM
Lead Management System
Workflow Automation
SaaS Development
Other Business Solution

Amaanullah Portfolio

Install for a premium experience