Kelvin Private Working Dossier
A private operating map of Kelvin’s professional context, writing voice, key relationships, active threads, and open loops synthesized read-only from Gmail, Calendar, Drive metadata, and available CRM status.
Generated: 2026-05-29T16:28:35.406Z
Run: 20260529162835-f92dcb
Safety: read-only; no emails, drafts, CRM updates, or calendar edits. Meeting links/meeting access details excluded.
Run: 20260529162835-f92dcb
Safety: read-only; no emails, drafts, CRM updates, or calendar edits. Meeting links/meeting access details excluded.
292
Gmail threads
476
Decoded messages
163
Sent voice samples
339
Calendar events
581
Drive metadata
Unavailable
CRM
Executive read
Kelvin operates across two live business contexts: IIMMPACT, where he is CTO/cofounder of a Malaysian fintech/API infrastructure platform, and Calibrax AI, where he is involved in forward-deployed AI strategy and implementation. His strongest pattern is technical-commercial judgment: he can explain compliance controls and API behavior in detail, then turn around and frame partner timing, diligence, and owner handoffs.
Voice in one line: concise, direct, technical when needed, polite without theatre, and clear about next steps.
IIMMPACT map
- Unified APIs for payments/connectivity: bill payments, JomPAY, topups, eSIM/connectivity, payouts and related infrastructure.
- Visible work: bank/e-wallet onboarding, UAT and compliance evidence, settlement operations, transaction investigation, API docs and partner integrations.
- Active counterparties include AmBank, RYT Bank, MCash, Singer, Finexus, Eastel, ShopeePay/AirPay, Curlec/Razorpay.
Calibrax map
- Client-facing AI strategy and production deployment.
- Visible work: Koomi CSA, Everly bank reconciliation/sales agents, EQT Digital deep dive, GetGo workshop, Shipper affiliate management, Challenger baselining.
- Kelvin appears positioned as technical/product architecture support inside commercial delivery.
Key relationships — working top 20
CRM unavailable; inferred| Person | Class | Last known context |
|---|---|---|
| Alex Tan alex@iimmpact.com | team | Core IIMMPACT collaborator; recurring threads on claims, commercial matters, MCash, internal coordination, and investor/PeakXV cadence. |
| Zi Yang Gam ziyang.gam@iimmpact.com | team | Technical collaborator taking over integration threads such as Eastel airtime and involved in sanctions/JomPAY discussions. |
| Prakash Rao prakash.rao@iimmpact.com | team | IIMMPACT technical/compliance collaborator on sanctions screening, MCash terms, and documentation-heavy partner replies. |
| Veronica Pan veronica.pan@iimmpact.com | team | Legal/compliance partner on sanctions screening, Finexus Signiflow, NDA, and commercial/legal follow-through. |
| Clarence Gan clarence.gan@calibrax.ai | team | Calibrax deployment/commercial lead across EQT, Koomi, Razzaq onboarding, and client delivery recaps. |
| Tiffany Tan tiffany.tan@iimmpact.com | team | IIMMPACT ops/finance/admin collaborator on expense, Grab/TNG adjustment, office and invoice threads. |
| Tommy Chua tommy.chua@iimmpact.com | team | IIMMPACT team member in recurring one-on-one/office and internal coordination threads. |
| Amir Nauf amir.nauf@iimmpact.com | team | IIMMPACT ops/technical collaborator on JomPAY transaction checks, Shopee settlement slips, and webhook/ops incidents. |
| Nui Pek Tee nui.pektee@iimmpact.com | team | IIMMPACT operations contact around Maxis HERO, staff perks, office cadence, and product operations. |
| Fionne Tan fionne.tan@iimmpact.com | team | Finance/admin contact for expense claims and recurring claim submission workflow. |
| Ian Lai ian.lai@calibrax.ai | team | Calibrax commercial/operator collaborator on EQT prep, Everly proposal, internal commercials debriefs, and client materials. |
| YC Ng yc@calibrax.ai | team/advisor | Calibrax senior commercial/founder-side collaborator; involved in freelance contract, EQT follow-up, GetGo introduction, and commercial positioning. |
| Ling Hui Wong linghui.wong@calibrax.ai | team | Calibrax deployment strategist coordinating GetGo, Shipper, Koomi workflows, EQT prep, and meeting logistics. |
| Sebastian Lorenz sebastian.lorenz@eqtpartners.com | prospect/customer | EQT Digital contact; coffee/intro completed, deep-dive scheduling being coordinated for early June. |
| Maggie Chan maggie.chan@eqtpartners.com | prospect/customer | EQT scheduling/coordination contact; handled May 20 coffee meeting reschedule/confirmation. |
| Imran Shafie imran@mcash.my | prospect/vendor | MCash commercial counterpart; whitelabel terms under review with integration timing pushed toward Q3/Q4. |
| Sid Sivasubramanian sidhdharth@meetstream.ai | vendor/prospect | MeetStream founder/contact; replied that Kelvin can start directly with API/docs for meeting bot testing. |
| John Ong johnong@singer.com.my | prospect/customer | Singer Malaysia contact; sent due-diligence/commercial questions on Bill Presentment integration after Kelvin shared API spec. |
| Ting Feng Toh / Regina Sicat tingfeng@getgo.sg / reginasicat@getgo.sg | prospect/customer | GetGo CEO/Strategy contact path; intro converted into a June 3 exploratory call. |
| Andrew/Melvin/Caleb/Wayne at Koomi koomi.com.sg contacts | customer/prospect | Koomi stakeholders reviewing CSA prototype, knowledge-base materials, and commercial path to production. |
Active threads & open loops
Action map| Thread | State | Recommended next move / context |
|---|---|---|
| MeetStream meeting bot IIMMPACT / tooling | waiting on Kelvin | Sid replied that Kelvin can start directly through app/docs. Next move: create/test first bot or decide not to pursue. |
| EQT Digital deep dive Calibrax / prospect | waiting on Calibrax/Kelvin/YC | EQT offered early-June slots for a one-hour deep dive. Next move: pick a slot and prep technical/product architecture points. |
| GetGo x Calibrax Calibrax / prospect | scheduled / prep needed | Intro moved to a June 3 call. Next move: prepare Calibrax overview and workshop frame around AI strategy / roadmap. |
| Shipper-Calibrax affiliate management Calibrax / prospect | scheduled / prep needed | Kickoff is on June 3; folder and discovery recap were shared. Next move: review materials and align on what Kelvin owns technically. |
| Koomi CSA Calibrax / customer | waiting on Koomi / Calibrax follow-through | Prototype was well received; Koomi is reviewing proposal and KB materials. Next move: monitor Caleb/CS option decision and production path. |
| Everly agentic AI proposal Calibrax / prospect | waiting on Everly / internal commercial follow-up | Proposal framed bank reconciliation and sales/customer agents; internal debrief happened. Next move: confirm whether Everly wants phased scope/commercials. |
| Challenger baselining workshop Calibrax / prospect | internal follow-up | Internal recap after Notion review appears in Calibrax inbox. Next move: clarify whether workshop outputs created actions for Kelvin. |
| Razzaq internal info custodian agent Calibrax / internal | internal onboarding | Thread discusses onboarding, Jia Sheng coordination, and knowledge-base work. Next move: confirm start date, owner, and Kelvin’s build/review role. |
| AmBank sanctions/JomPAY controls IIMMPACT / customer-bank | waiting on AmBank or next compliance ask | Kelvin sent sanctions matching overview and UAT validation. Next move: watch for AmBank compliance response or additional offline flow/refund requirements. |
| Finexus x IIMMPACT coffee / Signiflow IIMMPACT / prospect-partner | waiting on external link/action | Veronica noted the new Signiflow link had not arrived. Next move: ensure Finexus/Syafiq resend or close the loop. |
| Eastel airtime distribution IIMMPACT / partner | delegated; waiting on Eastel | Kelvin looped Zi Yang in; IPs shared, NDA sent, Zi Yang chased for updates. Next move: monitor Eastel response and unblock technical onboarding. |
| MCash whitelabel terms IIMMPACT / partner | cold / future Q3-Q4 | MCash answered Kelvin’s architecture questions. IIMMPACT is keen but not ready to sign until integration DD closer to Q3/Q4. Next move: keep as future dated loop. |
| Singer Bill Presentment IIMMPACT / prospect | probably neglected | Kelvin sent technical API spec; Singer replied with platform-owner/payment-enabler questions. Next move: answer John Ong or decide if deprioritized. |
| Shopee settlement payment slips IIMMPACT / operations | recurring ops | ShopeePay sends daily settlement slips requesting reply after fund top-up. Next move: finance/ops confirmation process, not necessarily Kelvin personally. |
| Curlec payout maintenance IIMMPACT / vendor | ops awareness | Curlec announced bank partner maintenance on June 10/11. Next move: ensure payout/ops stakeholders know if affected. |
| Maxis HERO / OtomaX LHDN rules IIMMPACT / internal | internal technical debt | Kelvin documented production Maxis HERO flow and OtomaX jawaban rule gap. Next move: verify whether Alex/team implemented the retry rule. |
Writing style
What to emulate
- Simple openings: “Hi [Name]” or “Dear [Team]”.
- Short, useful paragraphs.
- Specific technical evidence when required.
- Transparent constraints instead of premature commitments.
- Clear asks, handoffs, or next steps.
What to avoid
- Generic AI/business filler.
- “Hope this finds you well.”
- Overly salesy words like “unlock” and “seamless”.
- Invented availability, pricing, metrics, or commitments.
- Leaving an external draft without an action.
Full guide written to ~/.hermes/reference/email-style-guide.md.
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.
Source coverage and limits
| Account | Gmail sent | Gmail received | Threads fetched | Calendar | Drive |
|---|---|---|---|---|---|
| kelvin.lee@iimmpact.com | 253 / est 253 | 500 / est 501 | 130 | 250 | 375 metadata hits |
| kelvin.lee@calibrax.ai | 1 / est 1 | 134 / est 134 | 42 | 44 | 2 metadata hits |
| leeweisern@gmail.com | 53 / est 53 | 250 / est 251 | 120 | 45 | 218 metadata hits |
CRM gap: Twenty CRM was unavailable because TWENTY_API_KEY is not set. Deal stages and relationship classes should be corrected after CRM is connected. Gmail pagination was capped by CLI results in several received/recent windows.
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?