6 ms·

> Have you used a low-code backend builder already for some ambitious/cool problems/use-cases? Yes, proprietary integration tools that are the only sane way to

> Have you used a low-code backend builder already for some ambitious/cool problems/use-cases? Yes, proprietary integration tools that are the only sane way to integrate proprietary systems. You'd be better off learning some proprietary tool and selling your consulting services than rolling your own half-baked solution.

anonzzzies 3y ago
So you have examples of those proprietary tools? I know quite a lot and integrated with many of them; if you can do code, it’s trivial, so writing a no code solution to do it is usually really easy; I do that for my own consultancy. Just a few clicks and sellable for 1000s$ per client, but not in any mass/saas setup, as then it has to be a lot easier to use and a lot less error prone on wrong inputs when setting up everything. But for me it’s really fast; even faster with LLMs; now my tooling can work with human spec -> my spec language (which is industry and process specific) -> working code, iac, test data, benchmarks and tests. Do note that my field is quite specific; human spec does not mean some drivel with ‘I want an input box here and a login there’; it’s pretty technical specs with a lot of references to specific proprietary (the tool that’s being integrated with) language. For me openly sold no code tools are like those ‘billionaires’ that write books and give talks about how to make money; why would I do that if it actually works? I would keep it to myself and make more money, unless, you know, it doesn’t work. Then you make more selling it to many until you get caught out.
- throwaway11460 3y ago
  That's simple - I just can't sell it like you do. I would love to, I am trying my best, but I just can't get the clients. Getting clients for a low/no-code tool is much easier, albeit way less profitable. Any sales tips you could share, please?
jarirajari 3y ago
How I see it is that Integration applications are different from what I understand as a backend: API+business_logic+Database

anonzzzies 3y ago

So you have examples of those proprietary tools? I know quite a lot and integrated with many of them; if you can do code, it’s trivial, so writing a no code solution to do it is usually really easy; I do that for my own consultancy. Just a few clicks and sellable for 1000s$ per client, but not in any mass/saas setup, as then it has to be a lot easier to use and a lot less error prone on wrong inputs when setting up everything. But for me it’s really fast; even faster with LLMs; now my tooling can work with human spec -> my spec language (which is industry and process specific) -> working code, iac, test data, benchmarks and tests. Do note that my field is quite specific; human spec does not mean some drivel with ‘I want an input box here and a login there’; it’s pretty technical specs with a lot of references to specific proprietary (the tool that’s being integrated with) language. For me openly sold no code tools are like those ‘billionaires’ that write books and give talks about how to make money; why would I do that if it actually works? I would keep it to myself and make more money, unless, you know, it doesn’t work. Then you make more selling it to many until you get caught out.

throwaway11460 3y ago
That's simple - I just can't sell it like you do. I would love to, I am trying my best, but I just can't get the clients. Getting clients for a low/no-code tool is much easier, albeit way less profitable. Any sales tips you could share, please?

jarirajari 3y ago

How I see it is that Integration applications are different from what I understand as a backend: API+business_logic+Database