Kelvin Living Dossier

Generated: 2026-05-29T16:28:35.406Z

Run ID: 20260529162835-f92dcb

Primary evidence: Gmail, Calendar, Drive metadata/details where available. Twenty CRM was unavailable (`TWENTY_API_KEY` not set), so relationship/deal classifications are inferred from email/calendar/Drive and should be reviewed.

Last incremental refresh: 2026-05-29T19:30:41Z. Deltas checked from 2026-05-27T16:52:12Z through 2026-05-29T19:30:41Z; only meaningful new items were added below.

1. Ten-minute summary

Kelvin Lee Wei Sern is CTO and cofounder of IIMMPACT Sdn Bhd, a Malaysia-based B2B fintech/API infrastructure company. IIMMPACT provides unified APIs around bill payments, JomPAY, mobile recharge/topups, eSIM/connectivity, payouts, and related payment infrastructure for digital banks, wallets, and tech companies.

Kelvin also works with Calibrax AI in a forward-deployed / applied AI delivery capacity. The Calibrax threads show him involved in client discovery, prototype demonstrations, production scoping, product architecture, and agentic AI implementations for companies such as Koomi, Everly, Shipper, GetGo, EQT portfolio discussions, and internal knowledge-agent work.

His operating posture is technical-commercial: he can write deeply on compliance controls and API behavior, but he also handles partner negotiations, sales engineering, customer/prospect scoping, and internal owner handoffs.

2. Source coverage

Known API caps: Gmail IIMMPACT received/recent search had a nextPageToken after 500 results; personal received/recent/unread had nextPageToken after 250 results on retry. The CLI does not expose pagination in this run, so analysis uses the returned windows plus fetched thread samples.

3. Professional identity and current work

IIMMPACT

IIMMPACT appears to be Kelvin’s main company and the strongest business context in the inbox/Drive. Active areas visible from sources:

• Bill payment and JomPAY integrations.
• Digital bank/e-wallet distribution and settlement operations.
• Topup/mobile products, including Maxis HERO / Hotlink Internet.
• Sanctions screening / compliance control explanations for bank partners.
• API onboarding, UAT checklists, cybersecurity/third-party risk materials, and bank statements/data files.
• Prospective or partner integrations: AmBank, RYT Bank, MCash, Singer, Finexus, Eastel, ShopeePay/AirPay, Curlec/Razorpay.

Calibrax AI

Calibrax work is client-facing AI strategy and implementation. Visible active or recent areas:

• Koomi customer service agent / knowledge base / production prototype path.
• Everly bank reconciliation and sales/customer agent proposal.
• EQT Digital intro/deep-dive and portfolio-company positioning.
• GetGo AI strategy workshop possibility.
• Shipper affiliate management discovery/kickoff.
• Challenger baselining workshop.
• Internal info-custodian agent and onboarding for Razzaq.

Writing and communication style

See `~/.hermes/reference/email-style-guide.md`. Short version: concise, direct, technical when needed, transparent about constraints, polite but not flowery, and action-oriented.

4. Business map

IIMMPACT business map

• Core offer: unified Malaysian payment/connectivity infrastructure APIs.
• Product surfaces: bill presentment/payments, JomPAY, mobile topup, eSIM/connectivity, settlement/payouts, compliance controls, dashboard/ops tooling.
• Operating model visible in emails: enterprise/bank partner onboarding, UAT, compliance evidence, incident/transaction investigation, settlement/top-up operations, vendor maintenance tracking.
• Commercial posture: partnership-led and technical-validation-led. Kelvin avoids signing or overcommitting before architecture and integration diligence are clear.

Calibrax business map

• Core offer: bespoke AI strategy and production-grade AI systems.
• Delivery style visible in emails: discovery, prototype, workshop, proposal/commercial framework, production path, knowledge-base/data substrate, and agentic workflow demos.
• Kelvin’s likely role: technical/product architecture and demo/build credibility inside client-facing delivery.

5. Key relationships — top 20 working set

Classification note: CRM was unavailable, so these labels are inferred. Internal recurring calendar events inflate team interaction counts; future CRM integration should refine customer/prospect/investor/vendor classifications.

6. Active threads and open loops

7. Patterns noticed

• Work sits at the intersection of fintech infrastructure and applied AI: IIMMPACT is payment/connectivity API infrastructure; Calibrax is client-facing AI deployment and strategy.
• Calendar load is operationally heavy: daily standup, weekly retro/wrap-up, frequent one-on-ones, Calibrax lunches/syncs, and client/prospect workshops.
• Kelvin writes much more when the subject is technical/compliance: long structured explanations, numbered scenarios, tables, and explicit UAT evidence. Routine replies are very short.
• Follow-up style is factual and non-needy. He tends to explain constraints transparently, e.g. not ready to sign terms until technical due diligence is complete.
• He delegates operational threads to specific owners rather than staying in the middle when another teammate should drive.
• The inbox mixes high-value commercial threads with a lot of automated/vendor/newsletter noise; future sweeps need aggressive filtering before treating inbox items as open loops.
• Automated IIMMPACT transaction-monitoring emails generated new Every/JomPAY/TNB critical/fail-rate alerts after the prior run. Treat these as transient operational signals unless they remain unresolved or Kelvin asks for ops triage; do not let them pollute the commercial relationship map.

8. Questions for Kelvin

