diff --git a/eip-splitter/README.md b/eip-splitter/README.md
index 92ade7cb4..b59147504 100644
--- a/eip-splitter/README.md
+++ b/eip-splitter/README.md
@@ -11,10 +11,22 @@ tags:
 ---
 
 ## Intent
+It is very common in integration systems that incoming messages consists of many items bundled together. For example
+an invoice document contains multiple invoice lines describing transaction (quantity, name of provided
+service/sold goods, price etc.). Such bundled messages may not be accepted by other systems. This is where splitter
+pattern comes in handy. It will take the whole document, split it based on given criteria and send individual
+items to the endpoint.
 
+![alt text](./etc/sequencer.gif "Splitter")
 
 ## Applicability
+Use the Splitter pattern when
 
+* You need to split received data into smaller pieces to process them individually
+* You need to control the size of data batches you are able to process
 
 ## Credits
 
+* [Gregor Hohpe, Bobby Woolf - Enterprise Integration Patterns](http://www.enterpriseintegrationpatterns.com/patterns/messaging/Sequencer.html)
+* [Apache Camel - Documentation](http://camel.apache.org/splitter.html)
+
diff --git a/eip-splitter/etc/sequencer.gif b/eip-splitter/etc/sequencer.gif
new file mode 100644
index 000000000..a925fa209
Binary files /dev/null and b/eip-splitter/etc/sequencer.gif differ