It was a Sinatra app for a while, and later I switched to Ruby on Rails 3. As the years went on I kept the codebase up-to-date by upgrading anytime a major new Rails version came out. (Running on Ruby on Rails 7 now with the Hotwire goodness.)

I played with the idea of moving away from Heroku for a while. For a few reasons. The most concrete reason being costs, but I also felt like their product development stalled the last few years and although I’ve had some good experiences with their support team, overall the company seemed more interested in serving huge enterprise clients rather than a startup like my own.

At one point one of their sales reps called me (still not sure how they got my phone number) and repeatedly emailed me trying to upsell me on a $1,400/mo Enterprise plan with a 12-month commitment. I guess someone needed to hit their quota 😅

Render

Because of these reasons I’ve been exploring alternatives. I briefly tried self-hosting with one app, but when the server randomly went down one night because my logfiles filled up the disk (apparently they don’t automatically get deleted?), I realized I don’t want to play devops engineer.

I ultimately settled on Render. They provide a similar “Devops done for you” product as Heroku at a more reasonable price point, the product is actively developed, and the team seems more in touch with their customers. Not just the enterprise ones.

Over the past year, I’ve been migrating all of my apps from Heroku to Render. First some smaller apps, and eventually some of my bigger sites like Startup Jobs. Since many makers are curious about switching to Render, I figured it would be valuable to document one of those migrations for others to benefit from.

I recently switched BetaList to Render as well and documented my approach below. I’ll also share some of the unexpected issues I ran into, and explain how I solved them.

Previous Heroku stack

• Rails 7.0.4 / Ruby 3.1.2
• Web dyno ($50/mo)
• Worker dyno for Sidekiq background jobs ($25/mo)
• Postgres ($50/mo)
• Redis (for caching and Sidekiq background jobs) ($25/mo)
• Scheduler ($5/mo)
• Adapt Scale for scaling up/down web workers ($18/mo)

On average I was paying around $175/mo at Heroku for BetaList. Not horrible, but if you run multiple sites like I do this will start to add up.

The migration process

Here’s roughly how I approached the switch:

1. Deploy a few smaller apps on Render.

2. Prepare the BetaList codebase.

3. Deploy a test version to Render.

4. Import (sanitized) production data.

5. Migrate for real.

1. Migrate a few smaller apps

Before migrating, I got familiar with Render and render.yaml. Rather than configuring everything through the dashboard (which is still possible as well), you can write a document as part of your codebase that defines which services to use, etc. It’s one of my favorite features.

You spend a lot of time configuring your servers, etc. so it’s nice to have a concrete copy of all that work. It makes it easier to experiment as well as you can always revert. Plus, you can easily copy your server setup between projects.

2. Preparing the codebase

Good preparation can save a bunch of work. I started by moving all of my API keys and other sensitive data from environment variables to the more portable Rails Credentials. I also backed up my config variables with this just to be safe. (Don’t commit this file to your git repository).

If you’re anything like me, you’ll see a multitude of opportunities to clean up. To streamline the design. Remove unused assets. Refactor that piece of code you wrote late last night.

Don’t.

Early on when building your startup, chaos is your friend. That mess of an HTML template? It reminds you it’s okay to be scrappy. The customer won’t mind. Making that border radius consistent with the rest can wait. It’s okay.

Enjoy the moment. Pretty soon you’ll have your structure. You’ll have a working product. And better yet, customers!

But this comes at a price. Rigidity. Changes will be harder to make. Bugs more costly. You’ll long for the chaos. Back when anything was possible.

Embrace the chaos… while you still can.

This is excellent advice for carpentry and working with physical objects. But, when it comes to building startups, I’ve come to realize it’s usually faster to “measure once, cut twice”.

You often don’t know yet exactly what you’re making. You’re figuring it out as you go along. The first cut lets you try out an idea. The second cut makes it right.

So next time you’re starting a new project, don’t spend too much time planning. Just start hacking away and see what you come up with. It’s usually faster and more effective than trying to plan everything out in advance.

Measure once, cut twice.

I’ve always been fascinated by seeing creative people work their craft. I don’t just want to see the finished product. I’d like to see the progress that got them there.

That’s why I make products like BetaList (discover startups in their early stages) and WIP (community of makers sharing their work in progress).

Over the last couple of years, the concept of “building in public” has become mainstream. People no longer wait to show off their project when it’s finished. Instead, they start sharing their progress from day one. It’s a great way to meet other makers, stay motivated, get early feedback, and build an audience.

