Frequently Asked Questions

Zorinthia is an independent data advisory firm that helps leadership teams make clear, defensible decisions about data and automation — before software, vendors, or implementation commitments are made.

Most data and automation projects fail not because the technology was wrong, but because the foundation was missing:

• Data sources were poorly understood.
• Governance was unclear.
• Quality issues were discovered after go-live.
• Ownership was never assigned.

Zorinthia works upstream of all of that — through a data strategy assessment, data governance assessment, or data maturity assessment — helping leadership teams understand what they have, what it costs to fix it, and what the right sequence of decisions actually is. For organisations evaluating analytics or AI investments, an AI readiness assessment clarifies what foundations need to be in place first.

No software is sold. No systems are built. The only output is clarity. Learn more about the advisory approach.

The distinction matters more than it appears.

A data consultant's business model depends on implementation. Revenue is generated by scoping large projects, staffing teams of analysts and engineers, and billing across multi-month engagements. This creates a structural incentive to recommend solutions that require build work — even when the client's actual problem is decision clarity, not execution capacity. The bigger the project, the better the commercial outcome for the consultant.

A data advisor operates differently. There is no implementation revenue. No team to staff. No vendor relationship to protect. The engagement ends when you have the clarity to make a good decision — not when a system is built. This means the advice is not shaped by what generates the most billable hours downstream.

In practice: if your organisation already has capable internal teams or can hire implementation partners, what you often need is not more delivery capacity — but independent judgement on what to build, in what order, and why. That is what advisory provides.

Most organisations already have capable technical teams and existing analytics tools. The challenge is rarely lack of technology — it is a lack of clarity around data ownership, governance and decision priorities.

Organisations typically seek a diagnostic when they experience issues such as conflicting reports across departments, slow decision cycles due to data delays, or difficulty scaling analytics initiatives. It is also common before launching large data or AI programs, after mergers or system changes, or when leadership wants an independent view of current data capabilities.

A data diagnostic — whether framed as a data maturity assessment, data governance assessment, or data strategy assessment — provides an independent view of how data actually flows through the organisation. It identifies where reporting delays occur, where definitions conflict across departments, and where data governance responsibilities are unclear.

Without this step, organisations often invest in new analytics platforms or automation initiatives before the underlying data structure is stable. This can result in expensive systems that deliver inconsistent metrics or limited operational value.

An independent diagnostic focuses on three outcomes:

• Identifying the highest value data opportunities across the business
• Clarifying ownership and data governance responsibilities
• Prioritising initiatives that improve decision making before new technology investments are made

The goal is not to recommend tools. The goal is to ensure the organisation understands where data strategy will deliver measurable value and where risks and opportunities currently exist.

A data diagnostic report provides a structured assessment of how data supports decision-making across the organisation. The report focuses on identifying risks, governance gaps, and opportunities for improving how data is used operationally.

Typical sections include:

• Current Data Landscape — Overview of the major systems and data flows across the organisation. This includes how operational data moves between systems such as ERP, CRM, analytics platforms, or operational databases.
• Key Findings — Summary of the most important observations discovered during interviews and system review. These often include conflicting data definitions, reporting delays, unclear ownership of key datasets, or fragmented data pipelines.
• Assumptions and Constraints — A clear description of assumptions made during the assessment, such as data availability, system limitations, or organisational boundaries. This helps leadership understand the context in which the analysis was performed.
• Risk Assessment — Identification of risks that may affect reporting accuracy, decision-making, or operational efficiency. This can include governance gaps, data quality issues, inconsistent metrics across departments, over-reliance on manual processes, or compliance exposure under regulations such as POPIA or IFRS.
• Data Ownership and Governance Observations — Evaluation of how responsibilities for key datasets are currently distributed across teams. This section highlights where ownership is unclear, where governance processes could be strengthened, and where regulatory accountability needs to be more clearly defined.
• Opportunities for Improvement — Identification of areas where better data management, analytics, or automation could improve operational performance or decision speed.
• Recommended Priorities — A prioritised list of initiatives that leadership can consider after the diagnostic. These recommendations focus on practical improvements rather than technology-driven solutions.
• Executive Summary — A concise overview of the most important findings, risks, and recommended next steps for leadership teams.

For organisations with 1–249 employees, automated invoice processing typically follows a straightforward flow — but the decisions made before automation starts determine whether it actually reduces manual work or simply moves it.

