Twenty Years of Field Knowledge, Running as Software
From vendor-locked prototype to subscription product: rebuilding Trinity’s key directory for speed, scale, and ownership.
ENGAGEMENT AT A GLANCE
Client
Trinity Locksmith Resources, the subscription key directory arm of The Locksmith Co.
Challenge
An aged third party platform that couldn’t accommodate the business or its scale
Approach
Three phases: clarify what the data means and does, design a data schema and pricing engine that aligns to the business, and execute a ground-up rebuild on a stack the client can control.
Key Results
Search results reduced from 4.0 seconds to 0.10 seconds
28,000+ data points optimized for use
Configurable price rules so that the business can move independently
INDUSTRY CONTEXT
Automotive locksmithing runs on decentralized knowledge: which fob fits a 2019 Armada, which cars need to be reflashed before key reprogramming, which decoder opens the lock, and what code series fits a vehicle.
There is no authoritative source, so the industry runs on experience. That experience has become a product, and Trinity provides access to it for its own dispatchers and field locksmiths as well as other locksmith companies who would rather subscribe than rebuild from scratch.
THE CHALLENGE
Trinity’s directory existed. It was live, it had paying subscribers, and it worked…barely.
Every constraint of the site had become a constraint on the business. Search took three and a half to five seconds per lookup, which is an eternity to a dispatcher with a customer on the phone. Subscribers could not make persistent adjustments for local pricing. Data that drove decisions in the field weren’t reflected in the architecture itself, leaving things like ‘Reflash’ warnings stuck in image captions and free-text notes where nothing could search them. There was no bulk upload, so Trinity had entered thousands of vehicles by hand, one model year at a time. The workarounds had become an accidental data model.
OUR APPROACH
Align
We started by understanding the backstory. Each workaround had a valid reason, and every one of them needed to be reflected in the new system as native function. This was not a site that needed optimizing; it was a business asset that needed to live up to its intent.
We then gathered as much supporting evidence from the original system as possible. We rebuilt the relationships from full exports of vehicles, keys, users, and media, and we screenshotted every admin and front-end screen. Because third party means third party, we needed to ensure we could build from reference rather than memory if the system was no longer available. When exports began failing six weeks later, we didn’t miss a beat.
Define
The hard part was never the catalog itself; it was the pricing.
Trinity’s owner prices from two decades of instinct. He does not mark up a flat percentage across all inventory, because a fob that costs a dollar in materials has a real price for skill to reprogram. He does not line-item labor, because the moment a customer sees the key priced separately they start sourcing their own. Rather, he prices by key type with volume tiers and programming skill factors with a different base for a duplicate than an all-keys-lost job. But he didn’t know that was his formula… he just knew the result was $130.
Nobody had ever written that down. We spent the definition phase testing against real use cases, then reverse engineered that intelligence as a rules engine rather than a spreadsheet. This mindset of defining the approach by the human workflow rather than the workaround was applied across the entire application.
Execute
The rebuild is a Laravel application with a curator’s admin panel and a subscriber-facing app; it launched in August 2026 at keys.trinitylr.com.
Migration ran through a purpose-built pipeline rather than a one-time script: a 28,000-row catalog file with traceability identifiers on every row so the owner could maintain his data in the spreadsheet he already knew while we re-imported and validated repeatedly without ever creating a duplicate. Where automation makes sense, we automated. We also updated naming conventions to ensure twenty years of knowledge populated to all the relevant products without row-by-row tedium.
Multi-tenancy, team-scoped roles, and per-user visibility controls shipped with it, so a dispatcher can see supplier part numbers without seeing supplier costs, and a dealership can be given tier pricing and nothing else.
THE OUTCOME
~4.0 s
under 0.1 s
Year, make, model catalog search time
28,000 + data points
Optimized for use in the field
6,799 vehicles
1,781 keys
Live data mapped against the NHTSA feed
Configurable Price Rules
So the business can move independently
The directory now runs on infrastructure Trinity owns, on a domain Trinity controls, and with an export button on the admin panel. Workarounds no longer define the workflow.
LOOKING AHEAD
Launch was the beginning of the client’s vision, not the end of it. The next steps are already happening throughout the new system: the real proof the model works. The pricing engine is built to move with the market, and the new architecture is built to enable the roadmap rather than require a rebuild. New tenants, new users, and new models don’t break anything, meaning our client and his customers can use the system as intended rather than struggle through it.
ABOUT ALWAYS CURIOUS
Always Curious is a strategy-led team of innovators who design and build the systems and brands that set the stage for evolution and growth. We combine technical excellence with deep attention to the human workflows and business objectives that systems exist to serve.
If you have a business running on knowledge that only lives in one person’s head — or in a system somebody else controls — reach out to [email protected].