No-code or custom software? Choose around the work.
Choose for workflow fit and maintenance. Prototype the hardest requirement first.
First decide whether something needs to be built
Before building a client intake portal, check whether an existing product covers the form, approvals, and exceptions.
List users, tasks, records, and what follows each action. Separate requirements, such as record-access restrictions, from preferences, such as button placement.
Treat no-code and code as a spectrum
No-code usually means configuring an application through visual tools. Low-code adds room for scripts, queries, or custom components. Custom software gives a development team direct responsibility for the application code. Real projects often combine these approaches: a visual interface, a small custom service, and an existing database.
None of those labels guarantees a quick build, reliable permissions, easy migration, or low maintenance. Capabilities differ between products and plans, and a tool may fit one part of a workflow better than another. Verify the specific features you need in the current documentation and a working trial before committing.
Compare the requirements that are expensive to change
Use this table as a set of questions, not a ranking. The answer should come from a small prototype or documented evidence. Ask the same questions of a custom build; having source code does not, by itself, make a system maintainable.
| Decision area | Check a no-code option | Check a custom build |
|---|---|---|
| Workflow fit | Can it express the real rules and exceptions without fragile workarounds? | Is the added flexibility worth designing and testing those rules? |
| Integrations | Test authentication, limits, failures, and required actions in each connector. | Identify API access, error handling, retries, and who maintains each integration. |
| Data portability | Try exporting records, relationships, files, and identifiers; check usable formats. | Define the schema, backups, export tools, and a tested recovery process. |
| Permissions | Verify the required record and action restrictions with realistic user roles. | Budget for implementing, testing, and reviewing those restrictions. |
| Maintenance | Name the platform owner and check change history, testing, and recovery options. | Name the code owner and budget for updates, monitoring, and documentation. |
| Future change | Prototype the most likely complex extension before committing. | Keep the first scope small and avoid building flexibility nobody needs yet. |
Use a scorecard after identifying the non-negotiables
First list any requirements that can rule an option out: a necessary integration, an access boundary, or a required export. A high total score must not compensate for failing one of these. For the remaining criteria, assign importance from one to three, then score each option from zero to two: absent, partial, or demonstrated.
Multiply importance by the demonstrated score and compare totals. Keep a short evidence note for every rating. An untested sales claim is not a demonstrated result. This is a discussion tool, not a scientific formula; close totals mean the tradeoffs and unknowns deserve more attention than the arithmetic.
Prototype the riskiest part, then price the whole job
For the intake portal, the riskiest requirement may be keeping each client's records separate while synchronising updates into an existing system. Test that path with representative data and two distinct user accounts. A polished public form proves very little about the harder work behind it.
Compare implementation, subscriptions, usage charges, hosting, training, support, and likely changes over the same period. Include the effort of leaving the chosen approach. A less expensive first version may be a good experiment, provided its limitations and replacement plan are explicit. A larger custom build needs equally clear reasons for its added cost.
Make ownership part of the decision
Before work starts, agree who owns the accounts, data, configuration, and source code where applicable. Define who can change the system, how those changes are tested, and what support is available after handover. Ask another person to follow the operating notes before calling the project finished.
Choose the option your team can use and maintain: an existing product, a visual builder with custom integrations, or a custom application. Base the decision on workflow evidence.
