Resources Building it
No-code or custom build for your first release?
No-code tools have become genuinely good. For some first products they are the right answer. For others, especially in regulated markets, they create problems you pay for later.
When no-code is the right choice
- Testing demand. A clickable flow or a simple working tool to show customers before committing to a build.
- Internal tools. Something your own team uses, where the risk is low and changes are frequent.
- Simple workflows. Forms, records and notifications with a small number of users.
- Very limited budget. When the alternative is building nothing.
When a custom build is necessary
- Regulated data. Health, care, financial and children's data often need control over where data is hosted, who can access it and how actions are logged. Check whether the platform can meet your buyers' requirements, not just today's.
- Multiple organisations on one product. Selling to many schools, care providers or firms, each with their own users and data kept strictly apart, is hard to do well on most no-code platforms.
- Deep integrations. Payments, industry systems, public APIs and webhooks for your own customers.
- The product is the asset. If investors are buying the technology, they will ask what you own. A configuration on someone else's platform is not much of an answer.
- Scale and cost. Per-user pricing that is cheap for fifty users can be painful for five thousand.
The hybrid approach
A sensible pattern is to use no-code to validate, then build the real product once customers have committed. Keep the no-code version simple and treat it as disposable. The expensive mistake is spending months stretching a no-code tool to do things it was not designed for, and then rebuilding anyway, with live customers relying on it.
Questions to ask before you choose a platform
- Where is the data hosted, and can I choose the region?
- Can I export all my data, in a usable format, at any time?
- What does it cost at ten times my expected users?
- Will it pass the security questionnaire from my largest likely customer?
How we help
Sometimes the honest answer to a founder is "do not build yet, test this with a no-code tool first". When you are ready for a product you own, our three tracks cover how to pay for it, and the first release cost guide covers what it costs.