Establish which route you are on
A short honest conversation about scale, data and what the card has to trigger. Often it ends with a licence recommendation and no project at all.
The card is not the point. Being saved is.
A paper card gets photographed and forgotten. A digital one should end with your details actually in someone's phone, your business easy to find again, and you knowing the exchange happened. We run our own platform for this, s͛Card, and we will tell you honestly when you need it and when you do not.
s͛Card, our own platform
Custom builds where they fit
Honest buy-or-build advice
No lock-in on your data
THE SITUATION
Most digital cards are a QR code pointing at a dead end.
The category filled up quickly with links that open a page, show a photograph and a phone number, and achieve almost exactly what the paper card achieved — except now it needs a signal. Nothing is saved, nothing is captured, and the next time that person needs you they search for a name they half remember.
The useful version does three things a card cannot. It puts your details into the other person's phone in one action. It stays correct after you change role, number or company, without anyone reprinting anything. And it tells you the exchange happened, so a conversation can continue rather than depending on whoever follows up first.
SYMPTOMS WE HEAR MOST
Cards get reprinted every time a title or number changes You meet fifty people at an event and follow up with four Nobody can say which conversations came from which event Your team all present themselves slightly differentlyHOW THE WORK RUNS
Decide, then deploy — in that order.
The buy-or-build decision takes one conversation. Getting it wrong costs months, so we make it first.
Get the presentation right
Wording, hierarchy and brand application. What appears first, what the primary action is, and what a stranger should understand within three seconds.
Deploy or build
Either configuration, branding and team rollout on s͛Card, or a narrow custom build inside your own platform with the same discipline.
Watch what it produces
Shares, saves, actions taken and where they came from. Then adjust the wording and the primary action based on what people actually do with it.
WHAT WE WILL AND WILL NOT BUILD
We own a platform in this category. That makes us more useful, not less.
Being both the product owner and the build partner is unusual, so here is exactly where the line sits.
WE WILL RECOMMEND s͛CARD
When what you need already exists. It is live, maintained, and costs a fraction of commissioning the same thing. If your requirement is a well-made digital card for yourself or a team, buying beats building and we will say so on the first call.
USUALLY THE RIGHT ANSWERWE WILL BUILD CUSTOM
When the card is really a feature of something else — a membership system, a directory, a portal, a field app. If it has to read from your database, sit behind your login, or match an existing product's interface, that is a build.
WHEN IT IS PART OF A SYSTEMWE WILL NOT BUILD A RIVAL
We will not take a brief to rebuild s͛Card under a different name. Not out of protectiveness — because you would be paying a premium for a worse version of something you could licence tomorrow, and we would be knowingly selling it to you.
A LINE WE HOLDAn agency with no product of its own will quote for whatever you describe. That is not always in your interest.
OPEN A REAL ONE
These are live. Scan one and hold it in your hand.
Not screenshots. Every card below is in use today. On a desktop, hover a card to bring its code forward and hold your phone up to it — that is how a card is actually met. Or click the code to open it here. On a phone, tap.
FOR A PERSON
One profile, one person, one action to save them.
Simple professional profile
With a pitch deck attached — the whole introduction in one link. scard.business/pro/friday-dmw TAP TO OPEN — scard.business/pro/friday-dmw
Professional profile on a custom domain
The same card served from the client's own domain. friday.dmw.sg TAP TO OPEN — friday.dmw.sg
Diamond and gemstone theme
With a live precious metal price ticker built into the profile. scard.business/pro/demo-jenny-1 TAP TO OPEN — scard.business/pro/demo-jenny-1
Marine professional profile
With a live wave and tide chart for the waters they work in. scard.business/pro/demo-jenny-2 TAP TO OPEN — scard.business/pro/demo-jenny-2
FOR A COMPANY
A general point of contact for a business or a business unit — not tied to one person, so it survives anyone leaving.
Davis Materialworks
Parent company card for general enquiries. scard.business/b/dmw TAP TO OPEN — scard.business/b/dmw
Supercharge Interactive
Business unit card, under the same group. scard.business/b/si TAP TO OPEN — scard.business/b/si
Second business unit
A separate card for a distinct line of business. scard.business/b/svg TAP TO OPEN — scard.business/b/svg
FOR A COMMUNITY
Groups, chapters and interest communities — one card the whole group can hand out, with no personal details attached to it.
BizJam
A business community card for members and newcomers to find the group. scard.business/comm/bizjam TAP TO OPEN — scard.business/comm/bizjam
WOL
World of Lim — a community card shared across the whole group. scard.business/comm/wof TAP TO OPEN — scard.business/comm/wof
More themes are in progress. If your profession has data worth showing on a card — rates, tides, indices, availability — that is the kind of thing the platform is built to carry.
WHY THIS HAS TO BE SECURE
A card holds real contact details. Ours defends them.
Most of this category publishes a profile page and hopes nobody misuses it. A card carries names, direct numbers, positions and relationships — the exact material harvested for impersonation and targeted fraud. s͛Card treats access as something to be earned, not assumed.
Scrapers do not get a copy
Automated extraction of contact details is detected and refused. A card is built to be met by a person, once, not enumerated by a script a thousand times.
Crawlers see what they should
Search engines get what you want indexed and nothing more. Personal contact detail is not left sitting in a public index for anyone to collect later.
Intent is assessed, not assumed
Access patterns are watched. Behaviour consistent with harvesting, probing or abuse gets cut off — the request is rejected rather than quietly served.
Captured contacts are handled as personal data
Consent recorded at capture, retention defined, access and deletion requests handled. Under PDPA this is your obligation the moment someone shares their details with you.
Control stays central
A card can be reassigned, suspended or revoked immediately. When someone leaves, their card stops being theirs — and anything already handed out still resolves correctly.
Operated, not shipped
Certificates, uptime, dependency patching and incident response are ours to carry. Security is a running cost, which is why it is the first thing an unmaintained build loses.
This is the least visible reason to license rather than commission, and the most expensive one to get wrong.
THE PART NOBODY QUOTES FOR
Building it is the cheap half. Keeping it working is the rest of your life.
A digital card looks like a weekend project until you own one. These are the things that need continuous attention, forever, whether or not anyone is using the product that month.
Contact saving breaks silently
The format that puts details into a phone behaves differently across iOS and Android versions, and a release can break it without any error appearing. You find out when a client mentions it months later.Wallet passes expire
Apple and Google wallet integrations need certificates, renewals and format compliance. Miss one and every issued pass stops working at once.Browsers move every six weeks
Camera permissions, share sheets, autofill behaviour and privacy rules all shift. Something that worked in March needs revisiting in May.Captured contacts are personal data
Consent, retention, access requests and deletion under PDPA are not optional and are not a feature you build once.People leave
One departure means reassigning a card, revoking access, redirecting anything already handed out, and keeping the record for whoever inherits the relationship. At four hundred staff that is a job, not a task.Analytics quietly stop being true
Tracking prevention, referrer policy changes and privacy defaults erode measurement over time. A dashboard that is wrong is worse than none.Someone must be on call
Hosting, certificates, uptime, backups and the phone call when a card will not open five minutes before a client meeting.None of this appears in a build quotation, because none of it happens during the build. It arrives afterwards, monthly, indefinitely — and it is exactly what a licence exists to absorb.
AND TO BE CLEAR ABOUT WHAT s͛CARD IS NOT
It is not an NFC card business. The plastic is the least interesting part and we are not trying to sell it to you.
It is not a hosted profile page with a contact form and a hit counter bolted on. That is what most of this category actually is.
It is not a thin wrapper around someone else's builder, assembled quickly and priced hopefully.
It is a platform we build and operate ourselves — one-action saving that is tested across real devices, contact capture routed into your CRM with consent handled, team templates under central control, actions that book, register or take payment, and an identity-aware assistant that answers for the person whose card it is. That last part does not exist elsewhere in this category.
See it for yourselfBUY OR BUILD
Four questions. An honest answer, including when the answer is not us.
This is the same conversation we would have on a call. Some routes end with you licensing s͛Card and never sending us a project brief.
ANSWERED 0 / 4
LICENCE s͛CARD
Buy it. Do not commission it.
Everything you have described already exists in s͛Card and is running today. Commissioning the same thing would cost several times more, take weeks longer, and leave you owning software to maintain. There is no version of this where building is the better decision.
See s͛Card Ask us to set it upWe can handle branding, team setup and rollout as a short engagement on top of the licence.
s͛CARD, PLUS INTEGRATION WORK
Licence the platform. We connect it to what you run.
The card itself is a solved problem — use s͛Card for that. What is not solved is the join: pulling profiles from your directory, pushing captured contacts into your CRM, keeping hundreds of cards correct as people move roles. That connective work is a genuine project, and it is much smaller than rebuilding the card.
Talk about the integration See s͛Card firstMost organisations at this scale spend more on keeping cards accurate than on the cards.
A CUSTOM BUILD
This is a feature of your product, not a card.
Because it has to read your own data or live inside something you already operate, a standalone card platform cannot do it. This is a build — and a well-scoped one, because the requirement is specific rather than general. We would keep it deliberately narrow and resist turning it into a card platform of its own.
Scope it with us See how we workTypically two to four weeks, built into your existing platform and owned by you.
NOT YET
Sort out what it should say first.
If it is not yet clear what the card is for, no platform and no build will fix that. A digital card makes an impression faster and more widely than a paper one, which cuts both ways. Get the positioning and the wording settled, and the delivery question usually answers itself in ten minutes.
Talk about positioning See branding and identityThis is the cheapest conversation on this page, and the one most often skipped.
WHAT AN ADVANCED CARD DOES
Six things a link to a profile page cannot.
This is the gap between a QR code and a platform, and it is where the commercial value sits.
Saves in one action
Details land directly in the other person's contacts, correctly formatted, without them typing anything. The single most important function, and the one most cards get wrong.
THE WHOLE POINTStays correct forever
Change a number, a title or a company and every card already handed out updates. Nothing is reprinted and nothing goes stale.
NO REPRINTINGCaptures the exchange
You know it happened, when, and from where. Which turns a stack of half-remembered conversations into a list you can actually work through.
FOLLOW-UPKeeps a team consistent
One template, central control, individual profiles. Nobody invents their own layout or uses a two-year-old logo.
BRAND CONTROLCarries the next step
Book a meeting, open WhatsApp, pay a deposit, register interest. The card stops being an endpoint and becomes the start of something.
ACTION, NOT INFORMATIONWorks without an app
No download, no store, no friction. It opens in whatever the other person already has in their hand.
NO INSTALLs͛Card does all six. Anything we build custom, we build because you need something beyond them.
WHAT YOU ACTUALLY GET
Whichever route, you get the same rigour.
- Buy-or-build recommendation, in writing
- s͛Card licensing, configuration and branding
- Team rollout with consistent templates
- Wording and hierarchy for the primary action
- QR assets for print, signage, email and events
- Contact capture routed into your CRM
- Custom build where the requirement genuinely needs one
- Integration with directories, portals or membership systems
- Analytics on shares, saves and actions
- Your data exportable at any point, on any route
HONEST SCOPE
Is this the right thing to buy?
GOOD FIT WHEN
Your people meet prospects in person, at events or on site Details change often enough that reprinting is a real cost You want to know which conversations actually happenedWAIT, OR DO SOMETHING ELSE FIRST
Nobody in the business exchanges details with anyone The brand and message are unsettled — fix that first You want a s͛Card equivalent built from scratch. We will decline that oneCOMMON QUESTIONS
The things people ask first.
What is s͛Card?
Our own advanced digital business card platform, live at scard.business. It handles one-action saving, always-correct details, contact capture, team templates and actions like booking or payment. It exists because we kept being asked to build the same thing, and building it once properly was better for everyone.
Why would you talk us out of a project?
Because recommending a build when a licence would do is how agencies lose clients permanently. If s͛Card covers your requirement, saying so costs us a project and earns a relationship. It also means that when we do say something needs building, you can believe us.
Will you build us something like s͛Card?
No. We will build a card that is part of your own system — inside a membership platform, a directory, a field app — and we will integrate s͛Card with whatever you run. We will not take a brief to reproduce our own platform under another name, because you would pay more for less.
Do our contacts need an app?
No. It opens in the browser they already have. Requiring the other person to install something defeats the purpose of a card, which is to work in the ten seconds you have with them.
Can we keep using printed cards as well?
Most clients do, with a code on the back. Paper still does something digital cannot — it stays in a hand and a pocket. The code is what stops it becoming the only record of the meeting.
What happens to our data if we stop?
You export it. That applies to s͛Card licences and to anything we build. Contact captures and profile data are yours in both cases, and we will not hold them hostage to a renewal.
Tell us who needs to remember you.
Describe the situation — a founder, a sales team, a few hundred staff, or a product that needs cards inside it — and we will tell you which of the four answers applies before anyone talks about a quotation.