A lot of people now build in public on Twitter. To connect, they use the hashtag #buildinpublic. Unfortunately, there wasn’t a great way to explore all these tweets and makers. Until now…

Introducing buildinpublic.com 🚀

A place to explore all the #buildinpublic tweets and see what everyone is working on.

Have a look and maybe give building in public a try yourself. Just post a tweet with the #buildinpublic hashtag and it will automatically show up on the site!

It’s also live on Product Hunt and BetaList, so if you’ve got an account there, your support would be appreciated! Looking forward to your feedback and #buildinpublic updates!

Continue reading for the full story on how I validated the idea, built a simple product, grew it to thousands of active users, tried monetizing it, and eventually sold it.

📝 Blog post as an MVP

People always tell you: start with an MVP, prove there’s demand for your product before investing all your time into something nobody wants. In my experience that’s good advice, but it seems many successful products often start out as accidental MVPs. Tweet Photo is a perfect example of this.

If you’ve ever tried posting an Instagram photo to Twitter, you might have noticed it looks like this:

Just a link. No photo. Useless. I don’t know the politics behind this, but I believe Facebook is the one that disabled the photo previews at some point. So now we’re stuck with useless tweets.

You can find many workarounds using automation services like IFTTT and Zapier. Because I was unhappy with all solutions, I decided to write my own article in May 2017:

A better way to post your Instagram photos to Twitter

Turns out I struck a chord. To this date that post has been read 70,000 times. Over three years later it continues to get over a thousand hits per month.

If you read the post though, you will notice how complicated the setup is. So I figured there might be an opportunity for a product here. I knew there was interest, but I didn’t know if I could monetize it.

It wasn’t until Yuko posted this question on WIP:

She mentioned she’d happily pay $20/mo for Zapier to tweet her photos. That got me thinking: maybe it’s a product that can be monetized after all. Plus, I already got the leads coming in via the blog post. I could funnel them through to this new service instead.

Rather than further validating the business model, I challenged myself to build a prototype over the next couple of days.

🛠 Building the Product

I believe in using the tools you’re familiar with, so I used Ruby on Rails to build the product.

Tweet Photo is technically quite simple. I’m basically gluing together the Instagram and Twitter APIs. I was able to do most of the work with open-source libraries.

I finished the product in just over a week during my spare time.

I initially went with the tweetphoto.icu domain name because it was only $1. That’s how much faith I had in the product I guess. But shortly after I decided if I’m going to do this, I might as well do it right and purchased tweet.photo for $130. It might not seem like a lot of money, but with all the projects I start things start to add up 😅. In hindsight I’m really glad I got this domain name…

I wouldn’t realize it until later, but the key feature I added was appending “via tweet.photo” to every tweet. This single piece of text would prove to be the driving factor of Tweet Photo’s growth.

🚀 Time to launch

December 12th, 2018, 11 days after Yuko’s post, I launched:

It got featured on BetaList (although no surprise here, as I’m the founder of BetaList) and Product Hunt.

At the end of the launch day over 100 accounts were created with a combined total of over 100 published tweets.

The product worked! 🥳

📈 Growth

As time went on the userbase continued growing.

Unlike most software services, the retention of Tweet Photo was basically 100%. Meaning that anyone that signed up, was likely to continue using it for a long time. Once signed up, everything was automated after all.

Combine that with the “via tweet.photo” in every tweet and you’ve got steady growth:

Here’s a screenshot of the Simple Analytics dashboard showing how tweets are driving new leads to the homepage:

We even got some major Hollywood celebrities using the service. In fact, Tweet Photo became a hot topic amongst her fans. Driving even more sign ups.

💸 Monetization

Okay, so we’ve got decent growth. But what about the revenue?

This was a lot harder. When I launched Tweet Photo I included a $19/year PRO subscription that would remove the “via tweet.photo” branding. I figured if people care enough about their Twitter profile to not want to show that link, they might be willing to pay.

People with more Twitter followers would pay more. After all if someone has a million Twitter followers it’s worth a lot more to me if they promote Tweet Photo in every tweet.

I eventually switched to monthly pricing starting at $5/mo. I figured churn rate would be really low anyway, so it would be better to charge monthly. Paying $5/mo instead of $19 for a year upfront is a lower commitment for the customer, but ultimately 3x the revenue for me.

