Prepare for the conversation
Start with a concrete need.
Describe the work your instrument should make easier. Download a file to keep or share yourself.
Your brief, at your own pace.
Choose the relevant topics, then describe a process: how it starts, who takes part and what gets in the way today. You can review the file before downloading it.
This brief stays in this page. Downloading it does not send it to Nordis. Avoid sensitive data; your input is not saved automatically.
Things to consider
- The start and finish
What starts the work? When do you consider it complete?
- The people involved
Who receives the request, who acts and who needs to approve? Use roles rather than names.
- Current tools
Where is the information kept? Which tools need to stay, and what data moves between them?
- A specific obstacle
Describe a missed step, duplicate entry or typical wait using a fictional example.
- The first priority
Which workflow should come first? Note known constraints and deadlines without assuming they are feasible.
Download, then keep or share the file.
Complete the brief below and download the text file to your device. You can review it, keep it or share it yourself through the channel you already use with Nordis. If you do not have an established channel, keep it for a future conversation. This page sends nothing to Nordis, and downloading does not confirm that a request has been accepted.
Your text file · local preview
The download uses this text and your latest choices.
Project handover
You own the entire custom project.
Construction and setup are a defined, paid initial project. You receive the source code, project-specific configurations, documentation and deployment instructions.
You can change teams or hosting providers without mandatory dependency on Nordis. Hosting, support and future changes still need to be planned; outside services retain their terms and fees.
Rights, outside services and costs
You receive the source code specific to the project, custom configurations, documentation and deployment instructions. You control your data and access. Access is handed over through the project’s authenticated mechanisms, never through the public brief.
You can take over the project, host it elsewhere and have another team develop it further. There is no mandatory dependency on Nordis or hidden Nordis usage royalty. Your custom project is not published without your agreement.
Construction and setup are a defined, paid project. After delivery, you don’t pay a Nordis subscription to use your instrument. Hosting remains a cost. Support and changes are separate work, with stated terms and costs.
Open source dependencies retain their licences; outside services retain their terms and fees. We identify them before the project. These licences do not hold back your specific code: they avoid pretending to transfer ownership of a public framework or an outside account without respecting its terms.
Examine subscriptions before replacing them.
We review what is used, what overlaps and what needs to stay. A custom project also needs to be assessed against its build, hosting and maintenance costs.
How to compare costs
Possible gross savings are the subscriptions actually removed over a time horizon chosen with you. To assess net savings and the break-even point, we also count the paid initial build and migration, then hosting, retained services, maintenance and relevant changes over that same horizon.
No project price, hosting cost or payback period is assumed here. A custom tool cannot replace all software and is not cost-effective in every situation. Scoping also helps recognize when keeping an existing tool is the better choice.
Questions that deserve a clear answer.
Do we have to replace all our tools?
No. We first look at what works and what makes the work harder. The project may keep a tool, add a custom function or provide an exchange between systems. A connection still needs confirmation based on the provider’s access options and capabilities; the existence of a tool does not guarantee that it can be connected.
How do we know what the project includes?
Scoping describes the users, functions, workflows to check and exclusions. The initial project includes construction and setup within the agreed scope. Deliverables, dependencies and validation terms need to be specified in the agreement. A request that changes that scope is discussed before it is added.
What do we need to plan for our data and access?
We identify the necessary data, its source and the people authorized to view or change it. If data needs to be migrated, the project must specify preparation, checks and responsibilities. For the first brief, use descriptions and fictional examples: do not include personal information, passwords or confidential documents.
Are outside services and subscriptions included?
No external subscription is assumed to be included. A connection may require an account, a paid option or usage fees from a provider. The accounts to use, authorizations, costs to cover and dependencies are clarified before selecting that connection. Those services’ terms and limits still apply.
What are the rights to the code and data?
You own the entire custom project: source code specific to the project, custom configurations, documentation and deployment instructions. You control your data and access. You can take over, host elsewhere and develop the project further with another team, without mandatory dependency on Nordis or hidden Nordis usage royalty. We hand over access through the project’s authenticated mechanisms, never through this website. Open source dependencies and outside services, identified before the project, retain their licences and terms; we do not claim to transfer their ownership. Your project is not published without your agreement.
What remains a cost after delivery?
You don’t pay a Nordis subscription to use your instrument. Hosting remains a cost. The project defines its environment, account ownership and operational responsibilities. Paid outside services you choose retain their fees. Changes requested later are separate projects; support terms are specified in the agreement.
How do support and changes work after handover?
Support terms are defined in the agreement: what is covered, who handles it and under which conditions. Recurring or unlimited support is not assumed to be included. Later improvements and changes are described and billed according to the agreed work. A gap in the delivered scope and a new requirement need to be distinguished before deciding what comes next.
What should we prepare to get started?
Choose a process that is causing difficulty. Describe its stages, the people involved, the tools used and an example without sensitive data. The brief on this page helps you put that into writing. Download the file to keep it or share it yourself through a channel already established with Nordis. Downloading does not send a request or reserve a project.