How the flow typically works:

• Invoices arrive — via email, supplier portals, or directly from vendors. Most arrive as PDF attachments.
• Data is extracted — OCR (optical character recognition) reads the invoice and pulls out vendor name, invoice number, date, line items, and totals. Quality here depends heavily on how consistent your vendor invoice formats are.
• Validation runs — the extracted data is checked against purchase orders, vendor master data, and GL codes. Mismatches or missing fields are flagged for manual review.
• Approval routing — invoices within defined thresholds move to the right approver automatically. Invoices outside those thresholds, or with exceptions, go to a queue.
• Posting to the accounting system — approved invoices are posted to Sage, QuickBooks, or Xero via API integration.

Where it breaks for smaller organisations: The challenge is rarely the software. It is the data. Vendor names are inconsistent. Invoice formats vary widely across suppliers. GL codes are missing or wrong. Purchase orders were never issued. These are data quality and governance problems — and automation amplifies them rather than solving them.

Before choosing a tool, it is worth understanding what percentage of your invoices would pass straight-through without manual correction, and what your true exception rate is. That answer determines whether automation saves time or creates a new queue to manage. Read the full guide to automated invoice processing.

No. Zorinthia operates exclusively as an advisory firm. There is no software to sell, no implementation services, and no vested interest in any vendor or technology platform.

Zorinthia's output is guidance: what your data actually looks like, where the risks are, what the right sequence of decisions is, and what you should require from any implementation partner or vendor you engage next. The advisory identifies what is broken in how your team handles data decisions; you can fix it yourself or hire someone else to build it.

This matters because vendor-independent advice is structurally different from advice given by firms that benefit from recommending specific tools. When a firm sells implementation alongside advisory, the recommendation is never fully independent — the commercial incentive shapes it.

This advisory firm operates exclusively on Phases 1 and 2 — foundation work only.

Phase 1 — Source: Data and automation diagnostic, data strategy assessment, data governance assessment, and data maturity assessment. Understanding what data you have, where it lives, what quality issues exist, and what decisions need to be made before anything is built. For organisations considering analytics or AI, an AI readiness assessment evaluates whether foundations support those investments.

Phase 2 — Integration: Evaluating integration requirements, data quality controls, and lineage mapping. Understanding what it would take to connect systems reliably and what governance needs to be in place before automation begins.

Phases 3, 4, and 5 — implementation, deployment, and optimisation — are delivered by your internal teams or implementation partners. Zorinthia does not operate in those phases. See the full evaluation framework.

Independent advisory is most effective when decisions are costly, politically complex, or difficult to reverse — and when vendor or implementation agendas make clarity harder to find, not easier.

Common situations and client types:

• After a failed data or automation initiative — the organisation spent significantly on a data warehouse, BI tool, or automation project that failed. Leadership is cautious and wants someone with no implementation agenda to explain what actually went wrong before trying again.
• Investor or private equity due diligence — buying a company or funding a tech transformation and need an independent assessment: is the data strategy real or PowerPoint fiction? This includes validation of compliance posture and regulatory data obligations.
• Large enterprises with capable internal teams — execution capacity exists but ownership, prioritisation, or decision rights are unclear. They need someone to facilitate the hard decisions; their team executes.
• CFOs or CEOs who do not trust their vendors — the TMS vendor recommends a premium data module, the CIO wants a custom build, and the COO is not sure either solves the real problem. Advisory cuts through the noise and avoids vendor bias.
• Budget is constrained — when you only want to pay for the thinking, not the doing, and have internal teams who can execute with clear direction.
• Post-merger or restructure scenarios — duplicate systems and conflicting data definitions appear. Someone needs to design the governance model before migrations start.

Zorinthia is not a traditional Big 4 or large consultancy. The advisory background was built inside operational organisations — including regulated environments such as NGO health sector — where data problems are messy, political, and resource-constrained. That experience means complex data governance failures can be diagnosed quickly, without months of onboarding or abstract frameworks.

A decade in data management roles means the advisory has lived through what actually breaks: failed dashboards, dirty data, systems that do not integrate, and stakeholders who will not agree on definitions. The focus is on real operational dysfunction — politics, unclear ownership, quality issues, integration gaps — not textbook governance frameworks. The distinction that matters: who owns the data when things go wrong at 11pm, not what the framework says on paper.

