For operations
Understand what needs attention, who owns the next action, and which site or asset the work belongs to.
Gridlock · Independent software product · 2024–present
Since 2024 I have independently built Gridlock as my own ERP and operations-management platform, connecting sites, assets, work orders, documents, inventory, and commercial records. I own the product and lead its vision, architecture, workflows, AI-assisted engineering direction, testing and pilot preparation. Gridlock is not a Royal Gas project or a duty of my employment there.
01 — The operating problem
A single site can have assets, inspection records, planned maintenance, open work, quotations, contracts, and invoices. When those live in separate tools, someone has to reconstruct the relationship each time a decision is needed.
Understand what needs attention, who owns the next action, and which site or asset the work belongs to.
Follow the quotation, contract, procurement, and financial records related to the work.
Maintain access, shared configuration, approval rules, and document settings as the operation changes.
02 — Product walkthrough
This representative workflow explains how the product is being organized. It connects the engineering scope to the task an employee needs to complete.
Open the site and its assets. Review the related service, documents, and operational context.
Create or review the work order, its scope, responsible team, checklists, and required materials.
Follow the configured approval or action path. Keep supporting documents and the record’s history close to the decision.
Review the resulting work status and its related inventory, commercial, or financial records where applicable.
Workflow illustration, not a production demonstration. Current work is focused on completing and validating connected user journeys for the pilot.
I define the domain models, record structures, user journeys, module boundaries, architecture, and acceptance criteria. I direct AI-assisted implementation, review architectural trade-offs, establish testing gates and prepare deployment. Professional experience informs the problems I choose to solve; Gridlock is a separate, personally owned software product.
03 — Configuration
Configuration focuses on the policies that vary between operations. The aim is to give those choices a clear administrative home and a visible effect on the relevant workflow.
Lifecycle definitions, approval steps, conditions, and the authorized actions available at each stage.
Record numbering, document templates, branding, and controlled outputs linked back to the originating record.
Roles and permissions that determine which records a person can view and which operations they can perform.
Rules for communicating changes and directing the next action to the people responsible.
Maintenance schedules, assignment rules, and the information needed to coordinate recurring work.
Related-record navigation and a timeline that helps explain what happened to a record over time.
04 — Engineering approach
The platform brings multiple business domains into a single application while keeping their responsibilities explicit. A shared application is practical for the operating environment; defined module boundaries help keep changes understandable.
Keep the page focused. An interface should express the user’s task while application logic handles the operation behind it.
Connect domains deliberately. Shared contracts make relationships explicit and reduce reliance on another module’s internals.
Make changes inspectable. Permissions, state changes, record history, and related documents belong in the review of a workflow.
05 — Product scope
As of October 2026, Gridlock encompasses 36 modules in development spanning facilities, enterprise administration, and utility operations. Each family needs a usable register, record details, editing, related records, and the actions appropriate to its lifecycle.
| Area | Connected records and tasks |
|---|---|
| Facilities & work | Sites, buildings, assets, inspections, planned maintenance, work orders, and checklists. |
| Commercial & finance | Quotations, contracts, suppliers, procurement, invoices, receivables, and payments. |
| Utility operations | Metering, delivery planning, fleet activity, and the site context behind gas services. |
| Shared administration | People, access, workflow configuration, documents, notifications, reports, and support. |
| External access | Customer and supplier journeys with access appropriate to their authorized records and tasks. |
06 — Validation & next stage
The review work focuses on discoverable registers, complete record forms, authorized actions, connected history, and clear loading and error behavior. Those are the details that make a broad platform usable.
Map product requirements to application owners and visible user journeys. Distinguish existing capabilities from work that is still incomplete.
Follow representative records through creation, changes, approvals, and related records, including permission and failure paths.
Review the installer, environment setup, sample data, and the first tasks that staff need to complete independently.
Status as of 20 October 2026: independently developed and in development, with pilot preparation underway. This case study describes the product and engineering approach; it does not claim production adoption or measured business outcomes.