Why enterprise card rollouts stall
Digital business card pilots succeed constantly and enterprise rollouts stall constantly, and it is usually the same three failures.
The first is identity. A tool that cannot federate means a new password for every employee and a new offboarding step for IT, and security will not sign it off at scale — reasonably. The second is roster maintenance. A CSV import gets everyone a card on day one and nobody owns the refresh, so the data decays until the programme is quietly abandoned. The third is brand drift. Self-serve cards mean a thousand individual design decisions, and the resulting inconsistency undoes the argument that made marketing fund it.
All three are solved by the same move: make cards a governed resource driven by systems that already have owners. Identity owns who has one. Marketing owns what it looks like. Nobody owns a spreadsheet, because there is not one.
The questions an IT review will ask
If you are preparing an internal business case, these come up almost every time. Having answers ready is most of the work.
- Does it support SAML SSO? Yes — SAML 2.0 with Okta and Microsoft Entra ID, SP-initiated and IdP-initiated, verified by a real authentication round-trip rather than by saved configuration.
- Does it deprovision automatically? Yes — IdP deactivation triggers suspend, delete, or keep according to your configured policy, without a ticket.
- What employee data does it hold? Only what you map. Directory attributes that exceed what a business card needs are flagged as sensitive so publishing them is always a deliberate choice.
- Who can change what appears publicly? Template fields can be locked centrally, and API credentials cannot alter templates or mappings — that requires an authenticated dashboard session.
- What happens to printed material on a rebrand? Nothing. Codes point at managed short links; a template edit restyles every card without invalidating a single printed code.
Sizing the programme honestly
Not everyone needs a card. The instinct to provision the entire directory is common and usually wrong: it inflates whatever you are paying per active card, fills the dashboard with cards nobody has opened, and makes adoption metrics meaningless.
Start with the population that meets people outside the company — sales, customer success, field engineering, executives, recruiting, partnerships. That is typically ten to thirty percent of headcount, and it is where a card programme produces something you can measure. Use group-scoped provisioning to define it, and self-service or request-with-approval for everyone else so the people who genuinely need one can get one without a project.