Cruise
A luxury cruise line
One portal for a luxury cruise line's operations, from procurement to ship provisioning
- back-end services behind one portal
- 36
- functional areas, from procurement to crew payroll
- 20+
Custom software, at Codedesign, means web platforms, portals and operational applications designed around one company's processes, built on mainstream technologies, documented, and then run by us or handed over to your team.
Standard software is designed for the average company. When your processes are part of how you compete — how you provision a ship, pack a machine shipped in pieces, approve a supplier — the average becomes a cost: spreadsheets around the system, manual steps between screens, a team that adapts to the tool.
Custom software closes that gap. It is not always the right answer, and we say so when a product on the market does the job: see bespoke software or platform.
01
One portal in front of many services: procurement, documents, HR, budgets, operations. Each area has its own data, screens and roles, and they share identity and master data.
02
Software for production, warehouse and logistics: planning, packing lists, weighing, loading plans, barcode-driven shipping and labels.
03
Master data, approvals, documents, reporting, and exports to Excel and PDF, designed around the way your team decides.
04
Applications that run in the browser and install on phones and tablets, for people who work in the warehouse, on the shop floor or on the move.
05
Ageing applications rewritten or extended one area at a time, while the existing system keeps working.
06
.NET on the server, Angular in the browser, SQL Server for data, Microsoft Azure or your own servers for hosting, Keycloak for single sign-on.
01
We spend time with the people who will use the system and write down the process as it really is, workarounds included.
02
Data model, roles, integrations and architecture are designed and recorded before development starts.
03
Working versions are released in short cycles, each with a changelog, so you follow progress in the software, not in reports.
04
You choose: we run and evolve the system, or we hand it over to your team with the documentation to take it forward.
No generic product dressed up as bespoke. The system is designed for your processes and your people.
Architecture decision records, a changelog per release and technical documentation are part of the work, not an extra.
Supported, widely used technologies, so that any competent team can maintain the system after us.
Single sign-on, roles and permissions are designed at the start, not added before go-live.
A modular structure, so a new area can be added without rewriting the rest.
For a luxury cruise line we built a modular enterprise platform: 36 back-end services behind one portal, from procurement and crew payroll to the loading plan for provisioning ships in port. Read the case study. For an industrial fan manufacturer, a production and shipping application has reached 68 releases, each documented in a changelog. Read the case study.
Cruise
A luxury cruise line
Industry
An industrial fan manufacturer
Sometimes the right answer is a product off the shelf, and we say so. Sometimes the licence that looked cheap becomes one of the largest lines in the budget. How to tell the difference.
, 6 min read
Custom software development is the design and construction of an application for one organisation's processes, instead of configuring a product sold to many. The company gets software that fits its way of working, integrates with its systems and can evolve with it; in exchange, it takes on the cost of building and maintaining it.
At the start, usually yes. Over several years it can cost less, when per-user licences grow with the company, customisation is limited or integration is expensive. It costs more; it lasts longer. Codedesign compares both options before starting, and this article lists the factors.
Mostly .NET on the server, Angular for web interfaces, SQL Server for data, Microsoft Azure or on-premises Windows servers for hosting, and Keycloak or Microsoft Entra ID for single sign-on. They are mainstream and well supported, which keeps a system maintainable by other teams too.
Yes. Every system Codedesign builds is documented as it is built — architecture decision records, a changelog per release, setup and deployment guides — so that it can be handed over to an internal team. Alternatively, Codedesign runs and evolves it.
Yes. Codedesign is based in Taggia, Liguria, and builds software for international groups, with interfaces in the languages people use: recent projects run in Italian, English and German.
Yes, preferably step by step: new modules are built next to the old system and take over one area at a time, while data stays synchronised between the two. It avoids a single, risky switch-over. See systems integration.
Custom software
Tell us where the spreadsheets and manual steps are. That is usually where the system should start.
Request a private meeting