Unfortunately MRR grew very slowly. It’s about $135 MRR right now.

I think the main problem is that the free plan is already very compelling. So it’s hard to convince people to upgrade.

🤔 Now what?

While I had plenty of ideas for improving monetization, including removing the free plan altogether, it didn’t seem worth my time trying to grow a product that’s only doing $135 MRR. Even if I could 10x that, it’s still a low amount compared to my other products.

So over time I spent less time and attention on Tweet Photo. It continued to grow organically.

Another reason I didn’t want to invest too much time is the inherent platform-risk of building an API-powered product. I was dependent on both Twitter and Facebook continuing to provide me access to their API. They could revoke it at any time and Tweet Photo might be doomed.

Earlier this year Facebook did actually deprecate one of their APIs I was relying on, requiring me to upgrade my integration to use a different API.

💬 Acquisition offer

In April, Kevin reached out to me asking if I was interested in selling Tweet Photo. He had a strategic interest with his other products CreatorKit and Top Nine.

Of course the question of valuation quickly came up. Typically a SaaS product is sold for 3-4x annual revenue. In Tweet Photo’s case that would be around $5,000. But that didn’t factor in the many free users that required almost zero customer support, but drove continued growth.

If I were to sell it, it would need to be in the $xx,xxx range. Otherwise I’d prefer to just keep the service and see what happens. There’s always the possibility of another celebrity using it and it going viral.

💰 Valuation of $30,000

After some negotiation we ultimately settled on a purchase price of $30,000.

The first $10,000 is cash upfront with no strings attached. The remaining $20,000 is contingent on the revenue Tweet Photo will generate. Basically I will receive all revenue generated within 24 months of the acquisition, with a cap of $20,000.

We both ran the numbers and we believe that with the full weight of CreatorKit behind it, it seems very likely Tweet Photo will generate more than that.

But you never know how things turn out, so this was a way to de-risk the acquisition for the buyer while still allowing for a higher purchase than you’d typically see for a $135 MRR business.

Ask me in a few months how things are going 🙂

👀 What’s next

The $10,000 is in the bank and we’re now finalizing the asset transfer.

In the coming months CreatorKit will likely start marketing it to their existing userbase and possibly improving the service as well. Since we still have a shared interest in growing Tweet Photo me and the CreatorKit team will keep in touch to see how things are going.

Personally, I will continue to focus on WIP, BetaList, and Startup Jobs.

If you want to hear how the remaining $20,000 plays out subscribe to my newsletter below 💌

🛄 Only bring carry-on luggage.

It’s usually cheaper and you can check in online. For most airlines this means you don’t need to go to the airport counter and can go straight to the gate. It also saves you time when you arrive at your destination as you don’t need to wait for the slow luggage belt.

🛒 In case of doubt, don’t bring it.

The less luggage you bring, the less hassle. Smaller chance something gets lost, and less weight to carry around. If you’re unsure about whether to bring a certain item, consider that you can probably just buy it at your destination as well.

🎫 Flight ticket prices vary wildly.

Prices can change a lot depending on when you travel, with which airline, in which class, etc. If you’re traveling on a budget, make sure to do your research. Typically the more time between when you book and when your flight is, the cheaper. Use sites like Google Flights and Kiwi to compare different airlines.

💬 Meeting people.

It’s great if you can travel with friends. But if that’s not an option, there’s a bunch of different ways to make new friends at your destination. Joining a co-working place is one way. But also meetups through sites like Meetup.com or Nomad List. Dating apps like Tinder and Bumble can also be good ways to make new friends (or more).

📅 Stay flexible

If you’re visiting a new place, it’s hard to predict if you’re going to like it. And which area to stay at. So I try not to commit too much in advance and keep my options open. For example I might book a one-week hotel stay even if I plan to stay a few months. That gives enough time to explore the area IRL and pick a permanent spot.

💳 Use Revolut

Traditional banks can charge a lot for international credit card payments and ATM withdrawals. Newer banks like Revolut have a lot lower fees, and make it easy to order multiple cards so you always have a backup if you lose one.

✅ Make checklists

I’ve created a bunch of check lists for myself for travel. I’ve got a list for “what to look when booking an accommodation” (I have quite a few requirements 😅). Prep for a flight (including a packing list, etc). I even have checklist with what to do when arriving at my destination. It includes things like getting protein powder for exercise (as I usually find it too bulky to travel with) and properly unpacking rather than living out of my suitcase.

