<?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 Viktor Egri on Medium]]></title>
        <description><![CDATA[Stories by Viktor Egri on Medium]]></description>
        <link>https://medium.com/@viktoregri?source=rss-2384362cef0e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8C-TofOjZvhSPdi0.jpg</url>
            <title>Stories by Viktor Egri on Medium</title>
            <link>https://medium.com/@viktoregri?source=rss-2384362cef0e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:44:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@viktoregri/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[Radically improve customer service’s KPIs]]></title>
            <link>https://viktoregri.medium.com/radically-improve-customer-services-kpis-13384dee3bc5?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/13384dee3bc5</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-service]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Sun, 07 Feb 2021 22:17:28 GMT</pubDate>
            <atom:updated>2021-02-07T22:17:28.894Z</atom:updated>
            <content:encoded><![CDATA[<h4>How I identified and optimized the customer service with huge success</h4><h3><strong>Problem</strong></h3><p>From 2020 October to December, our customer support was overwhelmed due to many incoming requests on our support portal (we used Intercom chat). This is a seasonal thing in email marketing as there are many holidays and promotions during this time (Black Friday, Santa Claus, Christmas, etc.).</p><p>The number of new incoming requests getting higher and higher and the number of unanswered chats correlated with this number. Well, they weren’t unanswered, but it was very slow.</p><p>We saw it because the satisfaction rate of our customer started to decline week-by-week.</p><h3><strong>What I did</strong></h3><p>There weren’t serious things on the development side, they were working on some features that were already researched and planned.</p><p>So, I decided to join the support team as a customer support person to see, where are the bottlenecks and challenges better.</p><h3><strong>What I found</strong></h3><p>A <strong>support rep</strong> had the following challenges:</p><p>1. <em>Frequent context changes</em><br>Had to record bugs and technical issues in Jira, then suddenly answer to chat messages, then test a released hotfix. Multitasking at it best.</p><p>2. <em>High technical knowledge</em><br> Had to record the issues in the best way and answer technical related questions to the customers. It usually was difficult for a person who wasn’t technologically prepared and had to ask the developers about it.</p><p>3. <em>Chat availability was low<br> </em>Had to participate in meetings that were unrelated, spend time in the CRM, JIRA instead of answering chat messages.</p><p>A<strong> developer</strong> had the following challenges:</p><p>1. <em>Frequent context changes</em><br> As they were asked by support reps, they had to switch context continuously.</p><p><em>2.</em> <em>Overload of Tech support related issues<br></em>Tech support issues don’t necessarily need developer level knowledge, but many of it was reported. It just prevented developers form bug fixing.</p><p>The process basically looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*NbmQ6aY6804PQ4uu2BDSaQ.png" /></figure><h3><strong>Solution</strong></h3><p>When I asked around and I felt the pain of these things, I proposed a new way of supporting:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*Vq4R-JWspGXZdIFRdrpOGg.png" /></figure><p><strong>Chat support</strong>’s first and most important job is to <strong>be available</strong> and <strong>respond</strong> to incoming messages as fast as possible. Also, doing <strong>triaging</strong>: assign incoming messages to the person that is relevant to that specific topic (e.g. sales call, content collaboration requests to blog, customer requires education, etc.)</p><p>I established the <strong>Tech support</strong> role. Tech support person solves and answers everything that is technical but doesn’t need hotfix or bugfix. Also, the tech support person has to test hotfixes, record bugs in Jira.</p><p>The developers must focus on only hotfixes and bugfixes, nothing more.</p><h3><strong>Result</strong></h3><p>We started to implement this process in the beginning of 2021 January, and it <strong>delivered incredible results</strong>.</p><p>The median first response time decreased from <strong>2 hours to 20 minutes</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*XNVxHDlQertO-z5NZtOjxQ.png" /></figure><p>The median response time decreased from <strong>1 hour to 5–6 minutes</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/551/1*TJtmAt0LbxKWMJtfW9YSwQ.png" /></figure><p>The median time-to-close decreased <strong>from 5 hours to 1 hour</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*HIqGJkSnQIPfCG-ByBc9rQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13384dee3bc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Created a product-led go-to-market strategy]]></title>
            <link>https://viktoregri.medium.com/created-a-product-led-go-to-market-strategy-23b5e74284a2?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/23b5e74284a2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[go-to-market-strategy]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Sun, 07 Feb 2021 21:26:52 GMT</pubDate>
            <atom:updated>2021-02-10T08:04:43.147Z</atom:updated>
            <content:encoded><![CDATA[<h4>How I converted a problem map into an actionable product roadmap and go-to-market strategy</h4><p>In 2020 q2 quarterly planning meeting we collaboratively drew a problem map to visualize relations between our main issues. These were the challenges we knew we had at that time, we just tried to visualize it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*QmOuKfnajRmSBG7gWt8rcw.png" /><figcaption>Items were blurred out as those are company secrets</figcaption></figure><p>But -as you can see- it wasn’t structured enough. It just didn’t help us understand the links between the issues.</p><p>Therefore, I translated this whole map into a better structured graph, through the concept of product-led growth:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*xkQQYhPVYx5gWBuEfQl6Hg.png" /><figcaption>Items were blurred out as those are company secrets</figcaption></figure><h4>The first branch consists of challenges around <strong>perceived value delivering</strong>.</h4><p>It means that there are difficulties we must overcome to be able to improve this aspect: be able to deliver what we promise on our website in a better, faster way. Basically, provide better experience that meets customers’ expectations.</p><h4>The second branch is about <strong>differentiation</strong>.</h4><p>The topics are related to the question of standing out on the market. If we tackle those challenges, our product we’ll be unique and quite different than our competitors in the mind of our prospects.</p><h4>The third branch is about speeding up our internal <strong>learning curve</strong>.</h4><p>Iterative, continuous learning is needed if we would like to improve our service and innovate. If we can tackle the challenges we face here, we will be able to test hypothesizes and deliver MVPs faster.</p><h4>From this chart we could plan a <strong>product roadmap</strong>.</h4><p>Every item on the roadmap should represent one of the challenges that are present on this graph. It helped us focus on the important activities and prioritize better — basically reach our one-year goals easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hgPNAs9OW0UiCq_OPSHAww.png" /><figcaption>High level roadmap to reach yearly goal</figcaption></figure><p>On the roadmap every color matched a color on the problem graph: this is how we visualized which action will solve which challenge.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23b5e74284a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Increased the MRR by 12,54%]]></title>
            <link>https://viktoregri.medium.com/increased-the-mrr-by-12-54-af0e72e9c368?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/af0e72e9c368</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[bug-fixes]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Sun, 07 Feb 2021 18:46:06 GMT</pubDate>
            <atom:updated>2021-02-10T08:03:35.887Z</atom:updated>
            <content:encoded><![CDATA[<h3>Increased MRR by 12,54%</h3><p>Just buy decreasing the number of context changes for developers</p><p>During October, 2019, developers were working on mainly on refactoring a complete product portfolio element. Everything was planned beforehand and the PO could effectively lead the implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*l8RgbHoB_mhGaIUZHv1kKA.png" /><figcaption>USD values were hidden (as it is company secret)</figcaption></figure><h3><strong>Problem</strong></h3><p>This refactoring took a long time. We added 3–4 bug fixes to each scrum sprints.</p><p>But customer satisfaction started to decrease as the issues they faced were delivered much later than they expected it. Just too many bugs were reported but the resource we dedicated to solving these issues were not enough to fix them fast enough. It even caused higher level of churn.</p><p>On top of that, developers couldn’t solve these issues on time. Bugfix estimations were usually bad (due to unexpected root causes) and switching context between fixing bugs and refactoring wasn’t productive.</p><p>Basically, the short-term bugfixes were hindered by the longer-term project.</p><h3><strong>Solution</strong></h3><p>When I realized this problem, I proposed a solution to this:</p><p>Add another Jira board, that isn’t scrum but works in Kanban methodology. In addition, dedicate 1 regular person who works only on this.<br>I expected:</p><ul><li>It minimize the number of context changes which improves productivity</li><li>So the time-to-close for bug- and hotfixes will decrease</li><li>Therefore, customer satisfaction increases</li></ul><h3><strong>Results</strong></h3><p>It not only stopped churn, but by focusing more on bugfixes, the <strong>MRR increased by 12.54%</strong> in from January to March, because customer satisfaction radically improved.</p><ul><li>Kanban is “less documented”: therefore, <strong>fixes happened faster </strong>and customers’ problems were solved faster</li><li>Estimations were not for a 2 week sprint but for 1 bug: it <strong>increased precision</strong> and <strong>lowered the cost of turning back</strong></li><li>Working limit for Kanban columns also <strong>increased productivity</strong></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af0e72e9c368" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launched a feature that was used by the 50% of active users]]></title>
            <link>https://viktoregri.medium.com/launched-a-feature-that-was-used-by-the-50-of-active-users-fdb549658e82?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdb549658e82</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Sun, 07 Feb 2021 18:06:53 GMT</pubDate>
            <atom:updated>2021-02-10T07:47:51.355Z</atom:updated>
            <content:encoded><![CDATA[<h3>Launched a feature that was used by the 50% active users</h3><p>In 2020 May, more and more questions started to come in related to one specific area:</p><blockquote><em>How to hide bounce.automizy.com inside email clients to improve deliverability, and branding?</em></blockquote><h3>How I identified the problem</h3><p>Examples for this type of request in chat support:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*zKEVJVc4SR-5Wsk91diStQ.png" /><figcaption>User IDs and names were overwritten</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*ACqVGTep8m8eZ3PX49N-aQ.png" /><figcaption>User IDs and names were overwritten</figcaption></figure><p>Also, I implemented a <strong>feature request tool</strong> where it was requested and upvoted the most, compared to other requests:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*AqC_vQiBoq7WyeaT6GUmtg.png" /><figcaption>User IDs and names were overwritten</figcaption></figure><h3><strong>How I proved the value of the feature</strong></h3><p>During the discovery session, I conducted secondary research (checked how competitors do it and dig myself into authentication methods for emailing). Also, I discussed the question with our designer, one of the developers and our marketing guy.</p><p>When I identified that there’s a standard for it, I asked the designer to create a <strong>visual representation of the imagined feature</strong> (just one screenshot-like image).</p><p>I posted this drawing into the thread of the feature request and got this reaction:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*ZZxEdBtnEUbADGFKjGojJA.png" /><figcaption>User IDs and names were overwritten</figcaption></figure><h3><strong>First good feedback reduced the risk of missing the point</strong></h3><p>When I saw the initial first feedback, I committed myself to realize the feature. (I’m not mentioning here the questions around prioritization.)</p><p>I wrote the epic and stories, discussed the requirement with the designer who conducted 3 usability interviews and provided a proof that the solution will work. I also planned the measurement criteria too to be able to see the impact.</p><p>In the end of the discovery phase, we tweaked the prototype and documentation according to developers’ feedback and added the item to the sprint backlog and to the roadmap (so basically planned it into a scrum sprint).</p><p>When the feature was released, every help center article, marketing material was already prepared and <strong>50% of the customers started to use the brand-new feature during the first month</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdb549658e82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum delivery at Automizy]]></title>
            <link>https://medium.com/automizy/scrum-delivery-at-automizy-4ac4c8c66500?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ac4c8c66500</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[agile-development]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Sun, 15 Nov 2020 09:06:29 GMT</pubDate>
            <atom:updated>2020-11-15T11:51:54.624Z</atom:updated>
            <content:encoded><![CDATA[<h4>Delivery phase of the “Organized Chaos Product Development Process”</h4><p><strong>How scrum delivery works at Automizy: simple examples for notions, ceremonies and agile documentation.</strong></p><p><em>It is part of the series of the “</em><a href="https://medium.com/automizy/an-organized-way-of-being-chaotic-1d9113675aa7"><em>An Organized way of being chaotic</em></a><em>” post that shows how product management happens at Automizy.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dPqqnzr-JYhKWGTe" /><figcaption>Photo by <a href="https://unsplash.com/@epicantus?utm_source=medium&amp;utm_medium=referral">Daria Nepriakhina</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What’s the difference between agile and scrum?</h3><h4>The story of agile</h4><p>On the 11th–13th of February, 2001, 17 developers spent a little time at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah.</p><p>They skied, relaxed and had fun. Also, discussed the matter of document heavy software development. They named themselves “The Agile Alliance” and signed the “<em>Manifesto for Agile Software Development” </em>that stated the followings:</p><blockquote>“We are uncovering better ways of developing<br>software by doing it and helping others do it.<br>Through this work we have come to value:</blockquote><blockquote><strong>Individuals and interactions</strong> over processes and tools<br><strong>Working software</strong> over comprehensive documentation<br><strong>Customer collaboration</strong> over contract negotiation<br><strong>Responding to change </strong>over following a plan</blockquote><blockquote>That is, while there is value in the items on<br>the right, we value the items on the left more.”<br> /Source: <a href="http://agilemanifesto.org/">Agile Manifesto</a>/</blockquote><h4>The difference</h4><p>Agile is a software development philosophy that relies on iterative, collaborative software development and values the statements above.</p><p>Scrum is a software project management framework that helps a team stick to the agile values via its ceremonies and structure.</p><p>Among the people who created the Manifesto, there were Representatives from Extreme Programming, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development and Pragmatic Programming.</p><p>So you get the idea: agile is the underlying principle for the agile frameworks people came up with.</p><h3>Why is delivery is important in an agile way?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r6u8wJEn9XzT7kyR" /><figcaption>Photo by <a href="https://unsplash.com/@timmossholder?utm_source=medium&amp;utm_medium=referral">Tim Mossholder</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Execution is key for learning and improving. As Automizy is a cloud-based service, it faces many challenges related to the sudden changes of the technology and the market.</p><p>The iterative, agile, fast, incremental and continous delivery is sustainable and gives competitive advantage over other players on the market.</p><p>In addition, Automizy is a learning organization. The learnings gathered have the highest impact on penetrating this saturated market in the most optimal way.</p><h3>How does Automizy use agile notions?</h3><p>We use Jira as a project management tool and we also use their notions. Although’ internally we refer differently to specific notions on different abstraction levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RGgx6heExF-k1JV3ucXjSQ.png" /><figcaption>Agile notions</figcaption></figure><h4>Basic partition of agile notions</h4><ul><li><strong>Themes </strong>are<strong> large focus areas</strong> that span the organization.</li><li><strong>Initiative</strong>: are collections of epics that drive toward a <strong>common goal</strong>.</li><li><strong>Epic</strong>: are <strong>large bodies of work</strong> that can be broken down into stories.</li><li><strong>User Story</strong>: is a short, <strong>informal requirement or request</strong> written from the perspective of an end user.</li><li><strong>Task/Subtask</strong>: Stories will be implemented when developers done the related technical tasks.</li></ul><p><em>/Source: </em><a href="https://www.atlassian.com/agile/project-management/epics-stories-themes"><em>Jira Agile Coach</em></a><em>/</em></p><h4>Advanced partition of agile notions and Automizy specifics</h4><p>Inside Automizy we usually refer to Themes as Products. Although’ it’s not a good practice, still something we started to use and can’t really get rid of.</p><p>The very same applies to Initiatives — we usually refer to it as features. Maybe it’s incorrect too, but I believe focusing on the content instead of debating on these notions is more important.</p><p>Along the User stories, we use <strong>research spike</strong>s. A spike is a dedicated time to uncover a well-structured problem during a sprint. We also use Education a couple of times as item type, but it’s not that important in my personal opinion.</p><p>Also, one of the main confusions around User stories that these are the ones that only have to be in a sprint backlog. I don’t know how it came but I saw many people have difficulties when it comes to technical items — there’s a big confusion around this topic.</p><p>We use the<strong> backlog item</strong> type for things like infrastructure or other types of related technical items, that can’t be closely connected to any stories .</p><p>So we use story type inside Jira, but we add the “BLI:” prefix before these items and it only has to have a technical description, not a user story sentence.</p><h4>Show agile notions on an example</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJ4e8pIbtfePT_abr1YcSg.png" /><figcaption>Example for agile notions</figcaption></figure><p>Automizy service is broken down to multiple products/themes which are the biggest focus areas. One of them is the <strong>Lead Generation theme</strong>.</p><p>It is crucial for our customers to grow their email list using forms, popups, landing pages and similar solutions — this large focus area is the Lead Generation theme.</p><p>Below the themes there are multiple things (initiatives), but the one we are currently working on, is the <strong>Landing page initiative:</strong> help customers grow their email list by creating no-code one-pager sites with a specific purpose: make website visitors subscribe. Usually companies drive traffic to these pages using ads, social media sharing or google search.</p><p><strong>Delivering landing page for our customers is a common goal, </strong>and consists of many-many things, like landing page editor, SEO settings, stats, metadescriptions, segmentation availabilities, etc.</p><p>In order to be able to setup a landing page, we need many epics for this initiative: for example <strong>Page settings epic</strong> which helps companies customize how people can find their page, what URL it should be on and other metadescriptions.</p><p>This epic consists of <strong>user stories</strong>, such as: “As a small business owner I want to add Google Reacaptcha to my page so that robots on the web don’t spam my landing page.“</p><p>But we need to understand and identify what recaptcha technology we should use, so we create a <strong>Research spike</strong>, with the goal of identifying the best method to protect landing pages — e.g. Invisible Recaptcha. It is an independent item, connected to the epic and related to the user story.</p><p>Then developers create<strong> technical tasks</strong> that have to be performed under stories.</p><h3>Artifacts and Docs Automizy uses</h3><p>Although we value working software more over documentation, there is a lightweight approach to document the delivery phase to minimize information loss.</p><h4>Initiative level roadmap</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k51nhFgO0Upp4eWZ6AvmGQ.png" /><figcaption>Initiative level roadmap</figcaption></figure><p>Every quarter we take a look at our yearly goals and create a product roadmap on initiative level. It is not a project plan, just a map based on raw estimations. Every time something happens, we tweak it according to the changes.</p><h4>Initiative documents</h4><p>For every initiative we create a google doc (during the discovery phase), that consists of the following structure (maybe later on we’ll switch over to <a href="https://www.notion.so/">Notion</a>):</p><ul><li>Antecedent: Summarizes how the topic came up in 1–2 sentences.</li><li>Problem: Summarizes the problem the initiative aims to solve in 1–2 sentences.</li><li>Business advantages: How does this specific initiative helps us achieve the yearly goal? Summary in 1–2 sentences.</li><li>Impact: What are the main metrics it impacts and what the expected result is of the initiative?</li><li>Personas: Who will be affected by the initiative?</li><li>Notions: Collection of the most important notions so that everyone will be on the same page.</li><li>List of epics</li><li>List of stories inside Epics</li><li>Design: Clickable prototype with design (we use <a href="http://figma.com/">Figma</a>)</li><li>User flow: Visualizing <a href="https://careerfoundry.com/en/blog/ux-design/how-to-create-a-user-flow/#1-understand-your-user">paths in a flow-chart</a></li></ul><p>After the doc is finalized, we create the Epics, Stories and Backlog items in <a href="https://www.atlassian.com/software/jira">Jira</a> sprint backlog.</p><p>Also, we document everything in <a href="https://www.atlassian.com/software/confluence">Confluence</a> for tracking purposes as the Jira issue statuses will be updated in real-time when people work on them (maybe later we’ll move this to Notion as well):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CIhvGk_HZN-CZgpYdCBrmQ.png" /><figcaption>Docuementation of Initiatives inside Confluence</figcaption></figure><h4>Story’s structure</h4><ul><li>Epic label: what is the epic the story is related to</li><li>User story name: We just add a very short, descriptive label to the story</li><li>User story: We write the one sentence with the well-known phrasing. “As a [persona] I want to [do something] so that I [achieve something].</li><li>Scenarios: We write scenarios in <a href="https://www.guru99.com/gherkin-test-cucumber.html">Gherkin</a> so that QA will be able to write automated tests faster.</li><li>Related section of the clickable prototype</li></ul><h3>What agile ceremonies do we use?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IGNbiShj2MgREBxi" /><figcaption>Photo by <a href="https://unsplash.com/@rodlong?utm_source=medium&amp;utm_medium=referral">Rod Long</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Ceremonies in scrum helps us be agile while being organized at the very same time. Ensures events for information changes and learning or improving. Also increases transparency.</p><h4>Sprint</h4><p>Automizy’s scrum team works in 2-week iterations. It is enough time to ship stories but not big enough to get lost in the maze of project management.</p><h4>Daily standup</h4><p>Every morning developers discuss what they worked on and what they will work on or if they have any blockers. Our scrum master helps them and also the POs participate (usually just listening to understand how things go).</p><h4>Planning poker</h4><p>Although’ planning poker is just a tool, but we created a ceremony with its name. The main goals are:</p><ul><li>Give story point based estimations to stories (that not yet have been broken down to technical tasks)</li><li>Collect missing items or acceptance criteria</li></ul><h4>Sprint focus</h4><p>The sprint focus ceremony is a very short meeting where the PO shares every item that should be shipped during next sprint. Developers don’t take commitment, they just know what to plan on before they commit to a scope.</p><h4>Sprint planning</h4><p>Developers breaking down stories and backlog items into technical tasks for the upcoming sprint and also give time-estimations. Usually takes maximum 1 day.</p><h4>Sprint commitment</h4><p>After the planning event developers can decide what they can ship or what they can’t during the next sprint. Based on it they take commitment for the items they accept.</p><h4>Dev retrospective, Sprint close &amp; open</h4><p>On the last day of a sprint, we review it (this is the sprint close event). Then we hold a retrospective right away using <a href="https://www.parabol.co/">Parabol</a>. At the end of the retrospective the PO announces the next sprint’s main goals and the scrum master opens the next sprint iteration in Jira.</p><h4>Sprint Backlog Refinement</h4><p>When PO-s see that the sprint backlog is messy or an information is missing, they hold a quick, maximum 30 minute meeting to tackle it:</p><ul><li>Collect questions (so later on they can ask the responsible person about it)</li><li>Delete unnecessary items from the sprint backlog</li><li>Break down actual items in the sprint backlog</li></ul><h4>Agile minutes</h4><p>Every week the scrum master teaches the developer team on agile for approximately 30 minutes.</p><h3>How do we measure the scrum team’s success?</h3><h4>Sprint commitment</h4><p>When developers commit themselves to a sprint scope, they are kind of measured whether they could ship it or not.</p><p>But — to be honest — it is not really to measure success, just to bring up the topic of why something changed and how we can avoid it next time. Usually unexpected things will happen during a sprint that will certainly affect the commitment.</p><h4>Burn-down chart (extended artifact)</h4><p>The scrum master checks the burn-down charts of each previous sprints — based on it she most probably can understand impediments or problems better and come up with an idea to tackle it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ac4c8c66500" width="1" height="1" alt=""><hr><p><a href="https://medium.com/automizy/scrum-delivery-at-automizy-4ac4c8c66500">Scrum delivery at Automizy</a> was originally published in <a href="https://medium.com/automizy">Automizy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Organized way of being Chaotic]]></title>
            <link>https://medium.com/automizy/an-organized-way-of-being-chaotic-1d9113675aa7?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d9113675aa7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Mon, 02 Nov 2020 16:33:23 GMT</pubDate>
            <atom:updated>2020-11-15T09:10:41.003Z</atom:updated>
            <content:encoded><![CDATA[<h4>Product management at a SaaS early stage company</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qgyEZERAvjBQ7Ye1sKz6TQ.png" /></figure><p><strong>A quick overview of what challenges are faced by early stage stratups and how Automizy tries to solve it? An honest confession from a product manager at an early stage company.</strong></p><h3>What’s the aim of this article?</h3><p>In this article I try summarize our key challenges and how Automizy handles them: by implementing the “Organized Chaos Product Development Process” (OCPD) method.</p><p>This article gives you a quick overview of the challenges and the solution we came up with. The plan is to release focused articles that transparently show how the methodology works in detail and how it affects Automizy.</p><p>So for each step there will be at least one or even multiple articles that describe the processes in detail.</p><p>It’s not a finalized method (as it is always changing) nor it is a method that should be pasted to your own business without scrutiny. It is just how we do it.</p><p>Think of it as a honest and transparent way of showing you the engine of Automizy under the hood. Also, feedback is highly appreciated.</p><h3>Key Challenges</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m6K6DZ3rwHLM4C63" /><figcaption>Photo by <a href="https://unsplash.com/@jackmanchiu?utm_source=medium&amp;utm_medium=referral">Jackman Chiu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Many challenges are faced by SaaS companies. But I experienced a couple of relevant challenges. Sometimes it is unique to our organization but I think most of the time it is relevant to other companies as well.</p><h4>1. Resources are always way less than you think</h4><p>Software development companies always face the issue of having many things to do but not enough resources to execute.</p><p>It is obvious, but still something that every company has to tackle somehow. It is even more crucial when you meet this wall in a small, learning organization that tries to find the best way to penetrate a red ocean market however new to the organization.</p><p>It also applies to earlier stage cloud-based services: if you want to provide a quality product that truly solves the problem of enough people who can pay for it.</p><p><strong>1.1. FEATURE FACTORIES</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9L9ASnEP4I-dH9q8" /><figcaption>Photo by <a href="https://unsplash.com/@scienceinhd?utm_source=medium&amp;utm_medium=referral">Science in HD</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I see many companies releasing tons of features, even among our integration partners. I also see that most of those integrations were probably built because the options can be found in an API documentation but doesn’t solve any real problem.</p><blockquote>When you have limited resources, you can only try to reduce the scope and always make sure that your released MVP solves an issue. This way releases can happen a little bit less frequently — but sometimes slower means faster.</blockquote><p>This is the constraint of speed: your perception is that you do things fast, but you can never be fast enough to reach the wished business metrics on time if you don’t slow down.</p><p><strong>1.2. FLEXIBILITY</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GTFxB4oIFnuefFiB" /><figcaption>Photo by <a href="https://unsplash.com/@pavel_kalenik?utm_source=medium&amp;utm_medium=referral">Pavel Kalenik</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>But slowing down always raises the risk of not being able to change scope fast enough. Sometimes it can be an advantage but a disadvantage at the very same time.</p><p>You can never be sure that your qualitative research is a good enough proof — damn if we could have more time and money to conduct in-dept researches.</p><p>Not to mention that you can’t afford to AB test a feature when you are building up early traction, you can only try to mitigate risks early via prototyping or qualitative researches.</p><blockquote>The only way of maintaining the good-enough flexibility is to be aware of the risks and track it on the go. Intervene as soon as your data or gut feeling tells you to do that.</blockquote><p>It can be very painful to intervene even if you recognize the need for scope change (not to mention a full pivot). You want to penetrate the market enough by the time you run out of money — one of the most severe resource constraints.</p><p><strong>1.3. SET PRIORITIES</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a447_n9hyzdMISIt" /><figcaption>Photo by <a href="https://unsplash.com/@mi_desertlife?utm_source=medium&amp;utm_medium=referral">Alyssa Baches</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Mitigating risks emphasizes setting up priorities that comes from the belief that with this approach you will reach the wished business metrics on time.</p><blockquote>But when it comes to make hard decisions — and yes, sometimes hurting your own business performance on the short run — people start to explain why still that second thing is important (at least according to my experience).</blockquote><p>People are amazingly good at explaining why they think something differently a couple days later they agreed on a priority. And in the worst-case scenario they explain it only to themselves and try to add more todos for themselves.</p><p>This stress creates the “ghost backlog” that secretly undermines the strategy — people always work 16 hours a day but there is no delivered piece of software or content.</p><p>This is the human constraint coming from the uncertain circumstances of a market that has to be penetrated with insufficient knowledge.</p><p><strong>1.4. LEARNING LOOPS</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*71bl-vmlXkuQKSZR" /><figcaption>Photo by <a href="https://unsplash.com/@itfeelslikefilm?utm_source=medium&amp;utm_medium=referral">🇸🇮 Janko Ferlič</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Sanity check is the only thing you do when you want to re-evaluate your strategy and priorities.</p><p>Unfortunately, learning is not as easy as it is described in different articles. It is an abstract notion that means different things for most of the people.</p><ul><li>Should it be systemized knowledge or just share it via your educated guesses?</li><li>If it is systemized, how to break badly structured problems into well-structured problems that are explainable and provable?</li><li>How to connect it directly to the exact situation the comany is in?</li></ul><blockquote>Implementing this abstract “learning loop” into the business is even more difficult — decision on the level of preciseness.</blockquote><p>If it doesn’t give enough feedback, you can easily interpret data the wrong way. If it is too detailed, you can easily get lost in the maze of unrelevant data and never be able to sort out the important information.</p><p>This constraint is not knowing the best granuality level of information — driven decision making.</p><h4>2. Organized vs Chaotic systems</h4><p>This challenge is a continuous question in a company’s life. If you have an organized way of creating products you will be good at creating them. But a stabile environment with developed processes can easily cut the necessary individualism or “crazy”-ness. Being organized can be advantage but a huge disadvantage when you try to innovate.</p><p><strong>2.1. EVERY COMPANY TRIES TO INNOVATE</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tJDFxuEoNnHnhCHl" /><figcaption>Photo by <a href="https://unsplash.com/@kvalifik?utm_source=medium&amp;utm_medium=referral">Kvalifik</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Innovation on its own is a very difficult topic. But it becomes even more difficult when people try to create a system that ensures that innovation will be more likely to happen:</p><blockquote>Paradox situation can easily rise where the activities that should lead to innovation kill the chances of being innovative. Innovation somehow requires a little chaos in the organization.</blockquote><p>To make the picture even more confusing, too much chaos sometimes kills innovation and undermines production as well.</p><p><strong>2.2. VISION AND PRODUCTION REQUIRES ORGANIZED SYSTEMS</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fXjZE1k5HBQvt8fL" /><figcaption>Photo by <a href="https://unsplash.com/@joshuaearle?utm_source=medium&amp;utm_medium=referral">Joshua Earle</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Our vision is something we would like to reach — and it usually changes the way things happened before on the market: usually innovates consumer behavior or thinking.</p><blockquote>So visions are usually innovations on their own. Without being organized, it is difficult to get there.</blockquote><p>As my mentor, Balázs Tornai told be that agile methodologies support innovation: the product owner frames challenges in the context of reversal cost.</p><p>Framing the challenges the right way helps the team innovate inside the business context by defining the limits using the tools of control. But inside this frame the iterative and collaborative approach can help innovation to be nurtured by conducting research spike and focusing on collaboration.</p><p>But, (according to<a href="https://hackernoon.com/being-innovative-and-being-agile-are-different-1c5fef4db217"> Hackernoon</a>) being agile and being innovative are not the same things:</p><blockquote>“Innovating is creating change. Being agile is adapting to change. The mindset is radically different.”</blockquote><p>But I don’t want to get into this, as I’m not discussing agile here, but certainly false agile can undermine innovation as innovation takes time and many attempts and you have to stay on a specific path instead of changing scope over and over again.</p><p>Not to mention when it comes to production, chaos causes lower quality products than the market expectation.</p><h4>3. Product quality</h4><p>Product quality is something that is difficult to define. But the life-cycle stage of a company and the market’s specifics will define where to put more focus on first.</p><p><strong>3.1. FUNCTIONAL AND EMOTIONAL DESIGN</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U779FmhP_j6bLyMo" /><figcaption>Photo by <a href="https://unsplash.com/@halacious?utm_source=medium&amp;utm_medium=referral">Halacious</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Users have to experience your product’s perceived value on functional, emotional and social levels too — firstly we try to design functional, emotionally good products.</p><p>Social level is an abstract thing that relies not solely on product quality but on a complete brand experience you offer via all of your interactions with your users. I think this is one of the reasons we don’t really focus on this aspect during earlier stages.</p><blockquote>So, for most of the early-stage companies usability and design is one of the most important drivers for business growth.</blockquote><p>Design and usability has to be owned by someone as early as possible— not surprisingly a product designer in the team is a must have if you want to create good products.</p><p><strong>3.2. SOFTWARE DEVELOPMENT METHODOLOGY</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sZZM79hgRe5an2z-" /><figcaption>Photo by <a href="https://unsplash.com/@clemhlrdt?utm_source=medium&amp;utm_medium=referral">Clément H</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>But good quality product requires good-enough software development methodologies. As I’m not anexpert on this topic at all, I don’t really want to get in details. But still, it is a challenge for us.</p><h4>4. Technical debt</h4><p>When you start your business with 2–3 developers and you create a side-project from your well-established business, it is usually one of the main reasons you start to build up technical debt from the beginning.</p><p><strong>4.1. LOCATION AND PAST DEFINES KNOWLEDGE</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w8wGnqIXA0CgPEPR" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In case of Automizy, we started the business as truly a side-project of a business that was successfull on the Hungarian market — basically a market-leading company in the bigger companies segment.</p><p>But learning from that market segment in an Eastern-European country doesn’t really help you build successfull products for a completely different segment and for international expansion.</p><p>It is obvious that if you learn something from big customers, it won’t be valid to SMBs. They just have completely different needs and pains. It was a challenge on its own.</p><blockquote>Maybe it seems stupid, but being in the Eastern-European block makes learning much more difficult.</blockquote><p>Yes, you can search for news, listen to podcasts and everything is accessible via the Internet. Still, it is not in the culture, which means you can have much less meaningful conversations with others, simply because there are only a couple of experts (especially when it comes to SaaS or a software developer company that works on 1 product).</p><p><strong>4.2. EVOLUTIONARY APPROACH</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZLDZhf5effsQozmH" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Because of this knowledge gap, it was much easier to make (at least we did) many mistakes when we decided to create the side-project.</p><p>We started to break Automizy software from the enterprise level product step-by-step. We always faced difficulties that we had to tackle and this evolutionary approach led us to cummulate huge code-debt.</p><p><strong>4.3. CUSTOM MADE TECH</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*As0SPZTGT1MmgkoC" /><figcaption>Photo by <a href="https://unsplash.com/@barkiple?utm_source=medium&amp;utm_medium=referral">John Barkiple</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If we would have built the app with a completely different strategy that doesn’t rely on our custom made solutions in the enterprise product, we would have entered the market most probably faster.</p><p>But we chose this path. This mistake caused big issues: the custom made technology increased complexity and junior developers simply couldn’t work on our tool.</p><h4>5. Consumer behavior of B2B buyers</h4><p>Back around 2015, a huge numer of email marketing tools launched or pivoted to the micro-business/solopreneur segment.</p><p>Now it’s 2020 and a couple of businesses grew succesfully such as Convertkit, Mailerlite, SendinBlue.</p><p>And if you take a look at them, all of them rely on freemium model.</p><p><strong>5.1. B2B BUYERS ARE LIKE B2C BUYERS</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8D05yVKs_kDQYXhz" /><figcaption>Photo by <a href="https://unsplash.com/@freestocks?utm_source=medium&amp;utm_medium=referral">freestocks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>On this specific market (and most probably for most of the martech businesses) the way companies buy software became very similar to B2C buyers’ behavior.</blockquote><p>When they see the value proposition (perceived value) they want to experience it asap. Don’t even want to interact with anyone if possible, just look around and learn themselves.</p><p><strong>5.2. DON’T PUSH ME TO UPGRADE</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ClRrNL_OVOqYJ_NH" /><figcaption>Photo by <a href="https://unsplash.com/@greg_rosenke?utm_source=medium&amp;utm_medium=referral">Greg Rosenke</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>But people at companies don’t really want to feel the push of trial periods anymore. It was true before (e.g. Convertkit changed from free trial to freemium in 2020) but now it is completely different.</p><p>It is expected, that’s all.</p><p><strong>5.3. TRANSPARENT COMMUNICATION IS A MUST</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Zhf6dRfhCOxa5bbk" /><figcaption>Photo by <a href="https://unsplash.com/@aleksdahlberg?utm_source=medium&amp;utm_medium=referral">Aleks Dahlberg</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Help people experience your product and you can make the sales if your product meets their expectations.</p><blockquote>But it is also important that you have to explicitely make them realize they received value from you.</blockquote><p>Many times people don’t realize that you try to help them or already helped them without a clear, transparent communication. If you can’t dominate this narrative, it will very shortly hit back.</p><h3>Introducing the Organized Chaos Product Development Process (OCPD)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qgyEZERAvjBQ7Ye1sKz6TQ.png" /></figure><p>In order to be able to tackle all the challenges I listed above, we came up with a system we use internally to cover the whole life-cycle of the product development process.</p><blockquote>It is the actual state but it will change as we realize we can or can’t handle different challenges as efficiently as we want. Learning is important here and can be measured on the business impact of the product’s changes.</blockquote><p>This process can be divided into the steps below.</p><h4>1. Collecting needs</h4><p>The first topic covers how we collect needs from different stakeholders: prospects, users, customers, support, developers, management.</p><p>This is nothing but a wishlist that has to be evaluated, prioritized.</p><h4>2. Discovery track: the phase of “chaos”</h4><p>The discovery track’s main goals are:</p><ul><li>Eliminate the needs that are not truly needed, just “wishes”</li><li>Prioritize the most important problems according to their possible impact</li><li>Identify the real problem (as most of the time the route cause not the same as the experienced issue)</li><li>Transform badly structured problems into well-structured challenges</li><li>Design good solutions that tackle the problem (taking into account the desireability, feasability and viability aspects)</li><li>Align priority orders with the company vision</li><li>Create roadmaps according to our go-to market strategy</li></ul><p>In the upcoming articles I will touch all these points in detail.</p><h4>3. Delivery track: the phase of “organization”</h4><p>The delivery track’s main goals are:</p><ul><li>Deliver what is truly needed</li><li>Deliver continuously&amp;often in smaller batches</li><li>Maintain quality assurance for higher product quality</li><li>Improve delivery processes continuously</li></ul><p>In the upcoming articles I will touch all these points in detail too.</p><p>You can find the details of <a href="https://medium.com/automizy/scrum-delivery-at-automizy-4ac4c8c66500">Scrum delivery at Automizy in this article</a> (the first article in the series).</p><h4>4. Impact measurement</h4><p>The impact measurement’s goal is to see:</p><ul><li>Did it affect our business metrics?</li><li>Should we invest more resources into it?</li></ul><p>In the upcoming articles I will touch this too.</p><h4>5. Service-led go-to-market strategy</h4><p>The whole product management methodology happens in the context of our go-to-market strategy that is service-led.</p><p>It is directly linked to the whole product development process and to the impact of the different pieces of software we release.</p><p>In the upcoming articles I will touch this too in detail.</p><h3>Last words</h3><p>I think this quick overview touched most of the challenges Automizy faces and also introduces the model we are developing in order to be able to solve these challenges.</p><p>As I mentioned in the beginning of this article, there will be more posts that explain every aspect of the solution side in details and how we do it exactly, what works fine, what needs improvement or has to be changed completely.</p><p><em>This post has been published on </em><a href="http://www.productschool.com/?fbclid=IwAR0qtOmImcmnbgGx67J8M19feXHV4Yp6l4Nbs10Podm-nIg7U612lDg3cd0"><em>www.productschool.com</em></a><em> communities.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d9113675aa7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/automizy/an-organized-way-of-being-chaotic-1d9113675aa7">An Organized way of being Chaotic</a> was originally published in <a href="https://medium.com/automizy">Automizy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[20 simple SaaS Marketing Best Practices to boost your business]]></title>
            <link>https://viktoregri.medium.com/20-simple-saas-marketing-best-practices-to-boost-your-business-38c0305011ba?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/38c0305011ba</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Tue, 21 Feb 2017 17:08:46 GMT</pubDate>
            <atom:updated>2017-02-21T17:20:26.864Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*99Qq6vHKaHEdURFKsf2Iww.png" /></figure><p><strong>If you read only 1 list of SaaS marketing best practices today, this should be the one! 20 simple but very important tips to enhance your user acquisition, user retention and grow your business as a whole.</strong></p><h3>1. Avoid discounts</h3><p><strong>Discounts are deceiving</strong>: usually, companies try to get more users and clients. But in the end of the day, it can easily turn out that you brought in the <strong>wrong audience and they churn</strong>. Again: competing on prices is a very bad approach, <strong>compete on benefits</strong> instead! If you bring in a new customer based on your unique selling proposition but for the usual price, he will be more likely to stick with you for longer. The more they invest in your solution the more difficult is to leave you!</p><h3>2. Build growth engine into your product</h3><p>Growth engines are <strong>varying product by product</strong>: for example in Slack you share the tool with your colleagues, in Pipedrive you and your invited company get a discount. You have to build some kind of <strong>virality</strong> into your product even if it doesn’t seem to be good for a B2B business. You might hear that “it doesn’t work in B2B” but I hope you don’t try to sell to companies but to individuals… and in this case, it doesn’t really matter whether you are in B2C or B2B.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*glL-lbtAzeF3XH6sHQhBiA.jpeg" /></figure><h3>3. Get into review sites</h3><p>During <strong>the buying process</strong>, lots of people check reviews that are independent of you. Therefore they go to <strong>review sites and try to collect information</strong>. So it is important to “host your reviews” on your review sites too. For example on <a href="http://www.capterra.com/">Capterra</a>, <a href="https://www.g2crowd.com/">G2crowd</a>, <a href="https://financesonline.com/">financesonline.com</a>.</p><h3>4. Shorten your free trial period</h3><p>Maybe it seems contra-intuitive but a lot of time <strong>shortening your trial period </strong><a href="https://blog.automizy.com/2016/11/how-to-improve-conversion-rate-trial-sign-up/"><strong>increases conversion rate</strong></a>. It’s because there will be a bigger <strong>time pressure on your trial users</strong>. Scarcity is one of the most effective tools when it comes to sales!</p><h3>5. Increase your prices</h3><p>Prices are usually lower than they should be. Lots of companies think that it’s important to have low prices to make people even register. But that’s not true! People are looking at<strong> benefits and features</strong> first. If you can convince that <strong>your tool is able to kill the pain your prospect has, you’ve already won</strong>. But there can be exceptions: if you target companies or people on low-budget… But competing on prices can be very harmful.</p><h3>6. Offer annual payment</h3><p>Annual, pre-paid payment is usually <strong>cheaper than paying month-by-month</strong> and it is wise to offer this solution. It is a little bit cheaper as you <strong>get their trust for 1 whole year!</strong> And it is worth a lot to have a client with you for a year as they won’t churn until that time for sure which <strong>makes your numbers more predictable</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p49mrEfQocI_UloZRKwZhw.jpeg" /></figure><h3>7. Have a good customer support</h3><p>Yes, it sounds obvious but one of the most important things is your customer support. It is especially true if you have <strong>big competitors</strong> in your market: as they don’t have much time you will be even able to<strong> steal clients</strong> from them just <strong>by providing good customer support!</strong></p><p>But be aware: the level of your customer support should be <strong>highly affected by your business model</strong>. If it is self-service, it is enough to have a chat and email combination, if it is transactional, you might go to telephone too and if it is enterprise level, it can be a one-to-one, live solution!</p><p><a href="https://blog.automizy.com/2017/02/20-simple-saas-marketing-best-practices?utm_source=marketing-community&amp;utm_medium=medium.com&amp;utm_campaign=20+simple+SaaS+Marketing+Best+Practices+to+boost+your+business"><strong>&gt;&gt;Continue Reading for the upcoming 13 tips&lt;&lt;</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38c0305011ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marketers Guide to improve User Acquisition: Analytics to track in your drip campaigns]]></title>
            <link>https://viktoregri.medium.com/marketers-guide-to-improve-user-acquisition-analytics-to-track-in-your-drip-campaigns-67babe1e08ea?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/67babe1e08ea</guid>
            <category><![CDATA[marketing-automation]]></category>
            <category><![CDATA[content-marketing]]></category>
            <category><![CDATA[email-marketing]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Tue, 07 Feb 2017 14:55:00 GMT</pubDate>
            <atom:updated>2017-02-07T14:56:05.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*QPJQXSY6-gOHqOh0X7Wndw.jpeg" /></figure><p><strong>Inbound user acquisition is the process of converting visitors of your web- and blog pages into leads by asking their contact information. After that, you manage to convert them into users by giving them educational contents and offering your trial to them. In order to be able to get more sign ups for your trial, you need to track the user acquisition analytics that truly matters in your drip campaigns.</strong></p><h3>List building boosts your User Acquisition on the long run</h3><p>Big percent of your website and blog page visitors can’t be converted into trial users right away. Therefore your first task is to write free giveaways, ebooks, offer free email training courses.</p><p>Email list building is one of the most efficient steps to acquire much more users. Maybe not right away, but in the long run, it will boost your user acquisition, analytics will prove that the ROI of this channel is better than any other channel.</p><p>A good “hook” offers a solution to an ultra-specific pain point of your prospects so it provides high-perceived value. This will be the incentive that makes them give you their contact information and also give you the permission to send them emails.</p><p>One of the best ways is an email course that shows and teaches them something that is connected to your solution.</p><p>In addition, one of the best channels to collect subscribers is using pop-ups on your blog and web pages. Don’t be too irritating but setting up services like <a href="http://www.optimonk.com/">Optimonk</a> you will have the chance to offer targeted ebooks, training sessions or consultations to your visitors based on their behavior.</p><h3>Handle your Automated Emails as they were sent from your Personal Email Account</h3><p>As you managed to convert your visitors into leads, the next step is to send them the well-known welcome emails. You should also set up reminders and follow-up emails to nurture them and push them to the next level in your marketing funnel.</p><p>One of the most difficult parts of this process is copywriting and how to convince them to open it, click the right link and do what you want them to do. This guide summarizes <a href="http://blog.automizy.com/2016/05/how-to-write-an-autoresponder-series/">how to write autoresponder series</a>.</p><p>In addition, if you don’t want to write your emails from scratch, you can take advantage of these <a href="http://blog.automizy.com/2016/05/increase-conversion-rates-5-proven-emails/">proven email copies</a> that help you get started.</p><h3>7 drip campaign metrics that are crucial to improving your user acquisition analytics</h3><p>Like you would do for every marketing campaign, you have to know how your workflows and how your emails perform individually too.</p><h3>Overall workflow analytics to compare the efficiency</h3><p>In case you have more drip campaigns it is crucial to get a quick overview how they perform one by one. If you see extreme values for a drip it will show you where you need to improve or where you need to copy&amp;paste your procedure.</p><p>For the 7 drip campaign metrics and their interpretation, you need to track <a href="https://blog.automizy.com/2017/02/improve-user-acquisition-analytics/?utm_source=marketing-community&amp;utm_medium=medium.com&amp;utm_campaign=Marketers+Guide+to+improve+User+Acquisition%3A+Analytics+to+track">click here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67babe1e08ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 3 Ways to Target Customers Using Email Marketing]]></title>
            <link>https://viktoregri.medium.com/top-3-ways-to-target-customers-using-email-marketing-d967a734c472?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d967a734c472</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[email-marketing]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[marketing-strategies]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Tue, 31 Jan 2017 14:57:08 GMT</pubDate>
            <atom:updated>2017-01-31T14:57:08.227Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_USDMW4EX1blc-XIB5h_OQ.jpeg" /></figure><p><strong>“You have got new mail!” I am sure you have heard this phrase at some point in your life. It is the legendary time that made the history of Internet, when the roads were still being paved and we were making our way through the uncultivated region of what was the real World Wide Web. Although times have changed but because of social media, one could agree that Email has become, our place of solitude amongst the chaos.</strong></p><h3>Take your sales to a new level</h3><p>Email marketing campaigns and defining your companies’ target audience go hand in hand. <strong>Email marketing</strong> is an effective way to market your products, services and getting the word out about your organization. <strong>The challenge is to harness new technology and big data to target customer segments and even customers individually.</strong> Target emailing is a must to increase the ROI and to be more relevant to the customers. Starting a business anywhere in the world is not difficult. E.g. <a href="https://www.rizmona.com/business-setup-dubai/">Business setup in Dubai</a> is not so hard if you know which buttons to push to take your company to another level.</p><p>Email marketing can help you target customers and take your sales to a whole other level in just three simple ways.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/0*OZERHfflYD1jOKaX.jpg" /></figure><h3>Think like a customer</h3><p>Companies use email marketing campaign based on their past purchases, to identify and reach new customers. Because most of the email marketing lists consist of existing customers, there are good chances that you already have interacted with them and have good relationships. It helps knowing what they have purchased from you in the past, to learn about their specific needs and how your products helped them. Perhaps, you can even know what<strong> future challenges</strong> maybe faced by them and what new product developments can emerge from this knowledge. Many brands are perceived as failing to understand the <strong>basic motivations and concerns of their consumers</strong>. Thinking like the customer, rather than the marketer, can make huge differences when you create your inbound marketing strategies.</p><p><a href="https://blog.automizy.com/2017/01/top-3-ways-target-customers-using-email-marketing/?utm_source=marketing-community&amp;utm_medium=medium.com&amp;utm_campaign=Top+3+ways+to+Target+Customers+using+Email+Marketing">&gt;&gt;Countinue reading&lt;&lt;</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d967a734c472" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Debunking SaaS Churn Rate for Subscription Services]]></title>
            <link>https://viktoregri.medium.com/debunking-saas-churn-rate-for-subscription-services-a0139734deba?source=rss-2384362cef0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0139734deba</guid>
            <category><![CDATA[churn]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[customer-retention]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[retention]]></category>
            <dc:creator><![CDATA[Viktor Egri]]></dc:creator>
            <pubDate>Thu, 26 Jan 2017 10:51:23 GMT</pubDate>
            <atom:updated>2017-01-26T10:51:23.457Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hCB0w4j3Z9hqQRjMZxOXFg.jpeg" /></figure><p><strong>The churn rate for subscription services is a big deal — everyone talks about it but unfortunately, they don’t really try to summarize it in an easy-to-understand way. This is why we give you a concise overview of it and also give you awesome hints on how to reduce it.</strong></p><h3>Why is SaaS churn rate a key metric for subscription services?</h3><p>There are 2 main types of churn rates you can calculate:</p><ul><li>customer churn rate,</li><li>net revenue churn rate (NRR)</li></ul><p>While the first one shows you the percentage of users leaving you in a certain period of time, the second metric is the most important. “<strong>NRR is the “net” revenue</strong> left over from an existing cohort of customers, less any revenue churn (caused by customers leaving totally or staying, but paying less for the privilege), plus any expansion revenue from upsells, cross-sells, etc.” — <a href="http://sixteenventures.com/negative-saas-churn-rate">says Lincoln Murphy</a>, my idol of customer success.</p><p>So basically you can lose as many users as you want as far as your <strong>Monthly Recurring Revenue</strong> is growing.</p><p>But of course, <strong>customer churn</strong> is not a good thing: if you can keep your customers, you will probably have higher MRR too.</p><p>According to David Skok (check his short bio <a href="http://www.matrixpartners.com/team/david_skok/">here</a>, he’s not only famous but a very experienced entrepreneur and venture capitalist) the better you can handle churn rate for your product the faster you will grow. But real growth will come from <a href="http://www.forentrepreneurs.com/why-churn-is-critical-in-saas/">negative revenue churn</a>!</p><p>For the <strong>early stage SaaS companies</strong>, the percentage of churn is not that big problem. If you lose 5 clients it is possible to bring in 10 more (if your company sells a relatively low priced tool) so you will grow your MRR.</p><p>But for companies that have more clients, churn will be a number one problem. As you can see on the picture below, <strong>the more users you acquire the bigger the churn rate problem will be for you</strong>. And there will be a time when you won’t be able to grow your MRR — your company basically dies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*PJnRGCh6Y2yoZ-rs.png" /><figcaption>Source: <a href="http://www.forentrepreneurs.com/wp-content/uploads/2012/05/image_thumb.png"><em>Unlocking the path to negative churn</em></a></figcaption></figure><p>But if you can reduce the churn rate, or even create negative revenue churn using <strong>upsells andcross-sells</strong>, you will grow exponentially!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/0*hcZWzedBQaOIY8PM.png" /><figcaption><em>Source: </em><a href="http://www.forentrepreneurs.com/wp-content/uploads/2012/05/image_thumb4.png"><em>Unlocking the path to negative churn</em></a></figcaption></figure><p>So as your business grow and get more and more clients, you will need to find ways to decrease your revenue churn rate as there is higher potential than in your new clients.</p><p><a href="https://blog.automizy.com/2017/01/debunking-saas-churn-rate-for-subscription-services?utm_source=marketing-community&amp;utm_medium=medium.com&amp;utm_content=blog&amp;utm_campaign=Debunking+SaaS+Churn+Rate+for+Subscription+Services">&gt;&gt;Countinue Reading&lt;&lt;</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0139734deba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>