A personal wallet stops working on day one
The moment a second person needs to move company money, a personal wallet becomes a liability. Someone holds the seed phrase. Someone else asks for it over Slack. Now two people can drain the treasury and nobody can prove who did what.
A team wallet fixes the root cause: it separates who can propose a transaction from who can approve it, and it writes down every step. You stop trusting a person and start trusting a policy.
One ledger, every account
Most startups end up with a drawer full of wallets: one per chain, one per environment, one that someone made for a launch and forgot. With Guveno you run a single team wallet and segment it into accounts: Hot for day-to-day, Cold for the treasury, Payments for customers, Exchange for trading.
Each account keeps its own balance and its own rules, but they all roll up to one ledger you can actually reconcile at month-end.
Transparent by default
Transparency is not a report you generate once a quarter; it is the wallet behaving the same way for everyone, every time. In Guveno every proposal, approval and transfer is visible to the whole team in plain English, with no exports required to answer "who moved that, and why?"
For a small team this is the quiet superpower. Your accountant, your co-founder and your future auditor all read the same screen.
Roles your whole team understands
You do not need an org chart to run a team wallet. Start with three roles and resist inventing a fourth until you have lived with these for a month:
- Operators can propose transactions and prepare payouts, but cannot move funds alone.
- Approvers sign off; set a 2-of-3 quorum on anything above a day's float.
- Auditors can read everything and export the trail, but can touch nothing.
Set limits that match a startup, not a bank
Hard daily caps feel safe right up until the day they bite, usually mid-payroll. Velocity limits are the more honest control: how much can move in 24 hours, how much in 7 days, with a quorum unlocking the next tier when you genuinely need it.
Pin your limits to your real cadence, not your worst nightmare. A wallet that blocks payroll is a wallet your team will route around.
— Sofia Reyes
A Friday-afternoon setup
You can have a working team wallet before the weekend. The whole thing is about thirty minutes:
- Create the team wallet and segment a Hot and a Cold account.
- Invite operators and approvers separately; never share a login.
- Set a 2-of-3 policy on transfers above $5,000.
- Pin velocity limits at 1× and 4× your monthly outflow, for 24h and 7d.
- Turn on email and Slack notifications for new proposals.