🍛 Select specific in-flight meal during check-in.

You’ll get food first + your choice. AFAIK there’s never an additional cost for choosing beforehand

🎧 Noise-cancelling

headphones for flight

🗺 Nomad List

Add trip to https://nomadlist.com to receive arrival email with local tips (which sim card to get, tipping percentage, etc)

👕 You can wash clothes during travel.

No need to pack weeks worth of clothes.

💺 SeatGuru

Use SeatGuru.com to find the best seats in plane

👍 Enjoy

Yes

I learned many of these tips from @levelsio (@nomadlist), and @jelmerdeboer’s book: https://thuisblijvenisduurder.com

The timing is never right. The stars won’t align. Your plate is always full. It won’t be any easier tomorrow. You cannot do it all. But if you do choose to do it, you might as well do it now.

Updated on December 2024 to reflect new exchange rates for a total worth of about $6,000. The original post dated August 2017mentioned $310 worth of cryptocurrency.

Give-aways

A few years ago a lot of new cryptocurrencies started to pop up. Give-aways were a popular way to promote them. Generally all you’d have to do is create an account and you’d get some free coins generally worth a few bucks.

Many cryptocurrencies have risen significantly in value since, so those free coins you got… They might be worth a lot more today.

I personally re-discovered over $300 worth of crypto coins when I first wrote this post.

In this article I’ll walk you through finding out for yourself if you still own any crypto coins you might have forgotten about by now.

1. Ripple / XRP

On May 10th, 2013 a cryptocurrency startup named Ripple announced a promotional give-away. Beta users would receive 1,000 XRP (Ripple) just for signing up to their mailing list.

Back then that 1,000 XRP was worth a few dollars. Like many other cryptocurrencies, the value of those coins has increased significantly. Today, that free 1,000 XRP is worth over $2,000 USD. Cha-ching!

How to find out if you own 1,000 XRP

If you don’t remember whether you signed up four years ago, it’s relatively simple to find out. Just search your email inbox for “ripple.com”. If you’re using Gmail you can click this handy link.

Here’s one of the emails I found:

Didn’t find any emails?

Skip to the next section (2. Stellar) to see if you own any of those.

Found the email? Great!

If you read closely you’ll notice that this email merely informs you that you’re eligible for the give-away. Unfortunately it doesn’t seem like Ripple actually sent an email after you received the 1,000 XRP, so this is the closest thing we get to confirmation.

If you did receive this email however, I’d bet there’s a decent chance you participated and have 1,000 XRP sitting somewhere in an inactive account.

What’s next?

Ripple Trade, the service that initially hosted your “XRP wallet” containing the coins has been shut down. Unfortunately that complicates the process a bit, but it’s not a dealbreaker.

All you have to do is follow their instructions. You’ll need to migrate your old Ripple account to a new service called Gatehub. It’s all explained on Ripple’s official webpage: http://rippletrade.com/

Click the button “Migrate Wallet to Gatehub” to start the process.

You’ll be asked to create a new Gatehub account (assuming you don’t have one yet). After that you can follow the instructions to migrate your old Ripple account to Gatehub so you can access your coins.

Unfortunately I did this a few months ago and don’t remember the exact process anymore, but I think it was relatively straightforward. In my case I had to verify my identity first to activate my old Ripple.com account. I don’t recall why, but ultimately it worked.

If you’re having trouble signing in to Gatehub try a different browser. Safari didn’t work for me, but Google Chrome did. ¯\_(ツ)_/¯

Here’s my Gatehub dashboard:

And here’s a screenshot of the Exchange showing how much the 1,000 XRP is worth at the time of writing:

Update: the value of XRP has increased significantly since writing this post.

If you are now the proud owner of $2,000+ worth of Ripple, feel free to send some test payments to my wallet. Haha. Whatever you think is fair ☺️

Open Gatehub, go to Wallet → Send Payment, and enter my username: ~marckohlbrugge

2. Stellar

Stellar is another startup that gave away free coins in order to promote their service. I can’t recall what type of promotion they ran, but I found out I own 5,152 lumens which is worth a little over $100 USD. (Update: now about $1812.18!)

Figure out if you have a Stellar account

Search your email inbox for emails sent by “@stellar.org”. Use this link if you use Gmail. Here’s an email I found dated August 1st, 2013:

