I have an idea but I’m not an engineer, how can I build it?Featured

No code, no problem: Building a product with low code to no code solutionsWhen I built my first web app, I insisted on learning how to code. I thought that learning to code would give me the flexibility to build whatever I want. Whilst this may be true, after three months of blood, sweat and tears, I realized I hadn’t used my time wisely. Instead of spending a weekend building loaders, how many more customers could I have talked to? What if I found out I wasn’t building the right product in the first place and I didn't even need that loader?Building a product doesn’t necessarily mean building a product1. Your first product can be a RAT (Riskiest Assumption Test). Validating that the problem exists.Let's say you are interested in building a new hiring platform that is going to use competitions to find marketers. In your head, you see an app where candidates register, and then can save competitions etc. Building a product with the RAT in mind will allow you to strip this all away to focus uniquely on the assumption that needs to be true for the product to work. In our case, let's say this is the assumption that candidates will sign up to competitions. How could we build that? How about we go on Linkedin, message 100 candidates and ask them? To make it fancier, we could make the first competition an event on eventbrite and see how many sign up. That’s it! Technically, we just built our first product! And how much code did we need? None.2. From RAT to prototype: If the problem exists, what would my solution look like: Wohoo, 10 people signed up to our platform! That's great. Let's start building. For me, the next steps in the process look like this:
Sketch —> Whimsical —> Canva —> Justinmind
Sketch your product flow out on paper using Crazy 8’s (aka fold your paper into 8 and draw it out). A bit like this: Figure 1: My epic voice converter for emailMap that flow onto a flow-chart in Whimsical that looks like this:Figure 2: Breaking down every element of the productWhy all the steps? When do we get to build?! Do you see how the various boxes in the flowchart are differently colored? By breaking your product down into its core elements, it makes it easier to assign the various no-code tools to each step, preventing the build from becoming overwhelming. Your goal is to figure out how to make every element of the build work first, then worry about how they all connect. For example, let’s take the “user gets an email” step. The action is, “Once a user gets an email, send the content to a table. Then match those with the no-code tools.” This feels like Zapier and Airtable.Ok, I said four steps, realistically, you can skip the Canva step. I use Canva because it's a really quick way to make a pretty mock up of your crazy 8’s. Furthermore, did you know you can make landing pages there? Check out this one I built here! This page in Canva took me a couple of hours to make. It's all drag-and-drop and super intuitive. Enter the prototype. Justinmind is a drag and drop prototyping tool. I use it to build fully functioning dummy versions of the product. They are great because a) They give you a chance to show users what you are building, get feedback and iterate quickly without the sunk cost of a build, and b) it’s easy to make them do everything that you want exactly like in your build. For example, I wanted to make a tool that was connected to Lever, but I wasn’t yet convinced that I was building the right thing. In Justinmind, I just designed a page that looked exactly like Lever:The prototype is interactive, meaning people can actually click on the fields, and see exactly what the product looks like! The other advantage of Justinmind is that it’s drag and drop, meaning you can make a prototype in less than one day! You can check out the full prototype here; watching this, do you think you could tell I hadn’t actually built the product? BTW, if you are raising money, the prototype can be enough to get investors and get people signed up! You don’t even need the product! 3. Ok, I don’t feel completely comfortable with prototypes, I want an MVP, How do I choose what tools to use?The good news is that no-code tools are going through a boom. It's almost like there is a no-code tool for everything. Beware though, there is still a learning curve for all no-code solutions, and given a new one pops around the corner every month it can still be overwhelming to decide which one to use. Here is my rule of thumb:
  1. I want a simple website/e-commerce store : Squarespace, Carrd, Shopify
  2. I know how to use Adobe photoshop and want to store data: Webflow (alone) of Webflow + sortable
  3. I want to build a full app: Bubble
