Business work connects. Its context should too.

A connected business workspace brings records, conversations, tasks and approvals into a shared company context. Tenxora is being developed around that goal, so people and AI can carry work between teams without losing the decisions and evidence behind it.

Five foundations being developed and validated

• Accounting & Finance: business accounting, receivables, payables, assets, reporting and controlled close.
• Purchasing: requests, suppliers, orders, receipts, invoice matching and settlement.
• People: employee and organization records, employment information, leave, hiring and appraisals.
• Messages: human and AI conversations linked to context, proposals, approvals and handoffs.
• Sites: business websites, forms and domain management.

These are product foundations under development. A capability’s existence in software does not establish that every customer workflow is ready or available.

Follow a supplier invoice through the workspace

1. Purchasing provides the context. A purchase order says what was ordered; a receipt records what arrived. The invoice needs to be assessed against both, not read in isolation.

2. Messages carries the question. A finance colleague asks about a mismatch. The discussion should link to the relevant records so the purchasing colleague can answer the actual exception.

3. AI prepares a proposal. Within its permitted access, an AI role gathers the evidence and drafts a match summary. Missing information remains visible instead of being silently filled in.

4. Finance makes the decision. An authorized person checks the proposal and approves the relevant action. Posting an invoice and releasing a payment are distinct decisions; preparing one does not authorize the other.

5. The outcome remains attached. The record should show the approved action, its result and unresolved work. A failed attempt should be visible before anyone retries.

This is an illustrative intended workflow. It does not describe a live customer deployment.

Connected does not mean unrestricted

Shared context must still respect roles. A purchasing task should not expose unrelated employee information. A People workflow may require equipment from Purchasing and a budget check from Finance, but each participant should receive only the information needed for its work.

Sites has a different responsibility: public pages and forms must expose only intended public information. Connecting a website to business processes must preserve that public/private boundary.

Evaluate a complete process

For a design-partner conversation, bring a concrete workflow: the records it uses, the tools it crosses, its approvers, common exceptions and what a correct completed outcome looks like. This gives us something useful to validate beyond a feature checklist.

Tenxora is in development and validation. Country requirements, migration needs, implementation effort and readiness must be assessed for each use case. Final pricing, pilot dates and fixed savings have not been announced.

Explore the future of work vision and intended AI employee responsibilities, or read our company background.