How to Choose a Digital Business Card: 12 Checks Before You Pay
How to choose a digital business card: four provider types compared, 12 checks you can run yourself, and what to ask before the link is printed.

Looking for a digital business card worth recommending? Search Google and you will mostly find providers recommending themselves, plus "best of" lists with no explanation of why. In our view the right question is not which provider, but which type of provider, and what to check before you pay. A card that looks excellent in a demo can fail you on the day you want to leave, when the link is already printed on hundreds of cards. In this article we compare four types of provider, give you 12 checks you can run on your own, and finish with the questions to ask and the red flags that exist only in this product. Full disclosure: we have a card brand of our own, Studio 51, and a self-build card platform, SimplyCard, which is why we do not rank names here.
Which digital business card is right for you? A comparison by provider type

Provider prices and features change every few months. The type of provider, by contrast, decides the things that do not change: who controls the address, who updates the card, and what happens when you stop paying. So that is where to start.
| Provider type | Who it suits | The main risk | What to check first |
|---|---|---|---|
| Free card builder | Testing an idea, a one-off event | The address and the branding belong to the provider | Do not print the link |
| Monthly or annual platform subscription | Anyone who updates details every week | The card lives only as long as you keep paying | What the link shows once the subscription ends |
| A studio that designs to order | A business where the card is part of the sale | Dependence on the provider for every change | Who updates it, how fast, and at what cost |
| NFC bundle: a physical card plus a page | Meetings, conferences, a front desk | The chip points at an address you do not control | Which address gets written to the chip |
The types overlap quite a bit. Studio 51, for example — Simple Web's digital business card brand — is a studio that designs to order and also supplies an NFC card. So it, too, is worth running through the checks below.
Our decision rule is simple: if the link is going to be printed on something that costs money to replace, choose a type of provider where the address is under your control. What each type costs, including the costs that only surface in year two, we broke down in our article on the price of a digital business card. And when a free card really is enough, we explained in free versus paid digital business cards.
Simple Web also has a platform of the second type: SimplyCard, where you build a card yourself with AI. Building it is free, and you pay only when you publish the card. As with any provider, it is worth running the 12 checks on it too.
Checks 1–4: who controls the address, the leads and the exit

