#Feasibility Check: Building an EdTech ERP (Lead → Payment → Session Management)

1 messages · Page 1 of 1 (latest)

fossil stratus
#

Hi everyone!

I'm planning to build a full internal ERP for my EdTech company using Twenty as the core engine. Before I go all-in on research and dev, I’d love your opinion on whether the current architecture can handle this specific flow.

The Workflow:

  1. Lead Ingestion: Auto-capture leads from Website (API) and Meta Ads (Zapier/Make).

  2. Payment-Triggered Conversion: When a lead pays via Stripe, I need to auto-convert the Lead to a 'Student' object, assign them to a 'Cohort', and map the Stripe Transaction ID.

  3. The ERP Data Model:

    • Cohorts: Linked to multiple Students.
    • Sessions: Multiple class instances linked to a Cohort (these times change often).
    • Teachers: A custom object linked to specific Cohorts and Sessions.

  4. Access Control: Teachers need to see their specific Session calendar and Student lists but MUST NOT see financial data or leads belonging to others.

My Stack: Self-hosted Twenty + Antigravity/AI for custom middleware + Stripe.

The Big Question:
Is Twenty’s Custom Object API and Permissions (RBAC) mature enough to handle this "One-System" approach? Or am I better off using a dedicated ERP like ERPNext and just using Twenty for the top-of-funnel leads?

I really want to avoid "tool sprawl" and keep everything in one database. Is this a "standard" extension of Twenty or am I fighting against the grain?

#

To add to the above, regarding the UI and Calendar:

My plan is to use Twenty primarily as the "Headless" engine (Database + API). Since I need a custom view for Cohort/Session calendars that might not exist natively yet, I’m planning to:

  1. Build a custom "Teacher Portal" UI using React/Next.js, assisted by AI tools like Antigravity and Cursor.

  2. Connect this UI to Twenty via the GraphQL API to pull Session and Student data.

  3. Handle the 'Internal Leave Policy' and 'Attendance' as custom objects within Twenty, but rendered through this custom frontend.

Is the GraphQL API stable enough to serve as the backend for a custom-built portal like this? And has anyone else successfully mapped Twenty custom objects to a calendar UI (like FullCalendar or similar)?