Evaluate an AI-native Odoo alternative
01Tellency agents can work across business modules through a registry of supported actions and exposed business-entity tools. Demonstrate a request that reads records, creates or updates a document and follows the required approval path. Inspect permissions, document status and execution records. Compare the exact AI and workflow capabilities in each proposed platform rather than assuming either vendor’s feature list establishes parity.
Aiinak brings ERP and a productivity workspace together
02Aiinak is the company behind Tellency and offers a broader productivity bundle. Its public platform includes Mail, Meetings, Drive and Recruit alongside AI employees. Evaluate the workspace your team will use with ERP: identity and access, moving from a conversation to a business action, document context and ownership of records. Confirm the included applications, accounts, integrations and usage charges in the proposal. The Tellency starting platform rate is not a statement that every Aiinak application or service is included.
Identify the Odoo plan before comparing
03Record whether the proposal is for Standard or Custom, the hosting choice, user types and the apps your team needs. Include API access, multi-company requirements, custom modules and administration in the discussion. Odoo should not be dismissed as a toolkit requiring every customer to build an ERP from scratch. Tellency also requires discovery, configuration, data preparation and acceptance; neither proposal should hide that work.
Demonstrate a complete operating cycle
04Start with a lead and customer requirement, then follow stock or purchasing, fulfilment, invoice, payment and reconciliation. Add a duplicate lead, a changed order, a partial receipt and an overdue balance. Tellency supports lead duplicate handling and qualification, stock-transfer approval through posting, bank matching and reconciliation approvals, and reminder sending logs. Inspect the resulting records and reports in both systems.
Test manufacturing and retail depth
05Use an approved BOM revision, its component cost estimate, a held work order and a failed inspection. Tellency supports those lifecycle and quality outcomes. For retail, demonstrate gift-card issue and redemption, loyalty transactions and layaway collection or cancellation. Specialist planning, capacity scheduling, devices, payments, ecommerce and reporting require separate validation; overlapping module labels do not establish identical behaviour.
Price ownership over the full operating period
06Request the same user counts, migration history, environments, integrations and support expectations. Separate subscription, hosting, implementation, training, custom work and third-party usage. Agree who tests and fixes changes after updates and who owns exports and integration failures. Do not assume ongoing maintenance becomes free after go-live or that one vendor is cheaper without comparable written proposals.
Agree regional acceptance and cutover
07Include US and Canadian requirements and every Asian or MENA jurisdiction in scope. Use actual required documents and adviser-approved outputs to test tax, payroll, invoicing and reporting. Reconcile trial balances, aged balances, bank positions and stock totals before cutover. Tellency uses around eight weeks as a planning reference; the actual schedule depends on scope, data quality, integrations and acceptance.