<?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[UpLaunch - Medium]]></title>
        <description><![CDATA[Everything from marketing to leadership to software engineering to life. Get in here. - Medium]]></description>
        <link>https://medium.com/uplaunch?source=rss----6689ef4d33c8---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>UpLaunch - Medium</title>
            <link>https://medium.com/uplaunch?source=rss----6689ef4d33c8---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:04:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/uplaunch" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How Two Companies Became One]]></title>
            <link>https://medium.com/uplaunch/how-two-companies-became-one-4dcbb1a8ba95?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/4dcbb1a8ba95</guid>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[uplaunch-blog]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[fitness]]></category>
            <dc:creator><![CDATA[Matt Verlaque]]></dc:creator>
            <pubDate>Mon, 02 Jul 2018 23:35:53 GMT</pubDate>
            <atom:updated>2018-07-03T00:08:00.193Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jLODt8h4XZ_meSTmWF-ZtQ.jpeg" /><figcaption>Mike Wuest and his wife Kim at their home gym, CrossFit COMO</figcaption></figure><blockquote>This journey has been an interesting one…filled with twists, turns, pivots, and improvements. This one falls squarely into the “improvements” category.</blockquote><h3>The Origin</h3><p>Before UpLaunch came to be, there was a company called Run Your Gym. Started by Jake Johnson and myself in 2013, we developed a proof-of-concept platform that we called BoxBuilder. Our goal was to help people like Jake (owner-operator of an independent fitness facility) manage their leads and clients more effectively by leveraging technology.</p><p>Once we got some software built that actually worked, we had a grand vision: we were going to take these philosophies that worked well for fitness professionals and apply them to ANY industry. More is always better, right?</p><p>Right??</p><p><em>Hint: Interestingly, I talk about learning this lesson in a blog post a number of years ago. I think I learn things the hard way sometimes…</em></p><p>In order to deploy our awesome-sauce software platform far and wide, we needed to be able to branch out of only working in the fitness space. Turns out, the name “Run Your Gym” kind of paints you into a corner…so we became UpLaunch.</p><p>Enter Mike Wuest, owner of CrossFit COMO and TheBoxBusiness. Mike has his roots in the food service industry, where brand loyalty is fleeting, the customer experience is everything, and those that forget those points aren’t able stick around very long to lament their mistakes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*khWftFyYcKn5geIRYwAcNg.jpeg" /><figcaption>Some of CrossFit COMO’s incredible community</figcaption></figure><p>In other words, just the right philosophy to take what we started with Run Your Gym and BoxBuilder and turn it into something amazing.</p><h3>The Growth</h3><p>Our plan was to facilitate this multi-industry growth by bringing on partners. These partners would be subject-matter-experts in their fields with a good grasp on marketing automation best practices, and would be able to build a product on the UpLaunch Platform and distribute it to the world!</p><p>So naturally, we knew that Mike was the best person to be Partner #1. In other words, to take BoxBuilder and ensure that it continued to thrive.</p><p>Well, we were right about Mike. He took what we had started, re-built it from the ground up to better reflect his vision, and stacked the group with an amazing new cohort of top-tier gym owners.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*jdMhLWcckJcGffOZdEo7gw.jpeg" /><figcaption>Mike, hard at work during a work session in Gettysburg, PA.</figcaption></figure><p>While he was doing that, we were prepping our platform to be able to not just handle the fitness space, but any space that came our way.</p><p>Although we HAVE steadily increased the value that we deliver for gym owners, our quest to simultaneously provide a purpose-built experience for other industries proved to be more of a distraction than a benefit.</p><p>The reality is this: people in the fitness industry were getting massive value from the UpLaunch Platform, other industries were slow to catch on, and we were gradually getting away from focusing on the people who gave us our start: gym owners and fitness professionals.</p><h3>The Focus</h3><p>It was time to get back to our roots. To focus on fitness professionals — the group who supported us in the early days when our platform sucked, who gave us advice on how to best serve them, and who were in turn able to leverage our software to improve their businesses.</p><p>But with the dissolution of the UpLaunch Partner Program, how would we structure our relationship with Mike and TheBoxBusiness?</p><p>Easy. We got married.</p><blockquote>I’m proud to announce that TheBoxBusiness is now officially part of UpLaunch! Watch our video:</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F278073174%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F278073174&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F711006657_295x166.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="360" height="640" frameborder="0" scrolling="no"><a href="https://medium.com/media/ffc23079deb588075cc4d7f7c072792e/href">https://medium.com/media/ffc23079deb588075cc4d7f7c072792e/href</a></iframe><p>The entire team at UpLaunch is super grateful to have Mike as part of our team. He’ll be heading up Client Success, making sure that gym owners and fitness professionals around the world are getting the most value from the UpLaunch Platform as possible.</p><p>If you’re an UpLaunch client, you don’t need to do anything different. You’ll gradually see some branding changes here and there, some new content, and a feature pipeline that is MUCH more in-tune with the needs of the fitness community.</p><p>We’re excited to be on this path — at the end of the day, sometimes you need to zoom out just a touch too far in order to realize where you belong.</p><p>We are UpLaunch. The smartest way to build your fitness business.</p><p>And we’re excited to serve you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dcbb1a8ba95" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/how-two-companies-became-one-4dcbb1a8ba95">How Two Companies Became One</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Release Notes — April 20, 2018]]></title>
            <link>https://medium.com/uplaunch/release-notes-april-20-2018-506047b3185a?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/506047b3185a</guid>
            <category><![CDATA[uplaunch-release-notes]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[marketing-automation]]></category>
            <dc:creator><![CDATA[Matt Verlaque]]></dc:creator>
            <pubDate>Thu, 26 Apr 2018 13:53:02 GMT</pubDate>
            <atom:updated>2018-04-26T14:51:49.086Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UJarb4vTno0SuzH4." /><figcaption>“A woman working at a laptop near a half-open window” by <a href="https://unsplash.com/@thoughtcatalog?utm_source=medium&amp;utm_medium=referral">Thought Catalog</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>Customizable appointment notifications, upgrades to the contact listing page, and a better way to experience the new features that we’re shipping!</blockquote><h3>Overview</h3><p>Hope everyone is doing well today! This set of release notes covers some killer improvements to appointment configuration and to the main contact list! Along with that, we’ve done a bunch of small tweaks and corrections, and have some cool stuff coming down the pipe as well.</p><h3>Appointment Type Configuration</h3><p>As the Platform notifications continued to evolve, we’ve gotten consistent feedback that some customization is necessary to ensure that UpLaunch complements your existing workflow.</p><p>The biggest thing we’ve heard is that many customers would prefer to disable the SMS appointment reminders and disable and/or customize the appointment reminder emails that go out.</p><p>Well…now you can :)</p><p><strong>NOTE: Just like always, your appointment notifications are pre-configured and pre-loaded with content from your UpLaunch Partner. You don’t ever have to touch your <em>Notifications</em> page if you don’t want to.</strong></p><p><strong>Appointment Type Overview</strong></p><p>Starting at the regular <em>Appointment Settings</em> screen (available to admins and managers only), you’ll notice a small change — instead of a simple <em>Edit</em> button, we now have an <em>Actions</em> dropdown item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pxp1lqwVWyC5erJH.png" /></figure><p>The <em>Actions</em> dropdown contains four choices: <em>Edit</em>, <em>Notifications</em>, <em>Instructions</em>, and <em>Delete</em>.</p><p><strong>Edit</strong></p><p>The <em>Edit</em> screen contains all of the configurable fields that you’re used to — appointment name, duration, assigned staff members, booking form selection, etc. Nothing has changed there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Syk-oWxtzunoFAcW.png" /></figure><p><strong>Notifications</strong></p><p>This is the special sauce :)</p><p>On this page, you can customize or enable/disable all emails and SMS messages that are triggered when an appointment is booked.</p><p><strong>NOTE: The staff email is always sent to the staff member who the appointment is booked with.</strong></p><p>Each communication is organized by type (email or SMS) and recipient (client or staff).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CMVzi82m3Cm6H6sO.png" /></figure><p>You can simply click the <em>Edit Email</em> button to configure your content — using the same powerful UpLaunch email editor that you’re used to!</p><p>Same deal for SMS Messages — just click the <em>Edit SMS </em>button, and a small window will open that allows you to edit your notification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tR8OvTL_3XkhcSlm.png" /></figure><p><strong>Instructions</strong></p><p>The instructions page hasn’t changed either — it gives you some quick ideas about how to use your appointments, and provides you with the code snippets and landing page links for installing them.</p><p><strong>Delete</strong></p><p>Delete is…well, exactly what you would expect. Note that you can’t delete an appointment type that’s being used in an active funnel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oZg8VOWa_kLVciBU.png" /></figure><h3>Contacts List</h3><p>Alright, let’s be honest here — until we build a better <em>Sort</em> function, my decision to list the contacts in alphabetical order was pretty useless. If you knew their name…you would just type it into the search bar ;)</p><p><strong>Contacts are now listed with the newest ones at the top. That also holds true after you apply a filter(s) — the newest contacts will be at the top of the filtered results.</strong></p><p>In addition to that, we also made some visual updates as well as added the <em>Quick Action Icons</em>.</p><p><strong>Quick Action Icons</strong></p><p>You’ll see them on the right hand side of the below image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xgtv0pKupf-FLK77.png" /></figure><p>You can now send a manual email, add a telephone note, or open the contact’s SMS inbox <strong>without leaving the list page</strong>.</p><p>So (for instance) — if you want to pull up all of your contacts in a specific segment or smart group and send them all a different SMS — you can now do that without clicking into each individual contact record!</p><h3>Feature Release Tours</h3><p>From here on out, when we release new features, we’ll put a one-time walkthrough in the affected areas! This will be available to all users of the UpLaunch platform, and will help ensure that nobody misses instructions about how things work!</p><p>The walkthrough tours will highlight specific elements of the page, such as in the example below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lV5MeF9KvSzjnpJk.png" /></figure><h3>On-Demand Help</h3><p>We’ve also added another button to the top bar, right next to your <em>User Menu</em> — it’s a circular icon with a question mark, and will be your source to get help with the Platform.</p><p>It’ll always have a link to our docs as well as a link to our Help Dialogue, where you can submit support tickets.</p><p>However, in addition to that, we’ll be progressively adding on-demand product tours for specific areas of the Platform. When they are available, they’ll be in that menu as well under Platform Tours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f5ylASBXszqH5kJz.png" /></figure><h3>Small Updates &amp; Bug Fixes</h3><ul><li>Fixed an issue where the <em>Next Touch Point</em> date on a contact record was inaccurate after pausing and unpausing a campaign.</li><li>Fixed an issue that would cause the search in the top bar of the Platform to stop working after taking specific actions (creating a task, for instance).</li><li>Added better feedback to a few forms to explain why a form submission is invalid.</li><li>Removed <em>Branding Colors</em> from the business branding, as we’re not currently using them.</li><li>Fixed an issue where certain campaign customization areas wouldn’t let a user revert from customized content back to default content.</li><li>Fixed an issue that was causing some strange characters in task descriptions.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=506047b3185a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/release-notes-april-20-2018-506047b3185a">Release Notes — April 20, 2018</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The UpLaunch Methodology (how we help small businesses win)]]></title>
            <link>https://medium.com/uplaunch/the-uplaunch-methodology-how-we-help-small-businesses-win-818ea70c7e7d?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/818ea70c7e7d</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[uplaunch-blog]]></category>
            <category><![CDATA[entrepeneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Matt Verlaque]]></dc:creator>
            <pubDate>Tue, 02 Jan 2018 03:55:33 GMT</pubDate>
            <atom:updated>2018-04-26T16:50:34.608Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bIh0CvJccEglZByp1CtKvA@2x.jpeg" /></figure><h4>The Product Design Journey</h4><p>When we get together with one of our partners to create a product on the UpLaunch platform, it’s kind of a magical process. It’s typically done in-person, and it usually takes the form of a relatively intense work session filled with messy whiteboards, “Aha!” moments, spirited debates, and inspired creativity.</p><p>However, after the dust has settled and the strategies are outlined, we start to organize all of the chaos into a sleek, streamlined set of campaigns that are wide-reaching in scope, yet beautifully simple. We accomplish that by designing products and campaigns according to the UpLaunch Methodology.</p><p>What is this methodology, you ask? And how does it help small business across all industries?</p><p>It’s simple, really. The UpLaunch Methodology is nothing more than a set of four principles that we use as a benchmark for our work. If every campaign is aligned with all for principles, we know that not only will we be delivering a quality product, but we will also be delivering a product that aligns with our core values.</p><p>Alright, enough chit-chat. Here are the four principles that comprise the UpLaunch Methodology:</p><h4>Principle 1: Automation Can’t Replace Relationships</h4><p>Our platform, products, and campaigns are NOT magic bullets. To put it bluntly, there is no software in the world that can compensate for business owners and staff members who aren’t willing to build relationships with their leads and clients.</p><blockquote>In case you didn’t know: people aren’t buying because of what you’re selling. They’re buying because of WHO is selling it.</blockquote><p>Our platform and campaigns are built to help humans relate to other humans. Because of that, we almost always include a manual outreach component in our strategies, which encourages staff members to pick up the phone and have a conversation with the campaign recipient — building a relationship that is simply impossible to build via email or SMS messaging.</p><h4>Principle 2: Automated Communications Must Be Personalized</h4><p>This is one of our major market differentiators. Yes, we ship with turn-key content and yes, it’s super effective out of the box. However, for best results, it should still be personalized for your business — and for the specific person receiving it.</p><p>So how do we account for that? It’s easy. Not only do we empower small business owners to edit and/or replace all of the content for their default campaigns, we also allow you to edit the content — in advance — on a contact by contact basis</p><p>Let’s say you talk to a new lead and find out they’re getting married in two weeks. Awesome! You can drill into their campaign, find an email that is three weeks out, and edit it on the spot to congratulate them on their marriage.</p><p>It’s really that easy.</p><h4>Principle 3: Simple Journeys, No Spiderwebs</h4><p>What is a spiderweb? It’s what we call the flowcharts of overly complicated automation campaigns that have 7 different options after each step, super complex logic flows, and a nearly infinite amount of options.</p><p>Why isn’t it better to be that granular? It’s simple — marketing campaigns must be authentic in order to be effective. If you have a campaign that is so complicated that no one understands what is happening, and a customer comes in and asks you about something that was sent to them…what will your answer be?</p><p>“I’m not sure, our marketing program sent that out…”</p><p>It’s 2018. We can do better. Effective simplicity is a monumental challenge, and it’s one that we embrace.</p><h4>Principle 4: Consistent Value For The Win</h4><p>Effective campaigns and systems aren’t about simply overpowering your leads and clients with a deluge of information. It’s relatively common knowledge that customers usually take 6 to 8 touch points before they make a purchase, but it’s a process that can’t be rushed!</p><p>All of our partners are encouraged to write content that delivers insane amounts of value. Give, give, give, give, give, ask.</p><blockquote>In fact, when they ask us “are you sure I should just give all of that away?” — that’s when we know we’re on the right track.</blockquote><p>Providing massive value for your leads and clients will position your business as subject matter experts in your field, and that credibility — when combined with a good interpersonal relationship — will directly translate to a better bottom line.</p><h4>Conclusion</h4><p>Look, nothing in the four principles is groundbreaking in isolation. We didn’t invent authenticity, we’re not the first people to recognize that a good relationship is a powerful influencer on buying habits, and we’re certainly not the first company who has recommended delivering massive value with free content.</p><p>The problem we see is that when people go down the rabbit hole writing marketing automations that span the entire client lifecycle, sometimes they begin to stray from these simple principles. They start to chase the “shiny objects” — look at all the crazy stuff my platform can do, look at how complicated my logic tree is, look at how crazy this campaign is…</p><p>We’re simply not buying it. At UpLaunch, we steadfastly believe that our products will out-perform the competition simply due to a reallocation of energy. In other words, the energy that other people put into their business logic flow charts, we direct into our ecosystem.</p><p>We help our partners mentor their clients and improve their business systems. We in turn mentor our partners and help them level-up their game as well. With each group elevating the next one, everybody wins, and the pie just keeps growing larger and larger.</p><p>Keep it simple, be authentic, build relationships, and work your ass off. There, I did it. I just gave away our company secrets.</p><p>Now get out there and do something great.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=818ea70c7e7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/the-uplaunch-methodology-how-we-help-small-businesses-win-818ea70c7e7d">The UpLaunch Methodology (how we help small businesses win)</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Have The Hard Conversations!]]></title>
            <link>https://medium.com/uplaunch/have-the-hard-conversations-2f02fae6fe6a?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/2f02fae6fe6a</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[uplaunch-blog]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Jake Johnson]]></dc:creator>
            <pubDate>Tue, 10 Oct 2017 02:07:25 GMT</pubDate>
            <atom:updated>2018-04-26T14:57:40.736Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*88scMa5Gpuwwpqjl0cCytw.png" /><figcaption>The UpLaunch team in Las Vegas and Matt and I celebrating the official launch. (Some conversations happen with beer)</figcaption></figure><p>Last week, <a href="https://medium.com/u/252b48785754">Matt Verlaque</a> and I had a long conversation. We solved a ton of issues, did some strategic planning, talked about life, and reflected on our journey (check out some cliff notes from it — <a href="https://medium.com/uplaunch/the-no-bs-story-of-how-our-startup-started-up-and-the-5-rules-48926261aa82"><em>The No-BS Story Of How Our Startup Started Up</em></a>). One of the issues that we explored was a decrease in productivity because we weren’t utilizing our strengths (and each other’s strengths) the way that we have done previously. The takeaways from our conversations are incredible (except for this blog — the blog is average).</p><p>Naturally, a portion of our conversations are centered around solving problems or answering questions related specifically to UpLaunch. However, on a personal level, we end our conversations with more respect for each other and motivation to accomplish what sometimes seems insurmountable.</p><p>Over the last few days, I have reflected on the growth that has resulted from our phone calls and realized that our conversations are so good because we are committed to bettering ourselves. It comes down to raw, unedited truths that are spoken in support of similar goals: creating the best lives possible for our families, our team, our partners, and for anyone involved with UpLaunch!</p><p><strong>No one enjoys having hard conversations.</strong></p><p>But here is the deal: When you commit to working with a team, you commit to having hard conversations. By avoiding uncomfortable dialogue, you’re guaranteeing that your team will begin to build resentment and decrease productivity — which will impact every person on the team and ultimately begin a slow and steady breakdown of your organization.</p><p>With every new phase of a business, there are new challenges. New challenges create discomfort, and discomfort creates anxiety. You get the point! Being an entrepreneur is a roller coaster of emotions. Over the years, UpLaunch has had a ton of hard conversations, and through them, we have learned a lot. It would be pretty lame if we didn’t drop some of that knowledge.</p><h3>Here are five rules for enhancing team communication.</h3><p><strong>Rule #1:</strong> <em>You must reflect on your own individual performance</em></p><p>It comes down to emotional maturity and recognizing other people’s thoughts, opinions, and beliefs. You have to be comfortable with who you are and what you are capable of doing.</p><p>Notice I did not say <em>“comfortable with what you are doing.”</em></p><p>If you’re comfortable with your work, you’re complacent. Routinely as an entrepreneur, we are doing things we are uncomfortable doing. That is the beauty of it. You will not fail, you will figure it out (all about that mindset). A team depends on each player, so push yourself harder and challenge yourself! If you’re complacent or if you refuse to be your own harshest critic, you’re <strong>NOT</strong> a true member of the team — you’re an anchor who is slowing your team’s progress.</p><p><strong>Rule #2:</strong> <em>Embrace the difficult face-to-face conversations</em></p><p>Emails, texts, Slack messages, Notion comments, etc are all great, and they each have specific applications for team communication. However, there is <strong>NO</strong> replacement for face to face human interaction.</p><p>If you are working remotely — no problem! Use Zoom, FaceTime, or any of the hundreds of applications where you can see someone’s face and have a real conversation. Remember that it’s okay to have a little silence during these conversations as well!</p><p>Some of the best ideas or solutions we have ever had have come out conversations with awkward, mid-conversation silence. Just let it happen.</p><p><strong>Rule #3: </strong><em>Be open and honest</em></p><p>If you are playing a shell game, you should probably just save everyone the time. Jump back to <strong>Rule #1</strong> and look in the mirror for a little while. It almost seems childish to even bring this up. We are adults, working in the real world to accomplish amazing things. Right? Open and honest conversation solve a lot of problems before they even start. Be real, and say what’s on your mind — even when it makes you uncomfortable!</p><p><strong>Rule #4:</strong> <em>Don’t cry</em></p><p>I don’t mean in the “tears flowing” kind of way. It’s okay — grown men can cry. I’m talking about acting like a kid, throwing a tantrum, “how dare you to accuse me”, “it’s my way or no way”, the “blame game”, etc….</p><p>We are all playing together in the sandbox with the same toys trying to build a MASSIVE castle!</p><p>Do not let personal insecurities turn into an emotional outburst. When in doubt, go back to <strong>Rule #1</strong>. Never forget that we are all building the same castle — so don’t cry, just BUILD!</p><p><strong>Rule #5:</strong> <em>Keep the conversation focused on solutions</em></p><p>Nothing good ever comes out of conversations that start with accusations and negativity. If you are starting with that type of emotion, take a second and think about the fact that you are on a team. Put yourself in the other person’s shoes for a minute.</p><p>Your role as a team member is to help your teammates overcome weaknesses, not to just point them out without offering a solution. Ask if you can help them with anything! If everyone on the team takes a helping stance, each person’s strengths will be magnified, and their weaknesses will be minimized. The tide rises together!</p><p>Now round up your team and go have a conversation. Get in the sandbox and build that massive castle!</p><p>Have any thoughts or tips on communication? Drop us a line!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f02fae6fe6a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/have-the-hard-conversations-2f02fae6fe6a">Have The Hard Conversations!</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Beginner’s Mind]]></title>
            <link>https://medium.com/uplaunch/the-beginners-mind-a35d62ed7925?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/a35d62ed7925</guid>
            <category><![CDATA[uplaunch-blog]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Matt Verlaque]]></dc:creator>
            <pubDate>Thu, 21 Sep 2017 02:02:14 GMT</pubDate>
            <atom:updated>2018-04-26T16:51:36.600Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w-etiGz3qdZjdXIy9DJerg.jpeg" /><figcaption>The Beginner’s Mind…</figcaption></figure><blockquote>Shoshin is a concept in Zen Buddhism that means the “beginner’s mind” — in other words, shedding all of your preconceived notions about a particular topic and approaching it from a purely open and inquisitive standpoint.</blockquote><p>This “beginner’s mind” approach is something that I cling to vehemently as one of the leaders of UpLaunch. Our platform focuses on small business systems and marketing automations, but it’s certainly not unique to our industry — the principle can be applied to any aspect of life.</p><p>For our platform, we generally take a simple four step approach to planning a new feature — and like everything we do at UpLaunch, it begins and ends with our customers. Take a quick look into how we do things and think about how you could apply this in your own business, organization, or life.</p><h4>Step 1: Identify Core Requirements</h4><p>These core requirements for a new feature are primarily driven by our customers — sometimes they tell us what they need, and other times we already know, but either way it’s all about satisfying a particular use case for the users of our Platform.</p><p>These use cases are NEVER written in general terms — we always drill down to the specifics. For instance, we wouldn’t just say that we “need to improve contact segmentation” — that’s a subjective statement that means, well, precisely nothing.</p><p>Instead, we would compile a set of scenarios that our customers have told us that they need to satisfy, or that we predict that they would encounter. Once we get the specifics hammered down, only THEN will we zoom out and write up some general specifications about what the feature needs to be.</p><h4>Step 2: Identify the “Safe” Approach</h4><p>Unless you’re trying to go to Mars (Hey Elon), revolutionize the way that humans generate electricity (What’s Up Elon), or create unprecedented means of mass transit (Oh Hi Elon)…chances are whatever “brilliant” idea you’re working on isn’t quite revolutionary.</p><p>Don’t misunderstand me — I’m not saying it’s not valuable, or that you can’t do it BETTER than someone else, or repurpose it for a new application…I’m just saying that someone’s probably done whatever you’re trying to do in some way, shape or form.</p><p>Find it! Dig up whatever is closest to satisfying your use cases from Step 1. The best scenario is that it satisfies ALL of them. See what other people are doing. Get inspired. Figure out what you like and what you don’t like.</p><h4>Step 3: Shoshin!</h4><p>Now that you know what’s been done, you’ve also got a good idea what hasn’t been done. Wipe your mental slate clean. Look at the results from Step 2, and ask yourself and your team one simple question:</p><p><em>“How can we do it better?”</em></p><p>After you discuss all of the answers to that one important question, start to aggregate the good parts from each of them and identify your plan of attack. Devote a bit of time to this step, as it’s where your vision will start to truly come to life.</p><p>Don’t be afraid to try different approaches here! It’s ok if an idea ends up being horrible. It’s fine if it fails. It’s part of the process. Try things out, see what feels right, see what might make things easier for your customers. Eventually, you’ll settle on the best way to create your new feature — and hopefully, it’ll be better, smoother, and easier to use than whatever’s already out there.</p><p>One last note on this step — be prepared for the scenario that nothing you come up with seems to work. Maybe someone’s already delivering your functionality in the most efficient way possible. That’s OK, as long as you don’t let your ego get in the way.</p><p>Changing just for the sake of change doesn’t help anyone — if at the end of Step 3, you’re not convinced that any of your approaches are better than what’s out there…just go with the safe approach from Step 2. Your business exists to serve your customers, not yourselves — so whatever is best for your customers, in turn, is best for your business.</p><h4>Step 4: Circle Back To Step 1</h4><p>If you do indeed decide that you’ve figured out a new way to approach your problem or feature, circle back to your use cases that you identified in the beginning. That’s why getting the specifics in the first step is so important — you need to have test cases to evaluate the efficacy of your idea.</p><p>At UpLaunch, we’ll typically do this in phases — first, we’ll come up with some internal test cases, and if they pass, we’ll hit up some of our trusted customers and have them fire some hypotheticals at us to make sure our ideas don’t suck. Believe me — if you come up with some “great” idea that your customers will hate, you want to find out about that before you dump a month into writing code, creating designs, and implementing it (or whatever the equivalent of that is in your business).</p><h4>Final Thoughts</h4><p>It’s pretty simple. Figure out specifically what your customers need, see how other people are handling it, figure out how to do it better, and make sure that your new idea still delivers what your customers need. If you can do all of that with a small investment of resources until the idea is validated, you’ll win every time.</p><p>Remember: Innovation is actually iteration in disguise. A Tesla is basically an improved version of a horse, when you really think about it. To improve the status quo, you need to first identify what the status quo is — and then use your team’s ingenuity and infallible devotion to your customers to blow it out of the water.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a35d62ed7925" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/the-beginners-mind-a35d62ed7925">The Beginner’s Mind</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Little Bit On Culture]]></title>
            <link>https://medium.com/uplaunch/a-little-bit-on-culture-7001e35f9860?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/7001e35f9860</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[uplaunch-blog]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Matt Verlaque]]></dc:creator>
            <pubDate>Mon, 11 Sep 2017 18:09:36 GMT</pubDate>
            <atom:updated>2018-04-26T14:58:34.633Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PgtThdf5KMCd6olEO6bZlA.png" /><figcaption>Culture has its roots everywhere…</figcaption></figure><p>Culture. Everyone talks about it. Everyone wants it to be “strong” or “cool”…but what does it really mean? And more importantly, how do you get it? I may not have it all figured out, but I’ve got a few thoughts on the topic.</p><p>Before I started UpLaunch, I was a Lieutenant in the fire department. Not only did I truly love my career as a firefighter, but it taught me an incredible amount about culture, leadership, and motivating people to achieve a common goal. It certainly isn’t easy, especially in a job with so many traditions, quirks, and idiosyncrasies. But it’s doable — and the lessons translate very well into the business world.</p><p>Here are 3 important things that you can do in your company — TODAY — to create, improve, and get buy-in around your company culture.</p><h3>Lead From The Front</h3><p>One of my mentors in the fire department once told me that he would “never ask me to do anything he hasn’t done or isn’t willing to do”. That type of attitude will go a LONG way in business. For instance, I do my best to try out the work that I’m assigning to people BEFORE I actually assign it to them. If you do their job for a bit and it makes you want to jump off a bridge, you’d better find a way to make the work more inspiring before you cause someone else to stop enjoying their experience at your company.</p><p>This is especially true for recurring tasks — people want PURPOSE. They want to know WHY they’re doing something, and they want to see the RESULTS of their efforts. As a leader, it’s your responsibility to close the feedback loop and show everyone how their work is affecting the greater mission. If you can’t figure that out, it’s a pretty big clue that you’re wasting someone’s time — and can increase the return on their efforts by assigning more high-value tasks to them.</p><p>Of course, it’s not possible to do inspiring, engaging, high-value work all the time. Sometimes we need to do data entry, or sweep the floor, or write documents that are repetitive. It’s not always avoidable. If you want your people to make time for these unpleasantries, you’ll motivate the hell out of them by being the first one to get started. If a thousand records need to be entered in the database, knock out the first hundred real quick before passing it off. If the floor is gross, grab a mop. You get the idea. Be the person you want to hire.</p><blockquote>If you personally embody the culture you want to foster, the people around you will naturally follow suit. This holds true for good cultures and for bad ones — so pick your actions carefully.</blockquote><h3>Set Expectations</h3><p>It’s completely unfair to expect people to perform to a certain standard if that standard isn’t clearly communicated. In fact, it’s a recipe for disaster. You’ll end up pissed off that your people aren’t doing things “right”, and they’ll be just as angry because they’ll feel like failures. Nobody inherently WANTS to be bad at their jobs; they just need a clear “definition of success” in order to achieve it.</p><p>This is where business systems come into play. I get it — as a business owner, time is always in short supply. It’s crucial to look at the return on your actions over the long term in order to prioritize where you spend your time. Will taking 2 hours to write a detailed procedure take more time TODAY than it would take to quickly show someone how to do it in 15 minutes? Sure…but when it’s done wrong, and you have to show them again AND fix the items that were done incorrectly, you’ll quickly eclipse the amount of time it would have taken you to write a procedure in the first place.</p><p>There’s another benefit to written communication — it makes you THINK. Write the procedure down, read it out loud, think about it, read it a second time, and then teach it to someone. If you follow that recipe, you’ll be much more likely to remove ambiguity — you’ll also have provided your people with a reference so they can gauge the quality of their own work BEFORE it gets to your desk.</p><h3>Have Real, No-Bullshit Values</h3><p>Yeah, I said it. This is the most important out of everything that I’ve written today. People need to know the mission. They need to know why they’re working, who the true stakeholders are, and who they should be thinking about. Your values, ethos, expectations, whatever you want to call them — they should be communicated to EVERY single person who works for your company. And you, as a leader, had better be a walking, breathing example of each and every one of them!</p><p>It doesn’t matter if your business is a gym, a software company, a bakery, or a manufacturing plant — every business has a goal, every business has a customer that benefits from its product or service, and every business has a group of people who work their asses off so that it can thrive. Connect those dots together. Let people know what’s expected of them and why those expectations exist.</p><p>As an example, at UpLaunch, one of our ethos is about challenging the status-quo. We foster accountability across all channels, regardless of position, job responsibilities, or time in the company. If someone is dropping the ball, or a process of ours can be improved, it’s not only encouraged — but EXPECTED — that someone speaks up and brings it to the team’s attention. No egos, no feelings, no “rank” — the only thing that matters is the improvement of the team, which in turn provides more value to our partners and customers.</p><h3>Final Thoughts</h3><p>Culture is important. It can make or break a team. It can empower people to achieve incredible things or demotivate them to the point where they’re barely working at all. As an “intangible”, it can be tough to truly put your finger on what your culture is, what you’re willing to tolerate, and what your non-negotiable values are. To be a true leader, you’ve got to have BACKBONE. You’ve got to stand up for those values and ensure that your people represent your company the right way.</p><p>Another good one from my fire department days:</p><blockquote>“What you tolerate, you endorse”…</blockquote><p>If it’s a non-negotiable, make it non-negotiable. Build teams filled with people that you look up to and who prioritize the values that your company holds dear. It’s incredible what a hard working team of like-minded and mission oriented people can achieve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*OoZJ4echDZ2hVrm5DteNng.png" /><figcaption>The UpLaunch Company Ethos</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fab841a%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fab841a%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/072b3c0b0c1c05c012894d1b21b328d5/href">https://medium.com/media/072b3c0b0c1c05c012894d1b21b328d5/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7001e35f9860" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/a-little-bit-on-culture-7001e35f9860">A Little Bit On Culture</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Deployment Pipeline w/ Heroku]]></title>
            <link>https://medium.com/uplaunch/software-deployment-pipeline-w-heroku-3f45e2d5445e?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/3f45e2d5445e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[uplaunch-tech]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Matt Verlaque]]></dc:creator>
            <pubDate>Sat, 22 Jul 2017 17:06:18 GMT</pubDate>
            <atom:updated>2018-04-26T14:58:57.121Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qc0EClZfWPCnQR-MkN0hyA.png" /></figure><p>In the software engineering world, there’s a TON of super smart people who share their knowledge readily and without compensation, and it’s helped us immensely while bringing the UpLaunch Platform to life. The way I see it is now that we’ve figured a few things out, it’s up to us to help pay it forward.</p><p>If you’re not a nerd, read on at your own risk ;)</p><h3>Our Growing Needs</h3><p>Our software has been rapidly evolving — started out as a proof of concept, then to a prototype, and then to a production-ready application that’s about to start taking on live customers. Similarly, our development workflow has also evolved. In the beginning, it was just me — coding, pushing directly to master, breaking stuff, no tests…<em>cowboy coding</em> at its best.</p><p>Once the development team doubled in size (yes, there are TWO of us now!), we needed to formalize the process a bit. We started actually organizing our work into epics and user stories, which at least gave us a way to measure how close we were to being able to go to market. We then created a process where each user story would have its own branch, and conversely, that any branch we created would have a corresponding user story. The program we use to manage that is incredible (total JIRA killer)…but I’ll save it for another post.</p><p>We eventually got a test suite built out, and I protected the master branch of our repo by requiring that all branches be merged via a pull request with an approved code review.</p><p>Sounds legit…but something was missing.</p><h3>Protecting The Customers</h3><p>We understood that we needed a “staging” copy of our app — a place to test things out, make sure that the features we released weren’t going to break things for our customers, etc. I wanted to have very granular control over what got sent to production — in other words, I’m cool with merging a PR and it getting automatically deployed to staging if the tests pass. But when it came to production, not only did I want to have to press a button, I wanted to know exactly which feature branches were making the jump.</p><p>Enter Heroku Pipelines.</p><p>You can <a href="https://devcenter.heroku.com/articles/pipelines">read their docs here</a>, but basically think of it as a collection of Heroku apps that fall into three categories — development, staging, and production.</p><p>Once configured properly, every open PR will spin up a “review app” — so you (and/or your team who is reviewing your code) can check out how the new feature will work in an environment that more closely represents actual production conditions.</p><p>After the PR is merged into master, we have it set up where the test suite will run (also on Heroku) and assuming it passes, it’ll automatically push to the staging app.</p><p>Last but not least, Heroku conveniently supplies a “Promote To Production” button on the staging app — with a single click, you can push the already-compiled code to your production app, and all is well.</p><h3>The Devil Is In The Details</h3><p>If it was as simple as I just wrote to get it up and running, I wouldn’t be spending time writing this blog post. It took a bit of messing around (due in large part to my own inexperience) to get everything working right, and I had to track down a few other people’s blog posts for guidance — so I decided to aggregate it all in one place.</p><p><em>I’ve posted the links to the blogs that got me across the finish line in the footer — huge thank you to them for the work that they did, and a lot of what I’m sharing with you came from them. I’ve simply updated it and put it all in once place.</em></p><p>The problems that I ran into are as follows:</p><ol><li><strong>Heroku Setup via </strong><strong>app.json</strong>. Although Heroku generates a super helpful app.json as a starter, I needed to make some tweaks to it in order to get things working properly, which took some trial and error.</li><li><strong>Subdomains</strong>. We use Basecamp-style multitenant authentication, meaning that an account gets assigned its own subdomain, and each account can then have multiple users. This doesn’t work for review apps, which are spun up as a subdomain of <em>herokuapp.com</em> (for instance, <em>http://yourapp-name-pr-263.herokuapp.com</em>). Sub-sub domains on <em>herokuapp.com</em> are a no-no.</li><li><strong>Data</strong>. We knew that starting off with an empty DB would be counter productive, as making our QA guy create a brand new account, new user, new contacts, etc just to test a simple feature would be a HUGE time waster. However, we weren’t sure the best way to go, or how to do any of it.</li><li><strong>Migrations</strong>. Heroku doesn’t automatically run database migrations, including when promoting from staging to production.</li></ol><p>I’m proud to say that everything is up and running, after some trial and error and lots of bad words. The rest of this post will talk about how we tackled our four main problems.</p><h3>Heroku Setup / app.json</h3><p>When creating new apps that are based on existing ones (like review apps), Heroku uses an app.json file to allow you to set some specifications. This file should get saved in the top level of your Rails app and committed to version control. Like I said, I started with the Heroku-generated app.json, which puts every config variable you have into the schema.</p><p>Any config variable that you leave in the JSON schema as “required” will automatically import its value from the parent app. That’s really useful for things like API keys of essential services, but make sure you strip out the ones that don’t make sense — for instance, <em>HEROKU_RELEASE_VERSION</em>.</p><p>I also edited the app.json to include separate schema for the test environment, and to run rails db:test:prepare in the test-setup phase of Heroku’s CI workflow.</p><p>Honestly, it just took some good ole trial and error — Heroku’s builds will error out if your app.json is jacked up, so feel free to use mine as a reference to help get you started.</p><p>You can find an example app.json <a href="https://gist.github.com/mattverlaque/dd2e6b7a6d48d6d021d7701e77652045">here</a>.</p><h3>Subdomains</h3><p>Disclaimer: if you don’t use subdomain-style multitenant authentication for your app, this step won’t apply. But it has some cool stuff in it regardless :)</p><p>Setting this up was a big hurdle, and I NEVER would have gotten it up and running without <a href="http://blog.skorfmann.com/heroku-review-apps">Sebastian Korfmann’s article</a> about handling this exact problem. The rake task that he provided needed updating in order to get things going, so I’ll provide the details in this article instead of simply sending you to his post.</p><p>I, like many of you, have spent the past number of years purchasing domains on GoDaddy. It’s one of those things that you know isn’t a great idea, but you’re not really sure what the best alternative is so you just keep doing it.</p><p>I’ve found my solution, and it’s<a href="http://dnsimple.com/"> DNSimple</a>. The reason? You can programmatically create DNS entries for your domains via their API…and they have a Rails gem! This capability was essential to make our sub-sub-domain requirement a reality.</p><p>First things first: get yourself a domain that you want to use for review apps, or transfer one in. After that, you’ll need to install a couple of gems and set up your rake task.</p><p>Gems: dnsimple and platform-api.</p><p>Also grab your API key from DNSimple and Heroku.</p><p>Next, create a new file in lib/tasks and call it staging.rake. You can grab my copy <a href="https://gist.github.com/mattverlaque/146ab14095b329aaf9e3680f2220dd7f">here</a> — just make sure you set line 12 with your review app domain, and set up the config variables with your API keys. In my example app.json, I added the config variable names in the comments.</p><p>Basically, this task, which is called at the end of the postdeploy scripts in app.json, calls DNSimple and adds two CNAME records to your domain which point to the review app, and also calls Heroku and adds your DNSimple domain as a custom domain for the review app.</p><p>In short, instead of accessing your review app at <em>http://your-app-name-pr-267.herokuapp.com</em>, you’ll now be able to access it at <em>http://pr-267.your-review-domain.com</em>. And it happens automatically, every single time a review app is built for the first time.</p><p>The nice thing for this is that you can then use your account subdomains — for instance, if your normal account was <em>http://mike.your-production-domain.com</em>, you could access the review app at <em>http://mike.pr-267.your-review-domain.com</em>.</p><p>Problem solved…except your account doesn’t exist on the review app. Yet.</p><h3>Data</h3><p>We talked a lot about this one. Our initial plan was to just share the staging database with all the review apps. We thought we were soooooo smart — all of our accounts would be accessible, blah blah blah. It worked great until we needed to make a database change in a PR.</p><p>What would happen if you run the migration on the review app?</p><p>Of course, now I was dealing with my deflated ego AND a database with a jacked up migration, so we kept looking for a better method.</p><p>Enter EpiphanyMachine’s answer on <a href="https://stackoverflow.com/questions/33293169/heroku-review-apps-copy-db-to-review-app">this StackOverflow post</a>. Basically, on your staging (parent) app, set your postgres DB URL to a config variable STAGING_DATABASE_URL. Then, add pg_dump $STAGING_DATABASE_URL | psql $DATABASE_URL &amp;&amp; bundle exec rake db:migrate to your postdeploy script in app.json. This will copy the staging database over to your review app’s fresh DB and run migrations.</p><p>Now you have your accounts, data, etc ready to rock and roll, but you can F it all up without consequence.</p><p>Note that in app.json, we now need to run the above code to set up the DB as well as the code to run the rake task. When it’s all put together, the postdeploy script should look like this:</p><pre>pg_dump $STAGING_DATABASE_URL | psql $DATABASE_URL &amp;&amp; bundle exec rails db:migrate &amp;&amp; rake staging:publish_dns</pre><h3>Migrations</h3><p>Last but not least. The postdeploy script above runs migrations when the new DB is set up, but remember — postdeploy only runs ONCE. So what happens when we promote from staging to production?</p><p>Enter the Release phase script. For some reason, I had trouble finding good documentation on how this works. Even though it’s probably my own fault that I couldn’t find it, I’ll hit it here as well to make sure everyone’s good.</p><p>If your app is already on Heroku, you should have a Procfile in the top level directory of your Rails app. For most people, it likely contains one or two lines; one starts with web and sets some config options for your web dyno, and if you have a worker set up as well, a second line that starts with worker.</p><p>We’re going to add a third line: release: bundle exec rails db:migrate. This will essentially run rails db:migrate every single time a new VERSION of your app is created. If you update a branch with an open PR, Heroku will run your migrations when it updates your review app. When you close the PR, the migrations will run on your staging app. And, of course, when you promote your staging app to production, it’ll run again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*J0_8ymDzRl-DXXElZD2owA.png" /><figcaption>Release phase in the app.</figcaption></figure><p>Problem solved.</p><h3>Conclusion</h3><p>That’s a lot of stuff. However, it’s also a huge time saver once it’s up and running. As of now, all of our tests are running inside Heroku CI, and every time we open a pull request, we can all test it without having to pull down and run it locally. We’re still automatically merging closed PRs with green tests into master and onto our staging app, and finally, when I’m happy with the features that have been merged into staging, I can push it to production with one click.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k_hjTQONrYDNw-SekxCRmg.png" /></figure><p>Hope this all helps — please let me know if there are any questions.</p><h3>Resources</h3><ol><li><a href="https://gist.github.com/mattverlaque/dd2e6b7a6d48d6d021d7701e77652045">app.json with comment</a>s</li><li><a href="https://gist.github.com/mattverlaque/146ab14095b329aaf9e3680f2220dd7f">staging.rake</a></li><li><a href="http://blog.skorfmann.com/heroku-review-apps">Sebastian’s article about Review Apps</a></li><li><a href="https://stackoverflow.com/questions/33293169/heroku-review-apps-copy-db-to-review-app">SO post with DB copying information</a></li><li><a href="https://devcenter.heroku.com/articles/pipelines">Heroku Docs on Pipelines</a></li><li><a href="https://devcenter.heroku.com/articles/app-json-schema">Heroku Docs on </a><a href="https://devcenter.heroku.com/articles/app-json-schema">app.json</a></li><li><a href="https://devcenter.heroku.com/articles/github-integration-review-apps">Heroku Docs on Review Apps</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f45e2d5445e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/software-deployment-pipeline-w-heroku-3f45e2d5445e">Software Deployment Pipeline w/ Heroku</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Failure. Is it an Option?]]></title>
            <link>https://medium.com/uplaunch/failure-is-it-an-option-d34ba871e388?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/d34ba871e388</guid>
            <category><![CDATA[uplaunch-blog]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Jake Johnson]]></dc:creator>
            <pubDate>Wed, 12 Jul 2017 22:04:39 GMT</pubDate>
            <atom:updated>2018-04-26T14:59:15.939Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nZRRnlndFB_d1RAVPgy2Ww.jpeg" /></figure><p><em>I had a short but phenomenal conversation in the gym last week, and it triggered some insight, a little self-evaluation, and a lot of reflection.</em></p><p>In my life, I’ve failed many times, but in each failure, I’ve fought to find successes. Why? Our company Run Your Gym has failed many times, (like epic failures, you need to <a href="https://medium.com/uplaunch/the-no-bs-story-of-how-our-startup-started-up-and-the-5-rules-48926261aa82">read the story</a>) but in each failure, we fought to find success. Why?</p><p>Because failure isn’t an option.</p><p>With each individual failure turned success, I’ve built confidence, a desire to be more successful, and the realization that if I want to succeed I only need to do one thing. And guess what? That one thing will determine the success of UpLaunch too. You’ll have to keep reading, I promise, we’ll get to that one thing.</p><p>Before we do let’s dive into some common themes I can identify when it comes to failure.</p><p><strong>I gave myself permission to fail.</strong></p><p><em>I’ll do better next time, I’m not feeling it today, it isn’t that important.</em></p><p><strong>I let my ego impair my judgment which forced my failure.</strong></p><p><em>It isn’t my fault, it isn’t fair, I didn’t get the same chance as others.</em></p><p><strong>I got comfortable.</strong></p><p><em>Someone else will take care of it, I’ll do it another day, it seems fine — why change it?</em></p><p>I could go on for a long time, but regardless of how long the list becomes the theme will remain the same, I, I’ll, me, my, I’m.</p><p>Seems pretty consistent right?</p><p>Drum roll… here is the single realization I need to be successful.</p><h4>The only thing preventing my success is the image in the mirror.</h4><p>I view myself as fortunate because at a young age I was forced into an unforgiving world, one fueled by hate, rage, fear, irrational behavior, and life or death consequences for failure. With roots in the military and fire service the entire UpLaunch team has literally fought, bled, and sweat, through similar experiences.</p><p>As I look in the mirror I carry that experience and I know what’s convenient, comfortable, easy, and sometimes the popular, probably isn’t right. I also know when I look in the mirror I need to respect, honor and love the person looking right back at me. I’m in control of my life and want to be at peace with that. As for UpLaunch we will get into building a powerhouse team another day but know that same mentality is multiplied throughout our team.</p><p>Everything in this world worth being successful at takes the relentless pursuit of excellence.</p><p>Every day we can wake up and choose to fail, or we can wake up and choose to be successful.</p><p>Regardless of the circumstances that surround us we are always in control — take action, take ownership, and be better people.</p><p>Is failure an option? No, it isn’t.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d34ba871e388" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/failure-is-it-an-option-d34ba871e388">Failure. Is it an Option?</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The No-BS Story Of How Our Startup Started Up (And The 5 Rules)]]></title>
            <link>https://medium.com/uplaunch/the-no-bs-story-of-how-our-startup-started-up-and-the-5-rules-48926261aa82?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/48926261aa82</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[fitness]]></category>
            <category><![CDATA[uplaunch-blog]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Matt Verlaque]]></dc:creator>
            <pubDate>Fri, 30 Jun 2017 03:36:50 GMT</pubDate>
            <atom:updated>2018-04-26T16:47:20.508Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cvHVAHBWf-nJGb-nmIi04g.jpeg" /></figure><p>Everyone wants to be the one-stop-shop of everything. The Airbnb of their industry. Whatever. At this point, that kind of talk is just that — talk. 99% of successful companies are built on a solid foundation of caffeine, bad decisions, costly mistakes, and an irrational unwillingness to quit. This is a story about how UpLaunch came to be, and all the crappy ideas and dumb-luck successes that led us to actually becoming a legitimate software company.</p><p>I started a company called <a href="http://runyourgym.com/">Run Your Gym</a> in 2013, and it was just me. I was building websites for affiliate gyms. My buddy Jake, who is an <a href="http://uplaunch.com/">UpLaunch</a> co-founder and our Partner Director, had a gym in Gettysburg that he was opening and needed a website, so I hooked him up — and the (not so novel) idea was born.</p><p>I knocked out a few websites, met some cool people, but it was never more than a side hustle. That is, until this one time Jake and I had breakfast.</p><p>He wanted some changes to his website, and we sat down to go over them. That conversation led to some discussion about a greater vision — a vision where we were going to launch this massive venture that would provide web design services, consulting, business systems automation, and e-learning courses for gym owners. The good ol’ “four pronged approach” — what could go wrong? We were going to “kill it”.</p><p>Fast forward a few months, and we had lots of plans, lots of ideas, and jack shit for execution. Maybe — just maybe — two people trying to launch a web design company that also provided one on one consulting that also provided automated business systems that also wanted to build out a suite of e-learning courses was too much?</p><p>Yeah. Too much.</p><blockquote>Rule #1: If you try and do everything, you’ll accomplish precisely nothing. Learned that one the hard way.</blockquote><p>So we pared down. Websites? I was an alright web designer, but nowhere near the best — and there were already a handful of top notch web design shops catering towards affiliate gyms. So we dropped it.</p><p>Consulting? There are about a half dozen solid affiliate gym focused business mentors, and hundreds more outside of that industry. They all do a great job helping people get their businesses squared away, and we decided to ask ourselves if it would be better to have those consultants as potential partners or as competition. There went the consulting idea.</p><p>Then we got to the business systems automation. There HAD to be a solid solution out there for people to automate their funnels and intake process, communicate with their members, and build business systems, right? I mean, RIGHT??</p><p>I think we’re on to something now.</p><p>It was like a 10 year old at the McDonald’s soda station. Start with half a cup of <a href="http://pushpress.com/">membership management software</a>, add a dash of <a href="http://mailchimp.com/">MailChimp</a>, a little Google Forms, a shot of Excel, and top it off with a bunch of hopes and prayers…</p><p>Yeah, we WERE on to something.</p><p>Sure, there’s software out there if you want to take the time to build all your own campaigns, or hire someone to build them for you. But there wasn’t anything out there for someone with some killer marketing campaigns to build them, productize them, and deploy them to thousands of gym owners without a two month long on boarding process.</p><p>Afterburners…ENGAGE.</p><p>This is supposed to be the part where we’re like “Yeah bro, I coded some shit and Jake sold it to every gym on Earth bro, and that’s how we’re the most viral unicorn Silicon-Vally superstar app ever bro!”</p><p>Give me a break. Anyone who thinks that an overnight success is an actual thing just didn’t stay up fucking late enough to see all the work getting done.</p><p>We hooked up with one of the fitness business mentors that we knew (What’s up <a href="http://twobrainbusiness.com/">Coop</a>!) and Jake went on his podcast to talk about a program that he had run at his gym to get people off the couch. We wanted to use it as a springboard to build up some interest about our software that we were going to create (no big deal, right?) — so we decided to give the content for the program away, and sell an automated version of it for a hundred bucks.</p><p>Maybe we would sell ten or twenty of these automations, which was a completely manual process for me to set up — create a landing page on a WordPress Multisite installation, link up 3 other apps using <a href="http://zapier.com/">Zapier</a> integrations, insert logos, addresses, branding information into the content — you know, the whole “do stuff that doesn’t scale when you’re small” philosophy.</p><p>Podcast went live Monday morning. By lunch we had sold a half dozen. I knew right there, halfway through my turkey sandwich, that we were a) screwed, and b) going to eventually be super successful.</p><p>Day 2 — we had our 20. To make things better, after we on-boarded those 20, one of the key programs we were using to power the automations had a massive bug and all 20 sequences hung up for no good reason. Not going to name names, but it happened on Christmas Eve, which made it extra convenient.</p><p>I picked a new program to switch everyone over to, recruited a few of my buddies to help, taught them how all the apps worked, wrote up a 60 point checklist of how to launch an automation, and we made it happen. Got all the accounts migrated over in the middle of a campaign with no data loss and only a few hiccups. First big win.</p><p>Day 10 — we had 50. Lots more work.</p><p>Day 21 -we had 80, and tripled the price to make it stop. It didn’t, but it did slow down.</p><p>We were overrun. We made a little money (but not nearly enough). We were tired. But we didn’t fail, and most importantly:</p><blockquote>Rule #2: Validate the market before you make big moves. Short term chaos is preferable over long, expensive mistakes.</blockquote><p>We kept rolling. We captured pre-sales for this software that, at this point, didn’t even exist yet. We didn’t charge people, but we did authorize the CC charge and have them on a waiting list (thanks to <a href="http://trycelery.com/">Celery</a> for making that easy).</p><p>We decided it was time to create an MVP. I’m not here to bullshit you, we didn’t call it that because I didn’t even know what an MVP was unless we were talking about sports. Minimum Viable Product, as I would soon find out.</p><p>It was really insane. We onboarded 5 people. Each onboarding process took about 30 days and required a checklist to be completed that was about 200 steps long. More WordPress, lots more Zapier, along with <a href="http://unbounce.com/">Unbounce</a>, <a href="http://infusionsoft.com/">InfusionSoft</a>, <a href="http://knack.com/">Knack</a>, duct tape, popsicle sticks…it was “Frankenstein” as we called it. But it worked. We built funnels, we generated our first 5 subscriptions (legit recurring revenue, wahoo!), and people liked it. They also liked the content that shipped with the platform, and our campaigns were helping them get business.</p><blockquote>Rule 3: Even if you validate that the market wants what you have, make sure they’ll actually pay money for it.</blockquote><p>We went through a few ideas and trial runs at this point. We toyed with the idea of hiring a high-dollar software company to build the app for us, and actually came really close to going down that path. We instead pivoted at the last minute and partnered up with a large company who would use some existing technology to do the heavy lifting on the backend, leaving us to build our campaigns on top of it.</p><p>We met some incredible people at that company, built some really cool relationships, and went full steam ahead. And although we learned a ton and were finally able to onboard a few dozen gyms, it still just wasn’t quite right.</p><p>We needed to build OUR vision. No matter what the cost (dollars, time, effort, etc), we were determined to build the software that we had discussed with our clients. The software we saw in our heads when we closed our eyes. We had to do it ourselves.</p><p>Lots of people say that companies without technical co-founders have a pretty bad chance of making it. I see why. So I became a technical co-founder. I hit up a <a href="http://rubyonrails.org/">Rails</a> bootcamp (what up <a href="http://www.thefirehoseproject.com/">Firehose Project</a>!!) and attacked it like a rabid animal. I went in there with one goal — to learn how to build our software. I didn’t want theory, I didn’t want to learn how to be some idealistic coder who argues about tabs vs. spaces…I needed to make this thing come to life. And I did.</p><p>Lucky for me, I also asked for help. I knew that our platform wasn’t the typical “first app” that people create, and also knew that I couldn’t effectively be the only person writing code and also be the CEO. I went into our weekly office hours meeting and asked a few questions…then I just dropped it: “I’ve got some pretty cool stuff going on if anyone wants to jam with me.”</p><p>30 minutes later, I was pair programming with the guy who would become UpLaunch employee #1.</p><blockquote>Rule 4: Your ego is stupid. Ignore it. Ask for help, build a team, and do everything you can to make sure you’re the dumbest person in the room.</blockquote><p>So we coded for a few months. Nonstop. I thought I was kicking ass at building this app until our newly-minted Lead Developer pretty much stomped my face into the ground with the speed at which he could write code. That’s when I developed a brand new skill set as a product manager — if I couldn’t plan the sprints, write the user stories, and figure out what would make it into our initial release and what wouldn’t, I’d be wasting an incredible resource. So I got my shit together, planned it out, and we made it happen.</p><p>As we built out our platform, it became apparent to us that this was going to be much bigger than just gyms. We had all the building blocks — a completely innovative way to handle task management (that nobody in the industry had thought of), native appointment booking, full CRM functionality, bulk email and SMS capabilities…we could scale this thing big time.</p><p>That’s what spawned the partner model, and what put the Run Your Gym brand to bed. We brought in a talented marketer (Partner #1) that we knew from the fitness industry to take over creating the campaigns, handle the direct sales, and support for his customers — essentially building his business on top of ours — which let us focus solely on helping him and building the platform itself.</p><p>That’s a process that can be replicated. Another partner, another industry. Another 5 partners, another 5 industries.</p><p>I don’t mind being transparent — we gave up a large percentage of our revenue in exchange for that ability to scale. Lucky for us, we picked the right partner (hey <a href="http://theboxbusiness.com/">Mike</a>!) and we’re developing a close-knit and mutually beneficial relationship — and will still be able to help a ton of gyms in the process.</p><blockquote>Rule 5: Don’t be SCARED. Take a smaller slice of the pie and instead focus on making the pie itself as huge as you possibly can. Run your business based on abundance instead of scarcity.</blockquote><p>We talked about names for a while, and found UpLaunch — I cold-emailed the guy who owned the domain and social handles and he agreed to sell it to us — huge lucky break there. I promised him that we would do great things with the brand, and I think we’ll fulfill that promise.</p><p>So now, we’re here. We’re going to market with our first offering for gyms at the end of August, and will be starting the search for our second partner sometime before the year’s end. The platform is rock solid, doing things that nobody’s been able to pull off yet, and we’re still hustling our asses off to make it happen — just as hard as we were hustling on that one Christmas when everything broke.</p><p>No, we haven’t “made it” yet. We’re not getting invited to our favorite podcasts yet (but if anyone wants to hook us up with <a href="https://www.smartpassiveincome.com/">Pat Flynn from SPI</a> or <a href="http://www.npr.org/podcasts/510313/how-i-built-this">Guy Raz from How I Built This</a>, feel free), and we’re not taking selfies in our Ferraris (nor will we ever be…gross). We’re just a bunch of hardworking dudes who are getting ready to hit the market with something awesome.</p><p>But even to make it to this point, it’s been a crazy journey. This is the part that most people view as the starting line: launching a product. That’s true in a lot of ways, but the people who have done this before realize that it’s not just an idea and a week of coding — it’s a long process that’s taken us almost four years to complete.</p><p>But here we are. No more day jobs, no more side hustles. 100% UpLaunch, all day, every day. And we’re looking forward to showing the world what we can do.</p><p>Got a cool story about your startup, product, business, or something else? Drop it in the comments, cause I love talking with people and I get lonely easily ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48926261aa82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/the-no-bs-story-of-how-our-startup-started-up-and-the-5-rules-48926261aa82">The No-BS Story Of How Our Startup Started Up (And The 5 Rules)</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Sum Of The Parts]]></title>
            <link>https://medium.com/uplaunch/the-sum-of-the-parts-44f887919f0d?source=rss----6689ef4d33c8---4</link>
            <guid isPermaLink="false">https://medium.com/p/44f887919f0d</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[uplaunch-blog]]></category>
            <category><![CDATA[gettysburg]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Matt Verlaque]]></dc:creator>
            <pubDate>Sun, 28 May 2017 22:32:34 GMT</pubDate>
            <atom:updated>2018-04-26T15:00:07.717Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3UU-jv7_ZIrioQPCDXjAw.jpeg" /><figcaption>The view from Little Round Top</figcaption></figure><p>I should start by saying that the UpLaunch team is coming off of an incredible week. There will be an official announcement coming soon, but we just had our first partner join the team, and the results are going to be insanely cool.</p><p>I guess I should briefly explain the business model.</p><h4>How It Works</h4><p>UpLaunch was started to support a specific mission — we exist to break down the barriers that stand in between business owners and elite marketers who can help them succeed. Never before has there been an organization that allows marketers to focus on the process of <strong>creating </strong>instead of details of <strong>implementing</strong>.</p><p>But this isn’t a sales pitch disguised as a blog post (because those suck). In fact, we don’t actually <strong>sell</strong> anything.</p><blockquote>UpLaunch doesn’t have customers. UpLaunch has partners.</blockquote><p>The way it works is that we partner with marketers who work in a specific vertical and host them for an in-person work session in Gettysburg, PA. During this session, we dig into every detail of their marketing strategy and cross-reference it with the capabilities of our software platform. And in the case of this past weekend, we find that we’re a great fit for each other and move forward!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_48TylLVSMPydk9XqhcLIw.jpeg" /></figure><h4>The Sum Of The Parts</h4><p>This isn’t really intended to be informational — it’s a reflection piece about the straight-up magic that happens when a great team comes together. The partner we met with last week works in an industry that is near and dear to our hearts, and one that we have deep first-hand familiarity with. Despite that, the amount of new ideas that were introduced, developed, refined, and implemented was astounding.</p><p>We talked a lot about what it’s like to feel isolated when you don’t have access to minds that challenge you, talked a lot about values, life goals, and ways to ensure that our businesses help as many people as possible, and a lot about food too (Gettysburg has a lot of great local restaurants, by the way).</p><p>We capped off our week with a visit to the various points of interest of the Battle of Gettysburg, where we were able to take time to reflect on history, sacrifice, leadership, and leaving a legacy for those who come after us.</p><p>Aristotle said that “the whole is greater than the sum of its parts”, and of course that quote rings true — although we’ve had a few good ideas individually, the power of our growing team is going to be epic. We can’t be any happier to have brought our first partner into the fold.</p><p><strong>Great things are coming, and we’ll announce them soon.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IKrdbDLp_RAsE2zq1uw_Fw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44f887919f0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uplaunch/the-sum-of-the-parts-44f887919f0d">The Sum Of The Parts</a> was originally published in <a href="https://medium.com/uplaunch">UpLaunch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>