<?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 Josh Bitossi on Medium]]></title>
        <description><![CDATA[Stories by Josh Bitossi on Medium]]></description>
        <link>https://medium.com/@joshbitossi?source=rss-12e0dc5ed0ca------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lDZC7TINo0ovYs7G.</url>
            <title>Stories by Josh Bitossi on Medium</title>
            <link>https://medium.com/@joshbitossi?source=rss-12e0dc5ed0ca------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:15:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joshbitossi/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[Using Shopify to run a SaaS business — (Shopify “hacks” Part 3)]]></title>
            <link>https://joshbitossi.medium.com/using-shopify-to-run-a-saas-business-shopify-hacks-part-3-735bafff6a07?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/735bafff6a07</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[shopify]]></category>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[slack-tips-and-tricks]]></category>
            <category><![CDATA[shopify-development]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Mon, 07 Jun 2021 03:06:23 GMT</pubDate>
            <atom:updated>2021-06-07T06:41:44.104Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using Shopify to run a SaaS business — (Shopify “hacks” Part 3)</h3><p>A little under two years ago I wrote a quick post on how I <a href="https://medium.com/gobeyond-ai/building-launching-a-web-app-in-24-hours-w-shopify-sketch-printful-3709b684856">launched an idea in &lt; 24 hours with Shopify</a>. I followed it up with a post on <a href="https://medium.com/@joshbitossi/shopify-hacks-2-quick-and-dirty-recurring-saas-product-f50475f621a4">how (and why) I was using Shopify to launch a SaaS business</a> instead of integrating directly with Stripe.</p><p>2 years later, and that hacky little project has turned into a modest business with 2 independent products — <a href="http://slackscheduler.com/">Slack Scheduler</a> and <a href="https://formsforslack.com/">Forms for Slack</a>.</p><p>They’ve comfortably grown to 5 figures in monthly recurring revenue, helping hundreds of companies and thousands of users communicate over Slack during a period where everyone has been trying to figure out how to work remote.</p><p>Those two articles have also led to some great conversations and opportunities. I was hesitant to share specifics, but it seemed a shame to not publish what I’ve experienced the last couple of years running a SaaS business through Shopify. And then someone asked about <a href="https://www.reddit.com/r/SaaS/comments/nt06rw/a_billiondollar_opportunity_shopify_for_saas/">using Shopify in this way on /r/saas</a> which gave me the push to publish this.</p><p>2 years later and more and more of the operations are using Shopify, so it’s time to give an update. I’ve been taking notes on what has and hasn’t been working which I’ll share here.</p><p><strong>I’m still a bit hesitant to share this post — so if you enjoy it or get some value, send me a message on </strong><a href="https://www.linkedin.com/"><strong>Linkedin</strong></a><strong> or </strong><a href="https://twitter.com/_bitossi?lang=en"><strong>Twitter</strong></a><strong>.</strong></p><p>Once thing that’s stayed the same is I still work at Shopify — so the usual disclaimer that these thoughts and opinions are my own.</p><h3>Running a SaaS through Shopify — would I recommend it after 2 years?</h3><p>Yes.</p><p>One big clarification here — the actual software part of my SaaS doesn’t go through Shopify. I’ve totally done that in the past though and built an analytics tool where a customer would only get access to the tool in their Shopify account section. I’d still love to see more of that.</p><p>I’ve been the sole employee for the business (aside from experimenting with some marketing contractors) up until this month. And I think a large part of the reason I’ve been able to manage that while still giving 100% at Shopify is due to how much I leverage the Shopify product.</p><p>For my business today, I use Shopify for things like:</p><ul><li>Customer management</li><li>Pages and Blog posts</li><li>Subscriptions (with the help of Recharge)</li><li>Reporting (financial and custom behaviour)</li><li>Website hosting</li><li>Transactional notifications</li></ul><p>That might not sound like a tonne — but when you’re starting a new product, those are all things that are super important and a pain to set up.</p><h4>Third-party apps</h4><p>One of the strengths of Shopify has been how everything has an API endpoint. This is useful for connecting my own processes, but also because it means there is a marketplace of thousands of apps that build on the Shopify ecosystem.</p><p>This has allowed me the ability to quickly add functionality to my business without touching any code.</p><p>A few of the ones that I’ve used:</p><ul><li>Klaviyo for email marketing</li><li>Shogun for a couple of custom pages</li><li><a href="https://apps.shopify.com/order-printer-pro">Order Printer Pro </a>for some email templates</li><li>Gorgias for customer service (highly recommend)</li><li>Stamped.io for reviews</li><li>Recharge to manage subscriptions</li></ul><p><em>(again, these aren’t official endorsements in any way, just ones I’ve found to personally work for me)</em></p><p>These apps are often tailored towards eCom merchants for obvious reasons. I find that mostly to be a <strong>good</strong> thing, but it does mean I have to use the occasional workaround.</p><p>As an example, I had to tweak the settings on my review app so it would only send reviews on the <em>second</em> order. Otherwise, people would get a review request email every month when their subscription renewed.</p><p>Onboarding is also a lot different in SaaS than it is in eCom. And reporting is different since you’re expected to have a much higher rate of returning customers.</p><p><strong>Testing Apps Quickly</strong></p><p>About 12 months ago I started hitting a wall with support. All my time was spent answering support tickets.</p><p>I switched over to a customer service tool called Gorgias and immediately felt like I had more time back after implementing a lot of their prebuilt third-party integrations and heavily utilising their macros and automation features.</p><p>My point here isn’t that Gorgias is necessarily a better app for everyone (FWIW though I am a big fan), but rather that through the Shopify app store I had plenty of options for solutions that I could install and test in a couple of minutes. That’s super important when you don’t want to spend a lot of time having to validate solutions. And when you’re growing a new business there are so many new things to try that you want to be able to quickly implement to see what works and what doesn’t.</p><h3>Managing Subscriptions</h3><p>The biggest challenge with using Shopify for a SaaS business has been managing subscriptions.</p><p>For some context, up until somewhat recently, Shopify used third-party apps to handle the subscription logic which means you not only use these apps to manage your subscriptions but also used their checkout and orders that came to Shopify were all done via API.</p><p>What’s more is these products for the most part seem focused on traditional eCommerce subscriptions, and I was left dreaming of using more SaaS focused subscription solutions that have since come up like <a href="https://paddle.com/">Paddle</a> or integrating with Stripe directly.</p><p>Here are a couple of challenges I ran into and how I “solved them”:</p><ol><li><strong>Trial periods</strong></li></ol><p>Customers typically have a trial in SaaS. But<a href="https://stripe.com/en-au/atlas/guides/saas-pricing"> it’s recommended</a> you give customers the ability to complete payment before their trial has started.</p><p>To do this, I ensure customers sign in to Slack before they can complete checkout. From this, we can determine how much time they have left in their trial, and if it hasn’t expired they purchase a $0.00 product.</p><p>Then, using Recharge’s cool <a href="https://support.rechargepayments.com/hc/en-us/articles/360008683754-ReCharge-Workflows">Workflow</a> tool we can automatically update the price based on the plan they’ve purchased.</p><p>This can still be a bit of a confusing signup flow if a customer purchases a product for $0 and then shortly after gets an order confirmation for the full amount, so I’ve customised the order notification to be more akin to a “welcome” email to if it’s the customer’s first order and to also tell them when their first proper charge will be.</p><p>All of this is just done with liquid by picking up line item properties. Eg —</p><blockquote>{% assign trial = 14%}<br>{% for line in line_items %}<br> {% for property in line_item.properties %}<br> {% if property.first == “trial” %}<br> {% assign trial = property.last %}<br>{% endif %}<br> {% endfor %}<br>{% endfor %}</blockquote><p>…</p><blockquote>This email is to confirm your subscription. Your first charge will be in {{ trial }} days&lt;span</blockquote><p><strong>2. Subscription Information</strong></p><p>Here I use line item properties to track information like how long is left in their trial and even dictate things like when the first charge date should be.</p><p>I have some extra processes in the background to constantly validate this type of information. Line items alone aren’t super secure since a customer can add their own. It just happens to be how Recharge handles subscription information, and I haven’t really had any issues using them for non-sensitive info.</p><p><strong>3. Swapping Subscriptions</strong></p><p>People often want to upgrade their subscription to an annual plan. Because of the $0.00 product price I use to give people a trial, this can lead to a bug where people swap to an annual subscription and actually end up with a $0 subscription that doesn’t get charged for a year…</p><p>This requires some custom work to fix up since I couldn’t find a way to handle it with Recharge’s workflow tool.</p><p>What I’ve done in the meantime is use <a href="https://apps.shopify.com/flow">Shopify Flow</a> to send me an alert any time this happens and I just manually fix-up. Flow’s only available on Shopify’s Plus plan, but you can probably use another tool for this particular use case.</p><p>This has been a bit of a common theme the last couple of years. I don’t have time to work on everything and I need to balance dev time between working on the product and automation. The nice thing with Shopify is that it gives me plenty of tools to create relatively automated stop-gap processes.</p><p>Another example of this was an experiment I ran with a referral program. For a while, I was automatically creating a unique discount code via Recharge’s API every time someone installs the app. That code could then be used as an affiliate referral of sorts. Shopify Flow would just alert me if one of these codes was used — turns out it wasn’t as popular as I expected so I never built out the final piece to automatically apply the discount logic. And I’ve been able to use the discounting mechanism for other reasons like non-profit discounts.</p><p><strong>4. Reporting</strong></p><p>I haven’t found Shopify reporting <em>as</em> useful as I would if all orders were running natively. And finding a good reporting tool has been a bit challenging. Because Recharge uses Stripe I tend to use:</p><ul><li>Stripe’s dashboard for finances</li><li>Shopify for total order volume and high-level session, order and customer reports</li><li>Recharge for subscriber reports</li><li>Occasionally <a href="https://www.profitwell.com/">Profit Well</a> for diving into things like churn and customer segments</li><li>GA for traffic and session reporting with some custom funnels built into track checkouts via Recharge</li></ul><p>This isn’t a dealbreaker, but just another thing to think about — you’ll want to figure out where information about different aspects of your business lives and probably not expect it will all roll up into the native Shopify reports (for now).</p><p><strong>5. Custom Processes</strong></p><p>Because my actual apps run in Slack, I still need to track a team’s status outside of Shopify.</p><p>I have a separate little CRON service built on Heroku just to manage subscription stuff. Thankfully Recharge has a great API. So together with Shopify’s Order webhooks I can listen for order and subscription changes and update teams accordingly.</p><h4><strong>Future Plans</strong></h4><p>A lot of the above is now changing with Shopify introducing its own set of Subscription API’s. I’ve built some test apps using them and the possibilities and use cases are pretty exciting. When I finally migrate I might write another post. Because of the custom workflows and the time it’s taken for parity with my existing subscription solution, it’s a high, but not #1 priority for me. But I’m pretty excited at the idea of using Shopify scripts and native Shopify orders.</p><p>Aside from continuing to work on product improvements, I’m now at the point where I can fill in some of those manual gaps with proper automation and systems and build a more resilient business which I’m pretty excited to work on.</p><h3>Ecommerce vs Saas</h3><p>By day I’m surrounded by eCommerce, but nights and weekends I’m diving into the world of software and Saas. Thing is, there’s a remarkable amount of cross-over that doesn’t get spoken about.</p><p>IMO the differences come from the respective backgrounds of people in both fields. Ecom tends to be largely focused around marketing and product development. Saas tends to be more technical.</p><p>Of course, this is a gross oversimplification and there increasingly exists people of both backgrounds in each. But as an example, Ecom folk seem to focus much more on customer acquisition costs and optimising lifetime value. Whereas SaaS tends to have inherently higher LTV so focuses on reducing churn which tends to mean improving product. Same overall goal but generally different approaches.</p><p>Anyway — what I like about Shopify, is that it exposes my Software business to the world of eCommerce where I’m forced to think about things like conversion rate and site speed that might otherwise go unprioritised.</p><h3>Bootstrapping requires speed and quick Action</h3><p>In case you missed it, e-commerce got pretty busy last year, and working at Shopify was no different. So when I had time and energy I needed to make sure that I could focus my time on improving the product and working “on” the business instead of “in” the business (shout out to <a href="https://www.starknakednumbers.com/">Stark Naked Numbers</a>).</p><p>I needed to be able to implement something quickly and have it running in the background where I could test it for a couple of months and revisit it to decide if it was working.</p><p>Shopify has made that super easy. If I want to publish a blog post it takes 30 seconds to publish. If I want to set up redirects or navigation I can do that. If I want to build out a <a href="https://slackscheduler.com/pages/help">help page</a> I can use a tool like Shogun to quickly spin up some designs, or spend some time in the theme to tweak it as I need. Does it do all of these things perfectly — ehh. But it generally does 90% of what I need at a <em>really</em> high level and gives me the tools to build out that extra 10%. And there are probably hundreds of things that I don’t even realise I need it just handles, like customer accounts, SEO, image optimisation, file handling, etc etc. I’d much rather that balance than something that gives me 10% but requires me to build out the other 90%, or something that handles subscription really well but leaves me in the dark in other areas.</p><h3>What would I do differently / when not to use it</h3><p>My experience aside, there are still some really good reasons to consider if it’s the right choice.</p><h4><strong>Factor in Payments and the TOS</strong></h4><p>Payments are the biggest roadblock to a business online. If you can’t get payments approved or your business goes against the TOS (things like digital gambling etc) then you might not have a fun time on Shopify or most other big platforms.</p><h4><strong>It’s still a bit wild west</strong></h4><p>Shopify isn’t designed for SaaS specifically in mind. You’re going to be a little on your own in some regards.</p><p>For me that’s a good thing — it almost feels like a competitive advantage because it lets me move faster as a solo founder than I would otherwise. I take some compromises in some areas others think are a necessity to have a better-rounded business overall. As someone who works at Shopify — it also lets me discover these pain points first hand and help surface them to make Shopify better for online businesses.</p><h4>It could still require some custom work</h4><p>One thing I realised is that if you’re not developer inclined, requiring a small amount of dev work could be as equally inaccessible as a large amount of dev work depending on your access to developers. In which case maybe you want to go with something requiring even less customisation or something designed purely for handling subscriptions.</p><p>With some creative thinking, I’m sure you could get away with building a digital content business without requiring any code on Shopify. But integrating a SaaS is probably going to require some dev work.</p><p>What’s good is that Shopify lets you get up and running faster so you can validate your idea, do some work manually. Automate some things with tools like Zapier and a small amount of dev work using Shopify experts / freelancers and then when you’re ready start to build out more bespoke code workflows.</p><h4><strong>Might not be the cheapest</strong></h4><p>If you’re relying on third party apps, your monthly costs are going to be higher than if you build everything from scratch.</p><p>I’ve found that most software expenses are often going to be fixed like app fees. Variable expenses that scale with your business (think processing fees) might be a bit higher on Shopify in some cases, but you’ll likely be paying for those regardless of what platform you use. The difference is if you’re like me and using a tool like Recharge that lives on top on Stripe, so you’re getting stung with 2x processing fees and those grow with your business. For me the cost is still well worth it though, and again it’s something you can replace if and when your business outgrows it.</p><p>I don’t think these are inherent Shopify problems and you’re going to be paying a platform tax regardless of what you use. It’s just a matter of weighing up the cost of custom dev vs third party solutions.</p><h4>Factor in my own Biases</h4><p>Running a business has given me a huge amount of empathy for the merchants I work with day-to-day. My initial reason for using Shopify to run a SaaS was mainly curiosity in this regard, but it also felt like a good way to get some hands-on experience actually building and working with the platform.</p><p>It was also a way to save some money in platform costs with some of the support that Shopify gives its employees (<a href="https://www.shopify.com/careers">seriously it’s a great place to work</a>).</p><p>Most people don’t have those same factors, so that might tip the scales for you.</p><p>If I was starting out though, I’d still choose a Shopify or a platform like Shopify to sit at the centre of my SaaS business. It gives me the right amount of flexibility to integrate and customise while taking care of the operations side really really well. But one of the cool things about running a business is you can only really learn from experience and you can only get experience from the level your business is at or through others. So if you see something I can improve, have questions, criticisms or suggestions hit me up (<a href="https://www.linkedin.com/in/joshuabitossi/">on Linkedin preferably</a>).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=735bafff6a07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shopify Hacks 2 — Quick and Dirty Recurring SaaS Product]]></title>
            <link>https://joshbitossi.medium.com/shopify-hacks-2-quick-and-dirty-recurring-saas-product-f50475f621a4?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/f50475f621a4</guid>
            <category><![CDATA[shopify]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[saas-tools]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[ecommerce-web-development]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Sun, 26 Aug 2018 15:26:33 GMT</pubDate>
            <atom:updated>2018-08-26T15:37:05.228Z</atom:updated>
            <content:encoded><![CDATA[<p>Second in the series of late night quick and dirty Shopify hacks.</p><p>I’ve been working on a small SaaS app for a while now. It’s at the point where I need to implement a lot of the features outside of the core product I’m actually building.</p><p>Things like billing and associated workflows around notifications, checking card processing etc.</p><p>Two options I looked at:</p><ol><li><strong>Implementing it all with Stripe myself.</strong></li></ol><p>Not challenging but somewhat cumbersome and I’m sure I’ll miss aspect of the flow. A lack of “Cancel Subscription” button in lieu of an “email me to cancel” seems to be common in most early SaaS products because the founder can’t be f’d coding it in.</p><p>There’s also the associated emails etc mentioned above and handling when customers don’t pay.</p><p><strong>2. Chargify </strong>— looks like a straight forward library for Stripe based subscriptions.</p><p>But aside from billing, I was also at the point of starting to implement customer facing assets. Landing pages, contact forms and the like. More time spent away from the core product.</p><p>My goal is to <strong>build a product that 1,000 people can use everyday and can be built and managed by 1</strong>. ie 1000:1. To do that I want to be fast and smart.</p><p>I started thinking about Recharge which is what a lot of merchants on Shopify use to power their recurring subscriptions. (Similar options <a href="https://apps.shopify.com/recurring-orders">here</a> and <a href="https://apps.shopify.com/paywhirl-recurring-payments">here</a>. Both also good but I wanted to learn a bit more about Recharge specifically).</p><p>That got me thinking about all the other aspects I could use Shopify for:</p><ul><li>Quickly building home pages with themes</li><li>Easy contact forms and navigation</li><li>Easy integration with marketing apps</li><li>A blogging platform</li><li>A CRM</li></ul><p>So setting it all up just required:</p><ol><li>Create the Shopify store</li><li>Change my DNS settings so my app lives on https://app. and the main site is at the https://www. subdomain. This was probably an inevitability and seems common practice anyway.</li><li>Update domains in Heroku and Shopify</li><li>Install and configure Recharge. Recharge also has some good documentation for <a href="https://support.rechargepayments.com/article/28-guide-to-add-item-to-cart-with-ajax">custom integrations</a> including <a href="https://support.rechargepayments.com/article/28-guide-to-add-item-to-cart-with-ajax">AJAX API </a>for adding in subscription products for one page stores (my quick implementation of that code with some small additions is at the bottom).</li><li>Change my signup workflow. This is the most time consuming. But Recharge works with Stripe so all the old API calls and web hooks are still relevant.</li></ol><p>And that’s it. Using Shopify and Recharge you’ve got all the piping for a SaaS product set up in no time. You’ve also created a CRM, landing page creator, payment gateway processor, blogging platform, newsletter signup etc etc etc.</p><p>I’m sure there’ll be some gotchas. There’ll be some <a href="https://aeon.co/essays/dad-s-company-made-burgers-mine-just-eats-them">plumbing</a> to get it all connected and maybe that will be too shaky a foundation to build an app on. But right now it’s taking advantage of two great systems.</p><p><strong>Full Disclosure:</strong> I work at Shopify Plus (find me on <a href="https://www.linkedin.com/feed/">linkedin</a>)</p><p>Everything above is my own opinion. Implement at your own risk and be sure to check the t.o.s.</p><p>Recharge AJAX Code. Source: <a href="https://support.rechargepayments.com/article/28-guide-to-add-item-to-cart-with-ajax">Recharge Docs</a></p><pre><br>&lt;script&gt;<br> // Clear the cart to make sure the customer only ever has one item in their cart<br> // They won’t ever see the cart itself so just to make sure.<br> function clearCartOnLoad() {<br> jQuery.ajax({<br> type: ‘POST’,<br> url: ‘/cart/clear.js’<br> });<br> };</pre><pre>/* SOURCE: <a href="https://support.rechargepayments.com/article/28-guide-to-add-item-to-cart-with-ajax">https://support.rechargepayments.com/article/28-guide-to-add-item-to-cart-with-ajax</a> */</pre><pre>function reChargeProcessCart() {<br> function get_cookie(name){ return( document.cookie.match(‘(^|; )’+name+’=([^;]*)’)||0 )[2] }<br> do {<br> token=get_cookie(‘cart’);<br> }<br> while(token == undefined);</pre><pre>var myshopify_domain=’{{ shop.permanent_domain }}’<br> try { var ga_linker = ga.getAll()[0].get(‘linkerParam’) } catch(err) { var ga_linker =’’ }<br> var customer_param = ‘{% if customer %}customer_id={{customer.id}}&amp;customer_email={{customer.email}}{% endif %}’<br> checkout_url= “<a href="https://checkout.rechargeapps.com/r/checkout?myshopify_domain=">https://checkout.rechargeapps.com/r/checkout?myshopify_domain=</a>&quot;+myshopify_domain+&quot;&amp;cart_token=&quot;+token+&quot;&amp;&quot;+ga_linker+&quot;&amp;&quot;+customer_param;<br> window.location.href = checkout_url<br>}</pre><pre>function addItemToCart (variant_id, quantity, shipping_interval_frequency, shipping_interval_unit_type, subscription_id) {<br> data = {<br> “quantity”: quantity,<br> “id”: variant_id,<br> “properties[shipping_interval_frequency]”: shipping_interval_frequency, <br> “properties[shipping_interval_unit_type]”: shipping_interval_unit_type, <br> “properties[subscription_id]”: subscription_id<br> }<br> jQuery.ajax({<br> type: ‘POST’,<br> url: ‘/cart/add.js’,<br> data: data,<br> dataType: ‘json’,<br> success: reChargeProcessCart()<br> });<br> }<br> clearCartOnLoad();</pre><pre>// When below button clicked, add to cart. Change 123 to your<br>// subscription product variant.</pre><pre>$(‘#add-to-cart-button’).click(function(){<br> addItemToCart(123 , 1, “1”, “Months”, “143266”)<br> })<br>&lt;/script&gt;</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f50475f621a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building & Launching a project in < 24 hours w/Shopify, Sketch & Printful]]></title>
            <link>https://medium.com/gobeyond-ai/building-launching-a-web-app-in-24-hours-w-shopify-sketch-printful-3709b684856?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/3709b684856</guid>
            <category><![CDATA[ecommerce-web-development]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[shopify]]></category>
            <category><![CDATA[ecommerce-solution]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Thu, 07 Jun 2018 05:31:23 GMT</pubDate>
            <atom:updated>2018-06-08T13:58:29.469Z</atom:updated>
            <content:encoded><![CDATA[<p>Building and launching anything is hard. But if you’re doing that while <a href="https://medium.com/@joshbitossi/im-going-remote-er-f504d575cfc">working full time and travelling</a>, it adds some extra challenges:</p><ol><li>You have less time</li><li>You lose the middle of the day where you’re likely most productive</li><li>If you’re in front of a screen, it’s hard to want to keep working in front of a screen after hours</li><li>There’s a big cognitive load switching between work and personal projects.</li><li>Constant stopping and starting means it’s easy to lose direction</li></ol><p>All of these add up to become negative multipliers. Maybe you have half as much time, but it takes 4, 6, 8 times as long to finish the same project. And it’s not just the time, losing the ability to constant focus on a problem means quality and vision can suffer as well.</p><p>This is super evident if you’re building a project without enough users to give you feedback and keep you on course.</p><p>I was losing my ability to just build things. For me, this becomes evident when I start to go down idea rabbit holes, constantly exploring new ideas that don’t have any deeper purpose or would actually be something I wanted to build. You’re constantly asking “<em>could this actually be a business / cool idea?</em>” but never actually building something, because it’s easy to think of ideas, but executing takes resources. It becomes a dangerous cycle.</p><figure><a href="https://www.gobeyond.ai/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RKtzgYHK8kstprrS51FBsw.jpeg" /></a></figure><p>To fix this, I wanted to build and launch an idea in 24 hours. So this is how I built <a href="http://www.bigasstodolist.com/">bigasstodolist.com</a></p><h3>Idea</h3><p>Four criteria:</p><ul><li>It had to be able to make money straight away</li><li>It had to be simple in scope to avoid feature creep</li><li>I wanted a digital product</li><li>It had to be fun to make</li></ul><p>I was having trouble keeping track of big picture tasks and goals. So I thought, why not build a productivity tool.</p><p>What if I had a printed out list of big-picture goals. Something that was static and kept me on track?</p><p>I decided to make a tool that would let you design a todolist and have it printed out on a poster.</p><h3><strong>Building</strong></h3><p>I knew what I wanted to build and I knew there were three components to building it:</p><ol><li>The website where it was hosted and payments were processed</li><li>The interactive todolist builder</li><li>The design and printing of posters themselves</li></ol><h4>The Name</h4><p>I always use <a href="https://www.namemesh.com/">Name Mes</a>h when looking for a name since it helps give ideas while also searching for a domain name.</p><p>It was going to be big, this was a fun project. So I registered bigasstodolist.com 🤷‍♂</p><h4>The Website</h4><p>I decided to use Shopify for this.</p><p>For one, I work with Shopify everyday, so I’m familiar with it.</p><p>But it also meant:</p><ul><li>I wouldn’t spend time creating a Stripe set up and managing transactions / users / email notifications</li><li>I wouldn’t have to create a heroku instance and spend time managing that</li><li>I could leverage themes and apps instead of creating a front-end theme or having to build out extra features</li></ul><p>All of this meant I could focus purely on the main product.</p><p>I installed a<a href="https://themes.shopify.com/themes/jumpstart/styles/jumpstart"> one-page Shopify theme</a>, and configured all the usual settings around checkout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tR2OvGayfqN4hzVjgjkRXg.jpeg" /><figcaption>Shopify landing page with a mockup created with Printful</figcaption></figure><p>The biggest aspect was the todolist itself.</p><p>Using one of the 100’s of todolist examples online, I edited the home page liquid to include an interactive list that rendered a preview of what the list would look like.</p><p>It saved the list information into line item properties so anytime an order was placed, I would see what the person’s todo list item’s were.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djy8Y50hEoTl4ltpAf3n3A.gif" /><figcaption>The final working product</figcaption></figure><p>All of this was done with basic Jquery.</p><h4><strong>Printing</strong></h4><p>I created a basic template in <a href="https://www.sketchapp.com/">Sketch</a> that would let me quickly create each list as it came through.</p><p>Then I would forward the orders to <a href="https://www.printful.com/">Printful</a></p><p>This was definitely an area for automation given Printful’s API and integration with Shopify, but automation can come later and it lets me ensure the product quality is ok.</p><h3>Launching</h3><p>I first posted on a couple of reddit communities to get feedback on the build and idea.</p><p>After that I decided to <a href="https://www.producthunt.com/posts/big-a-todo-list">put it on Product Hunt</a> where it did quite well. Overall there were &gt; 1,000 visitors.</p><p><strong>But…</strong></p><p>No sales :(</p><p>For me that’s a lesson in itself. It could mean a couple of things:</p><ul><li>The product isn’t right — do people want a static todolist?</li><li>The audience wasn’t right (do people really buy things they’ve just found on Product Hunt? What is that conversion rate typically like)</li></ul><p>As much as I could have hypothesised and researched, I could have never truely known if that was the case without building and testing this.</p><p>The entire project at this stage took 10–12 hours from ideation to working product (spread out over a weekend).</p><h3>Learning</h3><p>Even though the initial launch didn’t lead to sales, here’s a couple of things I learnt from the experience:</p><ul><li>Knowledge on how to take advantage of tools like Shopify in a way to quickly build products</li><li>Improved knowledge of front-end JS. Especially some of the caveats around interactive experiences on mobile.</li><li>Discovered some potential niche’s where this concept would work well (weddings &amp; students doing summer projects being two). I now have a working product to test those markets</li><li>How to take advantage of customer feedback to improve the product</li></ul><p>I’m really interested in giving people the ability to create their own products by bringing together tools in perhaps unintended ways. Services like Printful are a great way to turn that concept into a business.</p><p>Like anything, I think building and releasing something is almost like a muscle that can be improved with constant practice, but it takes a lot of work before you can get to the point of having something to release.</p><p>Building something quickly lets you practice the actual launch, managing feedback and the realities of having an actual product vs something that will never see the light of day.</p><h3>Useful Resources</h3><p><a href="https://en.wikipedia.org/wiki/Krating_Daeng">Krating Daeng</a></p><p><a href="http://www.shopify.com/">Shopify</a></p><p>Sketch</p><p>Printful</p><p><a href="https://www.producthunt.com/posts/big-a-todo-list">Product Hunt</a></p><p><a href="https://www.reddit.com/r/sideproject">/r/sideproject</a></p><figure><a href="https://www.facebook.com/groups/ChatbotEcommerce/"><img alt="" src="https://cdn-images-1.medium.com/max/250/1*gSQyibBWA_11I6QdziE80g.png" /></a></figure><figure><a href="https://www.gobeyond.ai/"><img alt="" src="https://cdn-images-1.medium.com/max/250/1*2leowgACIyx6gUtjt_MgNA.png" /></a></figure><figure><a href="http://eepurl.com/dbDj79"><img alt="" src="https://cdn-images-1.medium.com/max/250/1*aJe18l1FW8mYp0wDkmsZHw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3709b684856" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gobeyond-ai/building-launching-a-web-app-in-24-hours-w-shopify-sketch-printful-3709b684856">Building &amp; Launching a project in &lt; 24 hours w/Shopify, Sketch &amp; Printful</a> was originally published in <a href="https://medium.com/gobeyond-ai">GoBeyond.AI: AI Agents and Automation Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Copterlist. My new sideproject to help you find cool drones]]></title>
            <link>https://joshbitossi.medium.com/building-copterlist-my-new-sideproject-to-help-you-find-cool-drones-8e7e8d4a63b2?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e7e8d4a63b2</guid>
            <category><![CDATA[quadcopter]]></category>
            <category><![CDATA[drones]]></category>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[digital-nomads]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Sun, 08 Apr 2018 11:49:54 GMT</pubDate>
            <atom:updated>2018-04-08T12:26:31.120Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*utbkeI2acpHWmztkNFKsiQ.jpeg" /><figcaption>www.copterlist.com</figcaption></figure><p>After building and selling a couple of projects last year, I needed something new to sync my teeth into. So this has been ongoing since Jan.</p><p><a href="https://www.copterlist.com/">Copterlist</a> is a completely custom tool that shows you the top drones on the market, lets you filter by things like price, type, brand, weight, speed and even if it has an app. It haves some cool features like a wishlist and price tracker and many more nice to haves in the works.</p><p>Basically, I wanted to buy a drone for someone and realised there are literally hundreds on the market now. That makes it hard to find the right one as a gift or to keep track of the latest. I knew there had to be a better way and I think the consumer drone space is only just starting to heat up.</p><p>Almost everyone I know has bought a small hobby/toy drone for themselves or a gift. And it’s telling that people with no photography experience don’t hesitate to spend $$$ on flying photography drones.</p><p>Side note: I’ve built this while working full-time and travelling (currently in Da Nang).</p><h3><strong>Data Collection</strong></h3><p>I knew this would be the most tedious process that would put me off. And since my time was limited I hired someone on Upwork.</p><p>I created a google sheet with the headers for data I wanted and gave them some guidelines on what I was looking for. Total cost was about $100 for most of the inital data (~100 drones).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R43uFOmDVV4wB1qNYD415Q.jpeg" /><figcaption>Lessons learned : define your expectations clearly, thoroughly check your results, make sure the data is easy to work with. More data = more work and can dirty up the data that’s actually important.</figcaption></figure><p>I’ve had to clean a lot of it up and continue to do so. But it helped fill out the site initially.</p><h3>Initial Build</h3><p>I had to fly return from Australia &gt; Canada for work in February…twice.</p><p>For me, these long flights are perfect for side projects because you have no internet connection. It’s a real test of programming skills and creativity since you focus on GSD with no outside distractions. If I see a new website I like I’ll want to change the design to match which I can ‘t do on a flight.</p><p>After these initial flights I had a basic version built up with basic filtering, data referencing and generic design.</p><h3>Refining</h3><p>It’s easy to buid a proof of concept. But refining it into a product is hard. I started ot get lost in scope and design creep. So decided to create some trello boards where I could keep track of what needed to be done vs nice to haves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BC257SlYhUjkM6d4jHgIxQ.jpeg" /><figcaption>What my development trello board looks like</figcaption></figure><p>I also started to set some timelines. I’m living in Vietnam for 6 weeks before going to Thailand this week and wanted to have it launched before then.</p><p>I wanted to have the filtering mostly done which is the core feature of the site, make sure it’s easy to use and build in some sticky features like wishlist and price updates that means people have a reason to come back or stay in touch.</p><h3>Monetisation</h3><p>Initially, Amazon affiliates. Eventually, I will link to individual drone resources and I’d like to start have the data more crowd sourced. Potentially leading to a nomad list style memberlist site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*huMQ1jxjJ-kzpWi8vFmJpg.jpeg" /></figure><p>The space still seems fairly open for a good Amazon driven drone resource. But I’m more interested in building a good tool and strong community first to see where that leads.</p><h3>Overall Tech Stack</h3><p>The site was all built from the ground up. Which took longer. But I prefer this approach for side projects. Since you only spend a few hours a day on it, it means the time spent doubles as time spent upskilling.</p><p>Basic tech things used is:</p><ul><li>Node.js with Express for Server</li><li>Hosted on Heroku</li><li>MongDB for database</li><li>Mailchimp for newsletter updates. Using the API for more dynamic list subscribing</li><li>Amazon API to make sure prices are up to date</li></ul><h3>Things I need to work on</h3><ul><li>mobile layout sucks (fixing this week)</li><li>advanced filtering — requires cleaning data a bit better</li><li>layout on secondary pages</li><li>Add more drones!!</li></ul><h3>Next Steps</h3><ul><li>Initial marketing and reach out</li><li>Add more drones</li><li>Better process for editing data</li><li>(maybe) introduce community aspect including community driven data</li><li>User reviews and classifying (how easy is this drone to fly? Would you buy this as a gift?)</li><li>Building out more dynamic pages. Ie see a list of other drones in that price/speed/weight range, generate dynamic pages that compare drone brands</li><li>List drone resources (if you have a site/guide let me know!)</li></ul><p>Thanks for reading! If you have thoughts or feedback I’d love to hear! And any questions happy to answer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e7e8d4a63b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m Going Remote..er]]></title>
            <link>https://joshbitossi.medium.com/im-going-remote-er-f504d575cfc?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/f504d575cfc</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[digital-nomads]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Fri, 22 Dec 2017 01:54:03 GMT</pubDate>
            <atom:updated>2017-12-22T01:55:17.609Z</atom:updated>
            <content:encoded><![CDATA[<h4>Experiments with working remotely for a big company.</h4><p>I’ve been working remotely full-time for over three-months, and part-time for years. Everyday I still discover new benefits not just for myself, but for the companies I work for.</p><p>For one, people are measured around results instead of clocking in &amp; out. It’s obviously still important to be building social connections on Slack and spending the right amount of time “at work”. But there’s days where I’ll start an hour later so I can get a coffee, and days where I’ll want to jump into work at 7am or keep going until well into the night. With the right goals and motivations there’s an impetus to just get work done that matters.</p><p>To have a team that can do that means there’s also a strong sense of trust and initiative in the people you work with, which makes for a lot of “getting shit done”.</p><p>But I think there’s still further benefits to being a remote worker that aren’t explored enough.</p><p>Professional benefits, like “How can I better understand customers in SE Asia” and “How do we bridge the black-hole of communication between employees in Australia and North America”.</p><p>There’s personal benefits to be discovered that focus more on how to best spend the other 16 hours of the day for personal growth and just generally getting the most out of life.</p><p>To that end, my partner and I are running a little experiment. We’re moving to SE Asia for a few months (to start) to try and discover some of the benefits and challenges. We’re lucky there’s such a thriving community of <em>nomads</em> that have laid the groundwork.</p><p>We’re looking for a chance to travel and experience other cultures while figuring out how remote work can really escape the constraints of a traditional working mentality to become it’s own thing. It’s how I would want to run my company and I’m very grateful to be <a href="https://www.shopify.com/careers">working for a company</a> that let’s me do this.</p><p>If you’re in Vietnam or Thailand from March, or have any tips I’d love to connect.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f504d575cfc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I’m working on in November]]></title>
            <link>https://joshbitossi.medium.com/what-im-working-on-in-november-3e4ffef27eb8?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e4ffef27eb8</guid>
            <category><![CDATA[instagram-marketing]]></category>
            <category><![CDATA[instagram]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Thu, 16 Nov 2017 08:19:31 GMT</pubDate>
            <atom:updated>2017-11-16T08:19:31.767Z</atom:updated>
            <content:encoded><![CDATA[<p>Here’s a brief summup on the things I’m focusing on this time of the year.</p><h3>BFCM</h3><p>Black Friday / Cyber Monday was a concept I was familiar with but didn’t fully grasp the important of until I started with Shopify Plus. It doesn’t seem to have as big an impact on Australia merchants but still lots of lessons to be learned in the lead up to Christmas sales.</p><h3>Ecommerce Workshop</h3><p>I held a 2 hour workshop at the University of Queensland IdeaHub incubator this month which was a new experience. I want to get better at facilitating events like this that allow people to experiment while still providing guidance and direction so I’m going over my notes from this event.</p><h3>New SaaS Product</h3><p>I’ve seen first hand how the fastest growing brands today are seeing huge success through Instagram marketing. These aren’t just teenagers selling clothes to their friends anymore, we’re talking brands with 500 million in annual revenue. Given this there is a severe lack in the quality of tools available for these brands. Most are all identical, just a thinly wrapped Facebook API wrapper.</p><p>I’ve been building something the last couple of months that will address this and want to have a working MVP before November end!</p><h3>Payment Gateways / Stripe</h3><p>I’ve wanted to use Stripe for almost a year now but could never justify the time to get everything set up when alternatives existed. Now that I have the above project to experiment with I finally have that chance. It’s fantastic how much control you can have with just the webhooks and a database and how easy it is. Payment gateway questions have also been a recurring theme with Shopify Plus merchants so it’s been a good opportunity to do a deep dive into that world for better context.</p><h3>Reading</h3><h4>Hitchikers Guide to the Galaxy &amp; Restaurant at the End of the Universe</h4><p>First is great and both some really subtle and non-subtle jabs. By the end of the second book it was getting a bit hard to keep reading.</p><h4>Engines of God</h4><p>Fantastic sci-fi read that feels like a constant cliff-hanger and too short.</p><h4>Remote</h4><p>Short but succinct book that perfect sums up the concept remote working. Great read, especially if you’re not working remotely in some capacity.</p><h4>Antifragile</h4><p>Fantastic book on building ideas/systems/governments that are the opposite of fragile. Meaning not just robust or resilient, but actually benefiting from chaos and disruption.</p><h4><a href="https://medium.com/@matt_11659/matt-barrie-australias-economy-is-a-house-of-cards-6877adb3fb2f?source=bookmarks---------0----------------">Australia’s Economy is a House of Cards</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e4ffef27eb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build your Community]]></title>
            <link>https://joshbitossi.medium.com/how-to-build-your-community-b75bfe30211f?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/b75bfe30211f</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[ecommerce]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Wed, 11 Oct 2017 00:03:43 GMT</pubDate>
            <atom:updated>2017-10-11T00:03:43.584Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IlPjl62PRdVNmn9HI2XSPw.jpeg" /><figcaption>Photo by <a href="https://medium.com/u/488a11cae523">Annie Spratt</a></figcaption></figure><p>I drew a lot of similarities between what Courtland said in his <a href="https://www.youtube.com/watch?v=HR4nKgDnPHs">recent Y Combinator interview</a>, and what I focused on when I was building <a href="https://www.builtwithshopify.com/">Built with Shopify</a>. Given BwS was intended to be a kind of Indie Hackers for eCommerce stores, and that I often looked to IH and Courtland as an example, this wasn’t particularly surprising.</p><p>Built with Shopify started out as a simple side project intended to help launch another SaaS idea I was working on. But after being featured on Product Hunt, it continued to grow and eventually was acquired ~six months after launching.</p><p>Built with Shopify showed me that a community can be an incredibly valuable thing. But there is no shortage of other great products that started with a community (Product Hunt, Scott’s Cheap Flights etc).</p><p>In his interview, Courtland gave some great tips for those who want to quickly build a lasting community around content, and I think his points are worth expanding upon a little deeper.</p><h3>1. Create a community around discussion, not answers.</h3><p>There’s a difference between topics that warrant discussion, and topics that just need an answer. Startups and business are a good example of topics that fall into the first category because there is never really one answer. Often the best way to discover the “least wrong” approach is to have a discussion with other people around content like the interviews here on Indie Hackers. Whereas the nitty gritty of taxes or domain registration are topics that usually have a more binary response.</p><p>With BwS I could have focused on specific aspects of eCommerce like drop shipping or app recommendations, but the purpose wasn’t to provide answers; I wanted to inspire other eCommerce entrepreneurs and show them real life examples that they could draw upon.</p><h3>2. Focus on a topic people love talking about.</h3><p>If you can nail number 1, you’ll find it’s much easier to create a community that values discussion. Topics that don’t have a clear answer will warrant varying opinions and approaches, which all lead to a healthy community.</p><h3>3. Don’t pinhole yourself.</h3><p>Communities are a melting pot of personalities and opinions so it’s impossible to know what people want to talk about . Your job is better spent providing content that sparks these discussions and being an active contributor to those discussions, rather than trying to define what should and should not be talked about.</p><p>This is particular true in the interview format on a site like Indie Hackers or Built with Shopify. The audience is so diverse that you want to focus on bringing out the best in the person you’re interviewing, not forcing them to talk about things they aren’t an expert in.</p><h3>4. Create a distinctive presence</h3><p>Like IH, I chose to create a custom website rather than relying on something like Medium or Wordpress. For me, that decision was about having the control to build unique features and not be reliant on any one system. This website was essentially my product, so I wanted to know it inside and out. As Courtland mentioned, it also makes working on the project a lot more fun, which keeps you motivated.</p><p>Courtland raised another great point. You’re not going to forget you’ve been on IndieHackers once you’ve been there. The colour is distinctive and the layout is unique. If you’ve subscribed to the IH email you’ll notice how unique it is as well. This uniqueness attracts good people who are interested in what you’re doing, and helps you stand out from the crowd.</p><p>Custom designs allow these kind of design choices and mean you aren’t reliant on your content alone to bring users back. It doesn’t have to be anything crazy. I based my design on a free HTML5 template and customized it until it fit what I had in mind.</p><h3>5. Have a Strategy to Continually Drive Traffic</h3><p>When BwS climbed up Ask HN and then Product Hunt, the traffic was great, but sustaining it for any more then even a few days is the hard part.</p><p>You have to be thinking about how you’ll keep bringing people in post-launch.</p><p>With the limited time I had to focus on BwS, I focused on creating great content around particular keywords (Shopify Examples). This was always my long-term strategy, to start organically ranking in search engines for terms like “jewellery store Shopify examples”.</p><p>Your acquisition strategy should be mapped out very early on. Will you be focusing on SEO or guest blogging? Where are your audience currently? How do you reach them?</p><p>I manually emailed every eCommerce founder I could find to request an interview at first. Even if I didn’t land the interview, there was a good chance they would check out the website and subscribe to the newsletter since their interests were aligned. This early traction helped to validate my approach and build up momentum.</p><h3>6. Build processes that scale</h3><p>Courtland talks about this in his interview as well. With every interview or piece of content you’re putting out, you should be looking at what similarities there were in the process to previous works you released.</p><p>For me, I learnt to rely heavily on Google Docs to rapidly create my interviews. This also meant that I could look back and see how I could improve upon my questioning with each interview. What questions had good responses? How could I rephrase for more in depth answers? It became a kind of A/B test for my interview questions and I could back it up with Google analytics and Hotjar data to see if it made a difference to engagement.</p><p>I remember with my first interviews I thought I would have a higher response rate by sending the full interview questions out to potential interviewees. I quickly realised very few would actually respond and even fewer would be great candidates, which meant I was wasting hours every week on interviews that would go nowhere.</p><p>From this I learnt how to vet my candidates. This gave me more time to spend my time more efficiently to create higher-quality interviews for the people I knew had a much higher chance of completing their interview.</p><h3>7. Leverage your Existing Resources</h3><p>Just as Indie Hackers is doing with their forum, I started experimenting with new tools that would provide greater community engagement.</p><p>I already had data on what Shopify apps people were using, so I created a ranking system of how often these were mentioned. This brought in a new crowd of people looking for app recommendations to achieve a specific feature, as well as developers who were interested in getting their app listed.</p><p>As everything on the site was running off JSON, putting this together was super simple. I’d always encourage people starting a community or content site to collect data from the get go about things their audience might be interested in and make sure this data is accessible.</p><h3>8. Stay Consistent</h3><p>This is probably the hardest part in the early days of starting a community. It can be really hard to stay consistent with the content you’re creating, especially if you don’t have a clear monetisation strategy in mind.</p><p>This is a problem. People come to rely on this consistency. I remember checking Indie Hackers every other day when it first started because I knew there would be fresh content. Now I’m still an avid reader more than a year on.</p><p>I found it important to set a metaphorical finish-line of at least six months where I could evaluate where the site was at and determine if the audience was still there and growing. To do this I had to have specific goals in mind that would keep me motivated until I reached this point.</p><p>Day-to-day, finding ways to automate your processes, batching tasks like sending out interview requests, and finding ways to make the mundane interesting (another reason for a custom-site build), helped me stay focused.</p><p>Having built SaaS applications as well, I was surprised at how valuable my community became . It was difficult to monetise initially, but quickly led to big opportunities. That’s why I’d recommend to anyone looking to build a SaaS product to start experimenting with a community or content based product first. Worst case, no one bites and you get a real sense of how hard it will be to actually sell a product in this space, without the investment.</p><p>I’m no longer affiliated with Built with Shopify, but I’d definitely encourage you to <a href="https://www.builtwithshopify.com/">check it out</a> if you are interested in eCommerce. Right now I write on <a href="https://medium.com/@joshbitossi">Medium</a> about my own SaaS experiences and how I help other entrepreneurs launch their stores at Shopify Plus. You’ll also see me around the Indie Hacker forums.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b75bfe30211f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why is Starting an eCommerce Business Harder than SaaS?]]></title>
            <link>https://joshbitossi.medium.com/why-is-starting-an-ecommerce-business-harder-than-saas-2836683cee76?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/2836683cee76</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[shopify]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Tue, 19 Sep 2017 20:54:45 GMT</pubDate>
            <atom:updated>2017-09-19T20:54:45.614Z</atom:updated>
            <content:encoded><![CDATA[<p>The last couple of weeks since starting with Shopify Plus, I’ve been thinking a lot about how I could get involved in the world of eCommerce by starting my own online store.</p><p>As well as just making sense to take advantage of the resources and encouragement provided by Shopify, I want to properly understand what it’s like to start and run an eCommerce business from all perspectives.</p><p>But more importantly, I think it is such an amazing channel to begin selling and their are some fantastic opportunities.</p><p>So why then is it so hard to commit to the right opportunity?</p><p>Maybe you don’t have this problem (and if you don’t lets talk), but I think the approach to finding good eCommerce ideas differs to SaaS, and for me, it’s much harder.</p><p>James Altucher used to always talk about the “<a href="http://www.jamesaltucher.com/2014/05/the-ultimate-guide-for-becoming-an-idea-machine/">Idea Muscle</a>”. When you’re looking for SaaS ideas, you are constantly finding problems that can be solved by software. It’s then relatively straight forward to get a rough idea behind the market and value behind it. You’re constantly building up that idea muscle which in turn helps you find better ideas faster.</p><p>With eCommerce, it seems I’m constantly trying to figure out the market first. “How many people would be willing to buy this”. But the really successful companies seem have to a deep understanding of your customers needs. To do this, you have to be involved in the product and industry the same way your customers are.</p><p>I think this problem is compounded by the resources required to start an eCommerce store. In SaaS you can usually spin up a basic MVP and scale it out. With eCommerce, committing to an idea means buying products, branding and a website.</p><p>I have a new admiration for people who start a clothing line. With software you know there is a problem to be solved, but how can you do that with a clothing label?</p><p>If you’ve worked in both industries I’d love to hear your thoughts. Maybe there are a lot more similarities that I’m missing? Did you face the same challenges when formulating your business?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2836683cee76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Built a Shopify App MVP and Got my First Customers.]]></title>
            <link>https://medium.com/ecommerce-magazine/how-i-built-a-shopify-app-mvp-and-got-my-first-customers-750f075cf983?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/750f075cf983</guid>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[web-apps]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[shopify]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Mon, 04 Sep 2017 16:09:52 GMT</pubDate>
            <atom:updated>2017-09-30T01:10:58.484Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VaLXoygWcjz_dRPM-AoeZw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/cqkbESEkhjk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mia Baker</a></figcaption></figure><p>Working with eCommerce stores and helping people to launch their own stores, I was constantly noticing problems came up that couldn’t be addressed by Shopify’s features out of the box.</p><p>As I became more adept at solving these problems with code, I decided this year was the right time to jump into launching a Shopify app that could address a problem that I knew existed for many merchants.</p><p>As more and more retail stores also adopt an online store, In store pickup is becoming an almost mandatory feature. I wanted to create a (slightly) less hacky solution that would allow any size Shopify store to offer their customers the ability to pick up their products in store.</p><p>In my first month I had a growing list of 30 paying customers signed up, just from being listed in the App Store. Not a life-changing amount, but it also required almost no work after the first couple of weeks unless I was working on new features.</p><p>But developing apps for Shopify stores isn’t necessarily the most straight forward process if you’re a beginner-intermediate developer. There can be a lot of moving pieces and it can be hard to find information about them all. And that isn’t necessarily a bad thing, nobody wants beginner level, error-prone software integrated into their business.</p><p>I spent a lot of my time just researching and understanding the Shopify ecosystem and I wanted to make that process a bit easier for anyone who is interested in developing Shopify apps themselves.</p><p>So this is my own summary of how to get started Building Shopify apps and some of the things you’ll need to consider.</p><p>Keep in mind, I created by app using Node.js and there are inevitably going to mistakes and things that aren’t best practice here. I always welcome criticisms and comments.</p><p>*<strong>Disclaimer</strong>:* I’ve since join the Shopify Plus team and should note that all of the opinions and suggestions are my own and were penned before I started working with them. Everything here was made with publicly available info (aside from some of my app figures).</p><h3>Why build Shopify Apps?</h3><p>There are over 500,000 merchants on the Shopify platform, and the average store <a href="https://www.shopifyandyou.com/blogs/news/statistics-about-shopify">has 4 apps installed</a>(most I have worked with have many more). Apps integrate seamlessly with your store, customizing it to suit almost any needs.</p><p>For me the reason is pretty simple, the goal of apps is to help merchants make more money. If you follow that one principle then building and selling your app should be easy…right?</p><p>There is also a <a href="https://www.apps.shopify.com/">dedicated marketplace</a> where users can safely browse for plugins which makes discovery a lot easier. For me, the marketplace is perfect. It provides a healthy supply of B2B customers, always looking for new tools to help create or improve their business. But it also utilises a more B2C model that helps people find the best possible software.</p><p>Shopify provides many great resources like the app store and <a href="https://developers.shopify.com/">developer portal</a>, but there are still a bunch of roadblocks I ran into. Some of these were a result of developing for the Shopify platform, such as the limitations put in place to ensure a smooth checkout process (not that this is a bad thing). Others were just down to my inexperience in building a fully functioning SaaS product.</p><h3>3 Criteria for defining your Idea</h3><p>Honestly, if you want to make money with your Shopify app here’s the three things to do:<br>1. Find a Shopify store<br>2. Find a problem they would pay money to have fixed<br>3. Make sure there aren’t a tonne of solutions already in the App Store</p><p>That’s really it. There are so many amazing ideas that could be made, but if you’re just getting started and want to start making money with Shopify apps, then that’s the criteria you should follow. Focus on creating a solution to a problem that a good number of people will pay to fix.</p><p>For me, I was working in an eCommerce store (<strong>point 1</strong>) that needed to offer in store pickups (<strong>point 2</strong>) and there was only one solution available (<strong>point 3</strong>).</p><p>While there was a similar app that looked fantastic and could have achieved something like what we needed, it was just too expensive and didn’t have quite enough of the features we needed.</p><p>If I was just a manager, I probably would have found a way to make it work, but I saw an opportunity to make something better suited to our needs and believed there would be similar stores with similar needs.</p><p>Remember, there’s over 500,000 Shopify stores now across just about every conceivable industry and business model. If there is only one or two existing apps, chances are there is still an area that they aren’t addressing.</p><h3>MVP</h3><p>Building an MVP for Shopify apps can be hard. You want to offer a minimum set of features, but you also have to be incredibly mindful that your mistakes could cost the store owner sales.</p><p>Again, my advice is to find a store to work with. There’s really no better way. Maybe that is through a beta program or maybe they’ll let you work on their store in exchange for some development help in their own store or free access to your app.</p><p><strong>Why is this so important?</strong></p><p>1. If a store lets you in, it validates that they don’t completely hate your idea/you<br>2. It exposes you to real customers with real risk</p><p>My store pickup app begin as a simple checkbox on the cart page. The customer to check to say if they wanted to pick up their order. But after testing it internally I started to realise all of the other features we would need to make this viable. If I had just built this for my own test store, there’s a good chance I would have missed a lot of these requirements.</p><p>This was compounded when we began testing it with actual customers. They would approach us with constant feature requests, bug reports, praise and complains. There was a certain element of pressure to make sure I was improving as fast as possible, but it made clear what features were really important.</p><p>So for your MVP:<br>* Define what the app should achieve<br>* Focus on the features that help you achieve this<br>* Make it robust enough to test with real customers</p><p>I knew that we had to offer store pickups that could collect extra information and integrate with shipping rates (*point 1*), that we had to include a certain number of features to cover all the use cases (*point 2*) and that it was already working with real customers (*point 3*).</p><h3>Pick your Programming Stack</h3><p>Shopify is fairly flexible with the language and tools you can use thanks to their API. But there are still a few decisions you’ll need to make about your technology stack. Here are the components of stack and why I chose them.</p><h4>Node.js with Express for the Server</h4><p>Shopify definitely favours Ruby on Rails. You’ll have a greater range of support and access to more libraries if it’s your language of choice.</p><p>That being said, I developed my app using Node.js &amp; Express and ran into very few issues thanks to Shopify’s robust API that isn’t language dependent.</p><p>Aside from just being most familiar with Node.js, I’ve found it works fast and also empowers me to build things quickly and in a way that is easy to understand.</p><h4>MongoDB for the Database</h4><p>I chose MongoDB for a few basic reasons:<br>1. I’ve used it successfully in other projects<br>2. It uses JSON which makes reading and writing with a Node application super easy.<br>3. It’s quick and easy to integrate with Heroku</p><h4>EJS for the Templating Language</h4><p>EJS is a templating language that lets you load HTML files with variables you can pass in. As my app had some features that impacted the front end, this meant I could swap out different settings depending on the user’s settings.</p><h4>Heroku for Hosting</h4><p>You’ll need some kind of server to run the application. I choose to use Heroku for the following reason:<br>* It’s easy to set up with a solid command line toolkit<br>* They have a generous hobby tier that’s great for testing new ideas<br>* Lots of integrations for testing, databases, monitoring etc<br>* It can scale up and gives provides basic monitoring out of the box</p><h4>Other Stuff</h4><p>You’ll also likely need to know a good amount of HTML, CSS, Javascript and Liquid.</p><p>Liquid is the templating language used in Shopify themes. You can include some logic in Liquid (such as for loops), but that page will be rendered as a static HTML file so you can’t change liquid variables on the fly.</p><p>If you’re appending anything to the store front itself like I did, you’ll need a decent understanding of Javascript and jQuery.</p><p>If you have an argument for better solutions for my next project I’ld love to hear it, but these seemed to work great for my purposes.</p><h3>You’re building your app <em>within</em> Shopify</h3><p>This means a couple of things. One, your app is essentially embedded in the Shopify admin using the <a href="https://help.shopify.com/api/sdks/shopify-apps/embedded-app-sdk">embedded SDK</a>. What this means is that your app is embedded within the Shopify admin, which makes the user experience much nicer and gives you access to the Window Api call so you can show dialogue boxes etc.</p><p>To make this happen, you’ll probably load each page of your app’s page with something like:</p><p>```<br>&lt;script type=”text/javascript”&gt;<br> ShopifyApp.init({<br> apiKey: ‘&lt;%= api_key %&gt;’,<br> shopOrigin: ‘https://&lt;%= shop %&gt;’,<br> });<br> &lt;/script&gt;<br>```</p><p>So that it can initiate the Shopi</p><p>(<strong>NOTE</strong>: <a href="https://polaris.shopify.com/">Polaris</a> is now the preferred method of developing apps, so some of this info is probably out of date.)</p><h3>Charging Customers with the Shopify Billing API</h3><p>Building within Shopify means you’re also going to have to use the Shopify Billing API to charge customers. Thankfully it’s pretty easy to do. Essentially the Billing API flow goes like:</p><p>1. User installs the App and is redirect to the billing page. You can check here to see if the app is already installed or not<br>2. User accepts/declines the billing charge which provides a token<br>3. You activate the billing charge utilising that token</p><p>It’s pretty straight forward, just make sure you activate the billing charges after they have been accepted!</p><p>There are a <a href="https://help.shopify.com/api/charging-for-your-app">number of ways</a> you can charge for apps:<br>- A one off application charge<br>- A monthly recurring charge<br>- A usage charge depending on how much your app is used</p><h3>Authorising your Shopify App</h3><p>If you want to interact with a merchants store in any way, you’ll need to authorise your Shopify app.</p><p>If you’re familiar with OAuth, then this process will be fairly straight forward. But this is a basic overview of how my authorisation process looks:</p><p>1. User clicks install button from the App Store<br>2. Show the “Install Application” page. Often the “embedded_app_redirect”. Here you’ll need to pass in your app_scope, api_key generated in the Shopify partner dashboard and the redirect URI where the user will be redirected after authorising. This is usually where you’ll generate your access token (to make API calls) and create your application charge JSON.<br>3. Show the app charge page using the JSON created earlier. Here the user can accept or decline the charge. Make sure you’re also storing the token provided by Shopiy somewhere so you can make API calls.<br>4. If the charge is accepted, activate the charge.</p><h4>Including your Scripts</h4><p>Most of the apps I’ve seen and worked with have to have some amount of code added to the merchants Shopify store in order to work.</p><p>This is usually done through the use of an {% include %} snippet.</p><p>Basically when your app is first installed (or at some other point in your onboarding process) you will use the Shopify API to PUT a file into merchants theme assets by sending a PUT request to:</p><p><a href="https://&/#39;">https://</a> {shop-name.myshopify.com}/admin/themes/{theme-id}/assets.json</p><p>with your content as the body of the request.</p><h3>Every Shopify Store is Different</h3><p>My app required adding a javascript snippet to the cart page. This wasn’t a very big challenge to do for one store, but consider that there are dozens of Shopify themes using various versions of jQuery etc, and many have multiple other plugins.</p><p>To overcome this, you’ll want to make sure you can test out your app on as many stores as possible before you go live.</p><p>You may find that you have to check which version of jQuery is installed, or include certain libraries for older themes. For example I had to manually include a date validation library.</p><p>This is another reason why beta testers (or patient early customers) are crucial. They’ll quickly point out the errors and flaws in your product and find bugs you would never think of. If you’re a small team, you need to utilise your customer feedback and experiences to move exponentially faster than trying to figure everything out for yourself.</p><p>Putting out an “MVP” also forces you to be incredibly responsive and move quickly to address customer concerns, so be prepared for that.</p><h3>How are you going to customize your app for customers?</h3><p>Almost inevitably, people are going to want to customize your app in someway to suit their store, especially if it is actually displayed anywhere in their storefront.</p><p>For the store pickup app, customers wanted the ability to make certain fields required or hidden, and change the date range that customers could pick up their order.</p><p>You need to be mindful of what features to include in your MVP. I found that I could develop the features I found to be important and my early customers were all too happy to share with me the features that they needed in their store.</p><p>By approach to customization was to create a dashboard where users can edit the functionality settings themselves. While I can’t customize the actual code running the app for each user, I did sneak in a section that detects if the user has custom CSS enabled. If it does it looks for the custom CSS file.</p><p>This means I can customize the styling for stores individually. But it also opens up opportunities to upsell this feature easily in the future.</p><h3>What happens when users uninstall?</h3><p>One of the most common complaints you’ll see on user reviews is how difficult the app is to uninstall. If users aren’t sure how easy the app will be to setup and uninstall, they will be more hesitant to try it.</p><p>You want to create some kind of abstraction layer between your code and the main shop code. When the user uninstalls the app from the dashboard, you lose your token, which means you also lose the ability to remove files.</p><p>Using a simple line of code like {% include ‘app-snippet’ %} is the obvious way to do things and makes it easy for the user to uninstall the app.</p><p>I also wanted to protect from savvier store owners from copying aspects of the code that was added to their store and then uninstalling the app. There are certainly better ways to do this, but for my initial version I created a simple database check that would return if the store still had the app installed or not.</p><h3>Onboarding</h3><p>It can be useful to map out your customers journey. What happens when they install? What pages do they first visit? You should design this so emails can be sent automatically at an optimal time (using something like the MailChimp API or send grid).</p><p>But for your first few customers, I found their was a lot of value in sending out more personalised emails to your first few customers. Before sending the email I could take a look at the store to see if the app was functioning perfectly and craft a more suitable email. This helped uncover some of the issues customers were having and led to several recovered customers.</p><p>You should look to send emails when:<br>1. <strong>The customer first installs the app</strong> — send them a welcome email with a link to install instructions and FAQ<br>2. <strong>Incomplete install</strong> — what stage of the install did they get to? Was there a specific reason or error that stopped them? You can check this by looking at the Shopify partner dashboard or by checking if the store has not made any server requests.<br>3. <strong>Customers who uninstall the app quickly</strong> — was there a feature missing?<br>4. <strong>Customer who uninstall before the free trial</strong></p><h3>Support and Documentation</h3><p>One thing you’ll need to make sure you cover is thorough documentation It’s actually a requirement for listing your app that you have a good amount of documentation available for your new users. You documentation should cover</p><ul><li><strong>How to install the app</strong> — this should be written for layman. Expect that they are new to the shoplift platform and aren’t familiar with code. Screenshots and videos go a long way.</li><li><strong>What your app does</strong></li><li><strong>How your app works</strong></li><li><strong>How to add any extra features or customizations</strong></li><li><strong>Troubleshooting</strong>— what are some common issues and how do you resolve?</li><li><strong>Uninstalling</strong> — Make sure it is easy to install</li></ul><p>Other than that, Shopify covers the images and requirements they have for your listing fairly comprehensively. You’ll need to create various images such as your icon and banner images .Using a tool like <a href="https://www.canva.com/">Canva</a> can make creating and managing your images quite simple.</p><p>You’ll also need to adhere to certain requirements when writing your app listing which are fairly straight forward (don’t make unsubstantiated claims, don’t align yourself with Shopify itself etc).</p><h3>Create a Test Store for Potential Customers</h3><p>An extra thing you should create for your store is to create a test or dummy store. Having a dummy store where users can go and test out your app is one of the best things you can do for conversions. I learnt how much of an impact it can have the hard way.</p><p>After a couple weeks of downloads trickling in, I noticed a sudden stop. It was only after a customer emailed me about a support issue and I went to refer them to the demo site, that I realised the store wasn’t working.</p><p>I checked Google Analytics and sure enough, nearly a quarter of the people who visited our app store listing, also visited the demo site.</p><p>If you’re creating a Shopify app, you need to have a demo site.</p><p>It will help customers experience your ap, and gives you an insight to how it functions from their perspective.</p><p>If you want to show customers how the app looks like from within the Shopify admin, you can create a fake staff account for them to use.</p><h3>Useful Resources (ongoing)</h3><p><a href="http://www.uptowncss.com/">Uptown CSS</a>] — The team at Shoppad made this awesome CSS library that makes styling your elements to look like native shopify super easy.</p><p><a href="https://www.canva.com/">Canva</a> — An easy to use graphic design program that is great for simple images.</p><p>(let me know in the comments what other tools have been useful for you)</p><h3>Wrapping Up</h3><p>As fate would have it, I’ve been lucky enough to join the Shopify Plus team where I’ll be helping stores continue their success on the Shopify platform. Unfortunately that means I won’t be actively involved in this app anymore, but hopefully the lessons I learned will help someone else along the way.</p><p>If there’s aspects of the actual development you’d like me to cover or discuss, leave a comment or send me a message anytime.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=750f075cf983" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ecommerce-magazine/how-i-built-a-shopify-app-mvp-and-got-my-first-customers-750f075cf983">How I Built a Shopify App MVP and Got my First Customers.</a> was originally published in <a href="https://medium.com/ecommerce-magazine">Ecommerce Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Ways I Ensure my Side Projects Can Go the Distance]]></title>
            <link>https://joshbitossi.medium.com/4-ways-i-ensure-my-side-projects-can-go-the-distance-8fc6e9eb5a62?source=rss-12e0dc5ed0ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fc6e9eb5a62</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[shopify]]></category>
            <dc:creator><![CDATA[Josh Bitossi]]></dc:creator>
            <pubDate>Sun, 03 Sep 2017 02:22:40 GMT</pubDate>
            <atom:updated>2017-09-03T08:41:16.973Z</atom:updated>
            <content:encoded><![CDATA[<p>My first project in 2017 was acquired in ~6 months, led to an awesome job offer and helped me build out a more successful product at the same time.</p><p>But I spent all of 2016 grasping at straws, trying to find projects I was interested in while simultaneously trying to learn the tech skills needed to be able to build out my own semblance of an MVP.</p><p>This is a lesson to myself on how to ensure the next project I build can go the distance to achieve the results I want.</p><h3>2016</h3><p>I was slowly making progress towards creating my own successful side-project/startup. I decided at the beginning of 2016 I wanted to focus on the Rental Real Estate industry here in Australia. It was an industry that impacted almost everyone I knew and after speaking to dozens of customers and agents I knew there were problems to be fixed. Plus I didn’t really know much about the industry so I knew I could learn a lot along the way.</p><p>Aside from some great practical coding experience with Node.js and chatbots (remember those), a brief stint in an accelerator and valuable connections, my efforts did land me a spot on a startup mission to Shanghai, where I got to spend a month working with an awesome <a href="https://propertypassbook.com/">real estate startup</a> there and experience the local culture and investor scene.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ESTpJFRuHWXJMNz6kyIEQ.jpeg" /><figcaption>(Me on the far left)</figcaption></figure><p>It sounds cliché, but when you’re working in a city with a population greater than your entire country, it definitely broadens your horizons as to what’s possible. In Shanghai I got to experience what it was like to be a small part of a team trying to build something big, and it made me even more eager to start building my own product.</p><p>But soon after I returned I realised it was all becoming very forced. Real Estate still needs to be shaken up, but it wasn’t going to be me, I knew there were much lower hanging fruit.</p><p>I made a decision to start focusing on creating solutions for eCommerce merchants. I had been working in eCommerce for ~4 years and knew there were plenty of problems to solve. Which leads me to my first point:</p><p><strong>1. Find an industry and project you’re passionate about.</strong></p><p>This is your side project after all. If you’re going to be working on it in your spare time, it should be in an industry that you enjoy learning more about.</p><p>So for me, that was eCommerce. I was excited about how quickly it was growing, I loved how it was enabling new forms of commerce to arise and how quickly it could iterate on new ideas compared to old methods. But I mainly just found it cool how it gave thousands of small entrepreneurs the power to create their own business.</p><p>I knew I wanted to build a SaaS product utilising the Shopify App Store, but I was still finding my feet, and didn’t know exactly what problem I wanted to focus on.</p><p><strong>2. If you can’t decide, narrow in on a vertical</strong></p><p>I didn’t know what I wanted to build, so in the mean time I launched a website called Built with Shopify. Inspired by Indiehackers, I wanted to interview other eCommerce stores to learn about how they started, what they were working on and what problems they faced.</p><p>Because this project was in a space I wanted to be in long term, it gave me four harmonious benefits:</p><p>1. It let me learn about the problems my customers were having<br>2. It let me build an audience for my future products<br>3. It gave me a testing ground for new ideas<br>4. Everything I learnt building this website could be applied to future projects</p><p>All of those points turned out to be incredibly valuable. I got to do real customer validation and create a detailed profile of what eCommerce merchants look like. I quickly started building up an email list of customers and even learnt how I could use the website to launch products when I launched a <a href="https://chrome.google.com/webstore/detail/shopify-quick-edit/jcihcelmeafpcclfeepablppinbjahbn?hl=en">simple Chrome Extensions</a>.</p><p>There’s a problem that many people seem to face, and I wouldn’t even call it analysis paralysis because I don’t think most people get to that stage. They get stuck thinking about an idea and then jump ship completely and lose all their progress if they don’t have a certain skillset. I was guilty of the same thing, so I decided if I was going to start over, I wanted to make sure I had still gained some valuable insight into the industry.</p><p>Thankfully, after being <a href="https://www.producthunt.com/posts/built-with-shopify">hunted</a> I made more progress in the first couple of months with this project than anything else I did in the Real Estate industry. I was a much more experienced developer, but I was also working on problems that I felt much stronger about and could relate to. Which is what my third point is about:</p><p><strong>3. You should have a natural inclination to the project</strong></p><p>This might sound similar to “be passionate”, but to me when I’m starting a side-project one of the most important criteria is also how well suited I am to the project.</p><p>I’m super passionate about blues music and space, but I have no real inclination to start a side-project in either.</p><p>For me, the ideal projects lie in the intersection between what I’m good at and the fields I’m interested in (like eCommerce). Finding projects here means I can work on problems that interest me, while knowing I have the skills to overcome the roadblocks that can quickly kill a side project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Esj9lKiOEqJIkoh1di6vZA.png" /></figure><p>But try as you might, a side-project can usually only sustain itself for so long and unfortunately that period is often shorter than the time it takes to start seeing a commensurate amount of value (whether that is revenue or otherwise). Which brings us to point four.</p><p><strong>4. Have an exit strategy</strong></p><p>“Exit strategy” might be a bit too narrow in this case, what it really translates to is “make sure you know what you want to get out of it, how you’re going to do it and at what point you jump ship”.</p><p>I had two different type of milestones that I would want to reach.</p><p>The first were development milestones, i.e “I want to be able to build X feature”. These were super important when there wasn’t a lot of revenue or traffic because it gave me tangible goals to work towards for my own personal development and I loved working on new features.</p><p>The second were more tangible. Every now and then I would have content partnerships come up or some spikes in traffic that would give a nice little boost of confidence and these always required a bit of work to reach.</p><p>I also had clear strategies for how I wanted to earn a small amount of revenue from the site and how I could grow this revenue. Eventually it started matching the time I had to put in to the site which made it somewhat sustainable at which point the focus shifted to “what do I focus on to grow this further”.</p><p>I knew at a few stages whether or not this project was something I wanted to keep going. Initially after I had spent some time getting my first 15 interviews, I wanted to see how well it did on Product Hunt. The success helped me validate the idea and keep going. From there it was a bit trickier, I knew it would take some time to get to the point I wanted but I constantly evaluated whether this was the best use of my time and if the growth was still strong.</p><p>But you also have to be open to bigger possibilities. Side projects often revolve around the risky ideas that can be tricky to find the value in. But if they pan out, they can become incredibly valuable to businesses that don’t want to take on that initial risk themselves.</p><p>I made sure to always talk to other people in the industry which led to some great partnerships and eventually an acquisition with my ideal buyer.</p><p>Being able to maintain my side project, even for just the 6–7 months it was active also led me to Shopify, where I’m now working as a Launch Manager for Shopify Plus merchants.</p><p>I’ll be writing more about specific parts of this journey, my other side-projects, my time at Shopify and more. If you’re reading this and there are things you’d like me to dive deeper into, leave a comment or send me a message :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fc6e9eb5a62" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>