Alphasyn
AI for the research desk

The speed of AI. A view your firm can stand behind.

Your analysts get the leverage: agents on the desk, research intel that runs overnight, skills built around the way they already work. Your firm keeps what matters: one governed record of what it believes, where automation proposes and the analyst decides.

A 30 minute call about your process. No deck, no follow-up sequence.

Alphasyn Acme Capital · research currentView · VOLV-B
Proposal accepted. currentView is now version 7.
Volvo B v7
Overall4 Quality3 Moat1.5
Approval queue
Accepted Daily intel v6 → v7

Overnight intel proposed an update to the Business section, sources attached.

One desk, one record, every change accounted for.
01What we do

On your coverage in weeks. Compounding for years.

We do the implementation, not just the license. An engagement starts inside your process, on your coverage, with your analysts, and builds toward one record the whole firm works from.

01 · Enable

Stand up Claude Cowork for the research team, connect the sources the desk already uses, and prove the first workflows on live coverage in weeks.

02 · Build

Skills built around your process: earnings preparation, screening, intel monitoring, notes in house style. Scheduled agents that run while the desk sleeps.

03 · Govern

Everything the agents produce connects to Alphasyn, the firm's system of record. Automation proposes, the analyst decides, and nothing happens silently.

Most firms start at stage one. The platform is where the work compounds: every agent, every analyst, and every conclusion working against one governed record.

02The platform

One living view per company. The whole firm behind it.

Ask what the firm thinks of any name and get one answer: current, versioned, and owned by a named analyst. The platform holds the collective view of companies, trends, and markets, runs the intel automations centrally, and never takes the pen out of your analysts' hands.

The living view

Every company carries one current view: thesis, ratings, assumptions, risks. Committed changes create a new version, and every prior version is retained.

The research log

Conclusions are appended, never edited. What the desk believed, and when it believed it, stays on the record permanently.

The approval queue

Proposals from analysts and automation wait in a queue with their evidence. Nothing enters the live view until the lead analyst accepts it.

03The closed system

Automation proposes, the analyst decides.

01 · Propose

Anyone on a company's coverage can propose a change to its view. So can the overnight intel automations. Proposals carry evidence and land in the queue.

02 · Decide

Only the lead analyst accepts. Acceptance is atomic: the new version is committed, the research log is appended, and the audit row is written, in one step.

03 · Record

Every mutation leaves an audit row. The log is append-only. Nothing is overwritten, and nothing happens silently.

These rules are enforced in the database, not in prompts. They live in Postgres row-level security, so they hold identically for every client: the console, the MCP tools, and whatever connects next.

The same rules that hold for an analyst hold for a model. That is the whole idea.

04MCP native

Bring your own AI. The record keeps its rules.

Pick an AI client today, switch next year: the record and its rules stay put. The platform speaks the Model Context Protocol, so any client your firm approves can query the brain, read the current view as markdown, and draft proposals grounded in the firm's own research. What no client can do is conclude: ratings and conviction stay the analyst's call, and acceptance stays with the lead.

The tool surface
ToolWhat it doesWho can call it
query_brainAsk the firm's collective view a questionEveryone on the tenant
get_company_contextThe full record for one nameEveryone on the tenant
propose_current_view_updateDraft a change, with evidenceCovered analysts and automation
accept_current_view_updateCommit a new version of the viewThe lead analyst only

See it against your coverage →

05Built for firms

Isolation you can test, not just trust.

Every row of content carries a tenant id, and Postgres row-level security isolates firms at the database layer: a rival firm's query returns zero rows, not a filtered list. Write locks are restrictive by default, the audit log is tamper-proof and insert-only, and the whole permission matrix is attack-tested as part of the build, from the reader who tries to propose to the contributor who tries to accept their own change.

Who can do what
RoleRead the brainProposeAccept into the view
Reader, PMYesNoNo
Covered analystYesYesNo
AutomationYesYesNever
Lead analystYesYesYes
From the founder

I run equity research with these tools on my own desk, and I have watched the economics of the job flip. Producing research got cheap: a model can read a quarter's filings overnight and draft a competent brief before the morning meeting. What got scarce is the other half of the work, the part where a firm can say what it believes, who decided that, and when.

Alphasyn is built for that half. It is not another copilot; it is the record the copilots work against. Every view is versioned, every change is proposed and accepted by a named analyst, and every step is on the record. The rules described on this page are not marketing language; they are enforced in the database itself, for every client that connects.

If this is the problem on your desk, write to me directly.

Kristoffer Lindström
Founder, Alphasyn
Get in touch

Start where you are.

Whether you want AI working on your coverage next quarter or a governed record for the whole firm, it starts with a conversation about your process.

No newsletter. Your email is used to reply, nothing else.

What happens next
1A reply within one business day, from Kristoffer, not a sequence.
2A 30 minute call about your process, coverage, and where AI fits.
3If there is a fit, a scoped first engagement. Weeks, not quarters.