Didn’t find the email?

No worries. There’s one more cryptocurrency to try out. Skip to the next section named “3. Circle”.

Found the email?

Great! Visit the following page to sign in: https://launch.stellar.org/

If you’re able to sign in successfully you’ll be walked through a migration guide as they updated their systems. Make sure to securely store your public and secret key or you’ll lose access to your account.

After migrating your account you should see how many “lumens” you have. They might take a few seconds to show up.

I personally have 5,152 lumens which at $0.02 a piece is worth about $109 at the time of writing. Not bad! (Update: it has 10x’d since writing this post!)

If you are now the proud owner of $100 worth of lumens, feel free to send some test payments to my wallet. Whatever you think is fair ☺️

Open your Stellar Dashboard, go to Send lumens, and enter my public key: GDIDVWKEBFKZ3274CEHFOGROJQXLMFR2LBMDA6LCS6JDUSATKPYN4FSG

Thanks to Tom Moor for reminding me about Stellar.

3. Circle

Back in 2014 a startup named Circle provided $10 USD worth of Bitcoin to new users. The value of bitcoin has increased by a factor of roughly 150x, so that means it’s worth about $1,500 now.

Figure out if you have a Circle account

Search your email inbox for emails sent by “@circle.com”. Use this link if you use Gmail. Here’s an email I found dated June 5th, 2014:

This email doesn’t guarantee you actually were invited to become a beta tester, or that you received the Bitcoin. However, it does make it more likely.

If you only find more recent emails you probably never received the bitcoin.

To be sure, try and sign in to Circle.com

My account didn’t show any transactions unfortunately. I reached out to customer support just to be sure they didn’t get lost somehow considering it was over 3 years ago that I signed up. I’ll update this post when I know more.

That concludes the guide. If you know of any other cryptocurrencies that gave away coins back in the day, let me know!

Send me a message on Twitter if you need any help. ✌️

Today I’m announcing my newest product: 😁.to (← yes that’s a link!)

An overview of all the emoji domains that are still available to register.

As you might know, a handful of domain extensions allow emoji to be used in the URL. The domain extension .to is one of them. It’s the official extension for the country of Tonga which is an island north of New Zealand.

This is what it looks like 😍

Most .to domains tend to be used as a domain hack though, where it can be part of a word (toma.to) or sentence (surf.to). This started all the way back 20 years ago in 1997 by Boris VvZ from The Next Web with his redirect service using domains such as come.to, welcome.to, surf.to, etc.

It’s still a very popular extension today and with the support for emoji it might get even more popular.

💡 The idea

Okay, so how did the idea for this site come about and how does it actually work? Well, I’m glad you asked!

About a week ago a nice guy by the name of Max Guerin sent me an email about how .to domains allow emoji to be used and he suggested I’d get one.

I manually checked a registrar’s site to see if my favorite emoji were still available to register. I quickly realised what I really wanted was just a list of every emoji domain that was still available. So I wrote a simple script which filled out the registrar’s form with each emoji and saved the results. I now had a list with about 1,500 emoji domains of which 70% was still available.

After checking with Max to make sure I wasn’t stepping on his turf, I decided it was a good idea to publicise the list. I figured it would save other people some time and figured I could potentially monetise it too.

🤑 The revenue model

I reached out to Register.to to see if they had an affiliate program. They happened to be working on one which was about to launch. I could get a 10% commission on every sale. Since each domain is $45, that works out to $4.50 per sale. It won’t make me a millionaire, but it might get me a ticket to Tonga. Who knows!

I guess it’s reasonable considering all I do is set up a page. I don’t have to worry about providing an actual service, ongoing support, etc.

I did check a few other registrars too, and Register.to seemed the most affordable so that worked out as well. They were also very responsive and implemented any feedback I had in a matter of days. 👏

An additional revenue model is selling premium domains. These are domains that are already registered and are now available for sale. Max has some great ones which I’m featuring on top of the page. I get a 5% commission on each sale. I also included some of my own:

• 👏.to
• 🙌.to
• 🎵.to
• 👋.to

If you’re wondering: do people buy these? Yes they do. Max sold ✉️.to the other day. (Not through me.)

⚒ How I built it

Since it’s just a one-pager with limited interactivity I was able to build most of it in just the weekend. I initially considered just creating a static HTML page, but quickly decided it would be better if the list was kept up-to-date automatically. So I created a simple Rails project and loaded in all emoji using the emojilib rubygem. It contains different keywords for each emoji which later would make it easier to implement search.

