Will this need our IT department?

The build happens inside licences the business already pays for, which is what keeps IT's involvement small. There is no new infrastructure, no data migration, no integration project with a steering committee attached; the work is switching on and shaping what Microsoft 365, Google Workspace or your cost system already contains. What the build does need is access: administrator rights, or a working session with whoever holds them, so the capture steps, registers and feeds can actually be configured. In a firm with a formal IT function that is usually one conversation and a permission; in most firms it is whoever pays the subscriptions finding the password. Where something genuinely does touch IT policy, such as single sign-on, retention rules or external sharing, I say so before it is built rather than after, and that change waits for the right yes.