Thumbtack helps homeowners care for and improve their homes by connecting them with local service professionals. The platform links more than 300,000 service businesses to homeowners across the United States, and runs on the engineering practices that define the rest of modern software: infrastructure as code, CI/CD, Git-based workflows, and code review before anything ships.

Apple MDM ran in a different world. Configuration changes happened in a dashboard. One person clicked, one change went out, no review. Feedback came back through a ticket queue. If a configuration was wrong, there was no second set of eyes to catch it before it hit every Mac in the company, and rolling it back was neither fast nor straightforward.

That risk was not theoretical. While updating the macOS nudge profile, the team got the version number right but accidentally set the date field to the past. Instead of giving employees the standard two-week window to upgrade, every Mac in the company was immediately forced to update.

*Before Fleet, a misconfigured update could immediately hit every Mac in the company and be very hard to roll back safely. Now every change is reviewed before it ships, and if something’s wrong, we can revert it.*

Manager, IT Systems Engineering, Thumbtack

Thumbtack evaluated several vendors. Fleet was the one that matched the way Thumbtack’s engineers already work.

With Fleet, device configuration is managed in code, reviewed before it ships, and reverted from version control if something is wrong. The only actions that still run through a manual interface are the ones that should: blocking a device, running a one-time script, executing a query. Everything that touches configuration goes through review.

*With Fleet, every change gets a second set of eyes on it before it’s deployed. That alone has prevented mistakes that would have been very expensive to fix.*

Manager, IT Systems Engineering, Thumbtack

Fleet’s API-first architecture meant configuration changes could be triggered, tested, and deployed inside the same CI/CD workflows engineering already runs. Open-source code and a GitOps model gave the team a full audit history of every change, who made it, and why.

Fleet’s support model removed another tax: instead of waiting 24 hours between ticket replies, the Thumbtack team could reach the Fleet team directly in a shared Slack channel.

*With our previous MDM vendor, every reply took 24 hours. With Fleet, I post in our joint Slack channel and within minutes I get a reply and we can have a conversation. Their support is huge - it’s a big selling point for us.*

**Adam Anklewicz**

Manager, IT Systems Engineering, Thumbtack

</div>

In addition, Fleet’s community engagement with the MacAdmins community helped Thumbtack gain confidence that other enterprise customers had had great experiences with the company and its software.

*All of Fleet’s issues being public on GitHub is huge because I can just search to see if anyone else is having the same problem.*

Manager, IT Systems Engineering, Thumbtack

Thumbtack migrated more than 90% of its Mac fleet to Fleet with no manual IT intervention. Direct Slack access to the Fleet team kept the migration unblocked. The team now ships endpoint changes the same way engineering ships product: fast, reviewed, and reversible.

With Fleet, Thumbtack has:

- Device configuration managed in Git, reviewed before it deploys, and revertable in minutes

- More than 90% of Macs migrated with no IT-driven enrollment work

- A clear audit history of every configuration change, who made it, and why

- Endpoint changes triggered, tested, and deployed inside the same CI/CD pipelines engineering already runs

- A direct Slack channel to Fleet’s support team, replacing 24-hour ticket cycles

What changed is not just the tooling. It is the cost of moving. The IT team used to ship cautiously because a single mistake could hit every Mac at once. Now every change goes through review, every change can be reverted, and the team keeps pace with engineering without flying blind.

Thumbtack continues to pull more endpoint operations into the same workflows the rest of the company runs on - deeper CI/CD integration, broader policy coverage, and automation that removes IT as a manual dependency anywhere a workflow can be code instead.

For an engineering-driven company, the role of Fleet is clear: not a dashboard to click through, but a layer that runs on the same review, version control, and automation as the rest of the stack. Endpoint management finally moves at the speed of the company.

<meta name="quoteAuthorJobTitle" value="Manager, IT Systems Engineering, Thumbtack">

<meta name="quoteContent" value="With Fleet, every change gets a second set of eyes on it before it's deployed. That alone has prevented mistakes that would have been very expensive to fix.">

<meta name="summaryChallenge" value="Configuration changes happened in a dashboard. One person clicked, one change went out, no review. Feedback came through a ticket queue. If a configuration was wrong, there was no second set of eyes to catch it before it hit every Mac in the company, and rolling it back was neither fast nor straightforward.">

<meta name="summarySolution" value="Thumbtack chose Fleet to bring code review, version control, and rollback to device management. Fleet’s API-first architecture meant configuration changes could be triggered, tested, and deployed inside the same CI/CD workflows engineering already runs.">

<meta name="summaryKeyResults" value="Device configuration managed in Git, reviewed before it deploys, and revertable in minutes.; A clear audit history of every configuration change, who made it, and why.; Endpoint changes triggered, tested, and deployed inside the same CI/CD pipelines engineering already runs.; A direct Slack channel to Fleet’s support team, replacing 24-hour ticket cycles.; More than 90% of Macs migrated with no IT-driven enrollment work.;">