Track a service visit
Bring a request, its owner and its status together. First result: one pilot visit tracked from start to closure.
Neoo Forge · Business applications, portals and websites
A tool for your team, a customer portal or a website: start with a concrete need. Choose Forge on its own, or extend Neoo according to your plan’s modules and access rights.
Discovery: €0 / month · Forge Starter: €29 / month, excluding VAT.
This page introduces Forge. Requesting a workshop opens a conversation with the team; it does not create an account, application or subscription.
neoo.× Forge
State the result, the people involved and the data needed.
Scope
Choose a first workflow. Check the plan, modules and access needed.
Build
In Forge, describe the screens and rules to create with Cortex.
Test
Try the workflow with test data, including errors and access permissions.
Validate
Ask the people who will use it to review the result.
Three projects to start with
These examples illustrate projects to build, not preinstalled applications or customer testimonials. Start with a focused workflow your team can test.
Bring a request, its owner and its status together. First result: one pilot visit tracked from start to closure.
Show each customer the information they need. First result: a test record with access permissions checked.
Present your service and a way to get in touch. First result: a page that works on a phone, before adding features.
Connections to other tools, required modules and any services are scoped for each project.
Budget and scope
These are Forge plans, separate from Neoo Starter, Business and MSP. No purchase or paid option is preselected on this page.
EUR, excluding VAT. Monthly equivalent, billed upfront for 12 months. Credits remain monthly. Rounded discount varies by plan. Hosting, deployments and tier-specific modules are included. Credits renew monthly, including with annual billing.
Explore your first idea.
Business modules Read-only preview
Discuss Forge DiscoveryLaunch a business on your own.
Business modules Customers + Invoicing
Discuss Forge StarterBuild a connected business.
Business modules Customers, Suppliers, Invoicing, Payments·PayPal and Neomat
Discuss Forge BuilderGive a growing team structure.
Business modules Customers, Suppliers, Invoicing, Payments·PayPal and Neomat
Discuss Forge ProOperate at a larger scale.
Business modules Customers, Suppliers, Invoicing, Payments·PayPal and Neomat
Discuss Forge ScaleShape Forge around your organisation.
Custom quote
Business modules By agreement
Discuss Forge EnterpriseUser counts come from the Forge pricing grid. The split between creators, end users and Business access still needs to be specified in your offer. Contact Neoo to get started. This page does not create a subscription.
Available from Starter. Packs are valid for 12 months and purchased only when you choose. No automatic overages.
Support depends on your tier. Scoping, data migration, connections and application-specific maintenance need to be quoted if required; they are not unlimited services included by default.
Two ways to build
Forge can be ordered on its own. To extend your Neoo setup, start with the modules you can already access and define the connections to build.
A management offer for your team, or a creation workspace for your project: start with the outcome you need. Forge can also be chosen on its own.
On a small screen, scroll the table horizontally. With a keyboard, focus the table and use the arrow keys.
| Your need | Neoo Business | Neoo Forge |
|---|---|---|
| Everyday outcome | Share a process across teams: customer records, projects and invoicing. | Create a business application or website; extend Neoo or build an independent project. |
| Modules and scope | Neoo Scheduling is included. Specify the modules needed for your process in your Business offer. | Customers, Suppliers, Invoicing, Payments·PayPal and Neomat: access depends on the Forge tier, not a promise of every Neoo product. |
| Application creation | A specific requirement can be addressed through a separate Forge project. | Build with Cortex. Project counts and capabilities depend on the tier. |
| Creator access | Business is billed per user. That price does not define a Forge creator allowance. | Each plan lists a user allowance. Have editor access specified in your offer. |
| End users | The number of Business users determines the subscription. | The creation allowance alone does not establish the rights or number of application end users. |
| Hosting and execution | 25 GB per user. Operational commitments and service levels are defined by your contract. | Hosting and deployments in the Forge plan, according to the tier. Third-party services remain separate. |
| Creation credits | Cortex credits are listed in the Forge plans, separately from the Business subscription. | Monthly credits depend on the tier. One credit is one Cortex instruction, not a token. |
| Maintenance and guidance | Distinguish support, one-off setup and optional ongoing guidance. | Maintenance of your custom application needs a defined scope: hosting is not a maintenance contract. |
| Options and separate costs | Desktop & Apps and Murphy are paid options. Accounting Apps requires Business and Desktop & Apps. | Credit packs are explicit purchases; payment fees and third-party APIs follow their own terms. |
| Integrated or independent | A management offer for the business; MSP serves a different activity, IT services. | Forge can be chosen on its own. To extend a Neoo environment, specify the modules and access required for the project. |
| Price and next step | €59 per user per month, excluding VAT, from 1 user. Options and services are separate. | A separate Forge plan. Monthly prices, annual billed totals and credits are detailed in Forge pricing. |
Not sure which one fits? Tell us what you need and we will point you to the right plan.
Getting started with Forge
Creation happens in the Forge environment, not on this introduction page. Build yourself, work with a partner or request a quote for delivery.
State the result, the people involved and the data needed.
Choose a first workflow. Check the plan, modules and access needed.
In Forge, describe the screens and rules to create with Cortex.
Try the workflow with test data, including errors and access permissions.
Ask the people who will use it to review the result.
Agree on operation and follow-up. Adjust based on actual use.
Simulation: click or use Enter / Space. Holding is optional.
Simulation: click or use Enter / Space. Holding is optional. Simulating approval… Simulation complete · nothing actually publishedThe approval demonstration below is a simulation: it does not publish an application.
Preparing your project
Use these six points to scope the application. They do not replace your plan’s inclusions or the commitments agreed for your environment.
Define
Define the first result and who needs access.
Describe the workflow to build with Cortex in Forge.
Check
Specify sources, exchange directions and required permissions.
Agree on tests, owners and launch criteria.
Operate
Hosting and deployments are included in the Forge grid; specify any particular requirements.
Check support, maintenance, exports and subscription exit terms.
Start with the right building blocks
The custom layer is built with Cortex. A module offered in another plan is not automatically included in yours.
Check the modules available in your plan before describing the extension.
Distinguish people who build from those who use the application.
Add a useful workflow, then check how it works with the rest of the project.
A concrete journey
An illustrative workflow to build for a services company. Connections, automation and permissions must be validated for the project; this is not a ready-to-activate module.
The request enters a single record with its source, timestamp and owner.
Missing context is detected and a focused question is prepared for the customer.
The site, asset and relevant history are attached to the record.
A time and resource proposal is built around the constraints.
A manager confirms the commitment before any external communication.
Status, evidence and next actions remain visible to authorised people.
The request enters a single record with its source, timestamp and owner.
Illustration · scope and connections to validateCheck before opening access
This illustration shows a proposed workflow, not an application being created live. Checks and responsibilities need to be defined for your project.
Track my field interventions, from quote to invoice, with approval before every send.
Advanced security, isolation and audit features depend on the plan and contract; they are not promised for every project.
Evolve with actual use
These project ideas are not a list of included modules. Choose the next improvement based on the actual need, access rights and your plan’s capacity.
Identify what the team actually uses.
Prioritise a concrete point of friction.
Check the modules, credits and connections required.
Test the addition before expanding its use.
Private project or distribution project
A Marketplace listing does not prove installation availability or a right to commercialise. Check a project’s status, rights and arrangements with Neoo before distributing it.
Define your project’s users and operating terms.
Agree on each party’s contribution and responsibility for follow-up.
Check listing, commercialisation and maintenance terms.
Data, deliverables and exit
Portability shown in an illustration is not a contractual guarantee. Specify the data, deliverables and access to retain before committing.
Define useful export formats and arrangements.
Check rights to deliverables and platform dependencies.
Specify the access, timing and services needed for transition.
A clear scope from the start. No universal portability promise.
Before choosing
Yes, Forge can be ordered on its own. Its plans and modules are separate from Business. Extending Neoo requires checking the relevant modules, licences and access rights.
No. Creation happens in the Forge environment. Workshop and plan buttons open an enquiry to the team; they do not create an account or subscription.
Neoo modules: Customers, Suppliers, Invoicing, Payments·PayPal and Neomat for accounting. Build your custom layer with Cortex. Pro includes Builder; Scale includes Pro. Listed capacities replace those of the previous plan. An unspecified capability is not presented as included: clarify the scope of your offer before choosing.
The grid specifies a user count per plan, not a universal licence for every end user. Support follows the tier; licences, application-specific maintenance and services need to be specified in your offer.
One Cortex credit is one instruction addressed to Cortex. It is not a token. Your plan’s quota renews every month, including with yearly billing.
No overage is billed automatically. From Starter, you can purchase a pack. Before choosing, clarify what a zero balance means for new instructions and for applications already deployed.
Review your offer’s terms before committing: cancellation process, notice, any refund and access to projects after cancellation. No notice period or refund is promised here. This page does not create a subscription.
Your first useful result
Bring an example of the need, the people involved and the tools to connect. The scope of the first version is defined with your team. No subscription is created on this page.