diff --git a/readme.md b/readme.md
index f0fc425..90f777e 100644
--- a/readme.md
+++ b/readme.md
@@ -9,4 +9,11 @@ This is a .NET clone of the very simple but super useful [github email reply par
 ```c#
 var parser = new EmailReplyParser.Lib.Parser();
 var reply = parser.ParseReply("I get proper rendering as well.\r\n\r\nSent from a magnificent torch of pixels\r\n\r\nOn Dec 16, 2011, at 12:47 PM, Corey Donohoe\r\n<reply@reply.github.com>\r\nwrote:\r\n\r\n> Was this caching related or fixed already?  I get proper rendering here.\r\n>\r\n> ![](https://img.skitch.com/20111216-m9munqjsy112yqap5cjee5wr6c.jpg)\r\n>\r\n> ---\r\n> Reply to this email directly or view it on GitHub:\r\n> https://github.com/github/github/issues/2278#issuecomment-3182418");
-```
\ No newline at end of file
+```
+
+## SigParser - Email Parsing as a Service
+
+If you need better results, [SigParser](https://sigparser.com/try?aff=ericjwhuang) offers an always evolving API for splitting email reply chains. As email clients change, the headers and footers of emails will often change which means static code libraries need to evolve. SigParser keeps updating their algorithms as new scenarios are encountered. Additionally, SigParser is stateless so they don't store any of the email.
+
+You can test [parsing emails](https://sigparser.com/try?aff=ericjwhuang) by copying and pasting an email message and seeing the API response. 
+