Full-Stack Developer Needed to Finalize Logic & Infrastructure for B2B SaaS MVP (Lovable + Supabase) -- 2

Job ID: 39489389

Budget: $250 – $750 USD

##Project Overview:**

We’ve built 80% of a modern, invite-based B2B platform using **Lovable** (a no-code/low-code visual builder similar to Webflow + React), combined with a **Supabase backend**. The project is fully designed with branded UI, core UX flows, and AI-assisted interactions.

However, Lovable has **limitations** when it comes to:

* advanced backend logic
* conditional user-based access control
* API authentication/verification flows
* edge cases in credits, flags, and dynamic quotas

That’s where you come in.

---

##What’s Already Done in Lovable:**

* Complete **UI/UX build** across key pages
* Basic **onboarding flows** for two user types
* User dashboards (with placeholder logic)
* Visual **credit tracker**
* Invitation form for connecting user types
* Filtering/sorting on main directory table
* Post-event evaluation form UI
* AI prompt integration via OpenAI plugin (for summaries and feedback)
* Stripe pricing tiers and interface placeholders (Premium/Pro)

---

##What Lovable Cannot Do (Needs Custom Dev):**

* Custom backend logic** (e.g., credits unlock only after specific actions)
* **Enforcing monthly interaction limits between user pairs**
* **Dynamic flag-based suspension logic** (e.g., 3 infractions = auto-ban)
* **LinkedIn validation (API or tokenized verification)**
* **Calendar integration** (Google/Outlook) with cross-user coordination
* **Handling repeat pairing limits + abuse prevention**
* *Full control over database tables + RLS policies**
* **Secure role-based access enforcement beyond visual blocks**
* **Admin-level override capabilities (e.g. reset flags, unban user)**

---

###What You Will Be Doing:**

1. **Backend Logic (Supabase)**

* Create and refine DB tables for:

* user profiles, roles, flags, subscriptions, referrals, pairings, feedback
* Implement logic to:

* issue credits based on contribution
* auto-trigger flags and suspensions
* manage pair limits and cooldown periods

2. **API Integrations**

* Setup and handle:

* LinkedIn profile validation (basic or OAuth-level)
* Google/Outlook calendar integration with meeting tracking

3. **Stripe Integration**

* Connect existing frontend with actual Stripe billing logic
* Enforce usage limits by subscription plan
* Allow plan upgrades and handle webhook logic (e.g., failed payment = downgrade)

4. **System Rules & Security**

* Enforce monthly quotas and pair caps
* Ensure bot/spam prevention on key pages
* Handle LinkedIn one-to-one usage restriction (1 profile = 1 user)

5. **Post-call Feedback Logic**

* Implement flag escalation system
* Store feedback and attach consequences to negative scores (e.g., automated suspensions)
* Restore credits in specific no-show cases

---

###Tech Stack You'll Work With:**

* **Frontend**: Lovable (React-based visual builder)
* **Backend**: Supabase (PostgreSQL, Auth, Functions, RLS)
* **AI**: OpenAI API (already integrated)
* **Payments**: Stripe (requires live integration)
* **Calendar**: Google Calendar + Microsoft Outlook (to be integrated)
* **Version Control**: GitHub

---

###You Should Be Comfortable With:**

* Writing custom **SQL functions, triggers, and policies** in Supabase
* **Extending** low-code apps via RESTful/GraphQL APIs
* Dealing with **multi-user coordination** (e.g. scheduling between 2 parties)
* Creating **robust auth + access logic** (including flagging and suspensions)
* Building scalable, secure backend infrastructure that integrates cleanly with a visual frontend

---

###Timeline:**

* Start: Immediate
* Target: Close off beta-ready build in 2–3 weeks

---



---

###To Apply:**

Please send:

1. Examples of platforms you’ve connected to low-code tools
2. How you'd approach handling dynamic user access (credits, quotas, flags)
3. Your preferred timezone and availability for next 3 weeks
4. Any questions you need answered before starting

---

Let me know if you'd like me to:

* Format this into a **PDF or Google Doc**
* Add a **simple NDA clause**
* Or write a **screening question** for applicants to validate their Supabase/API experience