Build, buy or no-code? Choosing for business apps

When a team needs a new business application, there are three realistic routes: build it with developers, buy an off-the-shelf product, or build it on a no-code platform. The build vs buy vs no-code decision is often made by habit, or by whoever is in the room, rather than against clear criteria. This guide gives you those criteria and a way to apply them to the application in front of you.

The three options, defined

It helps to be precise about what each route means.

• Build means developers, in-house or contracted, write a custom application. You own the code and, usually, the hosting and operations.
• Buy means licensing an off-the-shelf product designed for a common process, such as a helpdesk, a CRM or an expense tool, and configuring it within the options the vendor offers.
• No-code means the people who understand the process create a custom application on a platform that provides the database, screens, workflows, security and hosting. On Vibe, that application can be generated from a description, a spreadsheet or an existing database and refined by pointing and clicking or in plain language.

Each is the right answer for some applications. The mistake is using one route for everything.

Eight criteria that decide it

Assess your application against these criteria before discussing products or teams.

1. How standard is the process? Payroll and email are the same in most organisations. Your supplier onboarding or claims triage probably is not.
2. How often will it change? Processes that change with regulation, pricing or organisation structure need cheap, frequent change.
3. Who understands it best? If the knowledge sits with operations or finance rather than engineering, the hand-off to developers is a cost.
4. How quickly is it needed? Weeks of queueing and procurement may be acceptable, or may mean the spreadsheet carries on indefinitely.
5. What will running it cost? Hosting, patching, backups, monitoring and on-call, for as long as it exists.
6. What security controls does it need? SSO, fine-grained permissions, audit trails and encryption, and who will provide them.
7. How must it connect? To finance systems, identity providers, data warehouses or customer-facing tools.
8. How easily can you leave? Whether data, and ideally the application itself, can be exported.

A side-by-side comparison

Against those criteria, the three routes typically compare as follows. These are general tendencies, and individual products vary.

• Fit to your process
  • Build: exact, if requirements are captured well.
  • Buy: good for standard processes; otherwise your process bends to the product.
  • No-code: close, because the people who know the process shape it directly.
• Time to a first working version
  • Build: weeks to months, depending on the queue.
  • Buy: depends on procurement, configuration and integration effort.
  • No-code: on Vibe, a working application in hours.
• Cost of change after launch
  • Build: every change goes back to developers.
  • Buy: limited to what the vendor's configuration allows, or waits on their roadmap.
  • No-code: business users make changes themselves; every change is versioned and reversible.
• Running and operations
  • Build: yours, unless you arrange otherwise.
  • Buy: the vendor's, for SaaS products.
  • No-code SaaS: the platform's. For Vibe, that means deployment pipelines with staged environments and one-step rollback, patching, backups and monitoring.
• Security controls
  • Build: must be built and reviewed for each application.
  • Buy: whatever the product offers.
  • No-code: inherited from the platform. Vibe provides SSO over SAML and OIDC, role-based access on every entity and action, audit logging and encryption in transit and at rest.
• Integration
  • Build: anything, at a development cost.
  • Buy: the vendor's connectors and API.
  • No-code: depends on the platform. Vibe applications import CSV and SQL, connect over REST, webhooks and events, and expose their own APIs.
• Exit
  • Build: you hold the code.
  • Buy: usually a data export only.
  • No-code: varies widely. With Vibe, data and generated code are exportable on any plan.

When each option wins

Buy when the process is genuinely standard, is not a source of advantage, and a mature product already does it well. Accounting ledgers, payroll and email are good examples. Configuring an established product beats rebuilding it.

Build with developers when the application is part of your product, needs specialised technology or engineering control over every detail, or must run inside infrastructure you operate. A full-code platform with managed operations is planned for teams in this position; see what is the full-code platform?.

Choose no-code when the process is specific to your organisation, changes often, is understood best by people outside engineering, and needs proper security and operations without a dedicated team to provide them. Most internal business applications, such as trackers, registers, approvals, intake and case management, fall here. The detailed case is in no-code SaaS vs building business apps in-house.

Common mistakes to avoid

• Buying for a process that is not standard. You end up paying for a product and then working around it in spreadsheets.
• Building for a process that changes monthly. The application falls behind the business within months of launch.
• Choosing a no-code tool without checking the foundations. A tool without a real database, SSO, audit logging or export becomes the next migration project. Our checklist for choosing a no-code platform goes through what to check.
• Counting only the build cost. The running costs described in the hidden costs of self-hosting internal apps often decide the matter.

There is also a fourth route

Sometimes a team wants a custom application but has no one available to build it, even on no-code. In that case, a services team can build it for you on the same platform, so you still get a managed application your team can change later. The FAQ on whether to use Vibe or the services team explains how to choose, and the services page describes the work.

Apply the criteria to one real application

Take the application you are deciding on now and score it against the eight criteria. If it points to no-code, the product page shows what Vibe builds and how Vibe is priced. Ahead of general availability, the design partner programme lets you try the route on a real workflow, free during the programme. Get in touch.