I am building a reusable lead follow-up and consultation booking automation system for med spas and aesthetic clinics. I need an experienced automation specialist who can build, test, document, and hand off a production-ready workflow system. This is not a one-off Zapier task. I need a reusable system that can be adapted for future clients. What the system should do: * Recover missed calls and website inquiries before they go cold * Send fast SMS/email follow-up to new leads * Collect basic service interest without giving medical advice * Send a consultation booking link * Log every lead in a CRM or lead tracker * Track lead status from new inquiry to booked consultation * Notify clinic staff when a lead replies, books, or needs human review * Escalate medical, treatment-specific, pricing-sensitive, or sensitive questions to staff * Run a simple no-response follow-up sequence * Send appointment reminders after a consultation is booked * Provide a weekly lead activity summary showing new leads, contacted leads, booked consultations, no-responses, and escalations Preferred stack: - Make - Airtable - Twilio - Calendly - Google Workspace / Gmail I am open to GoHighLevel or other stack recommendations if you can explain the trade-offs clearly. Important compliance guardrails: The system is for appointment scheduling and lead follow-up only. It must not provide medical advice, diagnose, recommend treatments, collect sensitive medical history, or answer treatment-specific questions. Any medical, pricing-sensitive, treatment-specific, or sensitive question should be routed to clinic staff. Required deliverables: - Workflow diagram - Recommended stack document - Working demo system - CRM/tracker template - SMS/email message templates configured with variables - Testing checklist - Client onboarding checklist - Duplication/setup guide - Loom walkthrough - Handoff documentation - Monthly tool cost estimate - Limitations and risks document Budget: Fixed price: $1,500 Budget flexible up to $2,000 for the right reusable system. Proposed milestones: Milestone 1 — Architecture and stack recommendation $300 Milestone 2 — Working build $800 Milestone 3 — Documentation and handoff $400 PLEASE COMPLETE THE SCREENING QUESTIONS WHEN APPLYING: 1. Describe a workflow you built involving SMS follow-up triggered by a call or form submission. What tools did you use? 2. What is the most complex Make.com scenario you have built? 3. Have you built Airtable as a CRM or lead tracker before? Describe the structure. 4. Have you integrated Twilio with Make or Zapier for SMS automation? 5. Have you connected Calendly webhooks to downstream automation? 6. How would you prevent this system from giving medical advice or collecting sensitive information? 7. What does your documentation and handoff process include? 8. For this use case, would you recommend GoHighLevel or Make + Airtable + Twilio? Why?

Stripe Connect marketplace integration including: Client pays for a booking through the platform Payment is held by Stripe until the shoot is marked complete Platform automatically takes 15% commission Videographer receives 85% paid out to their connected bank account Videographer onboarding flow to connect their Stripe account and enter payout details Refund handling if a booking is cancelled before the shoot Booking status updates automatically when payment is made, held, and released Both client and videographer dashboards show accurate earnings and payment history NEXT: Email notifications via Resend when a booking is confirmed, payment is received, and payout is sent An admin dashboard where I can see all bookings, payments, and platform activity in one place What I'm looking for in a developer: Someone who has specifically built Stripe Connect marketplace integrations before, not just general Stripe experience but the full marketplace split payment setup. Please include examples of marketplace projects you've built in your proposal. Please answer these three questions in your proposal: Have you built a Stripe Connect marketplace integration before? If yes describe the project briefly. What is your estimated timeline for this specific scope of work? What is one potential challenge you'd anticipate with this project and how would you handle it? If you're interested and looking to take the site to next level. I would love to chat more, tell you about the business and see if we would be a good fit!

We are interested in developing a web app that will allow us to automate a lot of the administrative tasks we need to do to carry out our work. The app will serve three main functions: 1) Provide a simple and easily accessible interface that will allow users to submit expense information that will be automatically stored in our organization's Google Drive. 2) Allow for admin to review this information and engage in a dialogue with the user if necessary. 3) Track all expense data in an organized way to a) allow users to view project expense summaries and b) allow admin to create and generate expense reports. Attached is an overview of how each interface should articulate with the others as well as a detailed summary of what each interface could look like. Note that the details here are not comprehensive and questions are expected, but the general shape is there. Note that these interfaces will need to effectively and seamlessly articulate with one another as well as external systems like Quickbooks.

