Tellency
AI-native ERP · Cross-module agents

AI-native ERP: agents that work across your business.

Tellency brings ERP, CRM and agents into one connected platform. Agents can work with business records and execute supported workflows across modules, using the access, approvals and execution controls configured for your organization.

Architecture
Cross-module agents
Work
Read, create, update, execute
Access
Roles and permissions
Oversight
Approvals and action logs
01 — Buyer's guide

From a request to an ERP action

AI-native means agents can participate in operational work, beyond answering questions about a dashboard. Evaluate the full path from your request to the resulting business document.

Connected agents across ERP modules

01

Tellency’s agent architecture combines a registry of business actions with tools for exposed business entities. An agent can find records, use required inputs and request actions across connected modules. Cross-functional work can span finance, sales, procurement, inventory, manufacturing, CRM and people. The available tools and permitted execution depend on the agent’s role, configured access and enabled workflows.

Create documents and move work forward

02

The action catalogue includes purchase-order creation, purchase invoices, goods receipts, sales orders, sales invoices, quotations and customer records. These are concrete business operations, not just generated text. Bring a representative request and ask the team to demonstrate the selected action, required fields, document status and result in your proposed configuration.

An illustrative purchasing workflow

03

For example, ask an agent to look up a supplier and prepare a purchase order for specified products, quantities and prices. Review how the agent resolves records, handles missing information and creates the document. Where approval is required, inspect the pending request, decision and resulting action. This is a demonstration scenario, not a claim about a named customer’s results or a promise of unattended purchasing.

A sales and finance demonstration

04

Start with an anonymized customer and an agreed commercial request. Demonstrate a supported customer lookup, quotation, sales order or invoice action, then inspect the resulting record and approval state. Confirm which actions are separate steps and which handoffs your proposed workflow supports. This gives sales and finance teams a concrete way to evaluate agent-assisted work without assuming that one request automatically completes the entire order-to-cash cycle.

Tellency within the Aiinak productivity bundle

05

Aiinak Inc is the company behind Tellency. Alongside ERP and CRM, Aiinak offers a broader productivity workspace with AI employees, Mail, Meetings, Drive and Recruit. Evaluate the applications your team needs together: which records each application owns, how identity and access work, and which integrations are demonstrated. Confirm the included applications, users, services and usage in the proposal; Tellency’s starting platform rate does not establish the price of every Aiinak product.

Permissions follow the work

06

Agent actions are governed by declared ERP permissions and execution controls. Department-specific agents can have different module access from cross-functional agents. Configure access around actual responsibilities: the ability to find a document should not be treated as permission to approve or post it. Test a permitted action and a refused action using the intended agent role.

Approvals and execution records

07

Tellency includes approval handling and action logs in the agent execution path. Review which actions run directly, which require approval and how document-level workflows apply. Inspect the actor, inputs, status and outcome available for review. Ask how failures, rejected requests and corrections are handled before relying on an automated process.

Scope each workflow before rollout

08

Cross-module architecture does not mean every agent can perform every action without restrictions. Some business entities are intentionally excluded from agent exposure, and supported operations retain their own workflow requirements. Agree the enabled actions, integrations, approvals and acceptance criteria for your deployment. Specialist industry controls and external services require their own demonstration.

Evaluate an AI-native NetSuite competitor

09

Tellency is a direct ERP and CRM competitor to Oracle NetSuite. Compare the required records, workflows, agent actions, controls, deployment and total cost using the same acceptance scenarios. Platform pricing starts at $79 USD per user per month; implementation, integrations, support and AI usage are confirmed in the proposal. Managed cloud and self-hosted options are available. Around eight weeks is a planning reference, with the actual schedule agreed from scope and readiness.

02 — FAQ

AI-native ERP and agent questions

What is an AI-native ERP?
In Tellency, it means agents work with connected ERP and CRM records and can execute supported business actions across modules. The operating model includes permissions, approvals and execution records, alongside natural-language queries.
Can agents control all ERP modules?
Tellency is designed for agents to operate across ERP modules. Each agent works through enabled tools and business actions with its configured role and permissions. Cross-module access is different from unrestricted access to every internal table or operation; confirm the actions needed for your workflows during evaluation.
Can an agent create transactions rather than just suggest them?
The action catalogue includes creation of business documents such as purchase orders, goods receipts, sales orders and invoices. Demonstrate the exact action, document lifecycle and approval requirements in the proposed environment.
Does every action need human approval?
Approval behavior depends on the action, configured controls and document workflow. Review direct execution and pending-approval scenarios for the intended agent role rather than assuming one policy applies to every operation.
Is Tellency an AI-native alternative to Odoo?
Yes. Tellency is an ERP and CRM alternative to Odoo, with agents operating through supported business actions across modules. Compare the exact product configurations, required workflows, permissions, integrations and total proposal scope rather than assuming complete feature parity.
Is Tellency part of Aiinak’s productivity offering?
Tellency is Aiinak Inc’s ERP and CRM product. Aiinak also offers a wider productivity bundle including Mail, Meetings, Drive and Recruit. Confirm application inclusions, accounts, integrations and usage terms in your proposal.
How should we test an agent workflow?
Provide anonymized records and an expected result. Check record selection, required inputs, permission enforcement, document state, approval decisions, execution records and failure recovery. Agree these criteria before rollout.
Next step

See agents work through your ERP scenario.

Bring a business request, representative records and your approval requirements. Evaluate the action and its result with the product team.