Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Engineering

Custom development or packaged software, compared on fit to need, cost and dependency

In brief

The choice between custom development and packaged software is made function by function, between three routes: building software specific to the organisation, configuring a vendor's product, or customising that product with bespoke code. Management Square compares them here on fit to need, cost over time, dependency, lead time and changes, then describes the hybrid route.

Page contents

In common usage, the alternative “custom development or packaged software” contrasts two ways of obtaining an application. Custom development builds software for a single organisation, which decides each of its rules. Packaged software is a vendor’s product: the Trésor de la langue française informatisé (cnrtl.fr, consulted on 12 November 2026) defines it as a program, or a set of programs, that is “coherent, independent and documented, designed to be supplied to several users for the same application or the same function”. Practice distinguishes two uses of it: configured packaged software, set up through the options alone that the vendor has provided, and packaged software customised with bespoke code, written for a single customer.

The choice is therefore made between three routes, and it arises for each function taken separately. Five criteria decide between them: fit to need, cost over time, dependency, lead time and changes. Each route has its strong and weak criteria. A fourth, hybrid route gives the standard to packaged software and reserves custom development for the rest.

The boundary between configuration and bespoke code

Configuration uses what the vendor has provided: reference tables, rules that can be activated, approval workflows, document templates, permissions. These settings belong to the product: carrying them over from one version to the next is the vendor’s responsibility, according to its support terms, to be read before the choice.

Bespoke code begins where these settings are no longer enough. It takes two forms, whose consequences differ.

  • An extension relies on points provided by the vendor: application programming interfaces (APIs), add-on modules, scripts run at defined points. It holds as long as these points remain stable.
  • A modification touches the code of the product itself. It has to be checked, or even redone, with each new version, and the contract may exclude it from support.

When the packaged software is supplied online by subscription (SaaS) and the customer has no access to its code, modification is not possible: configuration and extension remain.

This boundary is established in an inventory. For each gap between the need and the product, the integrator states whether it handles it through a setting, an extension or a modification. A quote that announces “advanced configuration” without this detail does not say which of the routes is being proposed.

Custom development or packaged software against the same criteria

The table describes mechanisms, with no amount or duration: a figure is established case by case, on written assumptions.

Criterion Custom development Configured packaged software Packaged software customised with bespoke code
Fit to need The software follows the need as it was understood; the possible gap is that of a poorly expressed need The organisation adopts the product’s practices where configuration is not enough The gap is filled with code, for the functions concerned
Cost over time Build, then operation, fixes, changes and updating of components, borne by the organisation Licences or subscription, integration, data migration, checking of settings with each version The packaged software’s items, plus writing the bespoke code and checking it with each version
Dependency On those who know the code, in-house team or service provider On the vendor: prices, roadmap, discontinuation of a product Twofold: the vendor, and whoever maintains the bespoke code
Lead time That of framing, then of the first increments; it depends on the scope of the first version That of integration, data migration and the change in practices That of the packaged software, extended by the design and testing of the bespoke code
Changes Decided by the organisation, at the pace of the capacity it devotes to them Decided by the vendor for all its customers The vendor’s apply if the bespoke code supports them; the customer’s go through the bespoke code

Two rows call for care in reading. Cost is compared over the same period, the one during which the organisation intends to use the application, and with the same items on both sides, exit included: recovering its data and settings on the day the product is replaced, or taking over code that its author no longer maintains. Our page on custom development presents the estimation of this full cost and the decision file that records it.

Dependency, for its part, disappears in none of the columns: it changes in nature. With custom development it concerns knowledge of the code, whether held by an in-house team or by the provider of third-party application maintenance. With packaged software it concerns the choices of a vendor, which the organisation does not control.

When each route holds up

Configured packaged software holds up for a function in which the organisation does not seek to stand out (this may be payroll or general accounting), when it accepts aligning its practices with those of the product. This acceptance is decided before choosing the product, with the business managers concerned. Obtained afterwards, it is negotiated gap by gap, and each refusal can become a request for bespoke code.

Custom development holds up for the function that distinguishes the organisation or that no product covers; added to this is the case where it wants to keep control of the pace of changes. It requires a team to keep the software alive after it goes into service. The criteria for this trade-off are detailed in the service page cited above.

Customised packaged software holds up in a narrow case: a gap limited to a few functions, handled by extension, kept in a register in which each bespoke development has a justification, an owner and a test replayed with each version. It stops holding up when the bespoke code touches the core of the product and grows with each request. The sign can be spotted without any tool: the version upgrade, supposed to remain a routine operation, is prepared like a project. Bespoke code that nobody keeps up to date then joins the organisation’s technical debt.

When the question concerns an application already in service, to be replaced by a product on the market or rewritten, it falls under the migration strategies compared in our page on application modernisation.

A hybrid route, packaged software for the standard and custom development alongside

Take a manufacturer of conservatories renewing its management system. Accounting, purchasing and stock management follow common practices there: configured packaged software covers them. The configurator, which translates the dimensions of the structure, the glazing and the options into a bill of materials and a price, embodies its know-how. Programming it inside the packaged software would make it bespoke code to be checked with each version.

The hybrid route places it alongside. The configurator becomes a custom application, which reads items and prices in the packaged software and passes orders to it through the interfaces the vendor documents. The packaged software remains set up through its options alone, and its version upgrades only affect the configurator if these interfaces change.

This route has a counterpart: connecting the two applications becomes the organisation’s work, whereas a single suite arrives already connected. Each shared data item is given a reference application, each interface a written contract and a named owner, as our page on IT architecture requires. Extended to an entire information system, this assembly logic has a name, defined in our entry on composable architecture.

The work begins with a list of functions, each placed in one of these routes, with the reason for any departure from the standard. A function that nobody knows how to place signals a need to be clarified before approaching a vendor or a development team.

Insights

Further reading

All insights

FAQ

Frequently asked questions

Another question? Ask us

What is the difference between packaged software and custom software?

Packaged software is a product designed by a vendor to be supplied to many customers, who set it up through the options provided. Custom software is built for a single organisation, which decides each of its rules and bears its maintenance. The former imposes its practices where configuration is not enough; the latter follows the stated need, provided a team keeps it alive after it goes into service.

Where does configuration of packaged software stop and bespoke development begin?

Configuration uses the settings the vendor has provided: reference tables, rules that can be activated, approval workflows, permissions. Bespoke development adds code written for a single customer, either through the extension points the vendor documents or by modifying the product itself. The difference shows at version upgrade: a setting provided by the vendor is carried over according to its support terms, bespoke code has to be checked by whoever wrote it.

Can packaged software supplied as SaaS receive bespoke code?

When the customer has no access to the product's code, it cannot modify it. What remains is configuration and, if the vendor offers them, extensions: programming interfaces, add-on modules, scripts run at defined points. What these extensions allow, and their stability from one version to the next, is read in the vendor's documentation and contract before the choice.

Can packaged software and custom development be combined?

Yes. The hybrid route gives standard functions to packaged software set up through its options alone, and builds the function that distinguishes the organisation as custom software, in a separate application. The two communicate through the interfaces the vendor documents. The organisation then takes on the integration: one application that is authoritative for each shared data item, and a written contract for each interface.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.