marp exists to move organizations as one.

Different disciplines. One perspective.

My experience has moved across research, finance, business analysis, and building technology. Each discipline brings a different responsibility: asking better questions, finding the signal in complex information, understanding how decisions create value, and turning an idea into something people can use.

That combination shapes how I approach marp. I look at the business, the people doing the work, and the systems around them together.

Valuable work should not get stuck.

marp grew from seeing the same problem from different angles: valuable work gets trapped between people, inboxes, spreadsheets, and systems. Information exists, but the next person still has to find it. A decision is made, but the work still waits to move.

I wanted to connect that work in a way that respects how a business actually operates. Its language. Its rules. Its people. The details that make one organization different from another.

That is the idea behind marp: software infrastructure that connects systems, data, and workflows around the organization they serve. A more connected way of working, with people in control of consequential decisions.

A vision has to work in the real world.

My name is behind the work.

Today, marp is a team of four. I want you to know who we are and what guides our decisions. Trust starts with that visibility, and it grows through the work itself.

My standard is to understand the operation, be clear about what we are setting out to improve, and measure what changes. Prove one workflow. Learn from it. Earn the right to expand.

Our focus is gas and electric, healthcare, and engineering. Each has its own responsibilities and ways of working. The opportunity is to connect the systems inside those industries, so people have more room to lead, solve problems, and move their organization ahead.

marp reflects the way I see that future: ambitious about what is possible, and disciplined about how it becomes real.