1
0 Comments

The story of how I started no-code

So, back when I started freelancing, I was doing Growth marketing. It wasn't really my thing, you know: clients always wanted results, but a lot depended on their overall strategy and what they were offering.

But one day I discovered the no-code. At first, I was just creating basic websites, and then I moved to making simple apps with tools like Softr or Glide. I started offering my services there.

It was quite crazy how easy it was to make apps with these tools. You just hook them up to an Airtable or Google Sheet, and bam, you've got yourself a starting point for an app.
Super handy for a quick MVP, but there are limits of course. Like, when clients wanted a chat feature or custom designs, I had to tell them Softr couldn't do that. It was frustrating for them and for me.

So, I decided to try something more powerful, like Bubble. But man, Bubble's on another level of complexity, more low-code than no-code. I was totally lost but figured, "F*ck it, I'll learn as I go."

→ Then, this client comes along wanting me to recreate a design.
I signed it with my highest quote ever, over 15k€. I was super happy, I started the work, but hit a major issue right away. Importing the Figma design into Bubble didn't keep it responsive. It felt easier to just redo everything manually. But Bubble was so complex, and I was struggling.

I ended up outsourcing the design part. I hired a freelancer and watched his every move on Bubble, trying to learn and replicate it myself. Whenever the client wanted changes, I'd try to handle them, applying what I'd seen. For the workflows, the freelancer did most of the heavy lifting, maybe 60-70%.

In the end, the client was happy. The app was delivered on time, and he didn't notice anything. I got my "first" Bubble project under my belt, and the best part? I made more money than the freelancer I hired! I basically got paid to learn.

→ Of course, this approach isn't without risks. You've got to think about things like secret agreements and what the client expects. And there's the ethical question of not being totally upfront with the client. But in my view, it's all good as long as everyone's happy. The client pays for a functional product, and that's what they got.

on February 26, 2024