Building IT Infrastructure for a Growing Education Nonprofit

Challenge

The education nonprofit had experienced exactly the kind of growth that every mission-driven organization hopes for: more programs, more staff, more locations, and more impact across three NYC boroughs. But the technology had not kept up. There was no IT department, no IT budget line item beyond ad hoc purchases, and no coherent technology strategy.

The most alarming symptom was the donor database. Seven years of donor records, grant histories, and program outcome data lived on a single desktop computer under a program manager’s desk in the Bronx office. There was no backup. When asked what would happen if that computer failed, the answer was silence followed by visible anxiety.

Each of the three program locations had evolved its own technology ecosystem independently. The Manhattan office used Chromebooks. The Brooklyn location had a mix of Windows laptops purchased at different times from different vendors. The Bronx office relied on refurbished desktops donated by a corporate partner. Staff working across locations had to juggle multiple systems and could not easily share files or collaborate in real time.

The situation escalated from inconvenient to urgent when a major grant application was flagged during review. The funder required documentation of data security practices, access controls, and disaster recovery procedures. The nonprofit had none of these. The grant represented a significant portion of the upcoming year’s program budget, and the compliance gap threatened not just this application but the organization’s credibility with funders going forward.

Solution

SBK approached the engagement as a ground-up nonprofit technology build, designing infrastructure that was right-sized for a 40-person organization with limited budget but significant compliance requirements.

Discovery and Planning. Before recommending any technology, SBK spent two days visiting all three locations, interviewing program leads, reviewing the grant compliance requirements, and documenting every device, account, and data store in use. The resulting technology assessment gave the organization its first complete picture of where things stood and what needed to change.

Donor Database Migration. The highest-priority item was getting the donor database off that single desktop. SBK migrated seven years of donor and grant data to Salesforce Nonprofit Cloud, which is available at no cost for eligible nonprofits. The migration included data cleaning, deduplication, and the creation of custom fields aligned with the organization’s reporting requirements. Staff in all three locations could now access donor records securely from any device.

Cloud Infrastructure. SBK deployed Google Workspace across the organization, providing unified email, file storage, and collaboration tools. Shared Drives were structured by program and location, with permission models that reflected the organization’s actual workflows. All staff devices were enrolled in centralized management, ensuring consistent security settings regardless of device type or location.

Backup and Disaster Recovery. Automated daily backups were implemented for all critical systems, including the Salesforce database, Google Workspace data, and program-specific applications. SBK documented a disaster recovery plan with clear steps, responsible parties, and recovery time objectives, exactly the kind of documentation that funders expect to see.

Compliance Documentation. SBK created a complete set of data security policies and procedures tailored to the grant requirements. This included acceptable use policies, data classification guidelines, access control procedures, and an incident response plan. These were not generic templates but documents written specifically for how this nonprofit operates, reviewed with leadership, and formatted for inclusion in grant applications.

Device Standardization. SBK developed a device procurement plan that would standardize the organization on Chromebooks over the next 18 months as existing hardware aged out. The low per-unit cost and centralized management capabilities made Chromebooks the right fit for the organization’s budget and technical capacity.

Managed IT Support. With the infrastructure in place, SBK established ongoing managed support at $45 per user per month. This included help desk access for all 40 staff members, proactive monitoring, patch management, and quarterly technology reviews with the deputy director.

Results

The most immediate win was grant compliance. Armed with documented security policies, a cloud-based donor database with access controls and audit logging, and a tested disaster recovery plan, the nonprofit resubmitted its grant application and was approved. The compliance documentation SBK created became a reusable asset, included with every subsequent grant application without modification.

Data backup, which had previously been nonexistent, was now automated and running daily across all critical systems. The deputy director described the peace of mind as “one of those things you don’t realize how much you needed until you have it.”

All three locations were connected through a unified technology platform for the first time. Staff working across boroughs could now access the same files, collaborate on the same documents, and reach the same help desk regardless of which office they were in. Program leads reported that cross-location coordination, previously a source of constant friction, became significantly easier.

The managed support model at $45 per user per month gave the organization predictable IT costs for the first time. There were no surprise invoices, no emergency service call fees, and no ambiguity about what was covered. For a nonprofit that needed to account for every dollar in grant reporting, this predictability was as valuable as the technology itself.

Within six months, the organization went from having no IT infrastructure to speak of to operating on a modern, compliant, and fully supported technology platform. The deputy director noted that the engagement succeeded not because SBK deployed expensive technology but because the team listened to what the nonprofit actually needed and built exactly that, nothing more, nothing less.