Personally built

Nice to meet you. I’m Pieter.

At CoAchieving you work directly with me, Pieter Haijen. I investigate your question, help build the solution and check how it works. You can simply ask me why I approach something a certain way.

Pieter Haijen

Builder of digital commerce and practical AI systems

View Pieter on LinkedIn

Pieter Haijen

I like building something you keep using.

My work revolves around digital commerce, AI knowledge infrastructure and automation. What interests me is this: how do you make knowledge useful for the people who work with it every day? With traceable sources and agreements everyone understands.

I want to be able to explain what I build. It needs to be testable, well documented and clear enough to hand over. And if an existing tool is enough for now, I will tell you.

  • Facts before hype
  • Usefulness before tools
  • Small before broad
  • Handover before dependency

02 · Working together

The knowledge stays with your team.

You have direct contact with me, but the solution should also be understandable for your team. That is why I document decisions, process steps, permissions and recovery paths where needed. That handover is part of the work.

03 · Making decisions

Think carefully. Then decide.

I would rather take time for a good question at the start than for the wrong solution later. But that thinking must lead to a decision. Each phase ends with stopping, adjusting, solving something else first or building further with focus.

04 · Protecting the agreement

We agree what is included.

New ideas often emerge along the way. We then discuss straight away whether a request fits the agreement, is a small change or needs a separate follow-up. That keeps your time and budget in view.

Read how I approach a first trial

Directly with Pieter

Discuss your question with the person who will build.

Briefly describe what you want to improve. Pieter replies himself and suggests a time to clarify your question.