Operations for web3 and crypto companies
Web3 companies are usually excellent at the part that is on chain and improvising everything else. AI and automation built for exactly this, tested on your own work first.
Web3 companies are usually excellent on chain and improvising everything else. The entity structure has drifted from the filings, treasury is reconciled from memory, contributors are onboarded in a Discord thread. The fix is ordinary operations work, applied to a company that skipped it.
Where the money goes here
Filings match reality
The structure on paper is the one you run.
Treasury reconciles
Balances come from a record rather than from memory.
Onboarding leaves a trail
Contributors arrive through a process, not a thread.
Start here. Manual work is one symptom. You get back the one weakness holding the others in place, across six areas.
Check the whole operationWhat you get
Entity and good standing
Most of these companies run two or three entities across jurisdictions and can no longer say which one holds what.
Treasury that reconciles
Fiat in one system, tokens in another, and a spreadsheet holding them together in one person head.
Contributor operations
Contractors across eight time zones with no HR function behind them.
Support and community
Discord is a support desk whether or not anybody decided that.
Sophisticated on chain, a group chat everywhere else
There is a pattern in web3 companies that almost never appears elsewhere. The technical work is sophisticated, audited, versioned, tested against adversaries. The company running it is held together by a group chat and one person who remembers everything.
That gap is invisible while things are going well, because the people involved are capable and they absorb it personally. It becomes visible the moment a counterparty asks a normal question. Which entity signed this. Who approved that payment. Where is the record of the contractor agreement. What is your process when a wallet key holder leaves.
For the operating layer around a team that already ships software, San Francisco covers the same shape. The two questions that decide the build: who owns the code, and build, or buy.
What we build for crypto and web3 companies
We build the operating layer for crypto and web3 companies: backends and APIs, technology decisions, controls and access reviews, treasury and operations dashboards, reporting and entity records.
The operating layer only. We do not audit smart contracts and we give no advice on tokens or securities. Everything below is the company around the product.
The operating layer
Databases, APIs, authentication and the integrations behind the product, documented and handed over.
Backend and API development →What to build, buy or connect
The decision written down with the reasons, before anybody spends a quarter building the wrong half.
Technology consulting →Controls and access reviews
Who can reach what, reviewed on a schedule, with the evidence written before an investor asks for it.
Internal audit →One screen for treasury and operations
Balances, flows, runway and the operational exceptions on one page, current for the people who decide.
Admin dashboard development →Reporting that reconciles
On chain and off chain figures brought to one set of numbers that survives a question about them.
Data and reporting →Entity, filings and records
Registrations, filings and the corporate record kept current, with owners and dates rather than memory.
Legal operations →Nothing here is a package. We start with the one that is costing you most, and the rest waits until it is worth doing.
Questions we get
Do you understand this space or is this generic operations advice?
I cofounded a Web3 platform, structured it as a Delaware public benefit corporation, and ran its entity, IRS and platform work end to end. So the answer is the specific one: I have filed the things, held the calendar and had the awkward conversation with a bank.
Do you audit smart contracts?
No, and you should be wary of anyone who offers it alongside operations work. Contract auditing is a specialist security discipline with its own firms and its own track records.
Can you advise on token compliance or securities questions?
No. That is counsel, and it needs to be counsel who does this specific thing in your jurisdiction.
Our contributors are all contractors in different countries. Is that a problem?
It is normal and it is manageable, and it is usually the least documented part of the business.
More in the guides and every answer in one place.
The operating layer only. Records, reporting and controls, never the contracts or the tokens.
Shaheer leads the work, with engineers, writers, filers and analysts behind him. C-suite operations for a San Francisco AI company, Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built
Read next
The pieces this usually breaks into, and where each one is covered.