ORGOS Notes
Where did the MacBook go? A field guide to asset chaos
At thirty people, your asset list is a Google Sheet. At fifty, it's a liability. Here's what changes - and what to do before you find out the hard way.
A founder we spoke to recently realized, three years in, that the company owned forty-one MacBooks and could account for thirty-four of them.
The other seven were somewhere. Probably with former employees who had left amicably and were never asked. Possibly in a drawer at the old office. One was definitely at the bottom of a backpack belonging to a contractor who had worked there for six weeks in 2024.
This is the story of asset management at almost every growing startup. It is funny until it is not.
How it starts
You buy your first laptop. You put a sticker on the bottom with the employee’s name. You write it down in a sheet called assets.xlsx.
You hire five more people. You buy five laptops. You do not update the sheet that day because you will do it later. Later, you cannot remember which laptop went to whom, so you ask in the team chat. Two people answer. You update the sheet.
You hire fifteen more people across three countries. Now you also have iPads, MDM licenses, Figma seats, AWS root access, Notion admin slots, and a small fleet of YubiKeys that nobody knows the serial numbers of.
The sheet has nine tabs. Three are out of date. One has been duplicated and edited in parallel by two different people. You stop opening it.
That is when startup IT asset management stops being a chore and starts becoming a risk.
Why this matters more than it looks like it does
Asset chaos costs you in three places, none of which show up on a P&L until they are large.
Cash. You re-buy software licenses someone else already has. You replace laptops that are sitting unused in someone’s home. You pay for an Adobe seat that belonged to someone who left eight months ago.
Security. A former employee still has access to your shared password manager because nobody made a checklist of what to revoke. A contractor still has a device because nobody owned the return process. An admin account survives because offboarding was a conversation, not a workflow.
Trust. A new hire asks for a laptop and is told “we will figure something out.” You do not sound like a company. You sound like a group project.
The compounding cost is not the missing MacBook. It is the slow erosion of operational credibility.
What changes when assets are a workflow
The first thing to fix is not the inventory. It is the moments where assets get assigned and recovered. If those two moments are workflows, the inventory stays current by itself.
Onboarding triggers provisioning. When you mark someone as starting on the 15th, the laptop request goes out, the software seats get assigned, and the welcome kit ships. This is the same reason onboarding should be treated as a real workflow, not a folder of forms.
Role determines what they get. Designers get Figma and a higher-spec MacBook. Engineers get IDE licenses and access groups. Salespeople get CRM seats and headsets. You configure it once per role, then stop making the same decision every time someone joins.
Offboarding triggers recovery. When you mark someone as leaving on the 30th, the return-shipping label generates, the licenses get revoked, and the asset list updates.
The sheet stops being the source of truth. The workflow is.
What this looks like in ORGOS
ORGOS treats assets as a connected part of the employee lifecycle, not a separate database.
When you hire someone, ORGOS suggests what to provision based on their role and location. The engineer in Bangalore and the designer in Lisbon may need different vendors, taxes, and shipping steps, but the company should not have to reinvent the flow for each person.
Physical and digital assets are tracked the same way: laptops alongside SaaS seats alongside access credentials. That matters because the operational question is the same in every case. Who has it? Who approved it? Does it need to be returned or revoked?
When someone leaves, ORGOS generates a recovery checklist and tracks completion. The inventory updates as a side effect of the workflow, not as a separate chore someone remembers on Friday afternoon.
No more assets_final_v3_USETHISONE.xlsx.
When to start
The honest answer is: before you have forty MacBooks and can only find thirty-four of them.
The slightly less honest but more useful answer is: as soon as you are hiring across more than one country, because the spreadsheet model breaks the moment you have customs forms, regional vendors, and three different VAT regimes in the picture.
There is a window where asset discipline feels too formal. That is exactly the window where it is cheapest to fix. Once the company has grown around the spreadsheet, replacing it becomes political: nobody trusts the data, everyone owns a slice of the process, and every missing device has a story attached.
Start smaller. Connect the assets to the lifecycle. Make provisioning happen when someone joins. Make recovery happen when someone leaves. Let the inventory maintain itself.
Start a workspace and connect your first asset in under five minutes.