Operational Integration Platform

The brief

The business needed a central place to manage operational tools that had outgrown spreadsheets, inboxes and manual checks. Different teams needed different views, but the data still had to connect back to core systems such as SimPRO and other business platforms.

The result was a Laravel application built around multiple Filament panels, each focused on a specific workflow: job acceptance, stock adjustments, asset management, repair syncing, report generation and system administration.

What the system handled

• Role-based access for different departments and business units.
• Dedicated Filament panels for separate operational workflows.
• SimPRO API integrations for jobs, sites, customers, schedules, stock and attachments.
• Queued background jobs for long-running syncs and imports.
• Status tracking, retry-safe processing and activity history.
• Admin settings screens so non-developers could adjust workflow behaviour.
• Reporting tools that generated documents and uploaded outputs back to the right records.

SimPRO automation

The integration work was designed around reliability rather than one-off API calls. The system used a dedicated SimPRO connector, API token authentication, rate limiting, queued jobs and application-level logs so that syncs could be monitored and retried safely.

Examples included creating jobs from external repair data, matching properties to SimPRO sites, preparing sections and cost centres, pushing completion updates, pulling job status changes, and giving users direct links back into SimPRO when they needed to inspect the source record.

Admin dashboard work

The Filament panels gave teams focused screens for the jobs they cared about. Tables included searchable job numbers, business units, project managers, stages, statuses and last-updated timestamps. Actions opened records in SimPRO, displayed activity history, triggered background jobs or moved records through the workflow.

This is the kind of admin system I enjoy building: not a generic CMS, but a practical control room for operational work.

The value

The platform reduced repeated manual checks, made exceptions visible, and gave the business a clearer picture of where jobs, stock, assets and reports stood. It also gave technical users a maintainable Laravel codebase with separated actions, services, jobs, policies and resources.

For clients, that means less time chasing information and more confidence that the integration is doing what it should.