Do I need a data team to set up iDBQuery?

Setting up iDBQuery is deliberately light, so having a data team is a help for advanced cases, not a prerequisite for getting started.

• Guided connection. Adding a database, spreadsheet, file, folder or API is a step-by-step process, not an engineering project.
• Automatic understanding. iDBQuery introspects the schema and bootstraps a semantic layer on its own, so you do not need someone to model the data first.
• No pipelines to build. Because it queries in place, there is no ETL for an engineer to design and maintain.
• Ask straight away. Once connected, anyone can start getting cited answers in plain language.

Where a data team adds value is at the more advanced end: setting up complex row-level and column-level permissions, curating the semantic layer for tricky metrics, or managing a large multi-source deployment. But a small business or a single department without any data specialists can absolutely stand iDBQuery up and be productive. For example, an office manager can connect the company's accounting export and operational database and start answering finance and ops questions the same day. So the requirement is not 'hire data people first' — it is 'connect a source and ask'. If you do have a data team, iDBQuery makes them more effective by removing the flood of routine ad-hoc requests.