Skip to content

Marketplace in preparation

Your module serves only one customer. Prepare it for the Neoo Marketplace.

A feature built for one customer can meet the same need elsewhere. Forge first checks what already exists, you industrialise the module, then its publishing and distribution are scoped with Neoo.

Submit my moduleSee the path

Marketplace in preparation: no module is sold or installable yet. A submission is neither publication nor certification.

Looking for a solution for your business? Explore business solutions

Animated illustration: isolated functions become modules in a shared catalogue.
  • Forge Check before any development
  • Listing, tests and documentation validated
  • Distribution terms agreed

01 / THE REALITY

The same need comes back. The development starts over.

A feature designed for one customer often stays locked in its project. The next customer asks for the same thing, and the work starts from scratch.

Common situations

  1. 01

    The same need, elsewhere

    You rebuild a feature you already delivered because it was never industrialised.

  2. 02

    Variants to maintain

    Each private version is tested, documented and maintained separately.

  3. 03

    Value billed once

    The development is paid per project; it earns nothing afterwards.

  4. 04

    A channel to build

    Listing, terms, billing and support: offering a module to other companies needs a structure.

02 / FROM PROJECT TO CATALOGUE

Forge checks what exists. You industrialise the module.

Sometimes the best development is the one that never needs to happen. Neoo avoids duplication and turns every new request into reusable knowledge.

  1. Forge Check

    Activation, configuration, automation or an existing module: Forge recommends the most relevant option before any new development.

  2. Ownership qualification

    The module’s nature, funding and reuse are qualified before work starts.

  3. Build and tests

    The module is built with Forge, tested in isolated tenants and documented.

  4. Listing validation

    The listing and the module go through functional, technical, commercial and documentation validation.

  5. Distribution terms

    Publishing, distribution and commercial terms are discussed privately with Neoo after qualification.

Marketplace in preparation

PLANNED MODULE TYPES

What the Marketplace is designed to host

  • Extensions
  • Business modules
  • Industry Engines
  • Agents and automations
  • Connectors
  • Expert Services

These steps prepare a publication; they do not trigger it.

Neoo fleet management module: vehicles grouped by driver and status, with their contracts.
Real anonymised screen of a Neoo business module, shown as an example. It is not a Marketplace module.

03 / A concrete example

A business module, designed for more than one client.

Fleet management first answered one company’s need. Industrialised in Neoo, the same module sorts vehicles by driver and by status, with their contracts, for any company that needs it.

  • A shared data model, configurable per client
  • Permissions, tests and documentation specific to the module
  • Each client’s data stays in its own workspace

04 / FOUR PROJECT PATHS

One need, four economic paths.

01

Configuration

The need is resolved without development.

Partner revenue

  • analysis
  • configuration
  • training
  • support

02

Private extension

A feature specific to one company.

Partner revenue

  • analysis
  • project management
  • resale margin
  • deployment
  • business maintenance

03

Marketplace module

A feature industrialised for several companies.

Partner revenue

  • services
  • development contribution
  • recurring revenue
  • distribution

04

Vertical solution

A complete solution for one industry.

Partner revenue

  • licences
  • services
  • migrations
  • training
  • support
  • reseller network

05 / OWNERSHIP

Clear ownership from day one.

Neoo owns

  • Neoo Core
  • Forge
  • the runtime
  • generic components
  • security systems
  • internal APIs
  • the marketplace
  • cross-platform improvements

The partner owns or controls under its agreement

  • its commercial relationship
  • its services
  • its documented expertise
  • its vertical brand
  • its offers
  • the economic rights to its modules
  • its client network

The client owns

  • its data
  • its documents
  • its confidential rules
  • its content
  • its access
  • its business decisions

No project starts without qualifying intellectual property and reuse. Source code for Neoo Core or a Neoo module is not delivered by default.

06 / BUSINESS MODEL

One module, several companies.

An industrialised module can serve customers beyond the first one. Services, development contribution and subscriptions combine around the same asset.

Partner revenue · Marketplace module

  • services
  • development contribution
  • recurring revenue
  • distribution

Recurring modules

Receive a share of subscriptions generated by modules you initiated or commercialised.

Your services, your offers

Build a managed offer around Neoo: support and follow-up, optimisation and automation, tailored projects, or integrations and governance. You set your own consulting and service fees; Neoo takes no commission on these services. Define scope, responsibilities and billing in your proposal.

Licences and usage

The Partner of Record is the partner assigned to the customer account. The model provides for that attribution to continue across renewals, added users, upgrades, modules and Forge or AI consumption, including self-service, under the contract. Neoo does not approach the account directly to bypass its partner. Customers remain free to request a change.

Partner levels depend on skills, customer acquisition, onboarding, support and ongoing account management. Distribution, Forge and AI usage, and Marketplace publishing terms are discussed privately after qualification. Applying activates no economic entitlement and guarantees no revenue.

FAQ

Before you prepare a module.

Is Marketplace open for purchases?

No. The catalogue of installable modules is in preparation. This page enables no purchases, installations, module trials or verified reviews.

Can I publish in the marketplace?

Yes after functional, technical, commercial and documentation approval of the listing and module. Under the applicable programme, rights and allocations are defined before the project begins.

Is a Forge project automatically published on Marketplace?

No. Marketplace is in preparation. Delivery for a client, operation and any future publication or distribution are separate scopes to assess and agree. An application does not activate them.

What happens if the feature already exists?

Forge Check recommends the best existing feature, configuration, automation or module before new development is considered. Under the applicable programme, rights and allocations are defined before the project begins.

Who owns the module?

It depends on its nature, funding, reuse and the agreements made. Ownership is qualified before work begins. Under the applicable programme, rights and allocations are defined before the project begins.

How am I paid on subscriptions?

The calculation depends on the role, module origin, distribution, support and the marketplace listing terms. Under the applicable programme, rights and allocations are defined before the project begins.

Who provides support?

The partner generally provides first-line and business support; Neoo operates Core, Forge and the runtime within the agreed scope. Under the applicable programme, rights and allocations are defined before the project begins.