The code of the site is quite messy. My main priority was to ship the product. Clean code wasn’t much of a priority since I’ll probably not spend a lot of time on it in the future anyway.

Here’s what the homepage looks like:

I recently started playing around with Web Sockets in Rails 5 which makes it really easy to add real-time interactivity to a site. I wanted to try it out just for fun, so I added something where it will show a notification whenever someone clicks on a domain to order it.

It makes the page feel more alive, and shows you need to hurry if you want to get a good domain. 😁 #FOMO

📣 How I plan on promoting it

Since I launched the site just now, I haven’t done much promotion yet.

I did get in touch with Matthew Hughes at The Next Web before I launched though. I promised them the scoop. That’s a win/win, because The Next Web will be the first to cover the story meaning they will get more traffic to the article. For me it provides the certainty that I will reach many people at launch.

I also posted the site to BetaList and Product Hunt. You might notice a fun easter egg if you visit the site through Product Hunt. (or just check the source code above)

I show a message with a tweet button after you click on a domain:

👉 What’s next

To be honest I consider this more of a one-off project. A bit of fun, and quick way to make some money. (hopefully!) I might also add support for more domain extensions as they start supporting emoji.

Depending on how well the site does I’ll consider selling it to someone in the domaining industry. Maybe even the registrar itself, as it could be a nice way to drive traffic.

🤔 Should you buy an emoji domain?

Yes! — Well, obviously I’m biased haha, but I think they are pretty cool and get people’s attention. I wouldn’t go and spend hundreds of dollars on them as an investment hoping to sell them off, but if you find one that fits your product or personality it might be worth the $45/year investment.

Keep in mind there are some caveats to using emoji domains. Some software like Slack don’t support them well (links are not clickable), and at the moment Google Chrome doesn’t actually show the emoji in the address bar (although they work just fine).

If you do register one, let me know on Twitter!

👉 https://😁.to

This is an awful way to ask for feedback.

Often, after answering, they tell me “we’re not looking to change that part”, or “yes we’ve considered that, but we decided not to go that way”. So you’re wasting both my time and your own by me giving you feedback you didn’t want.

So, how do you ask for better feedback?

1. Be specific on what you’d like feedback on

Why are you asking for feedback? Are you stuck? Are you unsure of something? Explain that to the person you’re asking for feedback. Do you want feedback on the vision, concept, execution, the design, a specific part of the product, or maybe you are simply looking to squash bugs?

By clearly communicating what it is that you would like feedback on, you make sure you get exactly what you need. It’s perfectly fine to ask different people for different types of feedback based on their expertise.

2. Tell them what you DON’T need any feedback on

Let’s say you’re developing an app and you haven’t spent any time yet refining the on-boarding flow. You’ll want to tell them upfront they can disregard that part of the app. Otherwise you’ll just be wasting their time and will be less likely to provide feedback in the future.

3. Ask the right people

You want to make sure you ask the right people for the right feedback. I often see entrepreneurs asking their peers for product feedback, because these are the people that are easily accessible. If you’re building a product for other entrepreneurs, that’s great, but otherwise you want to make sure you talk to your customers instead. It’s the people that are paying for your product whose feedback you should value the most.

When it comes to business topics like hiring and strategy it does make sense to ask your peers, but then I still recommend being intentional about who you ask for which feedback.

4. Are you comfortable with harsh feedback?

I personally prefer feedback that cuts to the chase. It doesn’t need to be sugar coated. If something sucks tell me so I can fix it now, rather than invest more time and money into something that isn’t working. I believe that’s the most efficient, but I also realize not everyone is the same and it depends on the situation and your relationship with the person too.

Tell the person you’re asking feedback from if they can be blunt or if you prefer a little more sugar coating. If you’re uncomfortable saying you prefer sugar coated feedback you can use language such as “where do you see room for improvement?”, etc.

5. Make it easy

Asking people for their feedback can come in many different ways. Sometimes you’ll want to talk to a person. When you’re beta testing with dozens of users you’ll want an easy way for them to provide feedback from within your app or website (e.g. using Intercom). If you want feedback on an article you’re writing (like the one you’re reading now) use Medium or Google Docs so people can leave comments within the text. If it’s a design or visual mockup use a tool like InVision, etc.

Thanks for reading 🙌