From a87392b1d63c35719f549424ce56a65ffe08eece Mon Sep 17 00:00:00 2001
From: Dan-inpooling <47202702+Dan-inpooling@users.noreply.github.com>
Date: Fri, 2 Aug 2019 15:35:06 -0700
Subject: [PATCH] Update README.md

---
 README.md | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 81de6dc..b869d9f 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,17 @@
 # ApiGov
-API data governance tool that captures client API calls, visualize and monitor data flows
+API data governance tool that captures client API calls, visualize and monitor data flows.
+
 Refer to our [Architecture doc](./doc/architecture.md) for more details.
+
+# Why is this tool useful?
+
+
+# Why do we create this tool?
+In the past couple of years, we saw increasing usage of 3rd party APIs. Also, more and more data are shared via APIs.
+
+In my previous job doing cyber security risk consulting, I saw companies lacking visibility around data shared via APIs. With GDPR and CCPA, it is becoming mandate for companies to have data governance around their APIs.    
+
+My co-founder has extensive experience is DevOps and software development. He wanted to have a tool for client API monitoring, beyond exgress logging. He was constantly fighting with client API outages and could not optimize the API usage based on needs.
+
+We are both excited to build a tool that can log API calls, visualize API data flows, send alerts for outages and suspicious data flows.
+