Monthly full nimitFlow licenses with consulting for 2 private-sector customers

How the brief came about

The brief for this case comes from the orders of 2 private customers: a full nimitFlow licence on a monthly basis, paired with consulting services (Consult Services). From the items ordered, the customers wanted to use nimitFlow for data work and wanted consulting services alongside the licence.

The documents for this case are the quotations, purchase orders, invoices and receipts of the 2 customers, and the first customer's service report. No document states each customer's intended use, so we describe the brief only from the items the customers ordered.

Requirements and constraints

The scope of work was set according to the items in each customer's sales documents. The main requirements were as follows.

• Full licence (Full License), charged monthly, for a term of 3 months per customer
• Consulting services were purchased together with the licence. The scope and duration of the services were set by each customer's documents.
• For the first customer, the system was installed on a server and the full-edition tools were enabled, including the Share system for teamwork.
• We hold no service report in our documents for the second customer, so that customer's installation details do not appear on this page.
• We do not publish the prices paid by each customer.

What the consulting services did in this case

For the first customer, we installed nimitFlow on a server, opened the feature overview page, tested sample Python scripts, enabled the Share system and Data View, and then summarised the enabled tools for the customer. Every step is recorded in the service report. The steps were as follows.

1. 1

   Install the nimitFlow system on a server

   We installed the core nimitFlow system on a server and then opened the feature overview page (Feature Overview Diagram) so the customer could see all the available tools.

2. 2

   Test sample Python scripts

   We tested sample code in the Script tool of the Toolbox to confirm that the system can run Python scripts.

3. 3

   Enable the Share system and Data View

   We enabled the Share feature so users can share Flows or edit them together as a team, and enabled Data View (expanding the view of each box's data) to check data at intermediate points in a Flow.

4. 4

   Summarise the enabled tools

   We summarised the enabled full-edition tools as a list in the service report, so the customer can check which tools the licence covers.

We installed the system and ran the sample script first, to confirm that it worked before enabling other features. The steps above apply to the first customer only.

Deliverables

The 2 customers ordered a full nimitFlow licence on a monthly basis with consulting services. According to the service report, what was delivered to the first customer was as follows.

• Script: write Python scripts in a Flow
• Data Pipeline: connect CSV files and databases
• Data Cleansing (cleaning data) and Data Transform (converting data formats)
• Data Analytic and Machine Learning
• Condition: set conditions in a Flow
• Alert & Dashboard: alerts by email and LINE
• Share: share Flows and edit them together as a team
• Generate Code: generate code to run outside the system
• Run Code: run a Flow in the background even after the browser is closed

Confirmed results from the sales documents and service report

The 2 private customers ordered and paid for the full nimitFlow licence with consulting services in 2025, according to the purchase orders, invoices and receipts. For the first customer, the service report confirms the system installation, activation of the full features and testing of the sample Python scripts.

This case has no figures measuring usage after installation and no document summarising the results of the consulting services. We therefore report only what the documents can confirm, and do not conclude which Flows the customers built or what results they obtained from the system.

What we learned

This work offers 3 principles for selling platform licences with consulting services.

• Confirm the installation with work that actually runs, not just a screen that opens. In this work we tested sample Python scripts in the Toolbox, so the delivered system had already passed testing with a script that actually runs.
• A licence must come with a documented list of what is enabled. The tool list in the service report lets both parties check and agree on what the licence covers, and compare it with the next version when the tools change.
• A Flow that a team builds together must allow data to be checked at intermediate points. Enabling Share and Data View from installation lets the people who continue editing a Flow see the data in each box and work on it together.

How to apply this approach to your team

If your team has data work that regularly requires pulling, cleaning and analysing data and sending alerts, you can use the same model as this case: rent a nimitFlow licence on a monthly basis, paired with consulting services. What needs adapting is the deployment model, the data sources and the first job used for training.

• Choose a first job with data ready, such as CSV files or a database that must be summarised regularly, and work on it with the consultant during the licence period.
• Define who in the team builds and maintains Flows, and who the users are that Flows are shared with.
• Check the tool list of the current version against your work before ordering.
• Before the monthly licence reaches the end of its cycle, plan whether to continue or how to change the way you use it.