These four checks matter more than the design. They decide whether the card is an asset you own or something you rent.
- The address (URL) is under your control. A printed QR code and an NFC chip both point at one address. If that address sits on the provider's domain, then on the day you leave, every card, sticker and sign leads somewhere else. What to ask for: an address on a domain registered in your name, or at the very least a written commitment to redirect it to a new one. On the printed side we also wrote a guide to the QR code on a business card.
- Editing it yourself, or going through the provider. What changes at your business every month — opening hours, offers, photos? If every change has to go through the provider, ask how long it takes and whether it costs anything. There is no single right answer here. Some businesses actually prefer that someone else makes the change.
- Where the leads land. A form on the card collects a name and a phone number, which is personal information. Check where those details are sent, who else sees them, and whether you can export them. Responsibility for that information is yours, and what Amendment 13 to the Privacy Protection Law changed we set out in our practical guide to Amendment 13.
- A clean exit. What do you get on the day you stop? A file with the leads, the texts and the images? And what does the link show afterwards: an error message, an advert, or a redirect? The renewal questions and the three-year cost are covered in the pricing article, so we will not repeat them here.
Checks 5–8: what the client experiences on a phone
You run the next four checks on the provider's sample card, on your own phone, over a cellular network.
- A real save-contact. A "save contact" button should download a vCard file, the standard contact format defined in RFC 6350. Save it, then check: the name spelled properly in Hebrew, a number you can actually dial, and the email and website in the right fields. Worth knowing: a saved contact is a copy. If you change your number the card will update, but the contact already sitting on your client's phone will not update by itself.
- Call, WhatsApp and navigation buttons. Press every one of them. Call should open the dialler with the number in it. WhatsApp should open a chat, ideally with a message already written. Navigation should lead to Waze or Google Maps at the exact address, not to the city centre.
- Hebrew and right-to-left layout. Look for punctuation jumping to the wrong side, mirrored icons, a font with no Hebrew support, and lines breaking in the middle of a word. A provider that built the system in English and translated it afterwards gets exposed here quickly.
- Speed on mobile. According to Google's web.dev, the largest element on the page should load within 2.5 seconds at most (the LCP metric). A heavy gallery and auto-playing video are the usual suspects.
Checks 9–12: accessibility, measurement, NFC and support
- Accessibility. Check the contrast between text and background, text resizing, image descriptions, and buttons a screen reader can identify by name. A digital card is a web page a business puts in front of the public, so it should meet the same requirements as a website. What Israeli law demands we set out in our website accessibility guide.
- Measurement. How many people opened the card, how many tapped WhatsApp, and which source they arrived from. Ask to see a real statistics screen belonging to an existing client, not a screenshot from marketing material.
- NFC on iPhone and on Android. According to Apple's documentation, an iPhone XS or later reads NFC tags in the background only while the device is in use, and shows a notification the user has to tap. Reading is unavailable while the camera or Apple Pay Wallet is in use, or in airplane mode. According to Android Developers, Android devices are usually looking for tags when the screen is unlocked, unless NFC has been switched off in settings. So test the NFC card on both kinds of phone, and make sure a QR code is printed on it as well. How NFC works we explained in the complete guide to the digital business card.
- A support channel. WhatsApp, phone, or a form and nothing else? And what is the response time? A card that stops working on a Thursday before a conference needs a person to answer, not a support ticket.
Questions for the provider, and red flags that only exist on cards
Ask these in the first call, before you hand over any materials:
- Exactly which address gets written to the NFC chip and to the QR code, and in whose name is its domain registered?
- If I leave, will you redirect the old address to my new one, and for how long?
- Can you send me a sample card right now, so I can open it on my phone and save it as a contact?
- When a lead leaves their details in the form, where does it arrive, and how quickly?
- What exactly does the card show on the day the payment is not renewed?
Red flags:
- No sample card you can open on a phone, only screenshots or a video.
- "Save contact" downloads an incomplete file, with no phone number, or with a mangled Hebrew name.
- The chip is locked to the provider's address, with no way to change where it points.
- A form with not a word about what is done with the details and who gets to see them.
- Every small change, even swapping one photo, requires a request with no known response time.
What Simple Web does about it
Simple Web is an AI-first marketing agency from Bnei Brak, certified Meta partners and Google advertising experts, working with 200+ businesses and holding 35 five-star Google reviews. We build our digital business cards under Studio 51, Simple Web's digital business card brand. SimplyCard, the self-build card platform mentioned in this article, is also Simple Web's. Which means that in this article we are an interested party too, and that is exactly why we chose to compare types rather than names. To date we have designed more than 300 digital business cards.
Every card includes a WhatsApp button, call, navigation in Waze or Google Maps, a photo and video gallery, save-contact, sharing, and a lead form whose enquiries reach you by email. A branded PVC NFC card comes free with every card. The card is usually ready within 3 to 5 business days from the moment we have received all the materials. Changes during the first 14 days after launch are free of charge, and after that ₪200 per working hour — a figure worth weighing against check 2. Companies get a card for every employee, with central management. We give the price as a quote based on scope, after a free diagnostic call. In that call you are welcome to put all 12 checks to us.
Prefer to build the card yourself? In SimplyCard you build one on your own for free, and pay only when you publish it.
Summary
A digital business card worth recommending is not the name of a provider, it is a fit between the type of provider and the way you work. If the link is going to be printed, the address needs to be under your control. If your details change every week, editing it yourself is worth more than an impressive design. And in every case, open a sample card on your phone and save it as a contact before you pay. Want to run the 12 checks against your own card, or against a quote you have received? Book a free diagnostic call with us.
Sources
- RFC 6350: vCard Format Specification: the standard for the contact file that the "save contact" button downloads
- web.dev: Web Vitals: the 2.5-second threshold for a good LCP
- Apple Developer: Adding support for background tag reading: which iPhones read NFC in the background, and when reading is unavailable
- Android Developers: NFC basics: when Android devices look for NFC tags


