diff --git a/README.md b/README.md
index 409575c2..5386f0c1 100644
--- a/README.md
+++ b/README.md
@@ -7,6 +7,41 @@ JavaScript related workloads required by Web Developers nowadays.
 It's the explicit goal not to measure I/O or other non-JavaScript
 related tasks.
 
+## Philosophy
+
+I love the web! I love working on [Chromium](http://www.chromium.org) - more
+specifically on [V8](http://v8project.org) - to make the web even better! But
+building the best browser is only a small piece of the puzzle. I see browsers
+as similar to TV screens: They provide you with the *frame*. Having an awesome
+TV screen is nice, but doesn't buy you anything if there's no content and no
+one providing the infrastructure to deliver the content.
+With the web it's very similar, and so for the continued success of the web
+it's important to not only focus on the browser, but also support the
+content producers in the best way we can to ensure that we continue to have
+great websites with interesting content. V8 is in a kind of unique position
+here at this point in time, since it doesn't only power all Chromiun based
+browsers, but also powers [Node.js](https://www.nodejs.org), which in turn
+provides the runs a lot of the enterprise services today, but even more
+importantly powers almost all the tooling used to create the web experiences.
+
+And this tooling (plus the support story around it) is one of the critical
+factors for companies when choosing a platform. The web platform today has
+an amazing set of tools, a very active community around most of them, which
+makes the web attractive as the main platform for so many companies. Besides
+several other aspects, it's important that these tools run reasonably fast.
+For example for developers that use [test-driven development
+(TDD)](https://en.wikipedia.org/wiki/Test-driven_development) it's crucial
+that the tests execute quickly. Or when using
+[TypeScript](https://www.typescriptlang.org) for development, it's important
+that the type checking and compilation to JavaScript doesn't take too long,
+especially when combined with a test-driven work-flow.
+
+Driving progress on the engine related aspects of the web tooling is the
+main motivation behind this benchmark suite. It tries to isolate the
+JavaScript heavy workloads from the most common tools used by the web
+platform. Specifically I/O and other non-JavaScript related aspects are
+excluded from the measurement.
+
 ## Test suite
 
 The test suite currently contains: