BrilliantisCore implemented · introduction by agreement

CRM, quotes & business operations

Connect business records.
Keep the full picture.

Brilliantis brings CRM and business operations together: from a business partner and quote to contracts, invoices and payment allocation. People share one interface; connected software uses documented business actions.

A WORKFLOW IN CONTEXT
  1. 01Prepare a quote
  2. 02Track the contract
  3. 03Match invoices & payments

An example of a connected business workflow. Data migration and your specific integrations are agreed in advance.

For companies and service providers connecting sales and administration. We choose a starting point around a specific workflow and the systems you already use.

THE IMPLEMENTED FOUNDATION

What you can build on.

01

Customers and sales

Business partners, leads, pipeline and products form the foundation. Quotes bring line items together and preserve the state recorded when issued.

02

Quotes and contracts

An accepted quote is linked to a contract. Versioned actions and retry protection help prevent duplicate records after a connection failure.

03

Invoices and payments

Incoming and outgoing euro invoices, numbering, issued records and full cancellations. Allocate account transactions and payments, and track outstanding items.

04

Operational reporting

Journal entries, balances, monthly figures and open items support closing preparation. Pipeline estimates, booked revenue and liquidity remain distinct.

05

Campaigns and briefings

Structure campaigns, content planning and collaborations. Versioned text briefings and recorded manual hand-offs keep working editions traceable.

06

Integrations and access

Documented REST APIs, roles and limited agent access support specific integrations. Data flows, permissions and external execution require explicit setup.

A CLEAR BASIS FOR YOUR DECISION

Implemented scope. Your introduction.

Already implemented

  • Standalone CRM/ERP core with a web interface and documented API.
  • Quote, contract and invoice workflows, payment allocation and a journal.
  • Roles, traceable changes, and backup and restore workflows.

Agreed before introduction

  • Suitable modules, migration, user roles and acceptance criteria.
  • Your installation, managed operations, support scope and specific costs.
  • Required accounting, payment, e-invoicing and other provider connections.

The standalone Brilliantis core is MIT-licensed. Each organisation uses its own installation, database and access management. Setup, migration, operations and support are separate services; the intended version and licence documentation form part of the introduction.

FROM THE FIRST WORKFLOW TO HANDOVER

Start with a defined scope.

  1. 01

    Understand the task

    Walk through a real workflow, your users and current systems. Identify the needed functions, permissions and data.

  2. 02

    Agree and test a pilot

    Agree scope, costs, responsibilities and acceptance criteria. Test migration and integrations using suitable sample data before regular operation.

  3. 03

    Handover and operations

    Introduce the team to the agreed workflow. Document access, responsibilities and operating arrangements; commission ongoing support as needed.

SUPPORT FOR YOUR PROJECT

Plan the right introduction.

No blanket subscription or fixed implementation price is promised here. We quote the product introduction, integrations and operations against the agreed scope.

Request an introduction
BEFORE YOUR DECISION

Questions about Brilliantis

Does Brilliantis replace a complete accounting system?

That depends on your requirements. The implemented scope supports business records, a journal and closing preparation. It does not produce a complete statutory balance sheet or tax return. Requirements such as DATEV-EXTF, payroll, fixed assets, foreign currencies and tax filing need separate review; the journal CSV export is not a DATEV export.

Is Peppol included automatically?

An invoice in Brilliantis does not mean Peppol transmission is configured. Format, validation, receipt, delivery and any access point are agreed for your workflow. Our e-invoicing consultation helps with this decision; setup and provider fees are quoted separately.

Can I operate Brilliantis independently?

The standalone core does not require a NeuroFunken account. Self-hosting requires a suitable installation and ongoing operations. We can provide setup, adaptation and support under an agreed scope and price.

Do connected agents act automatically?

API access alone does not start an automated business process. Runtime, permissions, allowed actions and required approvals are explicitly defined. Introduction starts with one bounded, reviewable workflow.

Compare all products

A good place to start.

neurofunken knowledge assistant

Hello! What would you like to improve? I can explain our services and help you find a useful next step.

Replies from our editorial knowledge base.

Please do not enter confidential information. Privacy