What we will publish here, and what we will not

Most consultancy blogs are written by people who have never configured the system they are writing about. You can tell within two paragraphs: the advice is technically correct, plausible, and useless the moment it meets a real month-end.

We are starting this one on a different footing.

Who writes here

The consultants doing the delivery work — the people in the fit-to-standard workshops and on the cutover calls. Posts carry the author's name and role, so you know whether a piece comes from someone in Finance, Basis, or the service desk.

What we will publish

• Technical how-tos drawn from problems we have actually solved, with the transaction codes and table names left in.
• Delivery lessons, including the ones that cost us something to learn.
• SAP roadmap and release notes, translated out of marketing language into what it means for a company running the system today.
• Client work, when the client agrees to be named and the numbers can be evidenced.

The rule we are holding ourselves to

No figure appears on this site unless we can show where it came from.

That sounds obvious. It is not how most of this industry writes. "Reduce your close by 40%" and "99.9% availability" appear constantly, sourced from nothing. We removed exactly those claims from our own pages while building this site, because we could not evidence them.

If we quote a number here, we will say whose project it came from and how it was measured. If we cannot, we will describe what we committed to instead.

That will occasionally make our writing less impressive than a competitor's. We would rather you were able to trust the parts that are impressive.

Both languages

Everything here is published in Arabic and English. Not machine-translated — written in both, because a procedure your team cannot read is not a procedure.

If there is something you would like us to write about, or a finding you would like a second opinion on, the contact form reaches the delivery team directly.