INCARD MOBILE APP · SẮP RA MẮT
Meeting the right person is half of it. The other half is not letting it go cold.
NFC/QR business cards, a contact list that enriches itself, and the Inka AI assistant in one app — for people who meet customers and partners constantly and need to remember everything that was said.
At the meeting
Tap NFC or scan a QR code
After the meeting
A contact list that enriches itself
The days after
Inka reminds you what to do
InkaPersonal assistant
Open contacts
I saved a few contacts at today’s conference. Which of them is worth meeting again first?
Based on their industry and what you noted at the meeting, these two are closest to what you are working on:
Tran Minh Khoa
Saved via NFC · 14:20
Shared interest
Nguyen Thu Ha
QR scan · 15:05
Possible introduction
See why it was suggested
Draft a follow-up message
Ask Inka about contacts, calendar, tasks…
What Inka suggests
Awaiting approval
Send Khoa a thank-you message
Draft
You approve before it is sentInka never messages on your behalf
Recorded at the meeting
- Event
- Retail conference
- Note
- Looking for a customer-care solution
- Sync
- Your CRM
Approve and send
Contact saved and tagged with the eventNFC tap · 2 seconds ago
ILLUSTRATIVE INTERFACE · PRODUCT IN DEVELOPMENT
A relationship is not lost at the meeting.
They slip away in the days that follow.
You meet the right person, the conversation goes well — then the card goes in a drawer, the notes stay in a notebook, and a week later neither of you has messaged.
An illustrative relationship journey
01 / 04
The moment a piece of card changes hands
Nobody knows whether it was ever looked at again.
02 / 04
The moment the stack of cards reaches your desk
And sits there until the weekend.
03 / 04
The moment you should have sent a message
But that day was busy, and then it never happened.
04 / 04
The moment you open your contacts and cannot find anyone
Even though the right person is sitting right there.
01
Leak point · At the meeting
Once the card is handed over, the trail ends.
You do not know whether they saved your number, looked at it again, or remember what you do. The moment the card leaves your hand, every signal about their interest goes with it.
02
Leak point · After the meeting
Data entry always gets pushed to tomorrow.
After an event there are dozens of names to type up, each with a note on what they cared about. Typing them costs you an evening; not typing them costs you the memory of who was who.
03
Leak point · Follow-up
Even the best conversation goes cold after forty-eight hours.
Everyone knows they should follow up quickly. But back at the office work takes over, and by the time you remember a week has gone — and by then the message is hard to open and feels forced.
04
Leak point · Your contacts over time
The bigger the contact list, the harder it is to find the right person.
After a few years there are thousands of names, most with nothing but a phone number. When you need someone in a particular industry, the fastest route is still asking a friend — not opening your own contacts.
From the first tap to the follow-up message.
None of them require typing.
InCard carries the contact, the note and the context of the meeting through all three steps — so following up no longer depends on whether you happen to remember.
01 · At the meeting
Hand over your profile in one tap, and keep the context.
Instead of handing over a piece of card, you tap NFC or let them scan a QR code. Your profile appears immediately, and on your side a new contact arrives with a note on where and why you met.
What the app does at this step
Open contacts
Tran Minh Khoa
Saved via NFC
Consent given
Add a note
Tag the contact
The context is kept
02 · After the meeting
Your contacts fill themselves in — you do not type them.
The app adds what public information it can, tags by context, syncs to the CRM you already use, then points out which of the new contacts deserve priority.
What the app does at this step
Open contacts
Tran Minh Khoa
Close to what you do
Priority
Nguyen Thu Ha
Widening the network
Worth considering
View all 5 contacts
Sync to CRM
The context is kept
03 · The days that follow
The assistant reminds and drafts — you are still the one who presses send.
Inka reminds you who you have not followed up with, drafts a message based on what the two of you discussed, and proposes meeting slots from your calendar. No message goes out that you have not read.
What the app does at this step
Open contacts
Thank them and propose a meeting
Draft
Awaiting approval
Edit the draft
Approve and send
The context is kept
Context is not lost between the steps
An app that reads your contacts and your calendar.
So it has to say exactly how far it reads.
For each capability, this is what the app can read, what needs your approval, and what it never touches — even where you have granted permission elsewhere.
Capabilities
01 · NFC and QR digital cards
Share your profile with one tap, and know whether it was opened.
In the first release
InCard NFC card
Tap · No app needed on their side
Within the product scope
Profile QR code
Scanned with a phone camera
Within the product scope
Personal or company branding
Profile customisation
Within the product scope
Public profile link
Shared by link
Within the product scope
InCard App
Digital Card
Guardrails active
Your data: what is read, what needs approval
Permissions on your device
02 · AI Contact Management
Your contacts fill themselves in — you do not type them.
In the first release
HubSpot
CRM · Contacts API
Public API available
Zoho CRM
REST API
Public API available
Odoo
External API
Needs technical assessment
Salesforce
On the product roadmap
Not in the first release
InCard App
Contact AI
Guardrails active
Your data: what is read, what needs approval
Permissions on your device
03 · AI Networking & Profile Matching
Not more contacts — the right contacts.
In the first release
Profiles inside InCard
Industry · Role · Need
Within the product scope
Event context
Where and when you met
Within the product scope
Interaction history
Whether you have been in touch
Within the product scope
The InCard ecosystem
Users who consented to being shown
On the product roadmap
InCard App
Matching
Guardrails active
Your data: what is read, what needs approval
Permissions on your device
04 · AI Search
Actually find people in your own contacts.
In the first release
Personal contacts
The contacts you saved
Within the product scope
Team contacts
Per the organisation’s permissions
Within the product scope
The InCard ecosystem
Profiles consented for display
On the product roadmap
Publicly available information
Open sources
Needs technical assessment
InCard App
AI Search
Guardrails active
Your data: what is read, what needs approval
Permissions on your device
05 · The Inka AI assistant
Reminds and drafts — but never sends by itself.
In the first release
Google Calendar
Calendar · API
Public API available
Outlook
Microsoft Graph API
Public API available
Drafts for you to send
Within the product scope
Zalo · Messenger · WhatsApp · Telegram
Messaging channels
Needs technical assessment
InCard App
Inka
Guardrails active
Your data: what is read, what needs approval
Permissions on your device
06 · Security and administration
The data is yours, and you can see who touched it.
Configured per organisation
User permissions
Individual · Team · Organisation
Within the product scope
Access log
Audit log
Within the product scope
Data encryption
At rest and in transit
Within the product scope
Data residency
VN / SG / AU options
Per the rollout agreement
InCard App
Administration
Guardrails active
Your data: what is read, what needs approval
Per the agreement with the organisation
One tap at a conference.
A meeting the following week.
A conference leaves you with dozens of names. This is how InCard is designed to keep the relationships worth keeping.
L
Hypothetical scenario
“I met a dozen or more people today. Next week I will probably remember two or three.”
L
What InCard is designed to do here
From one tap to one meeting
Live scenario
Before you let an app into your contacts.
What users and teams usually want cleared up about release status, data permissions and integrations.
Not yet. The InCard mobile app is in development and coming soon to the App Store. For now you can book a demo to see how it works and talk through what your team needs.
Coming soon — for now, only viewable in a demo.
You tap the NFC card on their phone and your profile appears on their screen straight away. They do not need to install anything. If their phone does not support NFC, the QR code works instead.
Only within the permissions you grant, and each capability has its own scope — the “Six capabilities” section above lists exactly what each one reads. Inka drafts messages but never sends them: you read them and press send.
Inka drafts — you are the one who presses send.
HubSpot and Zoho have public APIs, so they are the clearest path; Odoo needs a technical assessment against the version you run. Salesforce is on the roadmap and is not in the first release. The final list depends on the release.
There are data-residency options in Vietnam, Singapore or Australia, with encryption at rest and in transit, role-based permissions and an access log. For organisations, the specific arrangement is settled in the rollout agreement.
Both. Individuals use it to manage their own relationships. Teams add permissions, shared contacts within an agreed scope and an access log — that part is configured per organisation.
See how the app works, before it ships.
Before it reaches the App Store.
A demo to see how InCard holds on to relationships after each meeting, and to talk through what your team needs in the first release.
Three inputs to get started