The situation
All the context existed, but none of it turned itself into action
An Asia-based digital-asset investment and asset-management firm gives traditional finance compliant exposure to crypto. The headcount is small and the tool stack is light, mostly Gmail and Notion, but the work is anything but simple: market and on-chain research, investor communication, writing, follow-ups, coordination, and the constant push to move the fund forward. It is the kind of team where one founder-operator carries most of that load personally.
The bottleneck was never the writing itself. It was the context each task carried. Before sending a reply, the operator had to re-read the thread. Before writing a memo, they had to dig back through Notion. Before making a call, they had to reassemble the background from email, notes, and memory. The information existed, but it lived scattered across inboxes, half-finished docs, and one person's head, and it did not turn itself into action.
The firm did not want another chatbot or a rigid app-to-app automation. It partnered with the Kuse team to connect Gmail threads, Notion notes, and internal context, define the context each recurring task required, and turn scattered information into review-ready follow-ups, action plans, and decision-ready briefs around the way the investment team already operated.
Impact TL;DR
- A context-aware second operator across Gmail and Notion, without adding headcount.
- Email threads become ready-to-send follow-up drafts, grounded in the real history.
- Notion notes become prioritized action plans, not a growing archive.
- Broad questions come back as decision-ready briefs, not a pile of links.
- The founder-operator spends less time collecting context and more time deciding.
“I no longer have to rebuild the background every time. The relevant context is already there, so I get a draft instead of a blank page.
Founding Partner, Digital Asset Investment Firm
01
Use case
From an inbox thread to a ready-to-send follow-up
The problem: Every reply started with re-reading the thread and rebuilding the background. The email itself was quick to write; the slow part was reconstructing what had been said, what the other side wanted, and what came next. Important threads stalled simply because no one had the bandwidth to pick the context back up.
How the collaboration worked: The Kuse team mapped the firm's follow-up process and delivered a workflow that pulls the relevant Gmail history, identifies the current state and the other party's request, and prepares a draft for review. What used to be a cold start becomes an edit-and-send.
“It reads the whole thread and hands me a follow-up that already sounds like us. I just check it and hit send.
Founding Partner, Digital Asset Investment Firm
02
Use case
From Notion notes to an action plan
The problem: Notion held everything and moved nothing. Meeting notes, research, and rough ideas all lived there, but someone still had to read them, decide what mattered, pull out the action items, and set priorities. Plenty got recorded; too little got pushed forward.
How the collaboration worked: The Kuse team worked with the founders to define a consistent action-plan format. The resulting workflow turns relevant Notion notes into decisions, open loops, priorities, and concrete next actions, so the workspace becomes an execution layer rather than an archive.
“Our Notion used to be where ideas went to rest. Now those notes become a plan we can actually run.
Founding Partner, Digital Asset Investment Firm
03
Use case
From a broad question to a decision-ready brief
The problem: Research demand was constant but fragmented: a market, a token, a fund thesis, a macro question. What the team needed was a structured brief that supported a decision, not a folder of links and raw notes to sort through later.
How the collaboration worked: The Kuse team designed a research workflow around the firm's decision criteria. It breaks a broad question into a research path and returns findings, implications, risks, and a recommended next step in a consistent brief, turning ad-hoc research into decision-ready input.
The workflow prepared drafts and briefs, while the investment team stayed responsible for review, judgment, and final decisions.
“I ask a fuzzy question and get back something I can actually decide on, not homework.
Founding Partner, Digital Asset Investment Firm
What changed after the engagement
A lean team now moves with connected context
- Context is not rebuilt from scratch every time.The connected workspace preserves how the team works and what each thread is about.
- Notion became an execution layer.Notes turn into prioritized next actions instead of piling up.
- Work ships as drafts, not blank pages.Follow-ups, briefs, and plans arrive ready to edit.
- The founder is unblocked.Less time collecting context, more time making decisions.
- A lean team moves like a bigger one.More gets done without adding a single hire.
About the customer
An Asia-based digital-asset investment and asset-management firm
An Asia-based digital-asset investment and asset-management firm that gives traditional finance compliant exposure to crypto. It runs on Gmail and Notion. The customer has been anonymized at their request.
Gmail read + draftNotion readresearch and synthesisrecurring digestspersistent memorydraft → review → send