Internal · Design reference

Accelerator platform — UX overview

Everything the Accelerator programme runs on, told as three journeys: the admin who operates it, the coaches who guide it, and the cohort who live in it. Each step names the screen you can open and the files that own that screen, so a fix has an obvious home.

3

Roles

16

Screens mapped

20

Admin tabs

6

Coach tabs

How a change lands

Six rules that explain where almost every update belongs.

One tab = one component

Every tab in the admin and coach dashboards is its own panel file under src/components/coordinator or /coach. Redesign the panel, not the dashboard shell.

Routes live in one place

New screens need a Route in src/App.jsx, wrapped the same way as its neighbours so it keeps the shared header and footer.

Navigation is role-driven

src/Layout.jsx builds the top nav per role (public, member, coach, coordinator, admin). Changing labels or order happens there.

Sign-in is platform-owned

There is no login page to design in this app. Login, invites and password resets are handled outside the app code.

Time is always AM/PM

Every screen and email shows 12-hour times with AM/PM — never 24-hour. Reuse the shared formatter rather than writing a new one.

Empty states are common

Most panels are data-driven and start empty. Design the empty state as deliberately as the populated one — admins see it every new cohort.

The three journeys

Pick a role to walk its flow step by step.

Runs the programme from the admin hub and one very large Accelerator workspace. Their day is triage: applications, coach submissions, check-ins, event logistics.
Step 1

Sign in and land on the admin hub

Admins are redirected here automatically after login. The hub holds account-level tools: users & roles, task assignment, meeting notes, slide submissions, mentor approvals, executive brief, AI agents, course modules and seed money.

Open screen /Admin

Tabs

OverviewUsersTasksMeeting NotesSlidesApp EmailsMentor ApprovalsExecutive BriefAI OperationsCourse ModulesSeed Money

Where to update

  • src/pages/Admin.jsx
  • src/components/admin/
Step 2

Open the Accelerator workspace

The operational home for the Accelerator. One page renders a header (program name, counts, quick links) and ~20 tabs. Every tab is its own panel component — this is where almost all admin work happens.

Open screen /AcceleratorDashboard

Tabs

ApplicationsCourse ModulesMentor MatchingInvite to MeetingCohort MeetingsPitch CoachCommunityCommunity ChatMarketingEvent PlannerCoachesSeed MoneyWeekly Cohort MeetingsWebinarsTraction DayEvent DaysThanksgivingWinter BreakInvite ParticipantsAI Agents

Where to update

  • src/pages/AcceleratorDashboard.jsx
  • src/components/coordinator/CoordinatorDashboard.jsx
Step 3

Review applications and admit teams

Admins triage incoming applications (submitted → under review → accepted / rejected), schedule interviews and send decision emails. Accepting a team creates their startup record and unlocks their cohort dashboard.

Open screen /AcceleratorDashboard

Where to update

  • src/components/coordinator/CoordinatorDashboard.jsx (Applications tab)
  • base44/functions/sendAcceleratorInviteEmail/entry.ts
  • src/pages/AcceleratorApplication.jsx (candidate-side form)
Step 4

Match mentors to teams

Admin matches mentors to each startup; matches appear on the founder dashboard under "Your Network" and drive mentor-facing views.

Open screen /AcceleratorDashboard

Where to update

  • src/components/coordinator/MentorMatchingPanel.jsx
  • src/pages/MentorMatching.jsx
Step 5

Set the weekly meeting rhythm

Admin defines day, start time, timezone, Zoom link and how many weeks the recurring cohort meeting runs, then sends the Outlook/ICS invite. Two automations then send a day-before reminder and a 1-hour-before reminder.

Open screen /AcceleratorDashboard

Where to update

  • src/components/coordinator/CohortMeetingsPanel.jsx
  • base44/functions/sendCohortMeetingInvite/entry.ts
  • base44/functions/sendWeeklyMeetingReminder/entry.ts
  • base44/functions/sendCohortMeetingHourReminder/entry.ts
  • base44/shared/cohortSessions.ts
Step 6

Run the coach bench

Approve coaches, chase unsigned Letters of Understanding, review submitted session hours, approve corrections and mark payments. This tab is the admin mirror of everything coaches submit.

Open screen /AcceleratorDashboard

Where to update

  • src/components/coordinator/CoachAdministrationPanel.jsx
  • base44/functions/sendCoachInviteEmail/entry.ts
  • base44/functions/sendLouReminderEmail/entry.ts
  • base44/functions/sendCoachSubmissionReminders/entry.ts
Step 7

Read the week

Founders submit a weekly check-in (focus area + status). Admins and assigned coaches review them, leave notes, and use them to steer the next session.

Open screen /AcceleratorDashboard

Where to update

  • src/components/program/WeeklyCheckInsPanel.jsx
  • src/components/student/StudentWeeklyCheckInCard.jsx (founder side)