We are seeking a Senior Software Engineer to join our team in Maryland. The ideal candidate will have experience with Ruby and Nest.js, and be able to work on a variety of projects. Responsibilities include developing and testing software applications, collaborating with cross-functional teams, and contributing to the design and implementation of new features. The candidate should have strong problem-solving skills and be able to work in a fast-paced environment.

search/ABLE: Making Travel Searchable for All Disabilities We're building the accessibility intelligence layer for travel. search/ABLE maps 300+ hotel accessibility datapoints to a structured taxonomy — powering the search and booking experience that 1.3 billion travelers with disabilities have never had. The MVP is live. Seeking someone to help scale the platform. The right candidate will be able to: Build code using an AI agent — this is an AI-native product development PostgreSQL database architecture and data integrity API design for third-party integrations (travel agencies, online booking tools, partners) Role-based permissions and enterprise-level security Workflow orchestration across the platform If you are seeking to join a start up with: Meaningful societal impact Real solution for a real problem Founder with deep industry knowledge and a network of customers to implement A live MVP — not a pitch deck An advisor role with a clear path to cofounder for the right person This would start as an hourly rate with co-founder potential.

What this is: I'm the founder of a working AI SaaS platform (FastAPI/uvicorn backend, React/Vite frontend, deployed on AWS). The product pipeline is built and live! I need an experienced engineer to build the authentication, payments, and usage-entitlement layer that gates the product behind login and paid usage. You'll work against a runnable stub repository (real routes + data shapes, proprietary internals removed) - so you can build and test the full layer without ever touching the core IP, and afterwards - I will merge your work into the production app! Scope: • Auth (Clerk): signup/login, session lifecycle, backend session/JWT verification, inject a validated `user_id` into protected endpoints. • Payments (Stripe): Checkout for purchasing usage credits, plus a webhook that credits the user's ledger on successful payment. The webhook MUST be signature-verified, idempotent (Stripe retries-credit exactly once), and reconcilable (handle webhook-failed-but-payment-succeeded). • Entitlement ledger (the core): a credit balance per user with atomic check-and-decrement (two concurrent requests must never double-spend) on PostgreSQL. A `check_entitlement(user_id, ...)`gate that expensive endpoints call before doing paid work. • Server-side route gating: enforce entitlement on every paid endpoint (not just hidden in the UI); clean 401/402/403 responses. • Frontend integration (React): login/signup UI, buy-credits/checkout flow, balance display,graceful "out of credits" states, wired to the above. • Tests for the money-critical paths (webhook idempotency, atomic decrement, gating-bypass attempts). Stack you'll work with: Python 3.11, FastAPI, Pydantic, uvicorn (Linux). React + Vite, Tailwind. PostgreSQL. Clerk. Stripe. Who I'm looking for: Someone who has shipped this exact kind of system to production before. In your proposal, briefly tell me: 1. How you ensure Stripe webhook idempotency and handle reconciliation when a webhook fails but payment succeeded. 2. How you'd implement the atomic credit check-and-decrement so concurrent requests couldn't double-spend. 3. A relevant production system you've built (Stripe + auth + usage metering ideally). *I'd much rather a short, specific proposal - than a long generic one!* Working with me: I'm an engaged founder who genuinely enjoys building, and I want this to be a good experience for both of us! I'm responsive, communicate clearly, and I respect your expertise - because you're the specialist here,and I'm hiring you because you know this much better than I do! I'm not a micromanager and I'm not nitpicky - I just want the end results to be solid! I review in milestones, asking questions because I like understanding the work (not because I'm second-guessing you), and I make decisions quickly so you're never stuck waiting on me! The scope is already well-defined (detailed spec + a runnable stub repo on engagement), so you're not pricing around a vague, shifting target - it's a clean, bounded build. I care about getting the money-handling pieces right, and I'm betting you do too - if that resonates, I think we'll work well together! IP / engagement: A mutual NDA + IP-assignment (work-for-hire) before repo access. You build against stubs; you won't receive the proprietary pipeline. Work is milestone-based, fixed-bid preferred. To apply: Answer the three questions above + share 1-2 relevant examples, and ballpark your timeline and milestone structure (suggested: auth → payments+webhook → ledger+gating → frontend → tests/docs)!

