(slide 1)

Intro..

(slide 2)

When you are the company owner , you have to fix the most critical bugs first. On a large project, when there are hundreds of bugs, it becomes harder to keep track of just how much money company loses because of bugs.

(slide 3)

To give you an idea of what I'm talking about, imagine you are a company owner and:

- Think about all the people who didn't subscribed to your newsletter because of broken captcha.
- Think about all the orders your online shop didn't received because customers abandoned your complex checkout form

There are many similar situations where you, as a business owner lost the potential revenue because of simple bugs or user experience issues you missed to spot.

(slide 4)

Here comes the SmartLogger which will help you track and analyze the bottlenecks of your online bussines. As soon as you integrate SmartLogger into your application, bug errors will start flowing in on one of the channels and at the end of the day, you will have a clear overview of potentially most expensive bugs & bottlenecks of your application.

Let me show you how all this looks like in a quick Demo.

(slide 5)



------------------------------------

(Open dashboard)

First thing we see on the dashboard is a list of Channel. each channel has the TMS value which determines how much revenue a company has lost because of the bugs that flow in this channel.

Let's take a closer look at this channel.

(Open channel page)

Here we see the analytics of this channel, on the right pie chart we see that there were 3 type of bug logs sent and the quantities were equal. However on the left chart we see that bug related to Timeouts made up 87% of company's loses so this is the bug that should be fixed as top priority. Finding bugs like those is what SmartLogger is all about.

Down on the page we have a list of all logs sent to this channel, we can filter by those and check their meta data for additional details

(slide 6)