2
1 Comment

Stop thinking Yes-code vs No-Code, think API-first vs UI-first.

It's easier for me as a developer, I guess, but as a startup owner and as a CTO-as-a-service work with larger startup companies (and some small ones too) I would like to note something.

I normally see non-developer struggle very hard with crafting a MVP.

When you're dreaming about your product at night, waking up and thinking of it all day, features just come in tens of thousands. Right?

And those features are so important. Not just for you, I mean, the world need them. Each and every one of them is a masterpiece.

But making them...
At the beginning, when working on a product called Modulla, it was too hard for me to be an UX\UI\Product\CTO all-in-one.
Then I thought, I'll start with the UXUI part, move on to coding, then validating and roadmapping and follow the circle of build-measure-learn,

AND THIS WAS SOOOOO SLOW. But I thought it's a good idea, then I started paying for other people on doing stuff. I thought that if I'll find a developer, I'll be able to plan the other things. But managing others can go slow at the beginning, and communicating your MVP to a paid developer is not the perfect lean strategy. I just gave up.

When trying to understand what went wrong, it is just that: I needed to think from ground-up.

There are many clients who are waiting for your feature. One wa is creating that perfect dynamic UI with some no-code tool so you'll have your app. Another way is coding it after work, component by component, and it is not easy either.

But even harder, it is not LEAN.

I think my customers are waiting for the app to do stuff. So the doing part, the dynamic part, is the main part of it. Instead of thinking in a full product or in features, with superCart I started thinking in functions. What should be the input, what should be the output, what should happen.

Focus on the interaction. The outcomes. The movement of value in your SaaS. You'll pass the option of giving customization to your customers, yes, but you will be able to start and serve customers.

Now, I said: I am a developer. I am NOT a designer. At all. F in design. Yet I think this approach can help also people which are not tech-savvy as me: having a working back end, sometimes can be much faster then a working front end. Using Integromat, Backendless or maybe some other open source apps with an API can be super for you at the beginning. The packaging will come later.

on January 20, 2021
  1. 2

    Thanks for this! I'm looking to start on a no-code project in March and I'm a marketer/designer with no coding knowledge. Nice to hear a suggestion for where to start, I was leaning towards trying to tackle all of the big features at once!