Hello - I Rebuild my website using Claude, now need to deploy on Netlify or GitHub and be able to maintain or update easily. Need to change domain from current platform to GitHub or Netlify.

We are looking to do a new build of our patch bay label designer tool. Customers are currently able to pick their model of patch bay, add text labels, colorize, and group. They can then checkout and it creates print ready artwork for our team to produce. The UI is a bit clunky and there are some features we want to add such as an admin tool to add and edit labels. You can see the current tool here: https://create.traceaudio.com/

Deploy an existing Node.js/Express app and configure SMS. I have a complete, working dispatching app (Node + Express + SQLite, plain-JS frontend). I need someone to: (1) deploy it to Render or Railway with a persistent disk and HTTPS, (2) set up a Twilio account/number and wire in the credentials so it sends automated daily texts, (3) confirm the 6 AM scheduled texts fire reliably, and (4) be available for small tweaks afterward. Code, README, and deploy steps are all included. Should be a few hours for someone experienced. Please share similar Node deployment work you've done.

Forum Intelligence: Project Brief & Initial Rollout 1. Executive Summary & Objective Forum Intelligence is a beginning as a localized data retrieval, processing, and archiving system designed to scrape public municipal records and state legislative data for public oversight. The immediate objective is to build a functional, highly resilient prototype focused on the Tri-Cities region (Burbank, Glendale, and Pasadena, California). The system will autonomously ingest messy, unstructured municipal data (City Council meeting minutes, agendas, public notices, and legislative PDF text, recorded mp4), clean it, and make it fully searchable and queryable via a localized AI agentic framework. 2. Phase 1 Scope: The Tri-Cities Rollout Th engineer will be responsible for building two primary pillars: A. Resilient Scraper Bots • Target Ingestion: Monitor and pull data from Burbank, Glendale, and Pasadena municipal portals and California legislative feeds. • Data Types: Brittle HTML sites, heavily nested tables, public notices, legislative drafts, and massive unstructured PDF archives. • Requirements: The scraping architecture must be exceptionally robust, utilizing intelligent error handling, retry semantics, and pagination tracking to handle frequent municipal website layout changes without breaking the pipeline. B. Ingestion & Vector Pipeline • Parsing: Extracting clean text from poorly formatted documents and scanned PDFs. • Local RAG (Retrieval-Augmented Generation): Chunking and embedding the data locally into a vector database (e.g., pgvector, Chroma, or Milvus) to enable semantically accurate entity linking and contextual search. 3. Targeted Hardware Stack To ensure maximum data security, strict public oversight integrity, and predictable operational costs, Forum Intelligence is skipping commercial cloud APIs in favor of an on-premise, localized NVIDIA enterprise deployment. The production roadmap aligns precisely with the new computing patterns detailed in NVIDIA’s latest hardware roadmap: • Inference & Token Generation: Running local open-weight frontier models (e.g., Neotron 3 Ultra or Claude/Llama equivalents) optimized for reasoning and long-context tool use. • Compute & Orchestration: The backend infrastructure is architected around NVIDIA’s dedicated agentic architecture, utilizing high-instructions-per-clock (IPC) Vera CPUs paired with Vera Rubin GPUs. • Memory & Storage Processing: Utilizing NVIDIA’s unified memory fabric and data processing units (DPUs) for ultra-low latency context management, KV caching, and fast vector database retrieval. 4. Immediate Milestones for the Engineer 1. Architecture Design: Map out the database schema and local inference ingestion loop. 2. Tri-Cities Scraper Deployment: Write and deploy the initial automated bots for Burbank, Glendale, and Pasadena. 3. Local MVP Pipeline: Demonstrate a local RAG pipeline where a user can query the Tri-Cities scraped records and receive grounded answers with exact source attributions. The above was AI generated from months long conversations with Gemini. The goal is to prove the concept then roll out to LA County, state of CA, and then the country.