diff --git a/README.md b/README.md
index c4a51952..369bf6f8 100644
--- a/README.md
+++ b/README.md
@@ -2,6 +2,64 @@
 
 # NServiceBus.IntegrationTesting
 
-Experiments with NServiceBus integration testing , for more information refer to my [Exploring NServiceBus Integration Testing options](https://milestone.topics.it/2019/07/04/exploring-nservicebus-integration-testing-options.html) article.
+NServiceBus.IntegrationTesting allows testing end-to-end business scenarios, exercising the real production code.
+
+## tl;dr
+
+NServiceBus.IntegrationTesting enables a test like the following one to be defined:
+
+```csharp
+[Test]
+public async Task AReplyMessage_is_received_and_ASaga_is_started()
+{
+   var theExpectedSagaId = Guid.NewGuid();
+   var context = await Scenario.Define<IntegrationScenarioContext>()
+      .WithEndpoint<MyServiceEndpoint>(g => g.When(b => b.Send(new AMessage() { ThisWillBeTheSagaId = theExpectedSagaId })))
+      .WithEndpoint<MyOtherServiceEndpoint>()
+      .Done(c =>
+      {
+         return
+         (
+            c.HandlerWasInvoked<AMessageHandler>()
+            && c.HandlerWasInvoked<AReplyMessageHandler>()
+            && c.SagaWasInvoked<ASaga>()
+         )
+         || c.HasFailedMessages();
+      })
+      .Run();
+
+      var invokedSaga = context.InvokedSagas.Single(s => s.SagaType == typeof(ASaga));
+
+      Assert.True(invokedSaga.IsNew);
+      Assert.AreEqual("MyService", invokedSaga.EndpointName);
+      Assert.True(((ASagaData)invokedSaga.SagaData).SomeId == theExpectedSagaId);
+      Assert.False(context.HasFailedMessages());
+      Assert.False(context.HasHandlingErrors());
+}
+```
+
+(Full test [source code](https://github.com/mauroservienti/NServiceBus.IntegrationTesting/blob/master/src/MySystem.AcceptanceTests/When_sending_AMessage.cs) for the above sample is available in this repo)
+
+The above test does quite a lo of things, but the most important ones are:
+
+- it's exercising the real production endpoints
+- it's asserting on the end-to-end choreography, for example it's checking that a saga was invoked and/or a message handler was invoked
+
+When the test is started, it sends an initial `AMessage` message to trigger the choreography, and then it lets the endpoints involved do their job untill a specific condition is met. In this sample the `done` condition is quite complex:
+
+- An couple of handlers and a saga need to be invoked
+- Or there are failed messages
+
+*NOTE*: Endpoints in the samples contained in this repository are using RabbitMQ as the NServiceBus transport, LearningPersistence as the persistence mechanism. Tests are using docker-compose to make sure the required infrastructure is made available to endpoints exercised by tests.
+
+## How to install
+
+Using a package manager add a nuget reference to [NServiceBus.IntegrationTesting](https://www.nuget.org/packages/NServiceBus.IntegrationTesting/).
+
+## Background
+
+For more information on the genesis of this package refer to the [Exploring NServiceBus Integration Testing options](https://milestone.topics.it/2019/07/04/exploring-nservicebus-integration-testing-options.html) article.
+
+---
 
 Icon [test](https://thenounproject.com/search/?q=test&i=2829166) by Andrei Yushchenko from the Noun Project