From phishable to phishing-resistant in one sprint.
What a Dapple rollout looks like, modeled on our design-partner deployment plans: time to roll out, tickets eliminated, and the milestones along the way.
Illustrative model. The organization below is a composite and the figures are modeled targets drawn from Dapple deployment planning — not measured results from a named customer. Design-partner case studies with verified numbers are in progress.
The organization (a modeled composite)
A 60-person professional services firm on Colorado’s Front Range, managed day-to-day by its regional MSP. Like most breaches-in-waiting, the identity stack was passwords plus code-based MFA — technically “MFA-compliant,” practically phishable.
The problem
Three pressures converged in one quarter: a cyber-insurance renewal that newly required phishing-resistant MFA, a near-miss phishing incident that spoofed the firm’s SSO login page convincingly enough to fool a partner, and a helpdesk queue where credential resets and lockouts consumed roughly a third of tickets.
The deployment
- Week 1: Microsoft Entra ID integration configured by the MSP; pilot group of 12 users enrolled — average enrollment under 5 minutes per user, no tickets generated.
- Weeks 2–3: Department-by-department rollout in coexistence mode; legacy code-based MFA retired per group as enrollment coverage was confirmed.
- Week 4: Full fleet passwordless. The planned hardware-token purchase for partners and finance staff was cancelled — unnecessary.
The modeled results (first 90 days)
- 58% reduction in credential-related helpdesk tickets — roughly 11 MSP technician-hours per month reclaimed
- Cyber-insurance renewal passed with phishing-resistant MFA attested on the questionnaire
- Internal phishing simulation: zero captured credentials, because there were no credentials to capture
- 9 in 10 users rated the new sign-in “easier than what we had before” in the post-rollout survey