I teach at a small private middle school in a developing West African country, and over the past two years I have gradually become the person responsible for most of the school's technology. I originally studied software engineering before becoming a teacher, and although I am still learning networking and systems administration, I have been building a small homelab and improving my skills with documentation, tutorials, and experimentation.
Our school now has a computer lab with 10 desktop PCs, but the lab currently has no proper network equipment and only unreliable Wi-Fi. I have been maintaining the computers, teaching basic technology classes, and making manual weekly backups. None of this was included in my teaching contract. The school has also purchased a small 3D printer, and I requested a 24-port switch and related equipment so the lab can have a proper local network. Those items are still being shipped.
I want to approach the CFO with a proposal for a separate, paid school IT or sysadmin role alongside my teaching contract. Taking on this work would reduce the time I currently spend tutoring after school, so I need to negotiate fairly despite the school's limited budget. I would appreciate advice on what responsibilities should be included in the proposal, how to structure compensation, and whether the school website should be part of the ongoing role or treated as a separate project with a one-time fee.
I also need guidance on the practical setup. Should the lab remain on Windows, or should I consider Linux? Would Active Directory or individual student accounts be worthwhile for only 10 computers, or would a simpler setup be better? The school has no server, so could I repurpose a desktop or laptop for backups and other services? Since power outages are common, I am considering a UPS, surge protection, and possibly refurbished hardware with redundant storage. Beyond the lab, should my proposed duties include managing staff computers, backups, archiving, networking, and basic security? I want to keep the design affordable and maintainable rather than creating a system that is too complicated for one person to support.
2 Answers
Start with a written scope of work rather than promising to be responsible for everything technical. List the lab network, computer maintenance, backups, account management, staff support, inventory, security updates, printer and 3D-printer support, and documentation as separate responsibilities. Estimate the time each one requires and explain what would no longer fit into your teaching schedule. That gives the CFO something concrete to budget for and makes it easier to define what is outside the role.
Treat the website as a separate project unless they specifically want you to maintain it continuously. Building it, hosting it, updating content, handling renewals, and responding to future changes are different responsibilities and should have their own price and support terms. For the infrastructure, begin simply: a reliable router and switch, wired connections where possible, UPS or surge protection, automatic backups, and clear documentation. You can expand later once the basics are stable.
Avoid designing an enterprise environment before the school has reliable power, networking, and backups. Windows 10 should not be the long-term plan because it is reaching the end of ordinary support, so use a supported operating system that the existing PCs can actually run. Linux can reduce licensing costs, but Windows may be more useful for students and simpler if that is what staff already know.
For ten lab computers, full on-premises Active Directory may be more complexity than you need. Separate local accounts, limited student permissions, consistent configurations, and a restore or imaging process may be enough initially. If the school qualifies for educational Microsoft licensing, cloud-managed accounts could be worth investigating, but do not build the plan around a subscription that the school cannot reliably afford.
A repurposed desktop or refurbished server can handle file storage and backups, but do not rely on one disk or one machine. Use multiple disks where possible, keep at least one backup disconnected or stored elsewhere, and test that files can actually be restored. A laptop’s battery can help during short outages, but it usually has fewer options for redundant storage and expansion. A UPS for networking equipment, the storage system, and the 3D printer would be more useful than relying on a laptop battery alone. Also document passwords, hardware, software licenses, backup schedules, and recovery steps so the school is not dependent on your memory.
The first purchases should probably be a properly sized UPS, surge protection, a router, a managed or dependable switch, network cabling, and storage for backups. A powerful server is less valuable if the network and power situation are still unreliable.
Make sure the proposal includes time for routine maintenance and emergencies, not just the initial setup. Otherwise the school may assume that all future support is included for free.