Digital Overhaul for a Community Land Trust
A decade-old CLT was running on a patchwork of outdated tools, manual spreadsheets, and institutional memory. We rebuilt their digital foundation without disrupting their operations.
The situation
Our client had been steward of community-owned land for over a decade — permanently affordable housing, community gardens, and commercial spaces across a mid-sized city. They’d done meaningful, sustained work. But the technology holding them together was held together with tape.
Their contact and property data lived across three separate spreadsheets, two of which were maintained by staff members who had since left the organization. Their website was five years old, built on a platform nobody on the current staff knew how to update. Their file storage was a mix of local drives, an old Dropbox account, and a shared drive that had never been organized. Every board meeting required a week of manual report preparation.
There was no single point of failure — which sounds like resilience, but was actually the opposite. There was no single point of anything.
What we did
We started with a two-week technology audit: a structured review of every tool in use, how often it was used, by whom, and what would break if it disappeared. We interviewed each staff member and the board chair. We documented what we found and presented it to leadership before recommending anything.
The audit surfaced some things they expected and some they didn’t. Two tools they were paying for were barely used. Their website, which they thought was a low priority, was actually their highest-traffic touchpoint for prospective residents and community members — it just wasn’t doing anything useful when people got there.
We agreed on a phased approach:
Phase 1 — Data consolidation (weeks 1–4): Merged and cleaned the three contact spreadsheets into a single source of truth, then migrated that into a CRM (Little Green Light, chosen for its nonprofit focus and affordability). Built standard reports so the team could pull what they needed without asking the data manager.
Phase 2 — Website rebuild (weeks 3–8): Built a new site on a simple, maintainable platform with clear content areas for prospective residents, current community members, and policy/advocacy work. Transferred content, updated copy throughout (with staff approval on every page), and provided a walkthrough recording so anyone on staff could make edits.
Phase 3 — File organization and documentation (weeks 8–12): Restructured the shared drive, established naming conventions, archived old files, and created a two-page guide to where things live and how they’re organized. This is the unsexy work that nobody ever does and everyone always needs.
Phase 4 — Training and handoff (weeks 12–14): Two group training sessions (recorded), individual walkthroughs with each staff member, and a documentation packet for each tool covering common tasks and troubleshooting. Left them with a 90-day support package for questions after launch.
What changed
The administrative impact was measurable within the first quarter. Monthly reporting, which had previously taken 6–8 hours, dropped to under 90 minutes. Board meeting prep dropped from a week to a day. The website started converting — prospective residents were filling out inquiry forms instead of calling a number that went to voicemail.
Less measurable but equally important: staff morale around technology shifted noticeably. In the initial interviews, almost every team member had described their relationship with their tools as stressful. By the end, several described feeling “in control” for the first time. That’s not something that shows up in a metrics report, but it matters.
What we learned
The hardest part of this project wasn’t technical — it was helping the organization trust that the migration process wouldn’t lose anything. We spent significant time on data integrity verification not because the technical process was complex, but because the data represented years of relationships and commitments. Getting that right, and being transparent about how we verified it, was what made the rest of the project possible.
The lesson we take from engagements like this: good technology work starts with understanding what data means to an organization, not just what it contains.