You could create a job that will use a Cmd Exec step to save the file. It'll save you a trip to SSIS.
Although there's a great amount of unnecessary fear about it, you could use xp_CmdShell to export it using BCP or SQLCmd.
--Jeff Moden
Change is inevitable... Change for the better is not.