The approach is pragmatic. No recommendations for expensive enterprise solutions you do not need. For under-resourced data teams, advisory is scoped around your reality — not an ideal-state playbook. And because data management requires daily translation between technical and business stakeholders, that ability is built into how the advisory communicates.

After a decade in implementation, the advisory knows exactly where strategy ends and execution begins. The advisory-only stance is deliberate — not an avoidance of implementation, but a focus on the phase where most projects go wrong and where independent judgement adds the most value. That phase is the diagnostic: clarifying decisions, ownership, and risk before solutions are selected or built.

What hiring executives typically want: Someone who has fixed broken data governance before. Operational credibility — able to talk to IT, ops, and the C-suite. Pattern recognition — knows what breaks and why. Scars from implementation — has lived through failures. The ability to navigate politics — data governance is 80% organisational, 20% technical.

Learn more about the advisory leadership.

Engagements begin with a conversation — not a proposal. The first step is understanding your situation: what decisions are pending, where the uncertainty sits, and whether independent advisory is the right type of support.

If it is, Zorinthia maps your current data sources and identifies where risks and opportunities sit. You receive clear, written guidance on data quality, integration requirements, governance gaps, and what to require from any vendor or implementation partner you bring in next.

Every engagement is scoped around the decision you need to make — not around a standard deliverable or a fixed methodology template. Start a conversation.

Structure: A monthly fee rather than project-based billing. Typically 1–2 board or leadership meetings per month, mostly virtual. An ongoing advisory relationship, not one-and-done.

What retainer clients are actually buying:

• Pattern recognition — "I have seen many companies make this decision; here is what usually goes wrong"
• Practical judgment — "This vendor's proposal looks good on paper, but here are three questions you should ask"
• Independence — "Everyone in this room has an agenda; I am telling you what I actually think"
• Speed — "I can assess this in 20 minutes because I have diagnosed this problem 30 times before"
• Continuity — the advisory learns your business over time and gets faster at adding value

Why companies choose retainers:

• Multiple data decisions underway — not just a TMS choice, but route optimisation, BI tools, fleet tracking, warehouse automation. An advisor on retainer can weigh in on all of them.
• No internal data strategy expertise — the CIO or CTO may be strong on operations but not strategic about data governance. Advisory fills that gap.
• Pre-empting expensive mistakes — catching a bad decision in a board meeting costs far less than unwinding a failed implementation.
• Board-level credibility — for PE-backed, family-owned, or boards that ask tough questions about tech investments, an independent advisor validates decisions.

When retainers are not the right fit: When the aim is to outsource thinking that should be built internally — retainers should not become a permanent crutch. Nor when used primarily for political cover ("the advisor said so") to deflect accountability. Retainers make sense when you are actively making decisions; they add less value when everything remains theoretical and nothing is being implemented.

Zorinthia works across industries — including finance, manufacturing, logistics, retail, mining and resources, and regulated environments such as banking and insurance.

The evaluation methodology applies to any data source: accounting automation, PLC-to-ERP integration for manufacturing, POS-to-inventory for retail, marketing analytics consolidation, supply chain visibility, and cross-functional data products for executive decision support.

The advisory typically starts where data problems surface most acutely — which is often in finance — and expands from there as operational data challenges become clearer. See example scenarios.

The core value is the same across industries: clarifying what data problems to solve and who should own them — before spending on new systems, dashboards, or automation tools.

In logistics, this typically shows up in a few ways:

• Considering a new TMS, WMS, or routing platform — advisory helps clarify what data actually needs to flow between systems, who owns data quality (dispatch vs. ops vs. finance), and whether you are solving the right problem or just automating a messy process.
• Data exists but cannot be trusted — on-time delivery metrics do not match between teams, or driver performance data lives in three places with three different answers. Advisory diagnoses why (usually unclear ownership or conflicting definitions) and maps governance before you build reports no one believes.
• Planning to automate — dynamic routing, load optimisation, or predictive maintenance — but unsure if data is ready or if ROI is real. Advisory assesses whether foundational data decisions (who maintains fleet data, how exceptions get logged) are solid enough to make automation worth it.

The advisory does not sell software or pursue implementation projects. It identifies what is broken in how your team handles data decisions, then leaves. Logistics and supply chain data advisory.

Zorinthia is based in Johannesburg, South Africa, and serves clients nationally and internationally. Advisory engagements can be conducted remotely or on-site depending on scope and client preference.