Digital business cards for teams and companies

A digital business card for teams is a web page for each employee, holding their name, role, contact details and links, that the company owns and controls centrally. An administrator creates the cards, applies the company logo and colours to all of them at once, and can lock the fields that must stay the same. Each person shares their card by NFC tap, QR code or link, and the recipient saves the details without installing anything. Because every card is a live page, a rebrand or an address change is made once by the administrator and takes effect on every card immediately, with nothing reprinted and no card left showing details that are out of date.

The company sets its brand once, at organisation level, and every card inherits it: logo, colours, fonts, website, address and social links. Individual fields can then be locked so employees cannot change them. Cardtly locks in groups rather than single fields, so "socials" is one decision covering six links and "link buttons" covers ten, which means adding a field later cannot silently leave it unlocked on every card. Locks accumulate downward: a department head can tighten what their own team may edit but can never unlock something the company set. Anything left unlocked stays the employee's to change, so a company can standardise the logo and the switchboard number while letting people write their own bio.

Yes. Cardtly supports three levels: a group at the top, companies beneath it, and departments inside those. A holding company with seven businesses under it runs all of them from one account, on one invoice and one seat pool, while each business keeps its own logo, colours, web address and manager. Each company chooses whether to wear the group's look or its own, and the group owner can lock that choice so a company cannot change it. Departments inside a company inherit from that company rather than from the group, so a business that has opted out stays consistent all the way down its own structure.

Cardtly is R97 per card per month in South African rand, billed monthly or annually. Teams of 2 to 20 cards are self-serve: an administrator buys seats and issues cards without talking to anyone. Above 20 seats the arrangement is quoted, because that is where invoicing, purchase orders and rollout support usually matter more than a checkout page. Every card carries the full feature set. There is no cut-down tier where analytics or lead capture are held back, so the price does not change according to which features a team turns on. Physical NFC cards are separate and optional: R150 each for the standard design or R200 for one designed around your brand, once off, plus R100 shipping per order rather than per card, and those ship within South Africa only. The digital cards themselves have no such limit.

An administrator can create cards one at a time or import a spreadsheet of the whole company. Each person is invited by email and claims their card with one click, at which point it is already branded and filled in with whatever the administrator entered. Nobody has to design anything or learn the product to start using their card. Somebody who leaves can have their card archived, which takes it offline immediately without deleting the leads it captured, and the seat can be reissued to their replacement. Every card is live from the moment it is claimed, so a rollout does not need a training session or a launch date. Leads captured by an archived card stay in the company's shared contacts list and can still be exported.

No. A Cardtly card opens as an ordinary web page in whatever browser the recipient already has, whether it arrives by NFC tap, QR scan or a link in a message. They can save the contact straight to their phone without downloading anything or creating an account. This matters more for teams than for individuals: a sales team hands its card to people who have no relationship with the company yet, and any step that asks a stranger to install something is a step most of them will not take. Cardtly does publish an Android app for the card's owner, which adds tap-to-share from the phone itself, but it is never required of anyone receiving a card. The details can also be added to Google Wallet, and that pass updates itself whenever the card changes.

Yes. Every card reports its own views, button taps, link clicks and saved contacts, and the team dashboard rolls those up so an administrator can see which cards are being shared and which have never been opened. A card with plenty of views and no captured leads is being handed out but not converting; a card with neither has not been shared at all. Both are visible without asking anyone, which is the practical difference between issuing cards and knowing whether they were adopted. Leads captured across the team land in one shared list with the source of each, exportable to Excel with the answers to any custom questions attached, and a Monday digest email summarises the previous seven days of views and new leads without anyone opening the dashboard.

Cardtly cards work anywhere with a browser, and are used internationally. The platform is built and billed in South Africa: subscriptions are charged in South African rand through Paystack, and physical NFC cards are printed and shipped within South Africa only. The digital cards themselves have no geographic limit, so a company with staff in several countries can run every card from one account, and only the optional physical NFC cards are restricted to South African delivery. Pricing is shown in rand with a live estimate in the visitor's own currency, so an international buyer can see what a seat costs them before signing up. There is an Android app for card owners; iOS is not released yet, and no app is ever required to receive a card.

Nothing has to be reprinted. Each card has a permanent address of its own, such as cardtly.com/card/name, and the page at that address is edited rather than replaced. A QR code printed on a banner, a signature block, or a physical NFC card keeps pointing at the same page, so a new phone number or a rebrand reaches everyone who has ever received the card. If a card's link is changed deliberately, the old link keeps redirecting, so anything already printed still works. The same applies to a whole company: an administrator changing the logo or the head office address updates every card at once, so a rebrand does not strand a single printed QR code or NFC card anywhere in the field.

A company where each person signed up individually has no shared brand, no way to fix a wrong logo across the group, no record of who has a card, and no ownership of the leads those cards capture. When somebody leaves, their card and their contacts leave with them. A team account inverts that: the company owns the cards and the data, applies the brand centrally, controls which fields staff may edit, and keeps the leads when a person moves on. It also changes what happens at scale. Fifteen people signing up individually produce fifteen slightly different cards, fifteen invoices and no way to audit any of it, where a team account produces one consistent set, one invoice, and a list of exactly who holds a card and whether they have ever shared it.