> For the complete documentation index, see [llms.txt](https://docs.intunepckgr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intunepckgr.com/about-pckgr/intro-what-is-pckgr/about-our-team.md). # About Our Team

## About Us **We’re Pckgr — Aussie-made, globally used.** Pckgr was built to take the hassle out of application management in Microsoft Intune. After years working in managed IT, we were all too familiar with how time-consuming and repetitive app packaging, deployment, and updates could be. So we built a platform to handle the heavy lifting—automating the process so IT teams can focus on more important work. We’re an Australian company, headquartered in Victoria. True to our roots, we believe in keeping things simple, efficient, and reliable. No fluff. No unnecessary complexity. Just solid tools that help get the job done. Although we’re based down under, the majority of our customers are overseas. That’s why we’ve designed Pckgr to suit a global audience—from workflow coverage to support responsiveness. While we’re not operating around the clock, we do our best to support customers across multiple time zones and respond quickly when it matters. [Learn how support works →](/support/pckgr-support-channels.md) We work with internal IT teams, MSPs, and enterprises alike—helping organisations reduce manual work, improve consistency, and simplify Intune app deployments at scale. And because our customer base is global, all pricing is listed in USD. [View our pricing →](/about-pckgr/pckgr-pricing-model.md) *** ### Meet the Team


Tom, CEO	Tom is the vision and drive behind Pckgr. With a degree in Business Information Systems and eCommerce, he combines technical insight with business smarts. Years in the trenches of managed IT gave him the idea for Pckgr—automating app deployments and updates to save time and headaches. Now he’s leading the charge to make Intune packaging faster, smarter, and way less painful.	/files/EqCmZuvSncnDvZPHcojQ
Miranda, Product Manager	Miranda oversees product strategy and development at Pckgr. Holding a degree in Biomedical Engineering with a software development and UX/UI focus, she has worked across both Germany and Australia in software delivery and project management roles. Miranda ensures that user experience and product functionality stay front and center, translating customer feedback into practical improvements and new features.	/files/AxpUgnvV7e4nBv9cdHnQ
Bri, Business Manager	Bri manages business operations, logistics, and team coordination at Pckgr. She has a background in SaaS administration, client relations, and people management, and plays a key role in supporting both internal operations and external partnerships. Bri’s work ensures that the business runs smoothly, supporting the wider team and contributing to customer satisfaction.	/files/y4OgwmdKIYlx65Hfd0NJ
Business Information	Company Name: Pckgr PTY LTD Location: Victoria, Australia ABN: 33 142 570 276 Email: support@intunepckgr.com Website: https://intunepckgr.com	/files/5cGYu6WUHsyivhJH3Lch

*** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.intunepckgr.com/about-pckgr/intro-what-is-pckgr/about-our-team.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.