The question of "why WeWeb and Xano" comes up every now and then. Why not use an AI code editor instead? Based on our mental model developed with Ray Deck, the core reason is ownability. We have found that WeWeb and Xano are enjoyable for the client to learn how to use, because they empower the user to create software using a truly visual approach, which is completely different from the experience of building with traditional code. This has created an opportunity for the client's internal team to be trained in powerful new skills - skills that they actually want to learn, which is key for them to be able to take ownership of the project, and truly own their investment.

I was wondering I can use Snappy as non technical person?

I'm excited to announce that we are collaborating with @Benoît de Montecler from ncScale to launch a brand new boilerplate! We'll be kicking things off with our early Beta Users starting next week. To accelerate this initiative, I've brought in @Daniel Migizi from Twenty Two Alchemy. Daniel has consistently stood out and brought tremendous value to this community; making him the perfect person to drive the education and expansion of this tool. We've been working over the past few weeks to build a robust boilerplate incorporating the tools we're currently using for our own projects and our clients' projects - namely, WeWeb and Xano! So what does that mean for you? It means that building projects just got WAY easier thanks to WeWeb's powerful library functionality, and native integration with Xano! Right out of the box, the WeWeb/Xano boilerplate will include: - Stripe Payments Integration - Sendgrid Email Functionality - Stripe MarketPlace Connect - Password Reset Functionality - Authentication System - ...and much more! But now, I need to ask for a favor from our community. I need to build hype for this on LinkedIn. If you could go to the link below: My Linked In Post It would mean a lot to me if you would like/comment/share my post! Thank you all for being part of this community - it has been a pleasure to see it grow with you all!

In the traditional agency model, you eventually reach a phase of the engagement where the core app has been built, and further features will be billed at an hourly rate for a dev managed by the agency. That hourly rate can be double or triple what the dev is receiving - because the agency will provide management services or some other kind of support alongside those hours. But by the agency charging rent on every hour that dev works, they become a pebble in the client's shoe, making it that much harder for them to accomplish their goal of building a successful product. It is unlikely that they are providing value on every hour that the dev works, to where a 2-3X multiple is justified. If our north star is the client's success, then it seems that a more favorable arrangement can be made; the client working directly with the dev, without the agency's involvement. For the client, they get a dev who is already trained, and the cost of hiring them just went down. For the dev, they get a client they are familiar with, and a raise relative to what the agency was paying them. For the agency, the amount of hours doing management work just went down, and the amount of hours doing high impact work just went up. You have allowed yourself to step out of where you are not adding much value, and step into areas where you are most needed. Areas such as training the client and their team in how to manage Stripe subscriptions themselves. Showing their UI/UX designer how to go straight from Figma to WeWeb, streamlining their development process. Workshops for their backend developer in how to use Xano, so they can bind data directly to the front end and eliminate bottlenecks. You can also continue to provide management to the dev, according to a set schedule. The agency becomes a high-impact catalyst, enabling the client to stand on their own two feet faster and more effectively. By focusing on empowerment rather than dependence, you can create a win-win-win scenario for the client, the dev, and the agency. The client gets a successful product, the dev gets on-going work, and the agency gets to make a real difference while maintaining healthy margins.

I am currently staying in this Yurt for the next few days, so I'm taking the time to share more about some of what I've been working on lately! For those of you who came from StateChange or know of Ray Deck, him and I have been collaborating to develop a system that not only produces products, it produces producers. The great opportunity of low-code/no-code is speed and own-ability. These tools enable businesses to create software themselves that's going to deliver great value for their customers with both a high rate of speed and where they are in control. Instead of being an agency, we act as change agents. We bring the business people closer to the technical side - and bring the technical people closer to the business side. But this requires working closely with the client and their team. This isn't an initiative they can throw far away from themselves - it is an investment in themselves and the skills of their internal team. We believe the results of this process will overtake the agency model, and we are already putting that theory to the test with clients.