Founders Box — Fundraising Cockpit (Phase 1)

The problem

Design and deliver a clean, extensible Airtable + Softr architecture for Crampton Partners to run CRM, client-facing portals, investor targeting pipelines and event/activity tracking — including a prioritized Phase 1 build that a developer can implement in a 2-day sprint and a roadmap for Phases 2–3.

What we built

Purpose: Audit existing Airtable bases (anonymised if needed) and deliver a simple, scalable operational architecture that supports investor targeting pipelines, activity tracking, founder dashboards, and future cohort/mentor features.

Deliverables (Phase 1 architecture sprint):

• ERD diagram showing entities and relationships.

• Clean Airtable schema (recommended 5 core tables: companies, investor\_firms, investor\_contacts, company\_investor\_targets, progress\_updates) with field types, primary keys, lookup/rollup strategy and sample rows.

• Softr app wireframe and page tree (Founder interface + Admin interface), user roles & permissions, visibility rules, and definition of editable vs read-only fields.

• Data flow map and recommended automation touchpoints (Make/Zapier) and minimal API/CustomJS patterns for integration.

• 1–2 page architecture summary and a prioritized backlog split into Phase 1 (must-have), Phase 2 (near term enhancements) and Phase 3 (scale/features).

• Developer checklist for a 2-day build (Day 1: core schema + relationships + sample data; Day 2: founder & admin interfaces, save views, polish).

Scope / Constraints:

Phase 1 focuses on an MVP fundraising cockpit (founder dashboard, pipeline Kanban, investor details, recent activity, add target/log update actions). It intentionally excludes cohorts, mentors/permissions model, staging/normalisation tables, advanced automations, and narrative tagging — these are scoped for later phases so Phase 1 remains deliverable in ~11–14 developer hours.

Expected Outcome:

A production-ready architecture that the client team can either build themselves from the provided checklist and assets or retain the architect to implement. The schema is Postgres-ready to support future migration to Supabase/Postgres if required.