Founder-led. Vendor neutral.
Bounded by design.
Shopstead is not a consultancy that hands you recommendations and walks away. The same person who diagnoses your operation stays involved through implementation, testing, documentation, training, and the final handoff.
Operating principles
Founder-led delivery
Derek Rinehart is the founder and principal. He stays involved in every engagement from diagnosis through handoff. This is operational, not marketing — the same person who maps your system configures it, tests it, and trains your team to run it.
Vendor neutrality
There is no preferred software stack. We start from the business problem and the existing workflow. We may recommend keeping what you have, removing a tool, changing a process without buying anything, connecting existing systems, or buying something new — only when a proven gap requires it. The only metric that matters is whether your operations are more reliable after the engagement ends.
Bounded engagements
Every project has a defined scope and finish line. No open-ended retainers disguised as deliverables. If the scope needs to expand, it becomes a new engagement with its own finish line.
Solve one meaningful problem at a time
We do not try to fix an entire company in one engagement. We identify a bounded operational problem, solve it completely, prove it works, and exit. If there is more work, we scope it separately.
Where the operating bias comes from
Before Shopstead, Derek spent 16 years as an air traffic controller. That background shaped a set of operating principles that run through how every engagement is approached. Not a heroic biography — a working bias toward reliability.
Operating principles carried into Shopstead
OWNERSHIP
Every piece of work has one explicit owner. Ambiguity about who is responsible is a failure condition, not a flexibility.
KNOWN STATE
System state is visible and current. If you cannot see where every work item is, the system is degraded.
HANDOFFS
Transfers of responsibility are explicit and confirmed. A handoff is not complete until the receiver acknowledges it.
EXCEPTIONS
Exceptions are expected, documented, and have defined escalation paths. Surprises are a design failure.
REdundancy
Single points of failure are unacceptable. Critical functions have a backup path that works without heroics.
PROOF BEFORE TRUST
Systems are tested under real conditions before they are trusted. A workflow that works in a drawing is not a workflow.
The goal is the same: systems that continue to work while people are busy, systems that do not depend on one person knowing everything, systems where the handoff is reliable and the state is visible.
Want to talk about your operational challenges?
The first conversation is about fit and scoping. If we are not the right match, we will say so.
Start a Conversation