Status Report

Strategic Objectives
Progress Update

Reporting periodMay 1 – 14, 2026
Prepared byJonathan (JAH)
Objectives covered01 & 02 of 04
Item Status
CRM platform selected⏳ Pending board approval
CRM dev instance running✓ Complete
CRM data model built✓ Complete
Donor data import⏳ In progress
Donor outreach standardsNot started
Project intake form✓ Live on website
Document organization⏳ Partial
Brand style guide✓ Complete
Website rebuilt✓ Live
Mobile responsive✓ Complete
Easy to maintain (CMS)✓ Complete
Social / email standardsNot started
01
Strategic Objective
Donor data & modern fundraising practices
⏳ In progress — strong foundation laid
Procure a CRM platform for donor and grant management
After evaluating Keela, LiveImpact, and CiviCRM (attempted and abandoned due to self-hosting complexity), Twenty CRM is the recommended platform. Twenty is open source, Docker-based, and has a modern UI with a full REST/GraphQL API. A dev instance is running at crm-dev.cloudbase.foundation. A board comparison document has been prepared. Cost: ~$144/yr for hosting vs $1,000–4,200/yr for SaaS alternatives.
Pending board approval. A formal comparison document covering Keela, LiveImpact, CiviCRM, and Twenty CRM has been prepared and is available for board review.
⏳ Pending approval
CRM data model & dev instance
A dev instance of Twenty CRM is running at crm-dev.cloudbase.foundation. Custom objects have been configured: Donor (via People object), Donation, Project, and Project Submission — with fields, relations, and views matching CBF's workflows. A Kanban view tracks submissions through New → Under Review → Approved/Declined. Full traceability from donor to donation to project is built into the data model.
✓ Complete
Update project intake form with requirements and approval timelines
A project submission form is live at cloudbase.foundation/contact with fields for submitter name, email, organization, region, project description, and estimated budget. In Phase 2, form submissions will feed directly into Twenty's Project Submission object via API, triggering an automatic notification to CBF staff. Approval timeline workflow is built into the Kanban data model.
✓ Live — API integration Phase 2
GiveLively donor data migration
GiveLively remains the active donation platform. An anonymized import of donor and donation history into the dev CRM is currently in progress for testing the data model. The long-term plan (Phase 3) replaces GiveLively with a native Stripe-powered donation form on the CBF website, with real-time sync to Twenty via webhook — eliminating manual CSV imports.
⏳ In progress
Standardize donor outreach and communications
Not yet started. Planned for Phase 6 once the CRM is stable in production. Will include branded email receipt templates, recurring donation confirmations, annual tax receipt emails, and a lapsed donor re-engagement sequence.
Gap. Email infrastructure and donor communication standards are the largest remaining gap in this objective. Will require SMTP setup, email template design, and integration with the CRM.
Not started
Organize key documents and ensure board-wide access
Key documents are referenced from the CBF website footer and maintained at cbf-documents.pages.dev. Board-wide access has not yet been formally structured or documented.
⏳ Partial

02
Strategic Objective
Brand & communications refresh
✓ Substantially complete
Build a cohesive style guide and logo
A comprehensive Brand Style Guide v1.1 has been produced and is available as a PDF. It covers the full color palette (derived from the existing logo), typography system (Barlow Condensed + Plus Jakarta Sans), logo usage rules for all four variants (horizontal, medium, stacked, round), voice and tone guidelines with sample copy, component patterns, and spacing/grid specifications. The guide is the canonical visual identity reference for all CBF brand assets going forward.
✓ Complete
Update website to be mobile-friendly and easier to maintain
The new cloudbase.foundation website is live. It is fully mobile-responsive, built on Next.js 15, and includes all eight pages: Home, Projects, Past Projects, Get Involved, Resources, About, News, and Contact. The projects directory is filterable by region and category. Content is managed via Tina CMS — non-technical staff can edit page copy directly from a browser at cloudbase.foundation/admin without touching code. A full on-brand favicon set has been deployed. The site is deployed on Cloudflare with automated CI/CD via GitHub Actions.
✓ Live
Create standards for social media, email, and web communications
Voice and tone guidelines are documented in the Brand Style Guide. Social media post templates, email newsletter standards, and formal brand application guidelines for social channels have not yet been created.
Remaining gap. Social media and email communication standards are the only incomplete item in this objective. The style guide provides the brand foundation — templates and channel-specific guidelines need to be built on top of it.
Not started

Looking ahead. A full technology roadmap covering Phases 1–6 has been documented, covering the CRM production deployment, CBF-site API integration, Stripe donation processing, the volunteer management app, and donor email communications. The roadmap is version-controlled in the CBF-site repository.