About

Operator-built systems, not lab theory.

Heuris exists because real casework exposes the same pattern again and again: capable people lose time when the workflow behind them is weak.

Who I am

I've spent over 20 years in security, intelligence, and investigations.

Executive protection. Surveillance. Threat analysis. Work across five continents, in environments where mistakes matter.

I've worked with:

  • private clients
  • corporate teams
  • government environments

Different settings. Same reality.

If the system behind the work is weak, the outcome suffers.

Featured by Business Insider.

What I have seen

Many operational problems are not caused by lack of effort. They come from weak structure.

I've seen:

  • investigations that produce reports but no answers
  • security teams reacting instead of anticipating
  • operations relying on individuals instead of systems
  • time and budget wasted on work that goes nowhere

Good people, weak structure. That is the pattern Heuris is built to fix.

What I do differently

I do not approach this as a detached consultant.

I approach it as someone who has been in the field.

That changes the design standard.

I look at:

  • how work actually happens
  • where information gets lost
  • where decisions break down
  • what needs to be structured

Then I fix the system behind it.

Why the system matters

Most people focus on results. But results come from structure.

If:

  • logs are weak
  • reports are inconsistent
  • intelligence doesn't carry forward

Then it doesn't matter how good the investigator or operator is.

The system limits them.

Fix the system, and everything improves.

Where this led

That is how everything here started.

Not from an abstract product idea. From a repeated operational problem.

InvestigOR was built to fix investigation workflow.

Other systems are being built for the same reason.

Different roles. Same issue.

No structure behind the work.

How I work

Direct and practical.

No long performance around the problem. No unnecessary layers.

You explain the situation.

I break it down and tell you what matters.

If it makes sense, we go deeper. If not, you move on.

What you can expect

  • Clear thinking
  • Honest assessment
  • Practical solutions
  • No unnecessary complexity

If something doesn't add value, it's not included.

What this is not

  • Not theory
  • Not recycled frameworks
  • Not corporate consulting

Everything here is grounded in real work.

If the workflow problem is real, let's look at it.

You will get a direct assessment and a practical next step.