Step 8

Run event days and Traction Day

Create event days (traction / demo / fundraising), compose the instructional email, send invites, and track presentation order. Teams upload their decks from their own dashboard.

Open screen /AcceleratorDashboard

Where to update

  • src/components/coordinator/EventDaysPanel.jsx
  • src/components/coordinator/TractionDayPanel.jsx
  • src/components/admin/SlideSubmissionsPanel.jsx
  • base44/functions/sendEventDayCommunication/entry.ts
  • base44/functions/sendTractionDayInfo/entry.ts
Step 9

Review seed-money grants

Founders apply for grants (with proof, W-9 and check request uploads). Admin reviews status: applied → first grant approved/paid → demo day → second grant.

Open screen /AcceleratorDashboard

Where to update

  • src/components/coordinator/SeedMoneyPanel.jsx
  • src/pages/GrantApplication.jsx
  • base44/functions/submitGrantApplication/entry.ts
Step 10

Communicate with the cohort

Group chat posts, marketing pushes, webinar invites, participant invites and the winter-break message series all live in their own tabs. Copy for automated sends lives in the backend functions, not in a template file.

Open screen /AcceleratorDashboard

Where to update

  • src/components/program/ProgramGroupChat.jsx
  • src/components/coordinator/MarketingPanel.jsx
  • src/components/coordinator/WebinarsPanel.jsx
  • src/components/coordinator/WinterBreakPanel.jsx
  • base44/shared/cohortEmails.ts

Screen map

Every Accelerator-related screen, its route and the file that renders it. Click a route to open it.

ScreenRouteWhoMain file
Marketing home/ Publicsrc/pages/Home.jsx
Admin hub/Admin Adminsrc/pages/Admin.jsx
Accelerator workspace/AcceleratorDashboard Adminsrc/components/coordinator/CoordinatorDashboard.jsx
Coach dashboard/CoachDashboard Coachsrc/pages/CoachDashboard.jsx
Founder dashboard/MyStartups Cohortsrc/pages/MyStartups.jsx
Chat & direct messages/ProgramDashboard Cohort · Coachsrc/pages/ProgramDashboard.jsx
Accelerator application/AcceleratorApplication Applicantsrc/pages/AcceleratorApplication.jsx
Next steps/AcceleratorNextSteps Cohortsrc/pages/AcceleratorNextSteps.jsx
Program overview/AcceleratorOverview Cohortsrc/pages/AcceleratorOverview.jsx
Program timeline/AcceleratorTimeline Cohortsrc/pages/AcceleratorTimeline.jsx
Week by week/AcceleratorWeekByWeek Cohortsrc/pages/AcceleratorWeekByWeek.jsx
Grant application/GrantApplication Cohortsrc/pages/GrantApplication.jsx
Mentor matching/MentorMatching Adminsrc/pages/MentorMatching.jsx
Slide submissions/SlideSubmissions Adminsrc/pages/SlideSubmissions.jsx
Courses & modules/Courses Cohortsrc/pages/Courses.jsx
Course module player/CourseModule Cohortsrc/pages/CourseModule.jsx

Shared systems

Things that sit underneath several screens — change these and the effect is global.

Emails and reminders

There are no separate email template files for the Accelerator. Every cohort and coach email is written as HTML inside the backend function that sends it, with the shared copy in base44/shared/cohortEmails.ts. Restyling an email means editing the markup in that function.

  • Senders live in base44/functions/send…/entry.ts
  • Scheduled sends are workflows in base44/workflows/
  • All times display 12-hour AM/PM (formatTime12 in base44/shared/cohortSessions.ts)

Where the data lives

Each record type is an entity schema in base44/entities/. Anything a new screen needs to show or save must exist on one of these schemas first.

  • AcceleratorApplication · Startup · Mentor
  • CoachProfile · CoachTimeReport · CoachSubmissionReminder
  • CohortMeetingSchedule · WeeklyCheckIn · Webinar
  • EventDay · TractionDay · GrantApplication · CourseModuleEnrollment

Design system

Colour and type tokens are defined once in src/index.css and exposed to Tailwind in tailwind.config.js. Base UI pieces (buttons, cards, tabs, dialogs) come from src/components/ui and are reused everywhere.

  • Buttons, badges, dialogs: src/components/ui/
  • Brand blue is the primary action colour across dashboards
  • Tab shells are shared: change a Tabs pattern once, it updates all dashboards
  • Dialogs are forced to solid white backgrounds

Reported rough edges

Fix candidates the team has flagged. Confirm each one on the live screen before redesigning it.

  • A duplicated block is reported at the bottom of the Accelerator dashboard.
  • Some meeting-invite Zoom links are reported as incorrect on older records.
  • Scheduling a meeting from the admin panel has been reported to error.
  • The coach dashboard has been reported to show only part of the assigned teams.