--- title: "No-code, low-code or custom development for a first product? — Orvun Labs" description: "Choose the approach against the hardest required workflow and the people who will maintain it." canonical: "https://orvunlabs.com/en/journal/no-code-low-code-or-custom" language: "en" last_modified: "2026-09-13" --- # No-code, low-code or custom development for a first product? Choose the approach against the hardest required workflow and the people who will maintain it. ![No-code, low-code or custom development for a first product?](https://orvunlabs.com/images/blog/mvp.svg) - Published: 2026-09-13T09:00:00.000Z - [MVP & validation](https://orvunlabs.com/en/journal/topic/mvp.md) ## The decision Choose the approach against the hardest required workflow and the people who will maintain it. A visual builder is still a software dependency with permissions, data and operating costs. Custom code does not remove those responsibilities; it changes who controls them. ## A worked example For an illustrative membership directory, test importing records, editing one member, limiting access and exporting everything. Then try a member leaving the organisation. If the tool cannot express that permission change safely, a quick initial setup is not enough evidence of fit. ## Run a representative platform trial Use a small set of synthetic membership records with different roles, missing optional fields and one person who belongs to two groups. Import them, invite a restricted user, change membership, export the results and remove the test data. Record every manual workaround and every capability that requires a different plan or extension. Check current vendor documentation for those commercial conditions before making a budget commitment. A trial that only creates attractive screens does not tell you how the product will behave after several months of editing, staff turnover and unexpected records. ## Compare the maintenance arrangement Ask who can investigate a failed automation and which parts are visible to that person. In a no-code product, they may depend on the platform's logs and export facilities. In a low-code product, a problem can sit at the boundary between visual configuration and custom code. In a custom application, the team owns more of the diagnosis but must maintain its tooling and dependencies. Include staff skills, account ownership, backup and rollback procedures in the comparison. A technology that a contractor can build quickly may still be expensive for the business to operate if no one can safely change it afterwards. ## Preserve a realistic replacement path Document identifiers, important relationships and the direction of each integration. Test exporting records and attachments into a format another system can understand. Decide which business logic is portable and which would have to be reimplemented. Avoid promising effortless migration merely because some data can be downloaded. If the platform is suitable today but has a known boundary, record a trigger for reassessment, such as a permission rule or integration requirement it cannot support. This allows the business to choose a useful first platform deliberately without pretending it will be the final architecture for every possible future product. ## Alternatives worth weighing - No-code can suit a standard workflow owned by operations. Low-code allows specific extensions but may divide debugging between platform and custom parts. Custom development offers broader design control and requires engineering maintenance. A hybrid works only when boundaries and exit paths are clear. ## Where the plan breaks Do not decide from the happy-path demo. Check limits in current vendor documentation before committing, including what can be exported and which features depend on a paid tier. Avoid numerical comparisons without a verified quote for the intended usage. ## Before you commission the work Who can repair a broken workflow? Can data leave in a usable format? Which requirement would force replacement? Use a short trial with real acceptance examples to make the MVP technology choice reviewable. ## MVP development A first product with a clear reason to exist. - [Discuss this service](https://orvunlabs.com/en/services/mvp-development.md) ## Related reading - [Which features belong in a first MVP?](https://orvunlabs.com/en/journal/choosing-mvp-features.md) - [The dependencies that shape an MVP timeline](https://orvunlabs.com/en/journal/mvp-timeline-dependencies.md) ## Let's make something useful. A first product, a difficult workflow or software that needs a fresh start. Tell us where you are. - [Tell us about your project](https://orvunlabs.com/en/contact) ## Structured data ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://orvunlabs.com/#organization", "name": "Orvun Labs", "url": "https://orvunlabs.com", "logo": "https://orvunlabs.com/orvunlabs-icon-512.png", "description": "Custom software, SaaS products and AI-powered tools — designed around your business.", "knowsAbout": [ "Custom software", "SaaS product development", "AI integration" ] }, { "@type": "WebSite", "@id": "https://orvunlabs.com/#website", "name": "Orvun Labs", "url": "https://orvunlabs.com", "inLanguage": [ "en", "es", "de", "fr", "pt", "ja", "hi", "ar", "id", "tr", "pl" ], "publisher": { "@id": "https://orvunlabs.com/#organization" } }, { "@type": "WebPage", "@id": "https://orvunlabs.com/en/journal/no-code-low-code-or-custom#webpage", "url": "https://orvunlabs.com/en/journal/no-code-low-code-or-custom", "name": "No-code, low-code or custom development for a first product?", "description": "Choose the approach against the hardest required workflow and the people who will maintain it.", "inLanguage": "en", "isPartOf": { "@id": "https://orvunlabs.com/#website" }, "about": { "@id": "https://orvunlabs.com/#organization" }, "breadcrumb": { "@id": "https://orvunlabs.com/en/journal/no-code-low-code-or-custom#breadcrumb" } }, { "@type": "BreadcrumbList", "@id": "https://orvunlabs.com/en/journal/no-code-low-code-or-custom#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Orvun Labs", "item": "https://orvunlabs.com/en" }, { "@type": "ListItem", "position": 2, "name": "No-code, low-code or custom development for a first product?", "item": "https://orvunlabs.com/en/journal/no-code-low-code-or-custom" } ] }, { "@type": "BlogPosting", "headline": "No-code, low-code or custom development for a first product?", "description": "Choose the approach against the hardest required workflow and the people who will maintain it.", "datePublished": "2026-09-13T09:00:00.000Z", "dateModified": "2026-09-13T09:00:00.000Z", "inLanguage": "en", "author": { "@id": "https://orvunlabs.com/#organization" }, "publisher": { "@id": "https://orvunlabs.com/#organization" }, "image": [ "https://orvunlabs.com/images/blog/mvp.svg" ], "mainEntityOfPage": { "@id": "https://orvunlabs.com/en/journal/no-code-low-code-or-custom#webpage" } } ] } ```