Fractional IT & Cloud Infrastructure Setup
Cloud, accounts & permissions
Who can see what, and what happens the day they leave.
The work
Who can open what, from which device, and what actually happens on somebody's last day. In most small businesses the honest answer is that nobody is entirely sure.
We set access by role rather than by person, write joining and leaving down as a sequence so nothing depends on remembering, make external sharing expire, and put two-factor on the accounts holding money and customer data. The result is a question you can answer in a minute.
How it runs
Understand
We watch how the work really moves, which is never what the process document says. Where does it stop? What gets typed in twice? What only works because Dawn on the front desk remembers the workaround, and what happens the week Dawn is in Portugal?
Scope
Then we pick. Whatever costs the most hours or carries the most risk goes first, written up as a bounded job with a price on it. You'll know exactly what you're getting before anyone writes a line of code.
Build
We build it, then put it in front of the people who actually have to use it every day, while it is still cheap to change. They always find things we missed, which is the whole reason they see it in week two rather than at the handover.
Handover
You get the working system, clear documentation, and a handover to whoever owns the process. Keep us involved afterwards if it helps. The point is that you do not have to.