I’m building a SaaS using WeWeb (frontend) and Xano (backend) and am exploring the best way to structure the project for a potential acquisition or equity partnership down the line. I understand that while I own the configuration (UI, workflows, DB schema, API logic), I do not own the platforms themselves — which introduces some complexity when transferring assets or structuring a sale.
I’m reaching out to ask,
Has anyone here successfully sold a SaaS built on WeWeb and/or Xano?
If so:
• How did you structure the handover of accounts, configurations, and assets?
• How did you present the value of the IP during due diligence, given the underlying platforms are proprietary?
• What were the buyer’s concerns (e.g., lock-in, lack of source code, dependency risk)?
• Did the buyer continue operating on WeWeb/Xano, or did they migrate to a custom stack post-acquisition?
Legal & IP Considerations:
• How did you document IP ownership in a way that was convincing to acquirers?
• Did you create an IP transfer agreement beyond the standard platform ToS? (e.g., assignment of configuration, workflows, databases)
• How did you handle multi-user ownership — if co-founders or contractors had access to the project?
Buyer Negotiation & Value Retention:
• How did you justify valuation when the code isn’t traditionally exportable?
• Did the subscription dependency on WeWeb/Xano affect deal terms (price, contingencies, warranties)?
• Were there requests to transition off the platforms before or after the deal? How did you handle that?
Best Practices & Lessons Learned:
• What do you recommend to make a no-code SaaS more exit-ready?
• Did you use versioning, documentation, sandboxing, or backups to future-proof?
• What would you do differently if you had to prep again for acquisition?
Would really appreciate any real-world insights, pitfalls, or even redacted LOI/SHA tips if you’re willing to share. Even if you haven’t exited yet, and are just building with this in mind, I’d love to hear your playbook.
Are you talking about selling a tech product or selling a business ?
You’re question are more related to selling a tech product.
I guess if you’re selling a business, there is much more involved to it, than just the tech
Thanks for the note — it’s a valid distinction, and you’re right that selling a business involves broader considerations.
To clarify: I’m building a SaaS on WeWeb (frontend) + Xano (backend), currently operating with a lean team (under 15 people) and generating $10M+ in revenue. So while it’s a functioning business, the core value is still the tech product — and it’s fully built on no-code infrastructure.
That’s why I’m focused on how other founders have navigated:
• Transferability of assets built on WeWeb/Xano
• Buyer perception of platform dependency and lack of exportable source code
• Properly documenting IP ownership (config, schema, workflows) for due diligence
• Valuation justification when the IP lives on proprietary systems
Even in a full acquisition, these factors play a major role in de-risking the deal, setting price, and structuring the transition.
If you (or anyone else here) has been through a similar process — especially with WeWeb or Xano — I’d really appreciate any insight.
Nice, mate, that’s very good numbers
Can you share the name of the company, or at least what the product does ?
I’ve never been in that situation, so I can help with experience.
I would think that in that situation, code or nocode, the most important are your
metrics, and recurring revenue
the ability for your product to work without you or your team,
and how well you’ve documented everything for an easy transition.
I’ve never done it, so there are a lot more subtleties and I’d be curious to know it goes
Hi @lighthama2 And first congratulations on such a successful product, those are Series A numbers!
Now to your question, I am also building a SaaS on weweb and just closed pre-seed. Not at your level yet, but this was something I thought a bit about, especially the coded assets part.
First, I avoided using Xano, because it was harder to translate 1-to-1 to real-world code without the Xano platform and since the majority of a product is its backend, I resisted that urge. I used Supabase (since that’s just pure postgres really, and I DON’T use supabase edge functions either, I use postgres functions) and everything else was coded JS and Python cloud functions that could run in any server setup.
Second, I exported my raw Weweb project (the source code export, not the built version) and I studied the file structure myself, of how weweb acually builds the raw project. It’s a bit unintuitive and not human friendly at all, BUT it is understandable after a bit of studying, you may need to hire a Dev if you’re not one yourself to help you document that. Your goal here is to be able to document HOW someone else can continue to add to your project frontend using code without weweb.
Third I avoided ALL weweb plugins and rely on http rest calls for most of my backend work. This way again it’s easier to extend with code when an acquirer wants to do so. Or if they want to move off the platform. In the end it is not very easy work. But I will say if YOU REALLY want to be able to sell the tech without your valuation taking a hit, then you will have to remove every piece of superlocked-in proprtietary tech and so your solution is re-creatable anywhere, Weweb isn’t the bottleneck in this case it would be XANO.
