Rolling Out Digital Business Cards Across a Team of 40: A Manager’s Checklist

A digital business card team rollout is not primarily a technology decision. It is a change-management task — and like most change-management tasks, it succeeds or fails on the preparation you do before anyone touches a phone. This checklist works through the practical steps: choosing the right plan for your headcount, building cards at scale, setting brand standards the team will actually follow, and bringing along the people who would rather keep doing things the old way.

Step 1: Confirm Your Plan Before You Build Anything

The first decision is structural, and it affects everything downstream. BONKT’s plans are tiered by team size. BONKT Pro covers one to 49 users at AUD $10.99 per user per month (GST inclusive). BONKT Unleashed covers 50 or more users at a flat AUD $384.45 per month (GST inclusive) — which actually becomes the cheaper option at around 35 seats, so if you are sitting at 38 or 40 people and expecting to grow, it is worth running the numbers now rather than after your next hire.

Neither plan requires a lock-in contract. You can cancel or downgrade at any time, and data is retained for 30 days after cancellation in case you need to reactivate. That gives you a reasonable window if the rollout stalls and you need to pause.

If you want to test the full feature set before committing the team, the BONKT Trial gives you 30 days of Pro features at no cost, with no payment details required to start. It does not include bulk card creation or team management, so it works for individual evaluation but not for a full team pilot. Factor that in when you are planning your timeline.

Step 2: Decide What Goes on Every Card Before You Build a Single One

The most common mistake in a team rollout is skipping the brief. Someone builds their card, shares it with the team as a template, and within a fortnight you have 40 cards that each look slightly different — different job title formats, different phone number styles, some with a headshot and some without.

Before you open the dashboard, write down the answers to these questions:

• What fields are mandatory? At minimum, most teams want: full name, job title (in a consistent format), direct phone or mobile, company email, and the company website. Decide whether mobile is mandatory or optional — for a field sales team, it probably is; for a back-office team, it may not be.
• What is the approved job title format? “Senior Account Manager”, “Sr. Account Manager” and “Senior Acct Mgr” are three different strings. Pick one convention and document it.
• What brand assets are locked? Logos, colour codes and approved headings should be set at the admin level using Brand Lock, so individual team members cannot accidentally drift off-brand when they update their own details later.
• What is optional? Some team members will want to add a personal LinkedIn profile or a direct calendar booking link. Decide whether that is encouraged, permitted or not permitted, and tell people before they ask.

Writing this down takes about 20 minutes. Not writing it down costs you an afternoon of corrections after the fact.

Step 3: Build Cards at Scale Using Bulk Creation

Once you have your brief, bulk card creation is the feature that makes a team rollout practical. Rather than asking 40 people to set up their own cards individually — with all the variation that introduces — an admin can create cards centrally from a single import, then assign them to users.

The web admin dashboard is where team management lives. From there you can create cards, assign them to team members, apply brand settings consistently, and monitor what has been set up and what has not. Get comfortable with it before the rollout day — ideally, build two or three test cards first so you know where the edge cases are.

A practical tip: export your team’s contact data from your HR system or CRM before you start, and clean it first. Bulk creation is only as good as the data you feed it. Duplicate entries, inconsistent name formats and stale phone numbers will follow you into the new system if you do not catch them now.

Step 4: Set Brand Standards with Brand Lock

Brand Lock is the feature that keeps a team’s cards on-brand after the initial setup — not just at launch, but when people update their own details six months from now. It lets you lock specific fields or design elements at the admin level, so individual users can update what they are supposed to update (their direct number, for instance) without being able to change what they are not supposed to change (the company logo, the colour scheme, the approved heading format).

Think of it as the difference between a template and a locked template. A template is a starting point that people can deviate from. A locked template defines the boundaries within which people can personalise, and holds everything else constant.

For a team of 40, this matters more than it might for a team of five. At five people, you can correct a rogue card quickly. At 40, you may not notice until a client mentions it.

The profile customisation options give you a sense of what can be configured at the card level — Brand Lock determines which of those options are available to individual users versus reserved for admin control.

Step 5: Brief Your Team on How Sharing Actually Works

