What you ask is possible in several ways. We use management frameworks like [JAMF Pro][1] or [Munki][2] to script and manage arbitrary changes and installations so that no user needs to download / package / install or prompt. These are powerful distributed automation options, but they cost time and salary and experience and licensing.

You can roll your own more minimal installer, Most require a bit of skill if you can’t change your installer to just run as non-admin, but they are lighter cost and weight than an MDM suite solution. See [homebrew][3] for a great example of an installer that needs admin only at setup and not when installing new code. 
If you need admin installer and can’t use brew cask to package your apps, a dependable way is to write a daemon that runs as admin. Microsoft Office, Adobe and many other software does this, the installer system runs at launch or as a daemon and gets admin privileges and then uses the OS to run periodically. 

This avoids the design intent for the installer to ask for admin at the last moment when installations trigger. Following the design intent is generally more secure and far less work for you and your customers. 


  [1]: https://www.jamf.com/lp/jamf-pro/
  [2]: https://www.munki.org/munki/
  [3]: https://brew.sh/