Of course, every project is specific, so if you want to build outside the above scope I would revert to the whimsical product flow and the appropriate tools for each step. In general, I try to stick to max three tools per project. Set timelines. In other words, try and make Step 1 work for one day. If it doesn’t work, ask! Makerpad is a great forum of super helpful no-coders where you can get advice, but also learn from tutorials of every no-code tool under the sun. Otherwise Google!So, to wrap it up:1) A product isn't always the finished product, it can be a prototype, a sketch or an experiment. 2) If you go the no-code route, break your product into steps using a tool like whimsical and 3) use the restrictions of the tools as an advantage to restrict the scope of what you are building. Lastly 4) If you are spending >1hr reading tool documentation, leverage support groups like Makerpad to ask!
This is SUPER helpful! If I had read this before we started our build, it would've saved us so much time (and $$$$).
I thought the same, This is super helpful
SO insightful and helpful! Thank you!!
💯 Thanks for sharing!
Hire a low cost high quality tech firm to execute the idea ? That’s what I’ve done.
If you have validated that you have a burning problem and your solution that makes sense!
I agree with you but finding a low cost high quality tech company is hard, do you have any that you can share with others?
Hi Tatiana- please contact me at [email protected]. I own a software development company and I can help with your software requirements.
Super duper helpful! All of this is totally spot on for process. Didn't know about Maker pad, thanks! A few other tools to consider for folks - Miro/Figma can handle whiteboarding and can be good instead of Whimsical. Figma is also a good prototyping tool - slight learning curve though. And I just got referred to Unicorn for simple landing pages that can help w idea validation (you can count how many people sign up before building!)
This is awesome, thanks @emilypatterson will add Unicorn to my toolbox myself!
Also, if anyone is interested in checking out what V1 of the actual epic voice converter tool I built as the basis of this article looks like, you can find it here: . Using the above process, I effectively built this thing in 3 weeks compared to 3 months with my first product.
This is SO helpful thank you
Great article and advice on how a non tech person can get going! I'd like to add that thinking about how you are going to fund your project/ business is also super important at the idea stage.It is MUCH easier and more likely for you to get an SBA loan BEFORE you start your business with a solid business plan even projecting no revenue your first 3 years. After you start your business you will not qualify until you have a year or two of revenue. While capital from investors is pushed a lot and seems like the natural path, it generally isn't. Knowing how you're going to fund your business and what the funding options are before you start is as important as building a product and maybe even more important.I wish I had know to apply for SBA funds when I started my startup!!!!
Great point @HeatherSawtelle!
I could not agree more. We have a technical team, including a world class founding engineer, and we still built our web app on Bubble. For us, it's about speed of execution. Just because you *can* build something more complex, doesn't mean you should.Speaking of, if anyone wants to see a Bubble product in action, head over and sign up at
Y'all built this in bubble!?!?
The secret is out. I can't tell if you're impressed or distraught...
IMPRESSED!!! It gets me excited to learn more on how to use it if I can maybe build something as cool as Topknot!
Omg this looks amazing! I'm new to Bubble and taking a course in how to create an app. What plugin did you use to create goals on your dashboard? Also, did you use the Typeform plugin for the intake process? I'm working on a startup in debt management and these two features are exactly what I had in mind in my prototype.I'm feeling more encouraged to use Bubble since looking at your site. It's so beautiful and complex. :)
We do use lots of plug-ins on our site, but everything you've mentioned is stuff that we built from scratch. A plugin in that flow was the wheel of life graphic, as an example.
Ok thanks!
It's a powerful tool. Our whole team took a moment to get into the swing of things, but now it's worth it. Sending you all the good Bubble vibes.
this looks great! I'm also building in bubble although mine does not look this sophisticated! agreed it took a while to understand it but I watched a lot of youtube tutorials and got the hang of it. I think it's super helpful especially when building a MVP, since it forces me to think through the process/ flow. Also i'm able to make changes in real time as I get more people to test it! +1 for bubble
Just made an account! The site looks great 😊
Awesome! I appreciate these kind words and am excited to grow alongside you.
Amazing to see this being covered and found so useful for people!
I joined this community just now and actually found a near about solution to the problem I was facing! this is amazing!
Great article! Makerpad was very helpful for us to get our creative juices flowing when we had no idea how to code anything. To get going, we used whimiscal to lay out ALLLL the user flows for our site. And then we made use of airtable and softr to put together a working no-code, fully-functioning site.