About

🔎 Project Overview I have 7 Custom GPT agents used in my leadership development and change-management programs. They fall into two categories: 🟦 1. Structured, step-based tools These follow defined sequences (“Step 1 → Step 2 → Step 3 → Final Output”). They often end with TSV/CSV or Word-ready structured outputs. 🟩 2. Coaching-style conversational tools These function more like guided coaching conversations that require guardrails, tone consistency, and a final reflection summary. I need these 7 agents rebuilt using the OpenAI Assistants API (via my API key), and presented through a lightweight, branded custom UI that embeds cleanly inside my Kajabi portal. This should be a very small, clean system built for longevity and easy maintenance. ⭐ SYSTEM ARCHITECTURE REQUIRED 🥇 Lightweight Micro-Backend (Serverless) The backend should: • Use Vercel, Netlify, or AWS Lambda • Consist of 1–2 serverless functions • Handle Assistants API calls • Load agent logic from configuration files, NOT hardcoded strings • Maintain session state per interaction (threads) • Support both structured flows and coaching flows • Accept optional user_id and org_id for future licensing/reporting No heavy frameworks, no databases unless absolutely required, and no custom authentication layers. Kajabi will handle user access. 🥇 Thin Custom UI (Embeddable Into Kajabi) The UI must: • Embed seamlessly into Kajabi via iframe / custom code block • Support chat-style interactions for coaching agents • Support step-based interactions with “Next” or buttons for structured agents • Display final outputs cleanly (TSV, summaries, Word-ready blocks) • Include copy-to-clipboard buttons (and download buttons if feasible) • Be responsive and mobile-friendly The UI can be built with simple HTML/CSS/JS or a very light framework—nothing heavy. 🧩 Key Requirements (Must Read Carefully) ✔ 1. Treat all 7 agents as configurations, not 7 separate apps There should be: • One system (“engine”) • Seven configuration files, each describing a tool Each configuration file should contain: • System prompts / instructions • Step ordering (if applicable) • Coaching question language • Output formatting rules • UI labels/text needed for that tool This ensures I can add or update tools without rewriting code. ✔ 2. I must be able to edit prompts and flows without touching code This is essential. I need a non-technical way to update: • System prompts • Step wording • Coaching questions • Output formatting definitions • Text labels used in the UI A JSON or YAML config file per agent is ideal. Absolutely do NOT hardcode prompts into backend logic. ✔ 3. Both coaching flows and structured tools must behave reliably Coaching tools: • Must maintain tone • Must not restart themselves • Must not drift • Should feel conversational yet contained • End with a final summary or reflection Structured tools: • Must follow the defined sequence • Must not skip steps • Must not jump around • Must deliver exact TSV/Word outputs ✔ 4. Output formatting must be exact This includes: • TSV • CSV • Word-style summaries • Formatted blocks The output must NEVER include: • Extra commentary • Auto-generated markdown • Stripped tabs or collapsed spacing • Altered formatting This is non-negotiable. ✔ 5. UI must embed cleanly in Kajabi You must: • Test inside Kajabi’s iframe • Ensure scrolling works correctly • Confirm mobile responsiveness • Avoid cross-origin problems • Match a clean, professional brand aesthetic Kajabi is the gatekeeper—do NOT build a login system. ✔ 6. Build for long-term maintainability I want: • A tiny backend that rarely needs changes • Clean file structure • Clear documentation • Straightforward deploy process • Easy instructions for updating agent config files I do NOT want: • Overbuilt architecture • Heavy dependencies • Multiple repositories • Complex authentication or databases Keep it simple, elegant, and stable. 🎨 UI Expectations The UI should support: • Chat bubbles or a simple message interface • Button-driven step navigation • A clean “Final Results” screen with copy/download functionality • Clear branding (light styling is fine) It should feel polished but not over-designed. 📘 Please Include in Your Proposal 1. Examples of Assistants API or similar AI tool integrations 2. How you would structure the editable config layer 3. How you will support both coaching and structured workflows 4. How you will ensure TSV + Word formatting fidelity 5. Your suggested tech stack for the micro-backend and UI 6. Timeline and budget 7. Any suggestions to improve stability, maintainability, or UX 💡 Additional Context These tools serve as part of a professional leadership + change management system licensed to organizations. Reliability, predictability, and clean output matter deeply. The experience must feel seamless with Kajabi, even though the intelligence is hosted externally. ⭐ Final Note I value clarity, simplicity, and smart architecture. If you prefer elegant solutions over over-engineering, we’ll be an excellent fit.