Read this first. Then book a short call.
Most of what a finance or security team wants to know is answerable in writing, so it is answered here. The call is for the part that is genuinely specific to you, and it is shorter because of this page.
The ten questions that come up every time.
Is our data actually separated from other clients'?
Yes, and at the database rather than in application code. The ledger, subledgers, banking, close, people records and portal identity all carry Postgres row-level security in FORCE mode, keyed to the tenant set on the connection for that request, and the role that runs application queries cannot bypass those policies. A small number of cross-tenant catalog and token tables sit outside that boundary by design: the client switcher's index and the magic-link store, both of which must be read before a tenant is known. Those are reachable only through a separate connection.
The full security page →Do you have SOC 2?
Not yet, and we will not say otherwise. Type II readiness is underway, covering control documentation and continuous monitoring, and a report goes to prospective customers under NDA once it exists. What is in place today is encryption in transit and at rest, per-tenant row-level isolation, SSO, mandatory second factor, role-based access with segregation of duties, and an append-only audit trail.
What is in place, and what is in progress →Does this replace QuickBooks or sit on top of it?
Either. TudoIQ has its own general ledger and can be the system of record, or it can read from QuickBooks Online and keep working alongside it. Firms most often start with the close and the client portal on top of existing books, then move the ledger across client by client rather than all at once.
Every capability, on one page →How do our existing books come across?
You load a trial balance and the system shows the entries it intends to create before it creates any of them: mapped accounts, unmapped accounts, and the amount that will hit each one. Two source accounts that map to the same target are held for a person rather than folded together. Every committed import carries a batch identifier and reverses as a single unit, posting mirrored entries rather than deleting anything.
How onboarding works →Multiple entities and consolidation?
Consolidation with intercompany eliminations, multi-currency with FX revaluation at period-end rates, and a firm-of-firms hierarchy where each client is its own isolated workspace under one console. Elimination postings and the FX revaluation both run through the close like any other schedule.
The technical accounting work →Single sign-on and provisioning?
Federated SSO through Microsoft Entra ID and Google Workspace, so your own conditional access and MFA policies apply. Where a magic-link email sign-in is used instead, a second factor is mandatory. Staff and client access are separate authentication domains, and client portal users are scoped to Executive, Department Head or Viewer.
Authentication and access control →How much of this is the AI doing on its own?
It proposes and people approve. That boundary is the product, not a caveat on it. TAI codes transactions against the client's own history, drafts the recurring entries a period needs, matches bank activity, and prepares the work for dates that have not arrived yet. Nothing posts to the ledger until a person approves it, and the period lock will not close over a check that fails.
What TAI does, and does not do →What is not built yet?
Each product page carries its own limits section rather than burying them. The short version: no SOC 2 report yet, and the connector list is exactly what is on the capabilities page: QuickBooks Online, Stripe, Shopify, Ramp, Brex, PayPal, Jira and Microsoft 365 SSO. If a system you depend on is not on that list, ask before you plan around it.
The connector list →How long does implementation take?
A single-entity client with clean QuickBooks books is usually running the same week, because setup is self-serve and the import is a dry run you can read before committing. Inherited books with a suspense balance and a chart that grew by accretion take longer, and the cleanup is the reason. That work is real regardless of the software.
Cleanup, and why it is one pass →What does it cost?
Pricing depends on entity count and which modules you turn on, so it is a conversation rather than a table, but a short one, and it is not the reason for the call. If you are a single company rather than a firm, start free for a month first and price it after you have used it.
Still something specific to you?
Bring the awkward question. A call that starts at the hard part is worth having; one that starts at “so tell us about your business” is not.