• Which of the three Google accounts should be treated as primary for business triage: IIMMPACT, Calibrax, or all three together?
• Twenty CRM was not connected in this run. Should Twenty be the source of truth for deal stages once credentials are configured?
• Which Calibrax client/prospect threads does Kelvin personally own versus merely being copied on as technical support?
• Are MCash, Singer, Finexus, Eastel, and AmBank current priorities, or should any be marked dormant?
• Who are the official IIMMPACT leadership/team roles for Alex, Zi Yang, Prakash, Veronica, Tiffany, Amir, Nui, and Fionne?
• For Calibrax, what title should future docs use for Kelvin: Forward Deployment Engineer, ADE, consultant, or another label?
• Should routine finance/ops emails such as Shopee settlement slips be ignored by Hermes unless explicitly addressed to Kelvin?
• Are there specific deal values/pipeline stages that should appear in future refreshes once CRM is connected?
• Is the Twenty “Personal” workspace suspension/deletion warning relevant to the CRM source of truth, or safe to ignore because Twenty is not currently configured?

9. Drive/document signals

Recent/relevant Drive metadata suggests these durable knowledge areas exist and should be read selectively in future task-specific work:

• IIMMPACT MIS / business data.
• IIMMPACT API Integration UAT checklists.
• Ambank onboarding / statement data.
• RYT Bank technology risk / third-party assessment.
• Cybersecurity checklist and control assessment materials.
• Distribution deck and Endeavor/IIMMPACT profile materials.
• Indonesia market expansion files.
• Calibrax Work Tools Claims Approvals and RPG Discovery Internal Cheat Sheet.

Do not treat Drive metadata as final truth for deal status; use it as a pointer to likely documents.

10. Operational guidance for future Hermes sessions

• For business writing, read this dossier and `~/.hermes/reference/email-style-guide.md` first.
• For deal state, query CRM first once Twenty is connected.
• For email drafting, read the full thread before drafting and preserve CC context.
• For Calendar/meeting prep, strip meeting links/meeting access details from generated summaries unless Kelvin explicitly needs them.

Email Style Guide

Kelvin Email Style Guide

Generated: 2026-05-29T16:28:35.406Z

Sources: sent Gmail across connected accounts, prioritizing `kelvin.lee@iimmpact.com`, plus smaller personal/Calibrax samples. This is a style guide, not a raw email archive. Secrets, meeting links, meeting access details, phone-like strings, and credential-like details are excluded.

Executive summary

Kelvin’s email voice is direct, practical, technically fluent, and low-theatre. He opens simply, states the useful information, and closes with a concrete next step or a clean handoff. Routine messages are short. Technical/compliance messages become structured and detailed, often with numbered sections, tables, test scenarios, and exact operational evidence.

Default voice

• Plainspoken and efficient. Minimal warm-up.
• Courteous without being over-polished.
• Factual, especially when dealing with banks, partners, vendors, and compliance teams.
• Transparent when there is a constraint or uncertainty.
• Comfortable delegating: “Looping you in… please take over from here.”
• Comfortable asking direct next-step questions rather than accepting unnecessary calls.

Common openings

• “Hi [Name],” for most threads.
• “Dear [Name/Team],” for bank/compliance/formal partner communication.
• “Hi team,” for internal operational updates.
• “Thanks for…” or “Thank you for…” appears often, usually tied to a specific action.

Closings

• “Regards, Kelvin” or “Best regards, Kelvin” for external business.
• “Thank you.” for short operational replies.
• Personal account replies may omit formal close or use a very short line.

Sentence and paragraph shape

• Short paragraphs, usually one thought each.
• Routine replies: 20–80 words.
• Formal technical replies: long, structured, and evidence-backed.
• Uses bullets/numbering when the recipient needs to act or verify.
• Uses explicit examples and scenarios in compliance/technical explanations.

Move patterns

1. Acknowledge the prior message.

2. Give the useful answer or status.

3. Explain constraints only when they affect the decision.

4. Ask for the next action, delegate owner, or state when the work will resume.

Phrases that fit Kelvin

• “Thanks for the information.”
• “Please let me know the next steps.”
• “We’ve checked on our end and can confirm…”
• “Just to be transparent on where we are…”
• “We’re keen on this partnership, but…”
• “Looping [Name] in… please take over from here.”
• “Hope this helps make the concepts clearer at a glance.”

Things to avoid when drafting for Kelvin

• Overly polished consultant language.
• Generic “hope this finds you well.”
• Long gratitude paragraphs.
• Salesy words like “unlock”, “seamless”, “exciting opportunity” unless the source email already uses that tone.
• False urgency.
• Invented availability, commitments, pricing, or technical status.

Formal partner/compliance style

When writing to banks, regulated partners, or technical approvers:

• Start with the request/context.
• Provide concise architecture or control explanation.
• Include numbered sections and test scenarios.
• State evidence and result clearly.
• Invite questions without sounding evasive.

Example shape:

Dear [Team],

As requested, sharing an overview of [system/control]. The objective is to [outcome].

1. [Component]
[Brief explanation]

2. [Validation]
[Test scenario / result]

Please let me know if you have any questions.

Best regards,
Kelvin

Commercial / negotiation style

Kelvin is not pushy. He protects optionality by being transparent about timing and diligence. When a partner asks for commitment too early, draft in a way that preserves interest while avoiding premature signing.

Good pattern:

Thanks for following up — appreciate the patience.

We’re keen on this partnership, but we wouldn’t be able to commit to signing yet. Before we do, we need to work through [specific technical/commercial points]. Realistically, we expect to revisit this around [sourced timing].

Will keep you posted as we get closer.

Internal style

• Direct, owner-oriented.
• Sends context and then a clear handoff.
• For technical ops, include exact endpoints/config only in private internal contexts; never expose credentials in external summaries.

Personal-account style

Personal messages are much shorter and more utilitarian: “Attached payment”, “Here are the required documents”, “Can you refund…”. Keep these drafts simple and do not over-formalize.