About Snag Labs
Built by technologists. Grounded by operators.
We understand software because we build it. We understand operational pain because we have lived it.
Where we come from
Four founders, four fields, and not one of us came to operational friction through consulting. We hit it in our own work first: in the software we shipped, on the projects we delivered, in the contracts we signed, and in the systems the day-to-day ran on.
One of us owns and runs a retail and wholesale franchise today: payroll, staffing, suppliers, thin margins, and customers who walk out if you get it wrong. Others have helped run family businesses across convenience and fuel, grocery, automotive services, and agriculture. That is a different kind of knowledge from having advised on it.
So a problem gets looked at from four directions before anyone proposes a fix. Often the most useful thing we can tell you is that the software is not your problem.
What guides the work
- Diagnose before prescribing
- Outcomes before technology
- Human judgment before AI hype
- Practicality before complexity
- Speed without recklessness
- Custom without unnecessary overhead
- Maintainability and scalability, not just a launch date
- Transparent advice, even when it means recommending less
- Respect for your existing team and your budget
- No pressure to buy implementation after the audit
The founders
Four people who notice different things.
Software & AI
Builds software and leads the teams that build it. Spends most of that time on the part people touch, and on the harder question underneath it: whether a problem needs new technology at all.
Infrastructure & project delivery
Plans and delivers large physical projects, from civil works to energy infrastructure. Knows what it takes to keep many trades, dependencies, and approvals moving toward a date that cannot move.
Procurement, contracts & risk
Sources and negotiates the supplier relationships a business runs on, and governs the risk that comes with them. Also owns and runs a business, which means sitting on both sides of the same contract.
Industrial data & materials
Works with the data underneath industrial operations. Knows how quickly records drift out of step with the physical world, and how much of that cost shows up somewhere else entirely.
We introduce ourselves by discipline rather than by name, and we don't name current or former employers here. Some of us hold senior roles elsewhere and keep those separate from this. You will meet whoever is working on your engagement, by name, from the first conversation.
What we won’t do
Being commercially smart doesn’t mean being aggressive about it. A few things we hold ourselves to:
- Sell you a platform before we understand the problem
- Push AI into a process where a simpler tool would do the job better
- Leave your team dependent on us to make a basic change
- Recommend implementation you didn’t ask for after the audit
- Pretend a system has no maintenance cost when it does