Trevor Amundrud

Contact / Start with the problem

Discuss an operational problem

If your business has a workflow that feels unnecessarily difficult, a process heavily dependent on manual work, or a system that is no longer supporting the operation effectively, I am interested in hearing about it.

You do not need to know what the solution is. That is often the point of the first conversation.

01 / A useful starting point

Good reasons to get in touch

You may have:

  • A process that relies heavily on spreadsheets or manual work
  • An operational problem that keeps returning
  • A software implementation that is not working as expected
  • A reporting or data problem
  • A transportation or warehouse process that needs redesign
  • An automation opportunity you are unsure how to approach
  • An AI use case that needs to be evaluated realistically
  • A business process dependent on one person's knowledge
  • A system-selection or implementation project
  • A problem that does not fit neatly into any of those categories

02 / Send a message

Tell me a little about it

Required fields are marked with an asterisk. Do not include confidential customer, route, or personal information.

You do not need to provide a complete project brief. A short explanation of what is happening and why it matters is enough.

20–3,000 characters. Avoid sensitive operational data.

Prefer another contact method? Email [email protected] or connect on LinkedIn.