About

Professionalism is staying present, and leaving a record.

Salleway has more than ten years of experience in Mac and Apple device management and more than one hundred projects delivered. We help organizations with requirements, proof of concept, implementation, and enablement, so the customer IT team can manage its Mac and other Apple devices, and run Jamf Pro, on its own.

Prove it in a trial, then scale

We treat proof of concept as formal work: an environment, a defined scope, and a written record, so decisions are not made from slides alone. A trial is not an attempt to apply every policy at once. It is a way to validate the enrollment, distribution, and security paths that matter most, and only then decide how to widen the rollout.

Implementation and enablement together

A finished configuration is not the end. If only the implementer understands the environment, the first policy change after go-live becomes difficult. Workshops, SOPs, and ongoing support help the customer team own their console, their groups, and their day-to-day operating path.

Acceptance criteria hold the quality

Key capabilities go onto a written checklist, and test results can be reviewed. Handover is clear, and later operations have a baseline. Outstanding items are marked with the gap and the plan, rather than closing a stage as “good enough in general.”

How we work

Write the process down, so it is still useful later.

We do not push a project by creating urgency, and we do not treat implementation as a turn-key visit that ends on handover day. Scope is aligned first, validation proceeds in stages, and the record stays with the customer team. That way, a later administrator can still see what was done and why it was configured that way.

Scope matters more than slogans

Every environment has a different mix of devices, identity systems, and security requirements. We ask what must be validated before we start configuring, rather than covering every customer with one fixed template.

The customer team owns operations

Salleway can be present during implementation and later support, but day-to-day management should still be led by the customer’s IT team. Enablement exists so that this becomes true as early as possible.

Start with the next concrete step

A first conversation does not require a complete tender pack. A note on fleet size, the current environment, and the capabilities you most want to validate is enough to discuss a sensible path. The delivery method page describes the steps in more detail.