<?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 mrb on Medium]]></title>
        <description><![CDATA[Stories by mrb on Medium]]></description>
        <link>https://medium.com/@mrb_bk?source=rss-909f3aea84de------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UxayO6AqCfGvenKEGi5tFA.jpeg</url>
            <title>Stories by mrb on Medium</title>
            <link>https://medium.com/@mrb_bk?source=rss-909f3aea84de------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:55:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mrb_bk/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[The real reason frameworks get adopted]]></title>
            <link>https://medium.com/let-s-begin/the-real-reason-frameworks-get-adopted-1a6893051686?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a6893051686</guid>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Mon, 03 Dec 2018 15:01:01 GMT</pubDate>
            <atom:updated>2018-12-03T19:16:38.796Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s all about the capabilities of new users</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JhA7903f0V0dHcAt" /><figcaption>Photo by <a href="https://unsplash.com/@danielcgold?utm_source=medium&amp;utm_medium=referral">Dan Gold</a></figcaption></figure><p>Sitting down to write a serverless application in 2018 feels a lot like it did to write a greenfield web application in the pre-Rails and Django times. Before the titanic Ruby and Python frameworks were <em>de rigeur</em>, things were slow, messy, and there were no conventions to speak of.</p><p>Looking back now, it’s hard to believe that people wrote web applications without a framework. And that’s the thing: compared to today, they largely didn’t.</p><p>The reason that Rails and Django have been so broadly adopted isn’t because it made writing web apps so much easier for people who were already writing them, it’s because they opened the door for so many new people to add writing web apps to their arsenal of skills. Users are attracted to frameworks that enable a wide swath of new technology at once. This is how frameworks gain wide adoption.</p><p>That pre-framework milieu of creating web applications felt a lot like what it feels like to develop and deploy a serverless application today. Even within a single cloud like AWS, there are way too many configuration options, services to stitch together, accounts to create, credit cards to enter, etc.</p><p>The complexity of XML Java config has been replaced with gigantic sentient CloudFormation YAML files which, once capable of describing themselves, may actually pose a threat to humanity. The cloud can be an intimidating place, and getting started with cutting edge tech like Lambda and DynamoDB just isn’t easy enough — or at least it wasn’t.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gmUOvox3m2mMn366xqUcVQ.png" /></figure><p><a href="https://begin.com/">Begin</a> is a serverless application platform that allows beginners and experts alike to deploy fully functional, production ready, secure, and scalable FaaS-based applications in under a minute. Begin is composed of three major elements:</p><ul><li>The <a href="https://arc.codes/">Architect serverless framework</a>, an opinionated, language-agnostic serverless application framework obsessed with usability and patterns</li><li>The <a href="https://begin.com/">Begin</a> frontend, which is mission control for your in-development and in-production applications</li><li>The Begin backend, which depoys, configures, and operates your serverless applications on top of AWS services</li></ul><p>When combined, you have a full-stack platform for developing, deploying, and scaling serverless applications that can provide the “gap-jumping” abilities that Django and Rails did for web applications because it focuses on one cloud, it was extracted from a serious serverless application, and it is very opinionated in the areas that count.</p><p>By focusing on the capabilities of the most advanced public cloud for serverless applications, AWS, Begin is capable of leveraging all of the tech that, when combined, make for the most on-demand and scalable application deployment platform available anywhere.</p><p>While the Architect framework and the Begin applications themselves are written in a modular, extendable way that will make adopting other clouds an option in the future, the fact remains that as of 2018, only AWS has the combined capabilities necessary to currently deploy performance intensive complex serverless applications.</p><p>At Begin, we have first hand knowledge of the capabilities of AWS and the limitations of other clouds. That’s because we were writing a complex, scalable, serverless-first application when we unknowingly began writing Begin.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3fcd53c5395e8398d86c7d50f61d6ac5/href">https://medium.com/media/3fcd53c5395e8398d86c7d50f61d6ac5/href</a></iframe><p>Much like the origins of Rails can be found in the Ruby application that made up the original Basecamp codebase, the origins of Begin can be found in a serverless realtime chat application platform that we started building in 2016. As we built out that original product, we began to realize the framework was bigger than the product itself — and extracted <a href="https://arc.codes/">Architect</a>.</p><p>After donating the framework to the <a href="https://js.foundation/">JS Foundation</a>, we built Begin on top of it as a serverless application platform. The current Begin frontend and backend helps erase so many of the complexities inherent in deploying serverless applications on AWS — and that’s because it’s opinionated.</p><p>If I had to guess why Rails and Django got so popular, and what made it possible for these kinds of frameworks to enable so many people to make applications that they weren’t making before, I’d say that it’s because of all of the decisions they <em>don’t force you to make</em>.</p><blockquote>It’s all because of the decisions frameworks <em>don’t force you to make.</em></blockquote><p>This became known as being “opinionated” back in the early days of Rails, which has philosophical roots in Martin Fowler and co’s <a href="https://martinfowler.com/eaaCatalog/">Patterns of Enterprise Application Architecture</a> book.</p><p>Patterns are helpful because they prevent duplicated effort and they make sure things get done the right way–in other words, patterns are opinionated. The Rails authors used these principles when they extracted Rails from Basecamp, letting the framework make hundreds of small, unimportant decisions for you, in addition to a small set of well thought-out important ones.</p><p>While not having to choose a filename here or a class name there may seem unimportant, all of these decisions add up and have a real drag on development time. It’s my belief that Begin has a real shot at gaining widespread adoption because knowing how to produce the correct YAML incantation to configure an API Gateway should not be a prerequisite for deploying a serverless HTTP API endpoint.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6f6a6d3c00f8994d2fa5dde49d013acd/href">https://medium.com/media/6f6a6d3c00f8994d2fa5dde49d013acd/href</a></iframe><p>While the opportunity presented by serverless applications is huge, the complexity of writing, deploying, and scaling applications on AWS from scratch is unapproachable for beginners, and still far too complex for the tastes of seasoned veterans. Begin aims to help a generation of programmers bridge the gap to serverless applications.</p><p>A focus on AWS, the experience of extracting from a real world application, and the attention on usability and opinionated sensible defaults means that Begin is miles ahead. And besides, it’s just plain fun to use — <a href="https://begin.com/">sign up for the beta and give it a shot</a>! We’d love to know what you think.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a6893051686" width="1" height="1" alt=""><hr><p><a href="https://medium.com/let-s-begin/the-real-reason-frameworks-get-adopted-1a6893051686">The real reason frameworks get adopted</a> was originally published in <a href="https://medium.com/let-s-begin">Beginners’ Guide</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Marketing Matters]]></title>
            <link>https://medium.com/reify/why-marketing-matters-2754f20aeb98?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/2754f20aeb98</guid>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Thu, 11 Oct 2018 16:58:11 GMT</pubDate>
            <atom:updated>2018-10-29T15:31:49.066Z</atom:updated>
            <content:encoded><![CDATA[<p>A web version of my Velocity NY 2018 Keynote</p><p><em>I was honored to be given the opportunity to give a keynote address at O’Reilly’s 2018 Velocity Conference in NYC. Below is a web version of the talk — not a transcript, but a summary of the main ideas (with fewer jokes). I hope you enjoy.</em></p><p><em>Update: The full talk is online!</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhykHdV0So6M%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhykHdV0So6M&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhykHdV0So6M%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/647743cb7407ecced883e01bff867add/href">https://medium.com/media/647743cb7407ecced883e01bff867add/href</a></iframe><p>Before I jump into the meat of the talk, I was told that all keynotes must begin with big, bold, provocative statements. I though to myself “I like big, bold, provocative statements — that sounds fun!”</p><p>So here’s mine:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fmhys3WUrF_YWcpOP6lIsA.png" /></figure><p>Let that sink in while we dive into the talk — we’ll get back to the provocation in a little bit. The title of this talk is “Why Marketing Matters,” which I wrote to answer a question I get some flavor of quite regularly. I guess this is what happens when you preach the value and necessity of marketing to software companies all the time — people will eventually ask “So … why does marketing matter?”</p><p>After thinking for a while trying to find a good way to answer this, something occurred to me. Asking “Why does marketing matter?” is sort of like asking “Why do people matter?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FoU6ZMySZOSM0SBnMIyOiQ.png" /></figure><p>Or put another way, it’s sort of like asking “Why does adoption matter?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGAhmWWekBdZE5bLIRHBug.png" /></figure><p>Why does it matter if anyone uses your software, or believes in your solution? Why does it matter if it never gets beyond a few people checking it out on your GitHub profile? It’s important to note that for some people it definitely doesn’t matter: there is always room for side projects. One of the best things about knowing how to write code is that you can scratch your own itches any time — please do not stop doing this.</p><p>However fun and cool hobby coding is, however, that’s not what I’m here to talk about. I’m here to address the people who are trying to build a software business, a software community, or both. For those folks, <strong>adoption is everything!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OU7p0zM8u3bzM-qSlqJzqA.png" /></figure><p>Since adoption is the key thing for people using software to solve other people’s problems, I wanted to dig into the prevailing attitudes amongst self-identifying Open Source developers and advocates. So while I was working on the content for this talk, I did what any sane person with a question does — I asked Twitter.</p><p>Between the $100 I spent promoting the tweet (my apologies if you saw this in your TL too many times) and the magic words “Please RT,” nearly 1,200 people answered this question:</p><blockquote>How important is marketing to the adoption of software?</blockquote><p>To be honest, the results were very surprising. When I turned them into a graph, they look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_AG79FBbxow42VnoQTEN5w.png" /></figure><p>I squashed the positive and negative categories down into one column each, which revealed that <strong><em>88% of respondents said marketing was important or very important to the success of a project.</em></strong></p><p>This did not meet my expectations, since I’m basically conditioned to think that technical people don’t appreciate or understand the basics of marketing and how important it is to the success of software communities or businesses. When I took a step back, however, I started to think about the results a little bit differently.</p><p>Instead of being bummed out that I mis-predicted the results, I started to feel a sense of hope — here’s why. If this many people feel that marketing is crucial to adoption, and not many of us are actually doing it, that means we have tremendous room to improve, and the hard part (convincing people that it’s worthwhile) is already done! The only thing left to it, as they say, is to do it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cp85ATDkJBNwZ2yayfb2YA.png" /></figure><p>The results also looked similar to a graph (completely made up and not based on data) that I often draw for people when they approach me asking my advice for how they can improve their software business or community toward the end of improving adoption.</p><p>“It’s this much writing code,” I usually say, holding up my hand and displaying a tiny gap of air between my thumb and pointer finger — “and THIS MUCH MARKETING,” spreading my arms out as wide as they can go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x17vPE0CpszGKFxQoG37xg.png" /></figure><p>So if it’s true that marketing is essential for adoption, my hypothesis can be stated simply:</p><blockquote>More and better marketing leads to more and better adoption.</blockquote><p>Stated differently, taking the time up front to build audience and interest will pay off handsomely when it comes time to actually sell your software or grow your community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iQNgf6Pbuw0hQ5vc5JWBSg.png" /></figure><p>If this hypothesis is correct, I think we’re in pretty good shape! As an engineer, I always like having a clear cut task in front of me, and I think this is one of those situations. Since we all want more adoption, we “just” need to improve at marketing.</p><p>That’s what I want to do: help everyone improve at marketing, right now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-zs0GohSTEjHzH2wE1fKuQ.png" /></figure><p>But after thinking about how we need to improve at marketing, I realized something important: to get better at it, we need to be able to appreciate it — as in really respect and trust the work that the people in charge of marketing do. We must really believe in it — it’s not something you can just do passively, not something you can sign up for and never follow through on. Improving at marketing must be an active, dominant process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t4nSnMYJJZJXh5GTV17WvA.png" /></figure><p>Taking even another step back, it occurred to me that if I want to get people to <strong>appreciate</strong> marketing toward the end of <strong>getting better at it</strong>, I really need them to understand it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O8-d8cXq37oTRFSsbmB_yw.png" /></figure><p>So let’s start right now. I want to help you understand marketing: what is it? What are the people who say they are doing marketing actually doing?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6f8D5vVL_Dr-Ald5rQzmBQ.png" /></figure><p>This is going to sound weird, but I think that the heart of understanding marketing is right there in the word.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1vFzox9ayEcUscLKtgI9-Q.png" /></figure><p>If you take the word literally, “Market-ing” your software is really all about getting it ready for market. Doing all of the things besides coding and operating your project. Doing all of the things that improve the experience for the people who you want to use your project.</p><p>The other mandatory element in keynotes besides a big, bold, provocative statement, is a parable. So here’s mine, in support of why marketing is so important.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-_7SObSiqhiPLn_YSXiveQ.png" /></figure><p>Close your eyes and imagine that instead of being involved in software, you’re a farmer. Since it’s likely that not everyone reading this knows how farming works, I’m going to break it down for you.</p><p>THIS is exactly how you can become a successful farmer:</p><ol><li>Get some land</li><li>Prepare the land</li><li>Get some seeds</li><li>Plant your crops</li><li>Water your crops</li><li>Watch your crops grow</li><li>Sit on your ass and wait around for people to come and buy your crops</li></ol><p>That’s how farms work! I’m not sure if you knew that!</p><p>Obviously, it’s not, and I’m just trying to make a point. This would never work in farming, and in reality, it doesn’t work in software either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qU1Boarr_SZwqOzM4_PoiQ.png" /></figure><p>To make this a little bit more concrete, I spent a few minutes with my business partner Brian coming up with this list of activities. These are some of the things that we could all be better at doing, at thinking about earlier on in the process of building communities or companies. If we never did any of these things, and all we did was write code, no one would ever use our software.</p><p>And keep in mind — this is a hell of a lot of work! It’s usually the responsibility of one or two individuals at companies (who are typically compensated very poorly relative to their ‘technical’ colleagues), or volunteers for Open Source projects that do this for free. In other words: in undervaluing the activities that go into Marketing, a crucial component of software adoption is severely undervalued and misunderstood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SKfmGXudW8ejhG5VMwMeFw.png" /></figure><p>Now we know that marketing software toward the end of getting it adopted comprises a ton of activities that are often opaque to the people building the software. And so having established a very loose definition of marketing toward the end of understanding it, I want to chat a bit about why I don’t think it’s properly appreciated by this very audience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Azm9jAy9YPhVda957Iolmw.png" /></figure><p>When I sat down and thought about why the typical developer may not appreciate marketing as deeply as they could, I thought about my own time as a professional programmer. During this reflection, three aspects of my relationship with marketing popped out at me, which in my experience apply to a large number of developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xwwTyfiFT4Z5Z4IxNCknJg.png" /></figure><p>First is interest. On a scale from not very interested to very interested, my experience is that many developers remain, to put it politely, EXTREMELY !@#ING UNINTERESTED.</p><p>This might be because they perceive marketing as being “squishy” or “soft” while programming is “concrete” or I guess … hard? The reality is that stepping outside of your comfort zone and really understanding the discipline behind understanding your users and what they care about is hard!</p><p>Beyond interest though, I think there are deeper issues preventing developers from truly appreciating marketing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EIXzTDTkC4QM4SqfNm6mig.png" /></figure><p>Because of the perception of developers that they don’t care about marketing, or because of the realities of the market, or whatever the cause, it is also my experience that developers are not given the opportunity to participate in marketing.</p><p>Sometimes they are given the task of writing a blog post or giving a talk in public, but in terms of the real nitty gritty of marketing, they aren’t given the say that they should often have, as stakeholders, to express how their deep understanding of the domain can inform marketing and product direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A_mPU248poWxIWEjMQZM7Q.png" /></figure><p>And so it essentially boils down to this: the perception that developers don’t care about marketing is embraced by leadership who don’t give developers the opportunity to participate, and this leads to a complete lack of encouragement. Developers are encouraged to pursue all kinds of interests, but I have very rarely seen real deep encouragement on the behalf of company leadership intended to get developers more and actively involved and interested in the crucial foundational aspects of marketing that they should be.</p><p>And I think this is wrong!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rONPqO_5OzN_A8i9XoWhIA.png" /></figure><p>So here it is: I am encouraging you! You hath been encouraged!</p><p>Whether you’re an open source developer who wants to get their software adopted, or a budding entrepreneur who wants to sell your product, or an engineer at a startup who wants to understand why you spend your time the way you do: I hereby encourage you — go out and learn! Improve!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KDpVHZGpwoNBVPJJdUZBqQ.png" /></figure><p>Don’t worry: I’ll tell you how.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KMvObYRpBoZsfVsG2P2mgA.png" /></figure><p>The single most important thing that you can do to be better at marketing and therefore get more people to use your software is to simply shift this timeline. In terms of the life of a project, here is where most projects start to consider the foundational elements of marketing I’ve been alluding to. As you can probably guess, I think that’s a little too late. Or maybe a lot too late.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rXxNHFQ0Gw1X9HFvrNrCOA.png" /></figure><p>If you want to nail marketing because you want to give your project the best chance of adoption, do this: think about it from the beginning. Before you even write a line of code, you should be conducting interviews with people who you think might use it. Before you raise money and hire several engineers you should be confident about your market and the message you’re selling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uqmumfq0nihV8hIO-o5v9w.png" /></figure><p>If you don’t start when I suggest, you need to be prepared to understand that everything happening during this gradient rectangle I’ve so expertly drawn may just be a waste of time. If you don’t know who your audience is and what message you’re trying to convey, you’re not calibrating properly. If you’re not participating in at least a handful of that long list of marketing activities, you’re just coding in a vacuum.</p><p>And coding in a vacuum doesn’t make successful projects or companies: it just makes one-off side projects. Which is fine when that’s what you’re after — but if you’re after adoption, the answer is easy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lwl5sAuCXvgcDdp0yQgpBQ.png" /></figure><p>If it’s worth building, it’s worth marketing. Or to put it a little more bluntly:</p><blockquote>If you build it — they won’t come. Unless you tell them about it.</blockquote><p>So do the hard but correct thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fCwrNsgj7zPVG3kldtwEQ.png" /></figure><p>Start now!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*honaeBzky_L_MlA7YbI7wA.png" /></figure><p>Define your audience: who are you trying to reach?<br>Design your message: what are you trying to communicate?<br>Refine your product: make your product match these expectations.</p><p>And then rinse and repeat until it starts to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19NuOOW36EiJcYOhYejVpg.png" /></figure><p>Because you didn’t do all of this hard work just to let your fruit rot on the vine.</p><p><em>Interested in learning more about how we can help you get better at marketing? Check out our </em><a href="http://reifyworks.com/"><em>website here</em></a><em>, or</em><a href="/service/mailto:hello@reifyworks.com"><em> email us today</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2754f20aeb98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reify/why-marketing-matters-2754f20aeb98">Why Marketing Matters</a> was originally published in <a href="https://medium.com/reify">Reify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Marketing “Decafail” — Ten Mistakes You Can’t Afford To Make]]></title>
            <link>https://medium.com/reify/the-marketing-decafail-ten-mistakes-you-cant-afford-to-make-42a418b02110?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/42a418b02110</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Tue, 21 Aug 2018 16:04:30 GMT</pubDate>
            <atom:updated>2018-12-13T14:30:24.280Z</atom:updated>
            <content:encoded><![CDATA[<p>Avoid these problems today to make your tomorrow more certain</p><p>At <a href="https://www.reifyworks.com/">Reify</a>, <a href="https://www.reifyworks.com/clients">our list of clients is growing</a>, we’re seeing the inner workings of more software companies, and we’re starting to notice some patterns. Comparing our direct experiences with the anecdata we’ve gathered from talking to founders and other colleagues in marketing, it’s becoming clear that there are certain mistakes that software companies can’t afford to make when it comes to marketing their products. Since people ask us all the time what they can do to be better at marketing, we thought we’d put this list out there in the hopes that it can help us with our mission to make everyone take marketing more seriously so that they can sell more software. We hope you enjoy.</p><p><strong>Mistake #1: Putting off on marketing until it’s too late<br></strong>The number one mistake software companies can make is to not take marketing seriously. This is usually a symptom of the belief that “what’s technically best will end up winning.” There are countless counterexamples to this point: oftentimes, whoever markets the best wins. Don’t lose because you overlooked this crucial activity.</p><p><strong>Mistake #2: More than one persona<br></strong>Companies that overcome the anti-marketing attitude that is pervasive in B2B software often stumble by trying to market to everyone at once. They read a bit about marketing, develop five personas, and wonder why it’s not working. <a href="https://blog.reifyworks.com/you-only-need-one-buyer-persona-for-now-4aed622b7494">We have some ideas about why</a>. First, get good at marketing to your core audience. Don’t run before you can crawl.</p><p><strong>Mistake #3: No messaging framework</strong> <br>Marketing gets a bad rep for being “squishy,” a “soft skill” that is “boring,” unimportant, and silly. Obviously, we feel differently. We take <a href="https://blog.reifyworks.com/how-to-write-persona-driven-marketing-copy-that-never-misses-its-mark-e445e4ade33f">a rigorous approach to helping our clients develop the best, most resonant messaging for their persona</a> (notice this is the singular persona, not the plural personas). If you don’t use data to develop your messaging, you’ll waste a ton of energy and risk failing before you ever get a chance to market properly.</p><p><strong>Mistake #4: That same old homepage<br></strong>It’s amazing how many software companies can go through rounds of fundraising, hundreds of thousands of dollars in ARR, and explosive employee growth, and still keep that same old homepage live. The one the founder threw together the night before launch. The one that you paid that web design company to make. The one that you didn’t even know had a typo on it. Your homepage is the front page of your product, the place more people will look than any place else. Develop your persona, produce your message, and make sure your homepage stays up to date with your value proposition — before you start to wonder why so many people think you’re selling your product from three years ago.</p><p><strong>Mistake #5: Never changing pricing<br></strong>Pricing and packaging software is extremely hard — so much so that we worked with Heavybit to produce <a href="https://www.heavybit.com/devguild/pricing-strategy/">a day long conference on the subject</a>. The top takeaway for us and many of the attendees was this: pricing is a subtle art that, much like your homepage, needs to change with your product and the needs of your users. Don’t settle for what you came up with before you knew what value you were bringing to your customers. Tweak your pricing until you’re confident. It’s the web — nothing is set in stone.</p><p><strong>Mistake #6: No feature faceting in pricing<br></strong>One of the most challenging aspects of pricing is how your product is packaged. A key technique in making sure your pricing aligns with the value you bring to your customers is feature faceting — aligning the pricing of your product with the features that different groups of customers need. If you give every feature of your product to every company and only charge differently based on usage, you’re missing out on a key price discrimination technique that may damage your ability to sell your software for the price you deserve to get. Check out <a href="https://www.enterpriseready.io/">our friends at Replicated’s enterpriseready.io site</a> for more ideas here.</p><p><strong>Mistake #7: No use of social proof<br></strong>The strongest signal that you can send to potential customers that they should try your product is the use of social proof. Seeing a company that they admire or know using your product will make your potential customers try your product out, or at least give you enough of a chance that they’ll read your homepage. Social proof is a deep, complicated subject — <a href="https://blog.reifyworks.com/a-maturity-model-for-social-proof-133de0bb0e23">check out more of our writing about it here</a>.</p><p><strong>Mistake #8: Selling green juice, not juicers<br></strong>The #1 idea that we try to communicate to our clients who are sold on diving into marketing and taking it more seriously is this: sell the what, not the how. “Value-based marketing” is a well-trodden term, but we think we’ve got a pretty unique way of describing what’s at the heart of the idea — <a href="https://blog.reifyworks.com/dont-sell-green-juice-sell-juicers-b8b763aab1c3">check out our blog post about juice and juicers here</a>.</p><p><strong>Mistake #9: Marketing for audience when you need buyers<br></strong>Sometimes<strong> </strong>clients engage with us because they have an interesting problem — they can write blog posts that get attention, they can climb the ranks on Hacker News, they get lots of RTs, but one problem remains: they’re not selling more software. Sometimes this comes down to one simple fact — eyeballs and dollars aren’t the same thing. Make sure that your external marketing activity is oriented around speaking to the potential buyer of your product if you need buyers. This can mean stepping outside your comfort zone if you’re a developer selling to enterprises, but it’s crucial. Typically, your bottom-up approach will only take you so far, and eventually, you will have to start marketing to the audience that will end up paying your bills.</p><p><strong>Mistake #10: Using too many words <br></strong>We hate to say it, but you talk too much. Too many words and too much jargon leads to confusion. There is an art to the parsimony of words you find in most marketing material, and though many people jeer at it, they can’t deny this: it works. We’ve written up some guidelines for how many words you should be using and where <a href="https://blog.reifyworks.com/messaging-numbers-every-entrepreneur-should-know-fd79474fba85">here — check it out</a>.</p><p><em>Some of these mistakes hitting a little too close to home? Want to avoid making the others? </em><a href="/service/mailto:hello@reifyworks.com"><em>Let’s chat</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42a418b02110" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reify/the-marketing-decafail-ten-mistakes-you-cant-afford-to-make-42a418b02110">The Marketing “Decafail” — Ten Mistakes You Can’t Afford To Make</a> was originally published in <a href="https://medium.com/reify">Reify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Architect, The Killer Serverless Framework]]></title>
            <link>https://medium.com/reify/architect-the-killer-serverless-framework-41565372811b?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/41565372811b</guid>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Mon, 11 Jun 2018 16:54:14 GMT</pubDate>
            <atom:updated>2018-06-11T23:26:21.577Z</atom:updated>
            <content:encoded><![CDATA[<p>Or: The Dream Of the 2000s Is Alive In <a href="http://arc.codes/">Architect</a></p><p>I’m a believer in the power of frameworks, and for good reason — the bulk of my career as a programmer and technology leader involved the use of Rails. During those early years (starting in 2006), I witnessed first hand how the potent combination of innovation, community, and proper stewardship could lead to massive advantages in product efficiency, hiring potential, and more. Since then, more than one company that relied on Rails has gone public, and dozens more companies have likely generated billions of dollars of revenue. Besides that, I <strong><em>still</em></strong> feel comfortable and confident using Rails, after all these years, and feel like it would be difficult to match its productivity for its chosen domain.</p><p>Since Rails was born, I’ve seen plenty of frameworks come and go, and have poked at a few here and there out of curiosity — I wondered if any could capture the right combination of nailing the abstractions and providing the right community framework. The first that has really caught my attention in that time is called <a href="https://arc.codes/">Architect</a>, and just as Rails leveraged Ruby to unleash massive potential for web development, Architect leverages Node and NPM to finally bring some structure and insight to the AWS Serverless landscape.</p><p>After seeing one of the framework’s creators <a href="https://twitter.com/brianleroux">Brian Leroux</a> speak at a conference about Architect, I decided to try it out. A lot of the ideas that Brian covered in his talk appealed to me: the desire to paper over AWS’s abstractions, the power of the NPM CLI ecosystem, how confusing it could be to approach a Serverless application that doesn’t follow conventions, and more. From his presentation, I was especially intrigued with the .arc file format, which describes an Architect application. Before I say anything more about what the functionality of the application I made, take a look at the .arc file:</p><pre><a href="http://twitter.com/app">@app</a><br>brainjams</pre><pre><a href="http://twitter.com/html">@html</a><br>post /sms</pre><pre><a href="http://twitter.com/events">@events</a><br>sms-emitter<br>stats-recorder</pre><pre><a href="http://twitter.com/tables">@tables</a><br>recommendations<br>  phoneNumber *String</pre><pre>jams<br>  id *String</pre><p>I think even without knowing much about the framework, you can get a pretty good idea about what these lines do. Similarly to describing database tables or routes in Rails and then having functions generated for you by running a script or at runtime, Architect takes an .arc file like the one above as input, and when you invoke the npx create command (<a href="https://arc.codes/reference/arc-create">documented here</a>), it compiles your directives into configured and provisioned AWS infrastructure . No need to set up API Gateways, wire components together, fuss with security roles, configure countless services, or really even know very much about how these pieces work together. It just works. Just as I like it.</p><p>The .arc file for Brain Jams creates one HTTP endpoint, scaffolds two SNS events for sending SMS messages and recording stats in a database, and configures two DynamoDB tables with primary keys. All of this infra is provisioned and configured for me, and the UX is a pleasure.</p><p>Beyond being used to generate infrastructure, the .arc file is the entry point into all Architect applications — sort of like running rake routes was the entry point for a lot of Rails programmers when trying to find their way around an application. Here’s what the capabilities of the framework include at this point:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5sG2pzw5PFhF932EgSXU-w.png" /><figcaption>The current list of .arch file sections, which is growing regularly.</figcaption></figure><p>Note that Architect is been actively developed —at this point you can use .arc files to provision all kinds of useful infrastructure for developing event-driven cloud applications, from S3 buckets to DynamoDB tables to CSS and XML HTTP routes. In the future, who knows what this file will let you do, or the diverse set of services or patterns it may encapsulate.</p><h3>An intro to Brain Jams</h3><p>On to the application I built, called Brain Jams (named after a segment of my on-hiatus podcast with <a href="https://www.kingstonbreadlab.com/">AQ</a> called <a href="http://beatsryetypes.com/">Beats, Rye and Types</a>) — here’s a use case scenario (sorry, I’m a marketer):</p><p>Let’s say you’re out and about, and suddenly you need a jam to fit your mood, but your old standby playlists won’t do. We’ve all found ourselves in this situation, right? Well now instead of just listening to the same old thing, you simply text some words to Brain Jams, which <a href="https://www.npmjs.com/package/sentiment">very naively measures the sentiment of your text</a>, and it responds with a song that has been tagged by hand (by me) to match that sentiment.</p><p>Dope, right? Here’s a screenshot of the application in action:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*65-_WX1VuyvyBR4BTGI6wA.png" /><figcaption>SMS gateway to the jams</figcaption></figure><p>Perfect jams, every time. Guaranteed.</p><p>The entire application is around 150 Lines of Code, and was built using Twilio and Architect. Here’s a diagram of how the pieces fit together:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*secUyCpvCGiY7jC7aw6yBg.png" /><figcaption>A high-level overview of Brain Jams’ application internals</figcaption></figure><p>The best part about Architect is that I didn’t have to do almost anything besides write the .arc file, implement a few JavaScript functions, and use the various npx commands to test locally, deploy to staging, and then to production. Architect does a lot for you, and as the old saying goes, <em>look at all the things we’re not doing</em>.</p><h3>Check out Architect, and Contribute</h3><p>In the past year or so, I’ve become quite bullish on Amazon’s implementation of the services which have been come to be used in Serverless architectures, but I haven’t had very many nice things to say about the experience of actually trying to use them on my own.</p><p>Now that Architect exists to make me not have to worry about or care how most of the moving parts work, I’ve been able to put together more than one experiment to scratch various development itches I have. It’s going to be an interesting experiment seeing how getting a few of these things into production will fare. Currently I’m relying on AWS Console tools like Cloudwatch to figure out what’s going on behind the scenes when necessary, but I’m planning on giving <a href="http://iopipe.com/">IOPipe</a> a shot to see what kind of insight that product can provide.</p><p>Building this project has been a blast. Kudos to the Architect team for focusing on users and realizing that a key strategic position will belong to whichever community seizes on the opportunity to make Serverless as usable as it is cool.</p><p><strong>Find Architect </strong><a href="http://arc.codes/"><strong>here</strong></a><strong>, at </strong><a href="http://arc.codes/">http://arc.codes</a>.</p><p><em>If you check out Architect and make something with it, </em><a href="/service/mailto:mrb@reifyworks.com"><em>let me know how cool you think it is</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41565372811b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reify/architect-the-killer-serverless-framework-41565372811b">Architect, The Killer Serverless Framework</a> was originally published in <a href="https://medium.com/reify">Reify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You only need one buyer persona (for now)]]></title>
            <link>https://medium.com/reify/you-only-need-one-buyer-persona-for-now-4aed622b7494?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/4aed622b7494</guid>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Wed, 09 May 2018 16:09:45 GMT</pubDate>
            <atom:updated>2018-05-09T16:09:45.639Z</atom:updated>
            <content:encoded><![CDATA[<p>How we think differently about buyer personas for B2B software companies</p><p>Our goal at <a href="http://reifyworks.com/">Reify</a> is simple: to help software companies sell more software. The most consistently impactful way that we’ve been able to achieve this is by helping companies define and articulate their messaging — in other words, they need to get really good at explaining to a potential user how they’re going to <a href="https://www.amazon.com/Badass-Making-Awesome-Kathy-Sierra/dp/1491919019">make them awesome</a>. Our thesis is simple: at the heart of selling more software is messaging, and at the heart of messaging is a user persona — so that’s always where we start.</p><p>When we’re pitching a client on a messaging engagement which includes helping them define their buyer persona, though, we notice something comes up a lot — they’ve already done some work defining a persona, usually with another marketing consultant, a branding agency, or sometimes at the behest of someone internally. This is always a good sign, because they’ve already begun to think about the user being central to successful marketing.</p><p>Sometimes, though, it causes a conflict, because our pitch makes it sound like the work that they’ve already done isn’t useful, and that we want them to duplicate that effort. This has happened enough that we wanted to take the time to document our persona discovery process and why we think it’s sufficiently different from the typical process to warrant going through ours to augment the work a company has already done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eUNs7wzgxUWxV1sme0UOrA.png" /><figcaption>What do you need to care about? What do you leave out?</figcaption></figure><h3>There can be only one</h3><p>The first thing we’ve told every company that we’ve worked with that has developed several personas has been the most contentious each time: you only need one. It can be Patrick Project Manager or Emily Engineer or Victoria VP of Engineering, but there can be only one. It’s time to choose between SMB Stephanie and Enterprise Erica, now — and the reason is really simple: most organizations can’t learn how to market to multiple personas at the same time because they don’t have the bandwidth, expertise, or both. Since our clients tend to be smaller operations that are still learning to develop their marketing muscle, typically having anywhere from zero to two or three people involved in marketing (and maybe none full-time), this is doubly true.</p><p>This doesn’t mean that you can’t eventually market to SMB and Enterprise at the same time, or develop campaigns for developers and whitepapers for CIOs, somewhere down the road. But now, while we’re working together, trying to find the very essence of the essence of your product and the value it brings to your customers, it just ain’t happening. There can be only one.</p><h3>Drop the wrong details and keep the right ones</h3><p>Once we settle on the general persona we’ll pursue, our discovery process begins with the questions in <a href="https://docs.google.com/document/d/19xBJml2V9EqzkLX6kAkcDrsOP4YaBY9Qen_tzK8Hsnk/edit?usp=sharing">this Google Doc</a> (which is based on <a href="https://www.geckoboard.com/blog/buyer-personas/#.WJIvXbYrKgQ">this great Geckoboard post</a>). Instead of noticing what we ask in this questionnaire, we want you to focus on what we don’t ask about: things like educational background, where they live, where they work, what kind of coffee they drink, etc. Instead of focusing on more surface-level questions (which are very helpful for branding and general marketing purposes, but fall down when looking for targeted messaging), we focus on the <em>domain specific</em> aspects of the user — what tools do they use to do their jobs? How large is the company? What other technology do they already use?</p><p>Remember, we <em>already know quite a bit about this individual by virtue of the fact that they work at a software company. </em>We’re not trying to sell a soft drink or a fashion line that is meant to have broad appeal. We’re working in a niche within a niche — software developers in the market for B2B software. The fact that we’re marketing to a niche can seem limiting — and it is! But don’t fret — this is a very, very good thing!</p><p>Because we know that we’re marketing to tens of thousands of potential customer instead of millions and millions, we know that there’s a whole lot that we don’t need to care about, and it lets us focus on what we should. Because our niche is so niche, you could get away with only asking three small sets of questions:</p><ul><li><strong>Company details</strong>: What size is the company? What kind of revenue stream do they have? What challenges do they face?</li><li><strong>Success criteria: </strong>What does this individual need to be successful in their role? How can your product help them achieve this?</li><li><strong>Potential objections</strong>: What reasons might this individual have to not use your product? How can you overcome these objections?</li></ul><p>Rounding out these lines of questioning with a few more details is more than enough to get you going down the road of developing messaging for the persona you’re trying to target. But first, one more trick.</p><h3>Make up a fake title and call it a day</h3><p>One of our favorite aspects of doing domain specific persona work for companies is making up fake titles. Since it’s not usually good enough to say that we’re marketing to Senior Engineers or VPs of Marketing or even CIOs, we often push companies further to think about the person that they’re trying to reach.</p><p>For a payments related company, it might be “The Payments Master.” For anything related to monitoring, you might want to call them the “Chief Monitoring Officer.” The person who always gets tapped when how to deal with sensitive data comes up might become the “VP Of Sensitive Data.”</p><p>While this may seem like a trivial component of persona definition, it’s actually anything but. The fake title is a tacit understanding that <em>no two software companies are created equal</em>, and that you can’t rely on titles alone to find the person you need to be marketing to within any given company. You’ve got to dig deeper.</p><h3>So start with your one, right now</h3><p>Make a copy of <a href="https://docs.google.com/document/d/19xBJml2V9EqzkLX6kAkcDrsOP4YaBY9Qen_tzK8Hsnk/">this Google doc</a>. Pass it out to a few stakeholders at your company. Focus on one path, and answer the questions to the best of your ability. Combine everyone’s answers, and have a conversation about them. Give them a fake title, compile them into the headings in the second part of the doc, and when you’re done, you’re ready to start working on your messaging. Curious how to get started there? <a href="https://blog.reifyworks.com/how-to-write-persona-driven-marketing-copy-that-never-misses-its-mark-e445e4ade33f">We’ve got you covered</a>.</p><p><em>If your software company is looking for its story, we can help — </em><a href="/service/mailto:hello@reifyworks.com"><em>get in touch</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4aed622b7494" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reify/you-only-need-one-buyer-persona-for-now-4aed622b7494">You only need one buyer persona (for now)</a> was originally published in <a href="https://medium.com/reify">Reify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Marketing Doesn’t Work]]></title>
            <link>https://medium.com/reify/why-marketing-doesnt-work-115160e6e287?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/115160e6e287</guid>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Thu, 03 May 2018 17:04:33 GMT</pubDate>
            <atom:updated>2018-05-03T17:04:33.423Z</atom:updated>
            <content:encoded><![CDATA[<p>…and what you can do about it</p><p>Marketing works. We all know it internally, even if we resent it at times. We know it works because we’ve all been successfully marketed to in numerous areas of our lives, both personally and professionally. Unfortunately though, sometimes Marketing doesn’t work, and if you’re the one responsible, it can be overwhelming and very frustrating.</p><p>Part of what makes diagnosing issues with Marketing so challenging is that it’s such a <em>big</em> activity. It’s easy to point at this or that number and say “it’s not working!” but it’s harder to take that information and <em>do something about it</em>. Because making <a href="https://en.oxforddictionaries.com/definition/reify">abstract things concrete is kind of our thing</a>, we decided to make this easier for everyone by doing one of our favorite things — <strong>we made a chart!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/879/1*hGbhZvq9gttKf2eTBcPTPQ.png" /><figcaption>It works until it doesn’t</figcaption></figure><p>For every part of your customer journey, we’ve named a specific problem, and something you can do to help solve it. The next time you’re feeling anxious about marketing, try this: take a step back, look at the chart, pick one area of your customer journey to work on, and start executing!</p><p><strong><em>Locating your audience</em></strong> means doing more than writing blog posts, posting them to HN, and hoping for the best. It means thinking hard about the people you are trying to reach, learning where they congregate, and tailoring your marketing to them directly.</p><p><strong><em>Calibrating your messaging </em></strong>means taking a hard look at what you’re communicating to your potential users, and making the necessary changes to communicate more effectively. Often, software companies settle on messaging early, and even as they tout themselves as <em>agile companies</em> that ship daily, they don’t take the time to tweak their messaging to make up for that delta. This can have serious and negative consequences as time passes.</p><p><strong><em>Tweaking your onboarding</em> </strong>is another area that tends to lag behind as products change. Your original onboarding experience likely leaves some things to be desired for new users and new audiences as your product and the market changes. If you’re struggling to gain traction, this is another area that deserves your regular attention — it’s the first chance you have to make a great impression on potential users.</p><p><strong><em>Examining willingness to pay</em></strong><em> </em>comes from our favorite book about pricing, <a href="http://monetizinginnovation.com/"><em>Monetizing Innovation</em></a><em>. </em>One of the central principles of the book is that big mistakes get made when products are brought to market without asking potential customers one simple question — <em>what are you willing to pay?</em> If you’re curious about this, read the book — it’s worth it.</p><p>Finally, <strong><em>investing in proper tooling</em></strong> can be a tough pill for some to swallow, but the dividends can be massive. By proper tooling we mean not building your own analytics pipeline, not hosting your own blog in a static site, etc. — basically, not reinventing the wheel. Invest in some solid marketing automation software, partner with a consultancy that can help you implement, and then start running and never look back.</p><p>Of course, this isn’t meant to be an exhaustive list by any means (though we’re thinking of working on a webapp version that has more suggestions — should we?). Instead, it’s designed to jar you back to remembering two things that are very important and all too easy to forget:</p><ol><li>Worrying won’t solve your problems (if it did, we’d literally have zero problems); and</li><li>Marketing is an every day practice, not something you do in an erratic frenzy to occasionally assuage your guilt.</li></ol><p>We hope this helps! <a href="/service/mailto:hello@reifyworks.com">Shoot as an email and let us know what you think.</a></p><p><em>If your software company needs help translating a helpless feeling of “We’re not doing marketing well enough!” into a sense of ownership and a concrete set of steps to take, </em><a href="/service/mailto:hello@reifyworks.com"><em>get in touch</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=115160e6e287" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reify/why-marketing-doesnt-work-115160e6e287">Why Marketing Doesn’t Work</a> was originally published in <a href="https://medium.com/reify">Reify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to spend money on Marketing when you don’t have money to spend on Marketing]]></title>
            <link>https://medium.com/reify/how-to-spend-money-on-marketing-when-you-dont-have-money-to-spend-on-marketing-b1f4aff40e0c?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1f4aff40e0c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Tue, 03 Apr 2018 16:43:26 GMT</pubDate>
            <atom:updated>2018-04-03T16:43:26.762Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s easier than you think</p><p>One consistent takeaway from <a href="https://www.key.com/kco/images/2017_KBCM_Technology_Group_Private_SaaS_Company_Survey.pdf">industry-sweeping surveys of how software companies operate</a> is that <em>faster growing companies spend more money on sales and marketing than slower growing companies.</em> This is something that most founders we talk to at <a href="http://www.reifyworks.com/">Reify</a> have internalized: they know that in order to make more money, they have to spend more money.</p><p>So if the problem isn’t a lack of information, what is it? Most founders would say that it’s even simpler than that — it’s a lack of money. You can’t spend money that you don’t have, or more precisely, <em>you won’t spend money that you don’t want to spend</em>, or to put an even finer point on it <em>you just aren’t going to spend money on marketing because it’s much easier to see the impact of an engineering hire and that’s what you’re used to</em>.</p><p>Fortunately, we have a solution for founders, executives, and good storytellers at software companies who want to spend money on marketing but don’t think that they have the money to spend — <strong>spend time instead</strong>.</p><p>The best way to convince yourself to take the function of Marketing seriously in your organization is to get a little bit of a taste for what successful marketing feels like, and the impact that it can have on your bottom line.</p><p>Just so we can avoid being accused of thought-lording you into spending more money on Marketing without giving you any constructive ideas, here are three ways you can spend some time and not any money* on marketing to make it way more likely that you’ll spend more money and less time on marketing in the future:</p><ul><li><strong>Send three newsletters to your mailing list in three months</strong>: This doesn’t seem very lofty, does it? If you don’t have a mailing list, set one up instead! Mail your customers! Mail your trial users! If you need more ideas, <a href="/service/mailto:hello@reifyworks.com">shoot us an email and we’ll give you a free 15 minute consultation to help you brainstorm.</a></li><li><strong>Write three blog posts in three months: </strong>We know you can do it. You probably have some ideas already, don’t you? If you want to get started, here’s a tip: Separate your planning from your writing. Spend one 60 minute session brainstorming 3 topic ideas, and then just commit. Keep them short and sweet, and keep your audience in mind. <a href="/service/mailto:hello@reifyworks.com">If you’re not sure what to write about, shoot us an email and we’ll give you a free 15 minute consultation to help you figure it out.</a></li><li><strong>Get one post published on a partner company’s blog: </strong>This will probably take a few months on it’s own. Getting referral traffic from partners or likeminded companies can do wonders for your traffic, can bring you new eyeballs, and get you in the habit of thinking strategically about your market place positioning. <a href="/service/mailto:hello@reifyworks.com">Not sure who to contact? Shoot us an email and we’ll give you a free 15 minute consultation to help you find a good partner.</a></li></ul><p>*<em>Yes, we know that your time is money. We’re trying to trick you. We really hope it works.</em></p><h3>Isn’t this kind of self-serving of you?</h3><p>Maybe a little, but isn’t all good marketing? Seriously though, we’ve been beating this drum for a long time — things will get better for everyone if technical problem solvers and business problem solvers cooperate earlier on in the lifecycle of startups. More thinking and spending up front on marketing means less burn out, clearer messaging, and less bullshit.</p><p>Besides, we’re not the only ones — the market is telling you to spend more on marketing, sales, and distribution if you want to make a bigger impact with your software company. We’re just here to tell you how, and t to assure you that it’s easier than you think.</p><p><em>Curious to hear more? </em><a href="/service/mailto:hello@reifyworks.com"><em>Shoot us an email and we’ll give you a free 15 minute consultation</em></a><em> to answer your questions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1f4aff40e0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reify/how-to-spend-money-on-marketing-when-you-dont-have-money-to-spend-on-marketing-b1f4aff40e0c">How to spend money on Marketing when you don’t have money to spend on Marketing</a> was originally published in <a href="https://medium.com/reify">Reify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Sell Green Juice, Sell Juicers]]></title>
            <link>https://medium.com/reify/dont-sell-green-juice-sell-juicers-b8b763aab1c3?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8b763aab1c3</guid>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Mon, 19 Mar 2018 18:52:10 GMT</pubDate>
            <atom:updated>2018-03-19T19:16:34.581Z</atom:updated>
            <content:encoded><![CDATA[<p>Avoiding a common consulting AntiPattern</p><p>Before we started a consultancy that sells strategic marketing and sales services to B2B software companies, we were both engineers that completely discounted the value of strategic marketing and sales services. We were interesting in the technical problems and felt like once we solved those, everything else would fall into place. Gradually, we started to see the error of our ways. Eventually, we started to look beyond our own experiences and realized that <strong><em>almost every B2B software company drastically underinvests in sales and marketing strategy.</em></strong> We saw an opportunity, and that’s how <a href="http://www.reifyworks.com/">Reify</a> was born.</p><p>Because we’re often found foaming at the mouth about the virtues of pursuing strong storytelling-based marketing and value-based selling, we’ve found ourselves in a bit of an interesting situation: <strong><em>some people think we’re selling green juice, when we’re really selling the juicer</em></strong><em>.</em></p><p>Before I explain the juice metaphor, there’s one more thing I need to point out: Reify is not a typical consultancy in a number of ways. We’re not trying to scale. We’re not hiring. We try hard not to be working constantly and we want every engagement to be as high impact as possible — we don’t like billing for the sake of billing. We optimize for customer LTV. We pride ourselves on repeat engagements.</p><p>So, back to the juice. Since part of our pitch is that marketing and sales activities are just <em>something everyone should be doing more of</em>, to some people it feels like we’re personal trainers. Like we want you to take your vitamins. Like we’re that thing that you reach for after you have a hangover from drinking too much the night before. The thing that makes you feel, temporarily, better about your bad decisions. Like a green juice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L8ON-WDeHi9n70L2h126Vw.png" /><figcaption>It really does make you feel better</figcaption></figure><p>We really don’t want to be green juice, and if you run a consultancy, we feel like you should avoid it as well. Instead of being green juice, the cheaper option, the thing that makes you feel better temporarily, you want to be the juicer. You want to be there for the long haul. You want a real conversation to happen around purchase. People should have to scratch their heads. Make room. Make a spreadsheet. Think about it.</p><p>If your takeaway here is that we have something irrationally against green juice, you’ve gotten us all wrong. We love green juice. We think everyone should drink it, every day. We just think that the best way to do that is to have a juicer at home. To have access to fresh ingr…wait, this metaphor is going a bit too far.</p><p>If you want to become great at marketing and sales, if you want to get to the point where you can think strategically about revenue as you do about technology, it’s going to take time. Just hearing our advice isn’t going to be enough. You need to put it in action. In growing your business, as in anything that counts, the follow-through is everything.</p><p>We’ve found ourselves in the position numerous times to engage with clients in a palliative way, and we’ve never ended up feeling good about it. Whenever we’ve taken the time to get to the bottom of the problems they’re experiencing, it’s always been worth it. Sometimes, it’s not the easy decision, but we think that if you want to build a lasting, sustainable consulting company, passing off the easy shallow sale for the harder deeper one is usually the right way to go.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8b763aab1c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reify/dont-sell-green-juice-sell-juicers-b8b763aab1c3">Don’t Sell Green Juice, Sell Juicers</a> was originally published in <a href="https://medium.com/reify">Reify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leave your gear set up]]></title>
            <link>https://medium.com/reify/leave-your-gear-set-up-38c73c1e2e11?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/38c73c1e2e11</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[music]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Thu, 25 Jan 2018 17:43:33 GMT</pubDate>
            <atom:updated>2018-01-25T17:43:33.239Z</atom:updated>
            <content:encoded><![CDATA[<p>Want to get better at something or at least do it more? Make it as easy as possible.</p><p>I’ve been making music at home for a long time, and have been talking to people about making music at home for even longer. During that time, the single best piece of advice I’ve gotten from people I admire is this: leave your gear set up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J1S_DFJBFoikbMv2-vk-jA.jpeg" /><figcaption>Buy my records please</figcaption></figure><p>If you want to play more, or get better, or both, having everything all set up and ready to go will make you approximately 1,000,000 times more likely to actually do it. This is scientifically proven.</p><p>It occurred to me the other day that this idea potentially generalizes to a whole bunch of other things that people typically want to do more or get better at: exercising, writing, making pottery, whatever.</p><p>The basic idea is this: make it as easy as possible to just get started and you’ll be so much more likely to actually do it. For running, maybe that means setting time aside and setting your clothes and shoes out the night before. Writing? A quiet spot and fifteen minutes should be enough.</p><p>Ask yourself this:</p><blockquote>What gear do I have stashed in the closet, messy and unplugged, that should actually be out and ready on my desk, ready to make my next hit?</blockquote><p>Once you’ve got your answer, take tonight to set it up, and make tomorrow day one of a long, fulfilling streak.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38c73c1e2e11" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reify/leave-your-gear-set-up-38c73c1e2e11">Leave your gear set up</a> was originally published in <a href="https://medium.com/reify">Reify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Comicless #1: The Conversation Begins]]></title>
            <link>https://medium.com/reify/comicless-1-the-conversation-begins-8b60ca707b5d?source=rss-909f3aea84de------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b60ca707b5d</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[comics]]></category>
            <dc:creator><![CDATA[mrb]]></dc:creator>
            <pubDate>Tue, 16 Jan 2018 14:33:32 GMT</pubDate>
            <atom:updated>2018-01-16T14:33:32.670Z</atom:updated>
            <content:encoded><![CDATA[<p>The first in a series of web comics where I try to explain serverless to myself</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*QjQd8pHO-8NOnPl1QIdN4w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b60ca707b5d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reify/comicless-1-the-conversation-begins-8b60ca707b5d">Comicless #1: The Conversation Begins</a> was originally published in <a href="https://medium.com/reify">Reify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>