<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anallytica on Medium]]></title>
        <description><![CDATA[Stories by Anallytica on Medium]]></description>
        <link>https://medium.com/@anallytica?source=rss-2a82722a64eb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Er0oa_2mANhoYm8lkvukYA.png</url>
            <title>Stories by Anallytica on Medium</title>
            <link>https://medium.com/@anallytica?source=rss-2a82722a64eb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:44:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anallytica/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Predictability of possible churns. How do we do it?]]></title>
            <link>https://anallytica.medium.com/predictability-of-possible-churns-how-do-we-do-it-d11883970734?source=rss-2a82722a64eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d11883970734</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[churn-prediction]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Anallytica]]></dc:creator>
            <pubDate>Thu, 17 Jun 2021 08:45:41 GMT</pubDate>
            <atom:updated>2021-06-17T08:45:41.318Z</atom:updated>
            <content:encoded><![CDATA[<p>We, product owners and/or founders of B2B startups know how difficult it is to bring a new customer in. Often the sale is not simple, the closing cycle is long, and/or the average ticket is high, which requires many decision-makers to “hit the hammer” when buying a new tool: in contrast to losing a customer, there is only bad service, a critical error in production, or a false selling argument that doesn’t actually exist.</p><p>Currently, only recurring new revenue isn’t enough to attract new investors and to have a steady, sustainable growing company: If your churn is above the 5% home, we have a problem.</p><p>We’ve already talked in another article about this: the weight of churn isn’t just in the income you missed. If a customer hires you, they have the pain you show. If you do not resolve, your competitor will. You have had a huge effort to bring a new lead, a job of the sales team to training and onboarding him in your solution — now it will be polite and prepared for your competitor. This without counting that, depending on frustration, this churn might speak badly of your company in the market, to peers of it who could buy from you, and if it’s someone market influent the noise will be even bigger/worse.</p><p>Do you want this for your company? I’m sure not. So why not invest in the quality of your active customer base, pro-activity customer contact, and predictability of customers who may churn based on historical behaviors?</p><h4><strong>We have the light at the end of the tunnel!</strong></h4><p><strong>Anallytica</strong> was born with the goal of helping companies build better software and make their users love it! Our purpose goes beyond monitoring NPS, DAU/MAU, and engagement data: we know the behavior of your users and know the health of each of them.</p><p>Each user within <strong>Anallytica</strong> has their own score that is updated in real-time based on 3 indicators vs. a weight each has. These are days of not accessing the software, NPS note, and events within your product (this has an essential role in this quality of the foundation and you can understand a little more about it in <a href="https://anallytica.medium.com/events-understand-everything-that-happens-in-your-product-1fb50d2ffe16">this link</a>).</p><p>Based on behaviors set by you we understand which customers are likely to cancel or not and show you this on a priority list about which to approach first. And the coolest: if set up correctly, we also show this information with the value of MRR next door, so you prioritize users who pay more!</p><p>And with this information in hand, we also know which users are super engaged with you — a super opportunity for an upsell! :)</p><h4><strong>And when we talk about predictability, we want to be assertive indeed!</strong></h4><p>The health of your base has been working since day 1 of <strong>Anallytica</strong> — and with that, you can already turn on the light of the room on everything that happens to your active user base. But we want more!</p><p>We are building functionality to capture all of your churned users (whether retroactive or today).</p><p>With this, we will understand the key behaviors that caused that user to cancel, to understand what pattern of behavior leads a user to this. So when a new user achieves this bad behavior the grade of it slows down dramatically and it gets a priority on your list!</p><h4><strong>And this is simple to set up!</strong></h4><p>If you as an <strong>Anallytica</strong> user are already monitoring the events, you already have the health function of the base available to you. We want you to build better products, that your users love, and that mostly stay with you. May they are promoters and that by referral basis, bring you new and good deals!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d11883970734" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Events: understand everything that happens in your product!]]></title>
            <link>https://anallytica.medium.com/events-understand-everything-that-happens-in-your-product-1fb50d2ffe16?source=rss-2a82722a64eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fb50d2ffe16</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Anallytica]]></dc:creator>
            <pubDate>Thu, 10 Jun 2021 09:48:21 GMT</pubDate>
            <atom:updated>2021-06-10T09:48:21.260Z</atom:updated>
            <content:encoded><![CDATA[<p>Yes, we spent some time with no new posts — but for a great reason. Like every company in an early stage, there’s more work than people to accomplish it. And with us it’s no different, deep down we can say, this huge amount of work is what motivates us.</p><p>In recent months, we have been focused on coddling some features to be part of our product core and being ready for the official release. We are still in the beta phase, validating ideas, conversations with users, and quick direction changes.</p><p>Now, we are getting closer and closer to going to the market, indeed. Like our plans, August 02 will be our official launch and we are very pleased with this. But, holding up the excitement of this special moment, I bring you our last feature before launch. This one will completely change our product and how you manage yours.</p><h4><strong>Event monitoring!</strong></h4><p>Both the legacy of your product and new features require a critical eye on them. Whether it’s to understand behaviors, generate improvements, or even predict a customer`s cancellation — this is our event monitoring goal!</p><p>By a simple setup in your product, through our code, you are able to monitor any users movements that make sense in your strategy.</p><p>Based in a new feature launch as an example, you obviously want to know which users, use that feature the most (or less). How many times is it used per day/week/month. What times it is used more. Which users use it the most.</p><p>Those information can provide you insights to improve your product. For example, if a feature has been used with VERY frequency by its user base, any simple tuning in it can create an overload on your support team. Or even your users’ lack of interest in your product. Don’t you believe it`s better to know who are the users who use that feature the most, talk to them, understand any movement in it and/or any improvement, release in a cadenced way and, after successfully validating, drop this to everyone at your base?</p><p>This is what event monitoring is about. Without visibility, you’ll hardly get the right things right for your product. Any decision made without a database is a shot in the dark — which can often hit an innocent without the intention.</p><h4><strong>And installing it is very simple!</strong></h4><p>With the <strong>Anallytica</strong> script installed correctly in your product, just call a simple function of ours on your front end that everything will work properly.</p><p>See the example:</p><blockquote>anallytica.event(3, ‘save-new-user’, { plan: ‘Basic’, cs: ‘leo@anallytica.com’ });</blockquote><p>How does this work? Note that we have 3 setups in our function: a number, a text and an object.</p><p>That is when this is configured in key places in your product, the more points the user wins lowest is the possibility of a churn. This scale has 5 different numbers: 3, 2, 1, 0, and -50.</p><p>From 1 to 3 are features that generate more and fewer points, according to what is essential for your SCORE. The score of 0 does not directly influence the score, but can be used as a LOG within the user and in automation in <strong>Anallytica</strong> (which we will talk about further in this article). And the -50 is a critical score that dramatically decreases your user’s score — we can use this when a user goes on a cancel page, for example. If he got there, it wasn’t just out of curiosity, right?</p><p>Our second parameter, the text is just the identifier of what that event is: save-new-user, update-client, delete-email, etc… here you configure according to what the event is monitoring. Remembering that when you’d better write this title, it’ll be easier for you to keep up with this within our product.</p><p>And lastly, an object field where you insert any custom information from that event, using this for filters in the future. In the above example, I’ve gone through my user’s Plan and Customer Success that serves that account, so I’m able to get a big detail of which plans take more or fewer actions.</p><h4><strong>What will the future bring us using events?</strong></h4><p>Let’s imagine a scenario where you own financial management software and you know that an engaged user is the one who does 40 events a month of new launches on your platform. With this monitored, inside <strong>Anallytica</strong> I can filter, for example, all users in the last 30 days who did NOT do 40 events from new expenses. Or users who over the past 60 days have made more than 80 points, generating a list of possible customers to upsell.</p><p>Our part of automation in the future will be amazing. With everything set up within your product we have the possibility to build whatever you want, according to what you want and what makes sense to you.</p><p>According to X events in X days, we can create a new list (updated in real-time), send an email to the account’s Customer Success, trigger an event via Webhook for a Slack, for example. The possibilities of the future are endless.</p><p>And for sure, we don’t just stay at the events. Why not combine events with non-use days with NPS notes and any URL that was accessed on such day? This is because we haven’t even talked deeply about our Health Score yet (next post, I promise!)</p><p>This is our next step. Where we are working now. Event monitoring is on the street. You can already configure it. Automations are in the oven and I’ll soon bring this novelty to you guys, with a lot of pride and excitement!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fb50d2ffe16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The filter viewing is going to give you relevant insights!]]></title>
            <link>https://anallytica.medium.com/the-filter-viewing-is-going-to-give-you-relevant-insights-7ad6fd1f09f?source=rss-2a82722a64eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ad6fd1f09f</guid>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[filters]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[nps]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Anallytica]]></dc:creator>
            <pubDate>Tue, 06 Apr 2021 14:03:01 GMT</pubDate>
            <atom:updated>2021-04-06T14:10:05.622Z</atom:updated>
            <content:encoded><![CDATA[<p>In our last post, we brought a new way to analyze the health of your base through the NPS: <a href="https://anallytica.medium.com/checking-nps-per-contract-length-5594c0619ec0"><strong>by active contract time</strong></a>.</p><p>In addition to this, we must not forget the importance and relevance of an analysis by other filters that are important to you, such as plan type, account responsible customer success, MRR, and even country/region.</p><p>Monitoring the NPS in a generalist way will bring to you, a view of your database as a whole, but often the problem is in one of those filters in particular — which, by consequence, will affect your KPI overall!</p><h4>Let’s talk a little more about…</h4><p>You started last month to monitor product usage KPIs, access peak by weekday and time, and, of course, NPS.</p><p>They all go according to market standard metrics, minus the NPS that insists on staying between 10 and 20 — what kind of action do you take when this information arrives?</p><p>When you don’t have a granularity of information that makes it easy to create custom filters, you won’t be able to take any action. You can bring your customer success team closer to your customers, you can create product news webinars, you can strengthen your message in Marketing, but in the background, all this will be a shot in the dark because you won’t be shooting where the problem really lies.</p><h4>Filters, Filters, Filters</h4><p>In another case of NPS monitoring with <strong>advanced filters</strong>, you can now do a comparison such as:</p><ol><li>What is my NPS per plan type?</li><li>Which regions/countries have the highest NPS?</li><li>Do any Customer Success have the NPS far above the others?</li></ol><p>-</p><p>For each of these 3 questions, we have 3 possibilities:</p><ol><li>If you have two plans, a Free plan and a Paid one and, making the filter for them you note that the NPS from the <strong>Free plan is far below the Paid plan</strong>, we found a problem: the client who doesn’t pay is a <strong>Detractor</strong>. In this case, the actions taken can be varied such as strengthening communication in onboarding new customers, having a human contact a few days after the account is created, analyzing possible product errors for this plan, and even, in more extreme cases, removing your company’s Free plan if it no longer makes sense;</li><li>Some regions and/or countries need more attention than others. For example: Latin countries like more of a human contact than a “self-service” software. Therefore, why not change the form of care for specific countries and/or regions?</li><li>Here we don’t want to look “guilty” for being with a low NPS and pointing fingers, but rather the other way around: understanding which Customer Success is having greater success and using it as a benchmark, strengthening a culture of information sharing with the entire team. Surely other CS also do an amazing job that can further help the CS that is already performing above average. Remember: we do not want to blame, we want to bring up the reality, <strong>with data</strong>, we can make the best decisions and, based on that, everyone wins!</li></ol><h4>Don’t forget the before and after</h4><p>When an indicator is monitored it is legal to keep in mind where we want to get to and often track progress.</p><p>On these examples above, if we realize the Free plan had an onboarding adjustment in March looking at the rise of the NPS, we will follow in April how this indicator will be in order to have a successful comparison or not.</p><p>If so, we were successful, great… let’s go to the next indicator that will be adjusted. Otherwise, we go back to the bunker, analyze what went wrong in this little project, adjust and go to the market again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ad6fd1f09f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Checking NPS per contract length]]></title>
            <link>https://anallytica.medium.com/checking-nps-per-contract-length-5594c0619ec0?source=rss-2a82722a64eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/5594c0619ec0</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[nps]]></category>
            <dc:creator><![CDATA[Anallytica]]></dc:creator>
            <pubDate>Mon, 22 Feb 2021 14:01:16 GMT</pubDate>
            <atom:updated>2021-02-22T14:01:16.569Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*r-80KNbqWOZrOwyekLqRVQ.png" /></figure><p>It is common for us to create several different ways to analysing an indicator. With NPS, for sure, it would be no different.</p><p>Generally speaking, NPS is installed within the software, sent via email or SMS, and measured in a generic way. After some time, when the demands get a little more advanced and filters come in: we commonly look at the type of plan, customer success that takes care of the account, region, MRR, etc… the filters and forms of analysis are countless (and amazing).</p><p>But what we want to address here is another type of NPS analysis: by active contract time.</p><h4>But at the end of the day, what is this?</h4><p>First, let’s understand what this means: active contract time is how long your customer is active, how many months/years he is a customer (whether paying or not).</p><p>We like to analyze this indicator here in Anallytica because it gives us a vision of when, and in how much time, your customer base is satisfied and/or not, so, being able to generate an action on this, whether in product or processes.</p><p>For example: if we analyze the company “X” and its customers that are active from 1 to 12 months, we note that from the fourth to the sixth month the NPS drops from an average of 40~50 points to 0~20 and then back up to 30. We can see that the highest value delivered to customers is at the beginning of the software experience and delivery, but after a few months all this value is no longer seen, or for whatever reason (company / product / delivery) is no longer generating so much attractiveness for users to come back, indicate to friends, etc…</p><p>In this case, it is a fact that an active communication action needs to be initiated in the third month to prevent this fall from happening — starting always as a preventive work so it never turns reactive.</p><p>This also can be an example for cases where the NPS score is low in the first months. The user only starts to see value after some time. This gives us insights that:</p><ol><li>implementation was slow and costly;</li><li>the product takes a long time to “heat”;</li><li>the product is complex and difficult to understand:</li><li>lack of communication as videos and supporting articles;</li><li>there are few features that bring the initial experience in a better way.</li></ol><p>All NPS analysis depends, of which issues you want to solve or attack. In this example above, we talked about long-term customer experience, focusing on an increase in LTV or even a reduction in early churns.</p><h4>One thing does not invalidate the other</h4><p>This type of analysis is one of the many ways we can look and analyze NPS. Segmented filters are great tools for insights to understand that, plan type A or B needs more attention, countries with a more direct culture need less human contact, or the other way around — Latin countries usually buy products from other people, which requires close, humanized service…</p><p>Data analysis is a passion we have at <a href="http://anallytica.com/"><strong>Anallytica</strong></a> and that we are taking to the world. Often data doesn’t tell us what we want to see, and to do that, studying and being close to your customers is critical, essential.</p><p>Normally the data only confirm our beliefs, which we have no way of “proving” to others. In this way, we prove with data, make the best and most right decision, avoiding walking with a compass inside a dark room!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5594c0619ec0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do not kill the Messenger]]></title>
            <link>https://anallytica.medium.com/do-not-kill-the-messenger-8be618573e3b?source=rss-2a82722a64eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/8be618573e3b</guid>
            <category><![CDATA[nps]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Anallytica]]></dc:creator>
            <pubDate>Mon, 01 Feb 2021 18:40:41 GMT</pubDate>
            <atom:updated>2021-02-01T18:41:34.490Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/539/1*Bb95x2S2rrrSS1ZZwsj7dQ.png" /><figcaption>Anallytica’s NPS Report</figcaption></figure><p>It’s a fact that in our diverse customer base we have promoters, detractors, neutrals; large, medium, and small customers; different countries and/or regions and, for sure, different opinions about our product.</p><p>When software companies start growing, this kind of diversity gets bigger and as result, some complaints begin to appear — with more or less energy. In early stages of the company, the investments end up being in marketing and sales or in product and technology, and the support moves to a second stage.</p><p>Thus, these complaints end up falling into a ditch and the most common is to hear: “this user complains too much all the time and is using our product wrongly, let’s cancel your account and stop wasting time with it because we can serve a lot more customers if this one goes away.” Right?</p><h4>Do not kill the Messenger</h4><p>Certainly, the problem that this customer is reporting is the problem of others as well. Whether it’s lack of service, lack of supporting content (knowledge base, educational videos, etc.) or product bugs — which is extremely normal at every stage of a company.</p><p>The fact is that we cannot ignore the richness of this information. You “Dismissing” this customer because of his “boring” behaviour, you’ll stopping receiving the biggest gold you can receive: <strong>your company’s real-time feedback as a whole</strong>. If you kill in the root the most important messenger, you will be losing revenue and building a wrong product, to the wrong audience, with the wrong message.</p><p>The “<em>messenger</em>” in this case complains because he loves and needs his product. He has the pain you propose to solve. It is telling you problems that other customers have and often do not report.</p><p>Customers with the same problems and who are silent, are the ones who will surely churn and you don’t know the reason. They’ll be educated by you, they’ll have the pain, they know the use process you’ve taught them and come ready for your competitors.</p><p>Knowing how to hear these customers with more complaints is an exercise of patience, for sure, but it will bring you direct and indirect benefits, such as:</p><ol><li>You will revert this client from a detractor to a neutral (or even a promoter);</li><li>He is going to tell about you to new customers;</li><li>You are going to correct process and/or product that are causing trouble to your base as a whole;</li><li>You will avoid unexpected churns;</li><li>Your satisfaction index will increase!</li></ol><h4>The way your company handles the “messengers” reflects the company culture</h4><p>If you, as a manager and/or founder of the company, apply the culture of dismissing those customers, don’t hear feedback, and live complaining about your active base, your followers will do the same and your service score will be horrible.</p><p>Create a culture of proximity to the foundation, be close to your first customers, and listen carefully to what detractors want to tell you. A well-served customer is worth 2, a poorly served customer is worth 10!</p><p>The culture of taking care of the foundation, being kind and attentive to customers, making your experience the best possible end-to-end is a job of the company as a whole. Charming your customers begins in the first marketing sentence until the greeting of a response on service tickets.</p><p>We should have the patience and calm to serve the hardest customers to have a peace in the future, a scalable product and a satisfied customer base, indicating you to new partners, increasing your retention and your LTV, with a practically null CAC.</p><p>Here at <strong>Anallytica</strong> we like to be close to our customers, help them build their products better, more scalable, with an extremely satisfied customer base, and of course help ourselves make <strong>Anallytica</strong> better. We are always in touch with our first customers, doing research and talking to people on the market so that constancy makes us a company of excellence in everything we propose to do. Whether it’s the content we post here on the Blog, whether it’s in our products or in our service.</p><p>We’re starting our first tests in <strong>February 2021</strong> (and many happy about this) and if you’re interested in getting to know more than we’re doing, <a href="https://docs.google.com/forms/d/1tg2DbKke2bMdxWxETb0Rt9tCr3QbnP-oyUdhvunFA-U/viewform?edit_requested=true">sign up for this link</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8be618573e3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do not be indifferent with your NPS]]></title>
            <link>https://anallytica.medium.com/do-not-be-indifferent-with-your-nps-406d1d476e8c?source=rss-2a82722a64eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/406d1d476e8c</guid>
            <category><![CDATA[nps]]></category>
            <category><![CDATA[software-kpis]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Anallytica]]></dc:creator>
            <pubDate>Mon, 18 Jan 2021 14:06:02 GMT</pubDate>
            <atom:updated>2021-01-18T14:06:02.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*iryKoXaTJpnCqi_MI-p94g.jpeg" /><figcaption>Anallytica’s NPS</figcaption></figure><p>Typically, when we start tracking a KPI, whether it’s product, financial, or operational, we want to get some insight from it. Whether it’s to find potential operations issues, to avoid revenue loss or possibilities for improvement across the company as a whole.</p><p>What would lead you to follow an indicator such as NPS without an action plan defined for it?</p><p>NPS tools mostly require investments (whether large or small) of intellect and time. You invest in hiring the tool, implementing time, and managing it. Why not make this investment get the expected return?</p><h4><strong>The feared scores between 0 and 6</strong></h4><p>A CRITIC has already talked bad things about your company to the market. Your customers communicate to other business partners and other professionals in the field. This information runs fast and soon a poor assessment becomes true for others and even potential customers. Acting quickly and in a humanized way is an excellent way to follow.</p><p>Avoid creating automations for CRITICS. Everything he doesn’t want, and needs is an automated email with no customization, asking if everything is fine. For sure it is not and with this automation, frustration increases, and give the feeling you don’t care about it.</p><p>One way forward would be the searching, internally with the service team if that account was in trouble in the last few days. Examine how long she has signed up with her company and other relevant information, and then send a personalized email, pointing for some issues that you have identified and, if possible, could combine a call to handle the issues.</p><p>If the call is accepted, you are prepared and ready with solutions (or directions) to the problems you have identified in that account.</p><p>Keep in mind that the customer almost always is already not satisfied with your product and the NPS reflects a churn that will come. The constancy in the contact with your customer base is important. Don’t leave to relate to them when you’re in trouble.</p><blockquote><strong>The key to big results is CONSTANCY.</strong></blockquote><p>Of course, with the scale service challenges grow and for that, tools like <strong>Anallytica</strong> exist. Knowing who is using little and/or wrong your product directs you to talk to customers who have a higher churn trend.</p><p>New companies have the advantage of being close to the early-adopters and learning from them. Create a high frequency of relationship and invest from the start in fulfilment tools so when that scale happens you’re ready. Great service compensates for product failures or a lack of functionality.</p><p>Do not forget that the NPS is the one who collects the results, but that the notification is not directly related to the product. If by a chance you are having problems charging with undue amounts, the NPS will reflect it.</p><blockquote><strong>NPS is a company effort as a whole!</strong></blockquote><h4>But not everything is just bad scores!</h4><p>Within a diverse base of active customers, you will have bad fit, different sizes customers, people of different cultures. An electronic newsletter that contains many unnecessary information, may be missed by less direct cultures in their communication.</p><p>In this world of diversity, PROMOTORS are your largest asset. Treat them as you would like to be treated (btw, this with everyone!).</p><p>Your promoters are your biggest sellers. Generating a lead through referral is the hottest lead you will have. Bring this to real life and you will understand: the best people you know or will meet to make friendships and/or partnerships will come from nominations. If your company is awesome, your customer will generate value for another friend by telling you.</p><p>In the business world, there is a lot of talk about building relationships and networking, and here it’s no different. Happy customers will promote your business and as result bring more revenue!</p><p>Ask the promoters for information. Invite them to unique events and to be beta-testers of functionality that will be released soon. The sense of priority and exclusivity will make him even happier with you.</p><h4>Be careful with the Neutrals</h4><p>The NEUTRALS are on middle of the wall and may fall to the side of satisfaction or to the side of public detraction. We do not want that. If possible, take all actions commented on here. Study it and invite him to a rich conversation of information. Invite you to unique events and maintain a relationship with them.</p><p>We all like to be heard and to know that our opinions are valuable. Listen to everything he has to say. Learn from him. If it makes sense for you and your business, act and communicate!</p><p>If your product has been contracted, there is a pain that needs to be resolved. Helping you with your frustrations has advantages for both sides: you strengthen your close relationship with customers who can tell you in the future, increase the satisfaction level of your active customer base, avoid revenue loss and detraction for others in the marketplace — and most importantly, your customer has the pain resolved!</p><p>To build products that people love, we must combine: data analysis x talk with customers x strategic market vision.</p><p>There is no way to measure in % which of the 3 is more important. These variants change according to business model, market size, product type, and so on. With clear indicators and a not of feedback from your base, you break down your chance of error, you can deliver more value with less feature, and forget what we’ve talked about here before, the “<em>spray and pray</em>”.</p><p>The constancy in the actions brings results. Increased NPS is a work that requires effort and long-term dedication.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=406d1d476e8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we’re born and what we do!]]></title>
            <link>https://anallytica.medium.com/why-were-born-and-what-we-do-2134b485b6e8?source=rss-2a82722a64eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/2134b485b6e8</guid>
            <category><![CDATA[nps]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[anallytica]]></category>
            <dc:creator><![CDATA[Anallytica]]></dc:creator>
            <pubDate>Thu, 31 Dec 2020 12:37:06 GMT</pubDate>
            <atom:updated>2021-01-12T13:06:23.546Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why were we created and what do we do!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3uDJfViDa7kpZ5J2gAqslw.png" /></figure><p>Today, who writes here, the first post of our blog, is <a href="https://www.linkedin.com/in/ahmfidelis/"><strong>Henrique Machado</strong></a>, co-founder of <strong>Anallytica</strong>. I want to share with you the vision, present and future of this recently founded company (December 16th, 2020).</p><p>In recent months, we have been thinking a lot about the impacts of SaaS companies with an increasing number of new sales, but with an engineering/product team that is not compatible with this demand. In addition to a small Customer Success team for the size of the active customer base.</p><p>We can list here the main impacts in the customers working process:</p><ol><li>If sales are not made at a good cadence during the month, the support team is overloaded with a hight number of new demands through the end of the current month and the beginning of the next one;</li><li>The customer has a bad experience because they were not able to receive the human support to use the product;</li><li>The product has no investment in improvements (whether performance or usability) and customer experience is undermined;</li><li>With this, the product team always works on the legacy, with little time to think about new improvements and release the right feature instead of many features and twist so that spray-and-pray works;</li><li>In addition to the Customer Success team not having enough time to take care of the active base and only serve those who “<em>scream loudest</em>”.</li></ol><p>See: we agree for sure, about investing in new sales and business growth, but we must not overlook the business base. A good product with investment in customer experience is stronger in a long term. We need to change our mindset about how the product is seen in the companies as cost and not as an investment. We also understand, in a long term the math matches but is more difficult to calculate an ROI for a developer.</p><p>The logic we would like to bring here is simple: use as a basis for calculating the growth of your company a new effective revenue and not just new revenue. Why? Because you lose customers every month and you don’t grow 1,000 a month if your churn was 800.</p><p>The loss of revenue, whether in reason of customer service and/or problematic products, has higher impacts than simply a number at the end of the month. Who has left will not be a promoter of your company. Those who use your product certainly talk to peers and other professionals in the market. A closed door, closes others too!</p><h4><strong>What is this all about Anallytica?</strong></h4><blockquote>Well, we believe in building better products. With long-term focus. That’s simple!</blockquote><p>We believe in healthy growth, really focused on the end-to-end customer experience. From the MVP that we are going to release, to the care in the logos`s colours choice and the type of information we are going to share.</p><p>For sure a well-designed/developed product naturally supports healthy growth, where we make our customers our own promoters, and especially our own sellers. And you cannot build a great product with no ways to analyse everything that happens on it.</p><p>In past times, we have tracked for months numerous KPIs: NPS, MAU, AAD, windows opening time, query loading time, MRR, ARR, etc…</p><p>We always believe we should analyze less data, but with greater assertiveness. Why analyzing the product heat map if I don’t have and/or don’t know what decision to make with this? Will I do it because it’s fashionable and my friends do it too (even if I don’t know what it is for)?</p><p>The main reason of measuring a KPI should always be about what I am going to do with it. If I am going to monitor the DAU that I hope to extract from it, what is a satisfactory number? What decisions I will make to reach my goal and, above all, what I’m going to do to keep this number there.</p><p>Taking all this in consideration, we are born. <strong>Anallytica</strong> will be a center for managing SaaS indicators. We are going to monitor the above in a simple and assertive way.</p><p>How? A script in your application and ready, will be monitoring everything that makes sense to you.</p><blockquote><strong>This will be our MVP. Planned to be released in mid-February 2021.</strong></blockquote><p>We are going to launch, after MVP, new KPIs that product managers must or can follow, always in this way:</p><ul><li>A monthly dashboard with the leading KPIs;</li><li>A detailed report per indicator on a daily basis;</li><li>MAU and DAU monitors;</li><li>And much more…</li></ul><h4>Let’s take advantage of all the opportunities that this will create.</h4><p>Monitoring data with no action, is the same as studying medicine and work as paraquedist. You study all indicators and/or books in depth and in the end taking the decision to jump into the void, with only one piece of equipment and one dream.</p><p>We like the idea of analyzing the data and bringing you opportunities for new profit and the prediction of what might be lost: if for you, a user who gives a NPS note 4 and makes only 3 logins per week is a reason to worry, let us help you prioritize it on a revenue “Danger” list with some action taking backlog.</p><p>We are going to use smart queries and personalize your action in a simple way, minimalist, and practical way with everything that makes sense to you and to your product. We are going to help you GROW in profit and product by selling “<em>less</em>”. Churn reduction, upsell opportunity, increasing engagement in your product, and increasing NPS are some of the results we will have for you. This brings you new revenue with a smaller CAC and a happy promoter base.</p><p>All this with a product created and designed for “<em>product people</em>”. We live the product and we will use it for ourselves, for sure. Have you ever heard about “<em>Eat Your Own Dog Food</em>”? Nothing makes more sense than that.</p><h4>The simple delights and solves!</h4><p>We won’t have heavy software, with a thousand features and a thousand KPIs that you’ll never use, and we don’t even know what it’s for. We will have few key KPIs, few important features, and the freedom to customize it the way you need it.</p><p>We want to do “<em>less</em>” for you. Well, do less, to do better. We are not going to release features that you don’t need, neither inflate an intermediate plan with software integrations that you don’t use to take your money.</p><h4>We are still in the sea of ideas and feedback is always welcome</h4><p>Creating an assertive product for the market seems simple to solve when the pain is yours too. But the challenge is greater than it seems, especially when we talk about launching less product to launch the right product. Our product is focused on those who want to build amazing products. For people who study the data generated and make the right decisions.</p><p>Sure, the data speak for themselves, but they do not always tell us what we want to hear: talking to people is the big difference of this game.</p><p>For this we are opening here the possibility of you becoming a beta-test of <strong>Anallytica</strong>. We want to hear you about what KPIs you usually monitor, why, how, when and where. We want to create the right insights and launch the right product for you.</p><p><em>We are limited to 30 people in this initial project (at no cost) so that we can create a product that the market needs and wants.</em></p><p>If you want to be part of this great challenge with us and you want to be one of the first to play with our amazing tool, <a href="https://docs.google.com/forms/d/e/1FAIpQLSfTKrLJjVcRhVa40B9vj9e0k8pfEEmPWKwn6jezdcW6_aecVw/viewform"><strong>join this link and register</strong></a> for the initial list of users. Let us limit ourselves to a small number to be close and to talk frequently (no exaggerations because, of course, we have our lives as well). We only ask for an initial commitment, because the idea is for both parties to help each other. We do not want you to join because of the hype. We want you being part of this, in fact.</p><p>So, let’s build better products? Are we going to build something people would love instead of building fast features and making mistakes in a big scale? Are we going to stop this idea of developing software with low quality, praying to sell to FFF and “<em>when we can</em>” correct legacy?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2134b485b6e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>