This step is often skipped, and it is the one that causes the most friction on rollout day. People assume the person receiving the card needs to do something — download an app, create an account, or already be a BONKT user. None of that is true.

When a team member shares their card — by QR code, NFC tap, or a direct link — the recipient opens it in their browser. That is it. They can save the contact details straight to their phone from that browser view, with no installation required on their end. This is worth saying explicitly in your team briefing, because if people do not understand it, they will hesitate to use the card with contacts who “might not have the app”.

Cover the three sharing methods in your briefing:

• QR code — the recipient scans it with their phone camera. No app needed on either side.
• NFC tap — if your team has physical NFC cards, they tap the card against the recipient’s phone. The profile opens in the browser.
• Direct link — shareable by text, email, or added to an email signature. The recipient clicks and the profile opens.

See how it works for a clear walkthrough you can point team members to before the briefing.

Step 6: Connect to Your Existing Workflows

A digital business card that sits in isolation from the rest of your team’s tools will get used less than one that feeds directly into the systems people already rely on. BONKT connects to Salesforce, HubSpot and over 1,000 other applications via Zapier or Pabbly Connect, so contacts captured through a card share can flow automatically into your CRM without manual data entry.

This is worth setting up before the rollout rather than after. If the first thing a team member has to do after sharing their card is manually copy a contact into the CRM, the friction point is in the wrong place. Business integration options and the CRM sync knowledge base article cover the setup steps in detail.

Step 7: Handle the Reluctant Adopter

In any team of 40, there will be a handful of people who are sceptical. Some will have a genuine question (“what happens to my contacts if we cancel?”). Some will have a habit that is hard to shift (“I’ve always used paper cards and it’s worked fine”). A few will simply be waiting to see whether this is a real change or a pilot that quietly disappears.

The most effective approach is not to argue about technology. It is to remove the practical objections one at a time.

On the “what if the other person can’t receive it” concern: address it directly in the briefing. The recipient needs nothing installed. They open a browser link. That is the whole process.

On the “what if my details change” concern: this is actually one of the clearest advantages of a digital card. When a phone number or title changes, the card is updated once and every future share reflects the new information. There is no reprint, no batch of outdated cards to work through. For more on that point, the post on editing cards anytime covers it well.

On the “I’ll get to it later” concern: set a deadline. A rollout without a go-live date tends to drift. Pick a date, brief the team before it, and treat the first day of active use as a milestone worth acknowledging.

Step 8: Plan for Ongoing Management

A rollout is not a one-time event. People change roles, phone numbers change, team members leave and new ones join. Build a short process for each of these before they happen:

• Role or contact detail change — who is responsible for updating the card? The individual, their manager, or a central admin? Document it.
• New team member — is card creation part of the onboarding checklist? It should be, ideally alongside email setup and system access.
• Team member departure — deactivate or reassign the card promptly. An active card for someone who no longer works at the company is a live problem.

The admin dashboard gives you visibility across the full team, so you can see at a glance which cards are active, which have been recently updated, and which may need attention. Use it as a periodic check — monthly is usually enough for a stable team.

If you run into questions during or after the rollout, the support knowledge base covers the most common setup and management scenarios, and support responds within 48 hours.

The Checklist at a Glance

1. Confirm your plan — BONKT Pro for up to 49 users, BONKT Unleashed for 50 or more (or from around 35 if you are growing).
2. Write the brief — mandatory fields, job title format, brand assets, and what team members can personalise.
3. Build cards centrally using bulk card creation, from clean source data.
4. Apply Brand Lock to the elements that should not vary across the team.
5. Brief the team on all three sharing methods, and be explicit that recipients need no app.
6. Connect to your CRM or workflow tools before go-live.
7. Address the reluctant adopters by removing practical objections, not by debating technology.
8. Build a process for ongoing card management — role changes, new starters, departures.

A digital business card team rollout done this way is a half-day of preparation and a straightforward go-live. Done without the preparation, it is a month of chasing people to fix their cards. The checklist is the difference between the two.

Ready to start? Compare plans to find the right fit for your team size, or explore the knowledge base for detailed setup guides.