VOCE designs your next operational capability: bespoke business systems powered by AI agents to prepare accounting records, compare contracts, follow a booking or reconcile sales. Free up time for clients and decisions. Shape your tools around your organisation. The Post-SaaS pathway defines what can be automated, built or replaced, then assesses the business case.
VOCE combines a multidisciplinary approach with knowledge of Chinese technology and commercial ecosystems. This perspective brings together how teams work, how distribution operates, how audiences behave and how systems are designed.
For a museum, hotel or international business, one project can connect client relationships, distribution and internal operations. Technology selection must consider actual capabilities, integrations, languages and the legal requirements of each market. The aim is to build a system suited to your business and demonstrate its value through a concrete workflow.
Before committing your organisation, you need to see the system work, examine its results and know who is accountable. The VOCE pathway structures that decision around five tangible elements.
LÉGIS, VOCE’s beta legal service, is available to try today. For your project, the demonstration to be built follows an entire workflow: an initial document or request, agent processing, approval and a usable output. A sales and commission reconciliation workflow can, for example, be scoped for a hotel or museum.
Try LÉGIS →The pilot should compare the baseline with the proposed process: time per case, errors, execution cost and frequency of human intervention. The protocol, sample and acceptance criteria are agreed before measurement. The calculator presents financial assumptions separately; its outputs are not observed client performance.
Build your financial scenario →The proposal should specify the delivered system, its functions, integrations and data migration. It sets out rights to code and third-party components, data access, training, maintenance, milestones and exit arrangements. You receive a defined scope to examine before committing.
Review the delivery pathway →Your project dossier should bring together architecture, suppliers, processing locations and data responsibilities. It records the selected controls, available evaluation results and security and incident procedures. The European framework below and the privacy policy provide the first public reference points.
Review the European framework →Before launch, the proposal should identify the contributors, their expertise and responsibilities for design, integration, acceptance and operation. It specifies your contact, support arrangements, agreed response times and escalation process. Any partners are identified for the engagement concerned.
Scope your project with VOCE →An invoice can be extracted, matched to an order and prepared for approval. A contract can be checked against your reference clauses, with deviations flagged. A booking can feed client follow-up and commission reconciliation. VOCE proposes to design these workflows around your rules, with human intervention at the points you define.
Prepare accounting documents and reconciliations, flag discrepancies, research legal sources and compare clauses. Each output should be traceable to supporting documents and routed to the designated reviewer.
Connect client requests to records, bookings and sales. Organise follow-up actions, distributor exchanges and commission checks, within available access rights.
APIs connect applications. MCP can provide an assistant with controlled access to tools. Neither replaces business authorisation: a generated suggestion does not, by itself, become an approved transaction.
Ticketing, audience and donor relationships, distribution and reconciliation. Define the data that remains under institutional control and the exchanges required with partners.
Connect the property management system (PMS), CRM and booking channels. Examine guest journeys, duplicate entry and synchronisation rules before replacing a function.
For online travel agencies and their partners: availability, rates, commissions, cancellations, refunds and reconciliation. Connections depend on available APIs and distribution agreements.
Assist or automate bounded tasks: document preparation, reconciliations, documentary research and clause comparison. Accounting entries, payments and consequential conclusions follow approvals defined with the responsible specialists.
Scope is built around each organisation’s processes. These examples describe engagements to be assessed; they are neither a catalogue of available products nor client references.
Functional and contractual inventory, data map, cost comparison and retained responsibilities. Deliverable: a decision brief that also documents reasons not to migrate.
One process, authorised data and measurable acceptance criteria. Deliverable: test results, observed costs and conditions for reverting to the original system.
Migration, data reconciliation, training and a cutover conditional on acceptance. Deliverable: operating procedures, service commitments and an exit plan.
The transactional database holds business state. Identity and access management (IAM) limits permissions. Documented interfaces and logs make actions traceable. Backups and recovery are tested. AI inference is a separate, replaceable layer evaluated against the selected tasks.
Qwen, Alibaba’s model family, and other models with accessible weights may be assessed against their licences, performance and hosting constraints. A model choice determines neither the hosting provider nor data location. Private and dedicated deployments are options to be assessed.
VOCE already applies this separation of functions in LÉGIS, its beta legal service. A business interface calls an API running on Cloudflare Workers. A curated catalogue of official sources constrains generation; rules check references and response structure. Cloudflare Workers AI runs Qwen and GLM models. A D1 database manages quotas and operating metrics. These components illustrate an architecture distinct from the AI model, with service-specific controls. The current legal scope covers France and the European Union; this example is not an ERP/CRM deployment reference.
Examine LÉGIS →Euros excluding VAT. Prefilled values illustrate how the model works; they are neither a quotation nor a client reference. Replace them with your assumptions, using equivalent functionality and service levels.
Local calculation, with no transmission or storage of amounts. Values remain available when switching language on this page; reloading resets them.
| Year | Current system | Alternative architecture | Difference |
|---|
If migration costs rise by 20% and coexistence lasts six additional months (maximum: 36 months): .
Investment is counted once at the start. Annual increases apply in months 13 and 25. During coexistence, the alternative bears its own costs plus current subscriptions and retained legacy administration. Retained licences must exclude subscriptions already counted during coexistence. The annual table includes investment in year one; cumulative curves include it at month zero.
The model assigns no value to productivity gains, additional revenue or the cost of capital. Exit penalties and supplier fees must be included in the relevant inputs. Incidents and migration risk are not priced. Results are rounded to whole euros; the CSV retains two decimals. A favourable difference is not a guaranteed saving.
The mission must identify the business owner, operator and people authorised to approve a critical action. Security, confidentiality and exit conditions are documented before the pilot. For an international organisation, scoping identifies jurisdictions, data location and transfers, working languages, support hours and local rules to integrate. Training prepares teams to operate the system and resume a process during an outage.
The Post-SaaS pathway incorporates data protection and AI governance from the design stage. Each engagement’s deployment dossier must identify applicable requirements and the measures agreed with your organisation.
Define purposes and lawful bases, minimise processed data, set retention periods and enable individual rights. Identify controller and processor roles, formalise the necessary agreements and assess whether a data protection impact assessment is required.
Document processing locations, subprocessors and any transfers outside the European Economic Area, with appropriate safeguards. Specify access, encryption, deletion and the terms of any data reuse by suppliers.
Classify the system by intended purpose, risk level and each participant’s role. Determine applicable duties, including transparency, AI literacy, documentation and human oversight.
Define access permissions, traceability, backups and incident response procedures. Plan recovery tests and exit arrangements. Sector-specific requirements are assessed against the activity concerned.
Specific commitments and evidence of implementation are defined for each project. This approach is not a blanket compliance certification.
These VOCE analyses examine third-party software and its mechanisms. Inclusion does not imply a partnership or an integration delivered by VOCE. Articles are in French; each publication details scope and limitations.
Bring a concrete case: accounts to reconcile, contracts to review, bookings to follow or data to re-enter. Scoping identifies the tasks to delegate, the system to build and the criteria for deciding whether the investment is justified.
Scope your first use case →