Bend standard software
The process gets reshaped until it fits someone else's model. Whatever doesn't fit moves into spreadsheets on the side.
The process has to adapt to the software.
Low-code platform for process digitisation
Leave requests, complaints, capex approvals, customer portals: with nexxcite you digitise any process the way it actually runs in your company. You build it yourself in low code. If you like, AI does the implementation and you review the result.
If you prefer, AI implements what you describe.
One process after another, all on the same platform
The starting point
Every company has processes that are too specific for standard software and too important for spreadsheets and email. Until now there were three ways to handle them, and each has clear drawbacks.
The process gets reshaped until it fits someone else's model. Whatever doesn't fit moves into spreadsheets on the side.
The process has to adapt to the software.
Specification, quote, implementation, sign-off. The first version arrives after months, and every later change is a project of its own.
High upfront cost, lasting dependency.
Email, Excel and informal agreements. This often works for a long time, until someone changes roles, a deadline is missed or evidence is missing in an audit.
There is no current status, no reporting and no audit trail.
The fourth way
nexxcite is where your business applications take shape: data model, interfaces, workflows, rules and permissions, assembled from ready-made building blocks. You make changes while the system is running, without waiting for a contractor. If you like, AI creates the first draft.
Use cases
nexxcite isn't tied to any one department. Most customers start with one pressing process and then take on the next. Each one goes faster, because the data model, the roles and the experience are already in place.
A common starting point, because the benefit shows early here.
Joiners and leavers involve several departments at once and need a lot of coordination.
Cross-departmental, and every company's approval logic is different.
Alongside the process itself, complete records matter here.
Wherever dates, responsibilities and evidence come together.
Dedicated interfaces for external users, with exactly the data they may see.
The list is a selection. If a process has data, responsibilities and rules, it can run on nexxcite.
Low code in practice
A process almost every company knows: the purchase requisition with amount-based approval. Every step is set up in the editor without programming, and you can change it yourself later.
A form you design yourself: required fields, picklists from your master data, attachments. Which fields someone sees depends on their role.
From the description, AI suggests the commodity group and cost centre. The requester confirms or corrects. The entries become more accurate without anyone needing training.
Team leads approve up to €1,000, heads of department above that, and from €10,000 procurement as well. You can change these thresholds yourself later in the editor.
The approver gets a task and an email. If nothing happens, the platform sends reminders and escalates according to your rule. Deadlines are counted in working hours.
Once approved, the platform creates the order in the ERP system through its interface, using the values from the request. Nobody has to retype anything, and both systems show the same status.
Requesters see their case in the portal, procurement sees its analysis in the dashboard. Both are views of the same data, so nobody has to keep a separate list.
This is how a process like this takes shape in the editor.
You make later adjustments yourself in the editor.
Areas
You divide nexxcite into areas, such as IT, HR, procurement or a portal for your customers. Each area has its own roles, navigation, design and logo, and sees only its own data. To users they are separate applications; for your IT it remains one platform.
Invisible to this role: HR files, purchase orders, customer data
Invisible to this role: IT tickets, purchase orders, customer data
Invisible to this role: IT tickets, HR data, customer portal
Invisible to this role: Everything internal and every other customer
Colours, logo and light or dark display per role. The customer portal appears in your brand, IT service in its own design.
Every role gets its menus and its entry point. Nobody clicks through features that don't concern them.
Reading, creating, editing and deleting are controlled down to the individual record. One area cannot see another area's data.
Each area gets the AI assistants and tools that suit it. They only work with that area's data.
Architecture
Whether your team builds in the editor or AI delivers a draft, everything lands in the same model, runs on the same platform and passes the same permission check. That is why the twentieth application also fits into the existing system.
| One-off solutions, coded or generated | nexxcite | |
|---|---|---|
| Result | Another codebase someone has to understand, test and run | Building blocks on the platform, readable and editable in the editor |
| Security | Each application has its own permission checks, sometimes none at all | One central permission check for everything that gets built |
| Consistency | Every solution is built a little differently | The same building blocks and patterns in every application |
| Change | Redevelop, retest, redeploy | Change in a draft, review, approve and undo if needed |
| Operations | The landscape grows with every application | One platform, updated and run as a whole |
| Knowledge | Lives in source code or in individual people's AI chat histories | Lives in the model, visible to the whole team |
AI as an option
You describe in your own words what the process needs. AI implements it with the same building blocks you use in the editor and places every change in a draft. You review the result, continue in the editor or discard it. Only what a person approves is published.
Set up complaint handling: sales records the complaint, quality reviews it, an 8D report is required for recurring defects.
From now on, every order above €25,000 also needs approval from the management board.
Give the customer portal a light theme in our brand colours and our logo. Customers only see their own requests.
Reversible at any time
AI works with the same building blocks your team sees in the editor. No program code is created that someone has to understand and maintain later.
What AI proposes is collected in a draft, visible change by change. Nothing is published until someone approves it.
The assistant acts within the permissions of its user. If you can't change roles, you can't change them through AI either.
Every draft knows the state before its first change. One click takes you fully back to that state.
Each change records which AI request it came from. So you can still see later why something was set up the way it is.
AI runs through your own account with the AI provider, or with an open model in your own data centre if you prefer.
Security
Whether someone works in the user interface or the customer portal, another system connects through the interface, an AI assistant answers a question or an automation runs overnight: every access passes the same permission check. This applies to AI as well.
Roles define which records someone may read, create, edit or delete, for example “own cost centre only”.
An assistant sees exactly what its user may see. Whatever the permission check filters out is not available to AI.
Single sign-on with existing company accounts, connection to your directory and two-factor authentication.
AI at work
nexxcite offers AI when building, in day-to-day work and in your customers' portal. It works with your data and always with the permissions of the person asking. Where you don't want AI, leave it out. The platform works without it too.
Which open purchase requisitions over €5,000 are still waiting for my approval?
Searched with your permissions
Comparison
When nothing on the market fits, custom development is usually the alternative. That is what we compare nexxcite with, not other standard software.
| Criterion | Custom development | nexxcite |
|---|---|---|
| First working version | After specification, quote and implementation | Built on the process itself, no specification up front |
| Who builds | Development team or contractor | Your business team, in low code |
| Change in production | Requirement, quote, development, delivery | In a draft, with approval, while the system runs |
| The second process | A new project with its own budget | On the same platform, with existing know-how |
| Security | Rebuilt and re-audited per application | One central permission check for all applications |
| Dependency | On the contractor or individual developers | Know-how in-house, platform as a standard product |
| Operations and maintenance | Own infrastructure and updates per application | One platform, one update for every process |
| Cost model | Per application, every time | Platform plus concurrent users |
Custom development has its place. For most business processes, though, the effort is disproportionate. For special cases, open interfaces keep every option open.
Operations and licensing
Operating model, scale and availability follow your requirements.
You decide where the platform runs and where your data lives. Switching the operating model later doesn't require a rebuild.
The platform grows with the number of processes and users. Critical applications run with high availability.
You license the platform and the users working at the same time. Additional processes need no additional licences.
We accompany the first process and train your team along the way. The aim is for you to build the second one yourselves.
Integration
Automation
Live demo
Instead of a sample workflow, we take a case from your company, ideally one for which there has been no suitable solution so far, and build it together with you.