Find Stripe Projects with Advanced Filters

We’re building a premium, category-defining product and need a top-tier motion designer/video editor to create an Apple/Google/Uber-level explainer video.

This is not a basic animation job—we’re looking for cinematic storytelling, clean UI-style motion graphics, and sharp narrative pacing that can clearly communicate a complex vision to both users and investors.

Think:
Apple product launches, Uber onboarding flows, Stripe-style explainers.

You should have experience producing high-end, minimal, story-driven videos that feel modern, intentional, and world-class.

If you’re someone who obsesses over detail, clarity, and visual storytelling—we want to work with you.

I’m adding a brand-new astrology service to my existing site and need a high-impact landing page that turns visitors into paying clients. The look should be professional and corporate while still feeling warm and intuitive. I’ll share a reference page, brand palette, copy points and anything else you need to hit the ground running.

Conversion is king here, so the page must load fast, adapt flawlessly to mobile and guide users smoothly through the booking funnel. Seamless PayPal, Stripe and direct Credit Card payments have to be integrated and fully tested before launch. Up-front sections for detailed service benefits, persuasive customer testimonials and time-sensitive promotional offers should draw the eye and nudge users toward the call-to-action.

Deliverables
• Responsive, production-ready WordPress landing page installed on my current domain
• End-to-end payment gateway setup (PayPal, Stripe, Credit Card) with sandbox proof and live switch-over
• Lightweight, conversion-focused design that meets Core Web Vitals and can be edited easily by my team

I have set aside roughly 5 k for the build, paid in milestones tied to design approval, development hand-off and final go-live.

Please reply with links to comparable landing pages you’ve built, a clear timeline and your total cost so we can lock in the schedule.

Skills: PHP, Website Design, WordPress, HTML, Conversion Rate Optimization, UI / User Interface, Payment Gateway Integration, Web Design

We are looking for an expert to help set up an AI-assisted marketing system for multiple businesses.

The goal is to build a workflow where AI supports our marketing operations, including:
* assisting with ad creation
* helping manage Meta ad campaigns
* supporting campaign deployment
* generating daily ad performance reports
* creating a repeatable workflow that can scale across multiple businesses

We are specifically interested in someone who understands how to use tools like Claude and other AI systems as part of a practical marketing workflow, not just for content writing but for real operational use.

Scope
We want someone to:
* Review our current setup and recommend the best way to structure this
* Explain what tools, accounts, access, and integrations are needed
* Set up the initial workflow/system
* Advise what parts can realistically be automated vs what still needs manual review
* Help create a daily reporting process for Meta ads
* Potentially train us on how to use and manage the system moving forward

Platforms / Tools
* Meta Ads Manager
* Claude
* Possible automation tools such as Zapier, Make, or similar
* Google Sheets / reporting dashboards
* Any other tools you recommend

What we want from you
Please reply with:
* Your recommended approach to setting this up
* What access or assets you would need from us
* What parts can be automated
* What parts should stay manual
* Examples of similar systems or workflows you have built
A rough idea of setup cost, timeline, and ongoing management requirements

This is for a serious business owner spending significant money on marketing and wanting to reduce waste by building a smarter internal system.

Thank you!

Jas A.

Attachment Description:

The attached document provides a high-level technical overview of our platform’s payment architecture. It outlines the system structure, data flow, and how payments are staged internally using a ledger-based model.

The document is intended to give developers a clear understanding of how our system operates and what is required for the Stripe integration. It includes simplified table structures, example payloads, and the expected payment execution flow.

This is a read-only overview and does not contain any sensitive data or source code.

• Have you built a Stripe Connect marketplace before? If yes, briefly describe the flow (client payment → platform → contractor payout)
• How would you process multiple payouts from a single job (one payment split across contractor, platform, and retained fees)?
• How would you prevent duplicate payments if the same payout request is sent twice?
• What Stripe webhooks would you use to track successful and failed payments?
• How long would it take you to build this system end-to-end?

I need a backend developer to build an automated SMS delivery system for my coaching platform.

CURRENT SETUP:
- FastAPI backend deployed on Railway
- Stripe payment integration
- Twilio account set up with phone number
- Program generation code already exists
- PostgreSQL/Supabase database

WHAT I NEED:
When a customer completes payment via Stripe:
1. The system already generates their custom content and saves it to the database (this works)
2. I need you to build a scheduled job that automatically texts them their content at a randomized time between 12pm-6pm ET the next day
3. Each customer should only receive their content once (no duplicates)
4. Proper error handling and logging

TECHNICAL REQUIREMENTS:
- Set up cron job or scheduled task on Railway that runs daily
- Query database for customers who paid in last 24-48 hours and haven't been texted yet
- Format and send data via Twilio SMS
- Mark customer as "content_sent: true" in database after sending
- Randomize send time between 12pm-6pm Eastern Time for each customer
- Handle timezone conversion (ET)
- Log all sends and errors

DELIVERABLES:
- Updated main.py with scheduling logic
- Any necessary database migrations
- Railway deployment configuration
- Brief documentation on how it works
- Test it works with at least 2 test customers

TIMELINE: 3-5 days

TO APPLY:
Please share:
1. Your experience with FastAPI and Python backend development
2. Experience with Twilio or other SMS APIs
3. Example of a scheduled/automated system you've built

We’re looking for a skilled GHL Expert to become a long-term extension of our team.

This role involves managing and supporting day-to-day GoHighLevel tasks across multiple client accounts. You’ll be working closely with our internal team to build, optimize, and maintain systems that directly impact our clients’ marketing and operations.

What you’ll be responsible for:

Setting up and managing GoHighLevel accounts for clients
Building and optimizing workflows, automations, and triggers
Creating and managing funnels, forms, calendars, and pipelines
Launching and maintaining email & SMS campaigns
Troubleshooting GHL issues and improving system performance
Handling integrations (Zapier, Stripe, APIs, third-party tools)

What we’re looking for:

Proven, hands-on experience with GoHighLevel (GHL)
Strong understanding of CRM systems and automation logic
Ability to work independently while following SOPs
Detail-oriented, responsive, and reliable communicator
Comfortable working with multiple client accounts

Why work with us:

Consistent, long-term work (not a one-off project)
Clear processes, SOPs, and expectations
Opportunity to grow with a scaling GHL agency
White-label agency experience

If you’re a GHL expert looking for stable, ongoing work with an agency partner, we’d love to hear from you.
Please include examples of your GoHighLevel work or past agency experience.

Senior Tracking Engineer (GTM Server-Side, Meta CAPI, TikTok Events API) – High-Impact Project

Overview
We’re looking for a top-tier tracking / growth engineer to build a best-in-class server-side tracking and attribution system for a large-scale endurance event company (marathons, races, etc.).

This is not a basic pixel install — we need someone who deeply understands modern attribution, iOS tracking limitations, and server-side event architecture.

Our goal is simple:
Track every purchase (race registration) back to the correct ad source (Meta, TikTok, Google)
Improve signal quality to drive better performance and lower CAC

Our registration platform is Let's Do This, and a key part of this project is ensuring accurate tracking and attribution through their checkout and purchase flow.

---

Scope of Work

1. Google Tag Manager (Web + Server-Side)

* Audit existing GTM setup
* Implement or refine GTM Web container
* Set up GTM Server-Side container
* Deploy via Google Cloud, Stape, or similar
* Configure custom tracking subdomain (e.g. track.ourdomain.com)

2. GA4 + Event Architecture
Implement clean, consistent event tracking:

* view_item
* add_to_cart
* begin_checkout
* purchase
* generate_lead

Ensure proper parameter passing:

* value
* currency
* product (race type)
* user identifiers

3. Meta Conversion API (CAPI)

* Full server-side integration via GTM
* Event deduplication (browser + server using event_id)
* Advanced matching:

* email (hashed)
* phone (hashed)
* IP, user agent
* Optimize for high event match quality (8–10/10)

4. TikTok Events API

* Server-side implementation (not just pixel)
* Track key events (ViewContent, AddToCart, Purchase)
* Ensure proper attribution and matching

5. UTM + Click ID Tracking

* Capture and persist:

* fbclid
* ttclid
* gclid
* Ensure these are passed through to purchase events

6. Data Layer Implementation
Design and implement a structured data layer including:

* user_id
* email (hashed where needed)
* event_name
* order_value
* race_type (product category)
* utm parameters
* click IDs

7. Registration Platform Integration (Let’s Do This)

* Ensure tracking persists from marketing site through Let’s Do This checkout
* Capture and pass UTM parameters and click IDs into the registration flow
* Ensure purchase events are correctly fired and attributed back to the original source
* Work within Let’s Do This constraints (redirects, hosted checkout, etc.) to maintain attribution integrity

8. Conversion Value Optimization

* Pass dynamic purchase values
* Enable value-based optimization in Meta and TikTok

9. QA, Testing and Validation

* Ensure proper event firing across platforms
* Validate deduplication logic
* Confirm attribution accuracy
* Debug discrepancies between GA4 and ad platforms

---

What We’re Looking For

You should have:

* Proven experience with:

* GTM (Web + Server-Side)
* Meta Conversion API
* TikTok Events API
* Strong understanding of:

* Attribution challenges (iOS 14+, ad blockers, etc.)
* Event deduplication (event_id)
* Match quality optimization
* Experience working with:

* E-commerce or high-volume conversion funnels
* Third-party checkout or hosted registration platforms (critical)

---

Nice to Have

* Experience with:

* Google Cloud or server deployments
* BigQuery or data warehousing
* Multi-step checkout tracking
* Familiarity with platforms like:

* Shopify, Stripe, or similar checkout systems

---

To Apply (Important)
Please include:

1. A brief description of a similar server-side tracking setup you’ve implemented
2. How you handle event deduplication between browser and server
3. How you track attribution through a third-party checkout (like Let’s Do This, Shopify, etc.)
4. How you improve Meta match quality
5. Any examples or screenshots of your work, if available

---

Project Details

* Timeline: ASAP (priority project)
* Budget: Flexible for the right candidate (fixed or hourly)
* Potential for ongoing work if successful

---

Why This Matters
This is a high-impact project — getting this right directly improves:

* Ad performance
* Attribution accuracy
* Revenue growth

We’re looking for someone who takes ownership and builds this the right way.

I’m looking for an experienced automation / funnel specialist to help set up the backend systems for my online course Wedding Studio Blueprint.

The course will be hosted on Skool, and I already have Stripe set up for payments. The course content is nearly finished. I need help connecting everything so the system runs smoothly and automatically.

This is a one-time setup project for the initial launch, but there is potential for ongoing work if things go well.

Overview of what I need built:

• Stripe checkout setup (including payment plan option)
• Automation connecting Stripe → Skool access for students
• Email automation setup for leads and students
• Lead capture + nurture sequence
• Basic sales funnel setup
• Instagram DM automation using ManyChat
• Testing the entire purchase → onboarding flow

Tech stack:

• Skool (course & community)
• Stripe (payments)
• Email platform (ConvertKit / Kit preferred)
• ManyChat (Instagram automation)
• Zapier or Make (automation layer)

What success looks like:

When someone finds our free training, they should be able to:

Opt in with their email

Receive the training and email sequence

Purchase the course through Stripe

Automatically receive access to the Skool community

Receive onboarding emails and instructions

The entire flow should be automated and fully tested.

Ideal candidate experience:

• Experience building funnels for online courses or coaching programs
• Strong familiarity with Skool, Stripe, Zapier/Make, email automation tools
• Experience with ManyChat or Instagram automation
• Able to keep systems simple and clean (not overly complicated)

To apply, please include:

A short explanation of similar projects you’ve completed

Tools you prefer to use for automation

A rough estimate of timeline for a setup like this

Any examples of course funnels you’ve built

Looking forward to working with someone who can help make this system run smoothly for launch.

I built an MVP that helps people to make legal filings online with minimal attorney oversight. I want to roll it out and scale it, and am ready to do so, but I vibe coded it on Lovable, and before I roll-out and scale, I want someone with expertise on Supabase integration, security testing, vulnerability addressing, and database architecture to do an audit. If you have skills in this area, and in particular, for technologies that handle lots of personally identifiable data in compliance with applicable privacy laws, I'd like to hear from you.

Here's my tech stack

Frontend: React 18, Vite, TypeScript, Tailwind CSS, shadcn/ui
Backend: Lovable Cloud — Auth, Postgres, Edge Functions, RLS. Supabase.
Payments: Stripe Checkout
Email: Resend (via send-agent-email edge function)
AI Chat: OpenAI GPT (via chat-assistant edge function)
PDF Generation: pdf-lib (server-side edge function)
Forms/Validation: React Hook Form + Zod
PDF Viewing: pdfjs-dist
Routing: React Router v6
State Management: TanStack React Query

• Describe your recent experience with similar projects
• Please list any certifications related to this project

**Overview**

I'm building a done-for-you AI receptionist service for home service businesses (tree service, lawn care, HVAC, pest control) using GoHighLevel. I have a fully documented 7-section technical playbook that covers every field, workflow, snapshot, SMS template, and automation step in detail. I need an experienced GHL builder to execute the build — not design it. Strategy and copy are already done.

This is a fixed-scope project with a clear deliverable checklist. If you're a strong GHL technician who can read documentation and build clean, reliable automation, this is a great fit.

---

**What needs to be built**

All of the following is documented in the playbook I'll share upon hire:

1. GHL custom fields (12 fields — dropdowns, radio buttons, hidden fields, short text)
2. Three automated workflows:
- Workflow 1: Demo call follow-up (trigger: Voice AI call ended → SMS fires with pricing page link)
- Workflow 2: Intake form onboarding (trigger: form submitted → tags applied → niche snapshot deployed → carrier-specific forwarding SMS → Stripe payment link sent via conditional branch by tier)
- Workflow 3: Payment confirmed (trigger: Stripe webhook → active-client tag → welcome SMS → Dominance tier dashboard credentials email)
3. Four niche snapshots (tree service, lawn care, HVAC, pest control) — each with pre-configured Voice AI greeting, FAQ responses, pipeline stages, and reactivation sequences
4. GHL intake form (embedded-ready, 14 fields, with hidden tier field passed via URL parameter)
5. Stripe webhook connected to GHL to trigger Workflow 3 on payment success
6. Voice AI agent configured on demo sub-account with qualifying question and niche branching logic
7. End-to-end QA test using a dummy contact through the full funnel

---

**Deliverables**

- All workflows live and tested in my GHL Agency account
- All 4 snapshots saved and deploy-ready
- Intake form exported as embeddable code snippet
- Stripe webhook confirmed active and triggering correctly
- Short Loom walkthrough (5–10 min) showing each workflow firing correctly
- Notes on anything in the playbook you adjusted and why

---

**What I'll provide you**

- Full 7-section playbook (Word doc) with every field name, workflow step, SMS template, branch logic, and snapshot content already written
- GHL Agency sub-account access
- Stripe account access (read-only + webhook setup)
- Direct communication via Upwork messages — I'm responsive and can answer questions quickly

---

**Requirements**

- Proven GoHighLevel experience — please share 2–3 examples of workflow automation or snapshot builds you've completed (screenshots or Loom)
- Demonstrated experience with GHL Voice AI / AI Employee setup
- Experience connecting Stripe webhooks to GHL workflows
- Strong attention to detail — this build has conditional branching and multi-step logic that must work correctly
- Fluent written English for communication
- Available to start within 1 week

---

**What I'm NOT looking for**

- Sellers who will read the playbook and ask me to redesign the strategy
- Template-based builds that don't follow the documented specs
- Developers who need to learn GHL during the project
- Agencies with long timelines — this is a focused, well-documented build

---

**Budget & timeline**

Budget: $400–$700 fixed price (based on your experience and portfolio)
Timeline: 7–10 business days from project start
I'm open to milestone-based payment: 50% on start, 50% on delivery + QA pass

---

**To apply, please answer these three questions in your proposal:**

1. Share an example of a GHL workflow you've built that uses conditional branching (if/else logic based on tags or form fields). A screenshot or Loom is ideal.
2. Have you configured GHL Voice AI agents before? If yes, describe what you built.
3. What is your process when a playbook has a step that's technically difficult or unclear in GHL — how do you handle it?

Applications that don't answer these questions will not be reviewed.

---

*Posted by: Brandon McFall — McFall Media, Orlando FL*
*AI receptionist service for home service businesses*

I am a men's transformation coach running a group coaching program called RMK — a brotherhood ecosystem for ambitious fathers. I need an expert automation builder to set up a complete AI-powered operating system for my business from scratch.

This system will connect all of my existing tools, automate my content creation, client tracking, accountability workflows, and calendar management, and give me a single dashboard where I can review, approve, and deploy everything with minimal manual effort.

You will be given secure remote desktop access to my Mac and all necessary account credentials. Your job is to build, connect, and test every component listed below until the system is fully operational.


Tools and Platforms Involved

Tools Already Active (You Will Connect These)
• Zoom — cloud recording and transcription enabled
• Skool — course delivery, call calendar, Zoom recordings
• Jotform — client applications and weekly Sunday reflection forms
• WhatsApp — community messaging (manual posting, automated staging)
• Google Drive — central file storage
• Google Calendar — call scheduling, event triggers, and weekly planning blocks
• Gmail — inbox management, priority flagging, spam cleanup
• Canva — graphic design templates for content
• ManyChat — Instagram DM automation
• Notion — brand SOPs and voice documentation
• WordPress — website lead capture and Calendly embedding

Tools You Will Set Up and Connect
• n8n Cloud — automation backbone (all workflows)
• Supabase — database for all structured data, client records, and reminders
• Claude API (Anthropic) — all AI processing, analysis, content generation, and planning prompts
• Retool (free tier) — full operations and executive assistant dashboard
• Kit (formerly ConvertKit) — email marketing, CRM sequences, and onboarding
• Calendly — qualifying call booking, embedded in WordPress
• Later or Buffer (optional) — content scheduling if client chooses to connect a scheduler
• 1Password Teams or Bitwarden Business — secure credential sharing with VA, hidden passwords, audit logging


Workflows to Build — Full Detail

Workflow 1 — Jotform Sunday Reflection Tracker
Every Sunday clients complete a Jotform reflection. The system must:
• Receive Jotform submissions via webhook into n8n
• Log each submission into Supabase table: jotform_submissions (client name, date, answers)
• At 8:45am every Monday AEST, run a scheduled workflow
• Query Supabase — compare submissions against full client list
• Send both lists to Claude API with a prompt that produces a formatted accountability post
• Post format: green tick emoji next to names who submitted, red cross next to names who did not
• Written in the client's brand voice (brand voice document provided)
• Output staged in Retool dashboard under Today's Tasks, ready to copy and paste

Workflow 2 — Zoom Call to Full Content Engine
This is the core workflow. When a Zoom call ends:
• Zoom cloud recording saves transcript automatically to Google Drive folder: Zoom Transcripts
• n8n detects new file in that folder via Google Drive trigger
• n8n reads the transcript file contents
• Sends full transcript to Claude API with a structured prompt
• Claude extracts: key themes taught, real phrases used by clients, questions asked, emotional moments, breakthroughs
• Claude then produces ALL of the following outputs in one workflow pass:
• 1. Call Review Summary — what landed, what to revisit, client engagement notes
• 2. YouTube Video Structure — crafted angle based on client responses, hook for target market, teaches value without giving everything away
• 3. Two Instagram Reel Scripts — short form, hook-led, in brand voice
• 4. One Carousel Hook and Outline — hook line plus 5-7 slide structure
• 5. Three WhatsApp Community Messages — in brand voice, varied angles
• 6. Potential Course Lesson Structures — any teachable frameworks that emerged
• Each output saved to its correct Google Drive subfolder automatically
• All outputs appear in Retool Review Queue awaiting approval
• Workflow logs call date and output status to Supabase

Workflow 3 — Content Approval and Banking
• Retool Review Queue displays all generated content with Approve and Rework buttons
• Approve — content moves to corresponding Google Drive Approved Content subfolder
• Rework — user leaves note, n8n resubmits to Claude API with feedback, revised version returns to queue
• Approved YouTube Scripts go to: Approved Content / YouTube Scripts
• Approved Reel Scripts go to: Approved Content / Reel Scripts
• Approved Carousel Outlines go to: Approved Content / Carousel Scripts
• Approved WhatsApp Messages go to: Approved Content / WhatsApp Messages

Workflow 4 — Canva Template Population
• Client builds carousel and reel cover templates in Canva once (template IDs noted)
• After Claude generates carousel outline and reel scripts, n8n calls Canva API
• Canva node populates template with generated hook text and slide copy
• Finished graphic files saved to Google Drive: Canva Outputs
• Outputs appear in Retool Review Queue alongside written content

Workflow 5 — Zoom Link Staging
• n8n runs a scheduled check every hour via Google Calendar trigger
• Checks for calendar events in the next 12 hours containing a Zoom link
• Claude formats a call reminder message in brand voice with time, Zoom link, and call context
• Staged message appears in Retool Today's Tasks at the appropriate time
• Client copies and pastes into WhatsApp manually

Workflow 6 — WhatsApp Chat Analysis
• Client exports WhatsApp group chat as .txt file (native WhatsApp export function)
• Client drops file into Google Drive folder: WhatsApp Exports
• n8n detects new file via Google Drive trigger
• File sent to Claude API with extraction prompt
• Claude identifies each community member by name and extracts:
• — Post count and frequency
• — Questions asked
• — Sentiment and emotional tone
• — Signs of struggle, disengagement, or withdrawal
• — Wins and breakthroughs mentioned
• Claude updates each client record in Supabase with new activity data
• Daily community insights report generated and posted to Retool: Community Insights section
• Any client flagged as struggling or going quiet appears in Retool: Needs Attention

Workflow 7 — Client Profile Intelligence
• Every workflow writes data back to the client record in Supabase
• Retool Clients section — searchable by name
• Each profile shows: check-in history, WhatsApp activity, Zoom attendance, Jotform answers, AI-generated flags
• Weekly summary runs every Sunday evening — flags clients who missed 2+ check-ins or show struggle patterns
• Flags appear in Retool dashboard Monday morning

Workflow 8 — Weekly Content Calendar
• Every Sunday evening n8n pulls data from that week — Zoom transcript outputs, Jotform responses, WhatsApp export analysis
• Claude produces a 7-day content plan: what to post, which format, which angle, based on real community data
• Calendar appears in Retool Weekly Calendar section every Monday morning

Workflow 9 — CRM and Email Automation via Kit
• Jotform application form submission triggers n8n
• New contact created in Kit with appropriate tags: lead, applied, active, past client
• Welcome email sequence fires automatically upon application
• Contact details also stored in Supabase clients table
• Retool CRM view shows pipeline: Lead, Applied, Onboarding, Active, Past Client
• Client can filter, search, add notes, update pipeline stage from Retool
• Email broadcasts sent manually via Kit — list is always current because n8n keeps it updated

Workflow 10 — ManyChat Instagram Integration
• ManyChat connected to Instagram account
• Trigger keyword flows built: comment on reel triggers DM sequence
• DM sequence moves prospect toward application or community
• When approved Instagram content leaves Retool Review Queue, caption and post details formatted and staged

Workflow 11 — WordPress Lead Capture
• WordPress website connected to n8n via webhook
• Any opt-in form, contact form, or lead magnet form on the website triggers n8n automatically
• n8n creates contact record in Supabase with source tag: website
• Contact added to Kit with tag: website-lead
• Welcome or nurture email sequence fires automatically in Kit
• Lead appears in Retool CRM pipeline under stage: Lead
• If lead came from a specific page or offer, that is tagged in Supabase for tracking
• Recommended WordPress plugin: WPForms or Gravity Forms — both connect cleanly to n8n webhooks

Workflow 12 — Qualifying Call Booking System
• Calendly account set up and embedded on WordPress website
• A qualifying Jotform or Typeform is placed in front of the booking calendar — prospects must answer qualifying questions before accessing the calendar
• Only qualified responses unlock the Calendly booking link (conditional redirect set up on the form)
• When a call is booked via Calendly, n8n is triggered automatically
• n8n creates or updates contact in Supabase with stage: Call Booked
• Contact tagged in Kit: call-booked — triggers confirmation email sequence
• Call appears in Google Calendar automatically
• 12 hours before the call: n8n stages a call reminder message in Retool Today's Tasks
• If prospect does not show: n8n detects no-show via Calendly webhook and triggers a follow-up email sequence in Kit
• If call is completed: stage updated to Applied or Active depending on outcome — triggered manually or via a post-call Jotform
• Full call pipeline visible in Retool CRM: Lead → Qualified → Call Booked → Call Completed → Applied → Active

Workflow 13 — Google Drive Auto-Organisation
• Full folder structure built and standardised as part of initial setup (see folder structure section below)
• All n8n workflows updated to save files with consistent naming conventions: YYYY-MM-DD_Type_Description
• Zoom transcripts named automatically: YYYY-MM-DD_ZoomTranscript_CallTitle
• Content outputs named automatically by type and date
• WhatsApp exports named and archived by date
• Approved content separated from drafts at all times — no file sits in the wrong folder
• n8n runs a weekly tidy workflow every Sunday: scans for any files not in the correct folder and flags them in Retool for review
• Canva outputs auto-named and saved to correct subfolder upon generation
• Old drafts (not approved within 14 days) automatically archived to an Archive subfolder to keep active folders clean

Workflow 14 — AI Weekly Planning and Executive Assistant
This workflow turns the Retool dashboard into a personal concierge that plans, prioritises, and organises the client's week with AI-guided prompting. It functions as an executive assistant for both business and personal life.
• Every Sunday evening a Weekly Planning session is triggered in the Retool dashboard
• Claude reads the existing Google Calendar for the coming week — pulls all current bookings, calls, and blocked time
• Claude prompts the user with a structured planning interview inside the dashboard:
• — What is your intention and outcome for this week?
• — What are your top 3 priorities this week across Business, Body, and Relationships (RMK pillars)?
• — What are your 3 Most Important Tasks for each day?
• — Are there personal commitments, appointments, or obligations to factor in?
• — Are there habits or routines you want protected and blocked in the calendar?
• Claude identifies blank spots in the calendar and prompts the user to assign or fill them
• Based on responses, Claude generates a structured weekly schedule posted to Retool Weekly Planner section
• n8n creates Google Calendar blocks for: MIT (Most Important Task) time, routine blocks, content creation sessions, recovery and personal time
• Daily morning brief delivered every day at 6am AEST — appears in Retool and optionally via email: today's schedule, top 3 tasks, one motivating line in brand voice
• Claude learns recurring patterns over time — favourite routine slots, preferred work blocks — and pre-populates future planning sessions automatically
• All weekly intentions, priorities, and outcomes logged in Supabase for long-term pattern tracking

Workflow 15 — Gmail Executive Inbox Management
Gmail connected to n8n via Google API. The system acts as an intelligent inbox manager.
• Gmail account connected to n8n via Google OAuth
• Daily at 7am AEST: n8n scans inbox and Claude categorises all new emails
• Priority emails — anything requiring action, response, or decision — surfaced in Retool under Email Priorities
• Recurring emails not opened in 30+ days listed in Retool under Unsubscribe Suggestions with one-click unsubscribe links where available
• Promotional emails, newsletters, and clear spam auto-labelled in Gmail for batch review or deletion
• n8n can auto-delete emails matching defined spam patterns — rules defined by user at setup
• Weekly inbox health report generated: emails received, actioned, unread count, suggested cleanups — delivered to Retool dashboard
• User approves bulk deletions and unsubscribes from the dashboard without opening Gmail
• If a known client or lead emails, their Supabase record is flagged in Retool automatically

Workflow 16 — Client Birthday and Retention Reminders
Every client record holds a birthday and program start date. No important date is ever missed.
• Supabase client table includes: date_of_birth, program_start_date, program_end_date
• n8n runs a daily check at 7am AEST against all active client records
• Birthday: 3 days before a client birthday, Retool notification fires and Claude generates a personalised message draft ready to send via WhatsApp
• Retention alert: 30 days before a client reaches 12 months in RMK, they appear in Retool under Client Retention Alerts
• Claude generates a personalised retention prompt — client wins, re-engagement message draft, suggested conversation starters — pulled from their full Supabase profile history
• Re-enrolment sequence triggerable from the dashboard — fires Kit email and stages WhatsApp message
• Program completion day: congratulations message draft generated and staged automatically
• All reminder triggers and outcomes logged in Supabase

Workflow 17 — Client Onboarding and Profile Builder
When a new client joins RMK, their full profile is built in Supabase automatically. Existing clients are imported in one pass.
• New client onboarding Jotform built — collects: full name, date of birth, email, phone, WhatsApp number, program start date, goals, background, family details
• Jotform submission triggers n8n — full client record created in Supabase instantly
• Contact created in Kit tagged: active-client — onboarding email sequence fires
• Client profile appears in Retool fully populated and immediately searchable
• Existing clients: a CSV import workflow built so all current client data can be uploaded into Supabase in one pass — no manual entry required
• AI onboarding prompt in Retool: when a new client is added, Claude asks follow-up questions to fill any profile gaps and capture goals and starting context
• All future workflow data — check-ins, Zoom attendance, WhatsApp activity, Jotform submissions — automatically appended to the profile

Workflow 18 — Content Scheduling and Publishing Pipeline
Connects the content generation engine to a full scheduling and publishing pipeline.
• Every Monday morning after the weekly plan is approved, Claude generates a full 7-day content calendar
• Calendar based on: Zoom transcript outputs, Jotform responses, WhatsApp activity, and the user's stated weekly intention
• Content calendar shows: platform, format, angle, hook, status (draft / approved / scheduled)
• Approved content assigned a publish date and time from within Retool
• If a scheduler is connected (Later or Buffer), approved posts pushed directly from the dashboard
• If no scheduler is used, content staged with a Retool notification at chosen publish time
• Content gaps flagged by Claude with suggested filler angles
• Monthly content review: Claude flags underserved platforms and suggests content mix adjustments

Workflow 19 — Role-Based Access Control and VA Security Architecture
The system must be built from day one with multi-user access in mind. The owner has full access to everything. A virtual assistant has a separate, restricted access layer with a full audit trail. No sensitive credentials are ever stored inside the system in plain text.

Owner Access — Full System
• Owner has full access to all Retool sections, all Supabase data, all n8n workflows, and all connected accounts
• Owner login protected with two-factor authentication on all platforms
• Owner is the sole admin on Supabase, n8n, and Retool — no other user has admin rights

VA Access — Restricted and Audited
• VA is given a separate Retool login with role set to: VA
• VA Retool view contains only: Content Queue, Client Task List, Workflow Health Monitor, Communication Drafts, Onboarding Checklist
• VA cannot see: Weekly Planner, Gmail Priorities, owner personal data, financial data, full client notes, or any section marked owner-only
• Supabase Row Level Security (RLS) enabled on all tables — VA database queries only return rows they are permitted to see, enforced at database level not just UI level
• VA does not have direct n8n access unless a specific workflow management task requires it — if so, a read-only n8n viewer account only
• All VA actions inside Retool are logged in Supabase: action type, timestamp, user ID — full audit trail accessible to owner at all times
• Owner can revoke VA Retool access instantly from the admin panel without affecting any workflows or data

Credential and Financial Security
• 1Password Teams or Bitwarden Business set up as the credential management layer
• All sensitive credentials — Stripe, banking, social accounts, API keys — stored in 1Password only, never inside Retool, Supabase, or n8n in plain text
• VA given access only to specific 1Password vault items they need — using hidden password sharing (VA can use credentials to authenticate but cannot read or copy the actual password)
• Owner receives a full 1Password audit log of every credential access event
• Owner can revoke VA credential access instantly from 1Password without changing the passwords themselves
• API keys stored as environment variables inside n8n and Supabase — never exposed in workflow logic or dashboard UI
• Two-factor authentication enforced on: Supabase, n8n, Retool, Google accounts, and 1Password

VA Dashboard Section in Retool
A dedicated VA view must be built inside Retool as a separate app or role-gated tab. It must include:
• Content Queue — all content in the review and scheduling pipeline, with ability to organise and move items
• Client Task List — daily task list generated from system workflows: who needs follow-up, new onboarding tasks, check-in flags
• Workflow Health Monitor — live status of all n8n workflows, error alerts, last run timestamps — so VA can flag issues without needing n8n access
• Communication Drafts — WhatsApp messages and emails staged and ready, VA can prepare and mark as ready for owner review
• Onboarding Checklist — when a new client joins, a step-by-step onboarding task list is generated for the VA to work through
• All VA actions time-stamped and logged — owner can see exactly what was done, when, and by whom
• VA section is built and role-gated from day one even if not immediately activated — ready to hand to a VA when the time comes


Retool Dashboard — Sections to Build

Section
Function
Today's Tasks
Morning brief, staged WhatsApp messages, Zoom links, accountability posts — ready to act on
Review Queue
All AI-generated content awaiting approval or rework
Community Insights
WhatsApp analysis report, Needs Attention flags
Client Profiles
Searchable client database with full history and AI flags
CRM Pipeline
Lead through to past client — filterable, searchable, with notes
Content Bank
All approved content sorted by type and date
Weekly Planner
Sunday planning interface — AI prompts, calendar view, MIT blocks, weekly intention and priorities
Client Retention Alerts
Clients within 30 days of program end — personalised re-engagement prompts
Email Priorities
Priority Gmail flagged — unsubscribe suggestions and inbox health report
Content Calendar
7-day content plan with scheduling, publish status, and gap alerts


Supabase Database — Tables to Create

Table Name
Contents
clients
Name, email, phone, DOB, WhatsApp, Kit tag, pipeline stage, program_start_date, program_end_date, family details, goals, notes
leads
Name, email, phone, source, applied date, stage
jotform_submissions
Client name, form type, submission date, answers
zoom_calls
Call date, transcript file path, content outputs logged, attendees
whatsapp_exports
Export date, file path, processed flag
client_activity
Client name, date, activity type, score, flags
insights
Date generated, insight type, content, client reference
content_assets
Type, title, file path, status, approved date, platform, scheduled date
daily_messages
Message type, content, scheduled time, posted flag
weekly_plans
Week start date, intention, priorities, MIT tasks per day, calendar blocks created
reminders
Client reference, reminder type (birthday/retention/anniversary), trigger date, status, message draft
email_flags
Email subject, sender, date, priority flag, action taken, unsubscribe status


Google Drive Folder Structure — Full Organisation

The VA must build this exact structure and ensure all n8n workflows save files into the correct folders with correct naming conventions (YYYY-MM-DD_Type_Description).

• RMK OS (parent folder)
• — 01 Zoom Transcripts
• — Archive (transcripts older than 30 days auto-moved here)
• — 02 WhatsApp Exports
• — Archive
• — 03 Content Drafts
• — YouTube Scripts
• — Reel Scripts
• — Carousel Scripts
• — WhatsApp Messages
• — Archive (unapproved drafts older than 14 days)
• — 04 Approved Content
• — YouTube Scripts
• — Reel Scripts
• — Carousel Scripts
• — WhatsApp Messages
• — 05 Canva Outputs
• — Carousels
• — Reel Covers
• — 06 Call Reviews
• — 07 Client Documents
• — 08 Lessons and Course Content
• — 09 Website and Lead Assets
• — Lead Magnets
• — Opt-in Forms
• — 10 Brand Assets
• — Logos
• — Templates
• — SOPs


Deliverables — What Must Be Working on Completion

The following must be fully operational and tested before the job is considered complete:

1. All 19 workflows and system components built, active, and tested end to end
2. Supabase database created with all tables and relationships
3. Retool dashboard built with all sections functional and connected to live data
4. Google Drive folder structure created and connected to n8n triggers
5. Claude API integrated and tested — content outputs verified in correct voice
6. Kit account set up with tags, welcome sequence built, and connected to Jotform via n8n
7. ManyChat connected to Instagram with at least one trigger flow active
8. Canva API connected and template population workflow tested
9. Full walkthrough video recorded — screen capture of every workflow and dashboard section
10. WordPress website connected to n8n — lead capture forms triggering full automation sequence
11. Calendly embedded on WordPress with qualifying form gate — full booking to follow-up sequence tested
12. Google Drive fully organised with correct folder structure — all workflows saving files with correct naming conventions
13. Role-based access control implemented — Supabase RLS active on all tables, VA Retool role built and tested, owner and VA logins both verified
14. 1Password or Bitwarden set up — all sensitive credentials migrated in, VA sharing configured with hidden passwords, audit logging active
15. VA dashboard section built in Retool — all five sections functional, role-gated, and ready to activate when a VA is hired


Applicant Requirements

You must have demonstrated experience in:
• n8n — building multi-step workflows with webhooks, scheduled triggers, conditional logic, and AI nodes
• Supabase — database design, table relationships, querying via n8n
• Claude API or OpenAI API — prompt engineering, multi-step AI workflows, and conversational prompting
• Retool — building multi-section operational dashboards connected to live Supabase data
• Google Drive, Google Calendar, and Gmail API integrations
• WordPress webhook integration — WPForms or Gravity Forms preferred
• Calendly — embedding on WordPress, webhooks, and n8n integration
• Jotform webhooks and form logic
• Kit or similar email marketing and sequence platforms
• Canva API (preferred — must be willing to learn if not)
• ManyChat or Instagram DM automation (preferred)
• CSV import workflows into Supabase for bulk data migration
• Google Calendar write access via n8n — creating and blocking calendar events programmatically
• Supabase Row Level Security (RLS) — experience implementing role-based access control at database level
• Retool role-based access — building multi-user dashboards with separate permission levels
• 1Password Teams or Bitwarden Business — credential vault setup and hidden password sharing

Please include in your application:
• Examples of similar automation systems you have built
• Your estimated timeline to complete this project
• Any tools in this stack you have not worked with before and how you will handle them
• Your approach to testing and handover


Budget and Pricing Rationale

Item
Detail
Estimated hours (expert builder using AI tools)
18–24 hours
Rate basis
USD $6–$8/hour (VA automation specialist rate)
Budget range (USD)
USD $140–$190
Budget range (AUD)
A$215–A$295 approx.
Payment structure
50% on start, 50% on completion and verified testing
Bonus available
A$35 bonus if completed within 7 days and all workflows pass first test

Note: This budget reflects a specialist VA rate. If you are quoting significantly above this range, please explain what additional value you are bringing. We are open to negotiation for the right person with verified experience in this exact stack.


What to Include in Your Proposal

Keep your proposal direct. We do not need long introductions. Tell us:
• Which tools in this stack you have built with before (be specific)
• One example of an automation system you have built that is similar to this
• Your honest timeline to complete the full build
• Any part of this project you would approach differently and why
• Your fixed price quote in USD

Proposals that are clearly copy-pasted or do not reference the specific tools in this project will not be considered.


RMK — Built for Men Who Lead

Project Overview
I’m building an AI-powered payment assistant (Smither) that allows users to send and schedule payments through a chat interface (starting with Telegram). The goal is to launch a functional MVP quickly that demonstrates end-to-end flow: user input → AI parsing → confirmation → logging → payment trigger.

⸻

Scope (MVP Phase 1)
Looking for a developer who can connect the core pieces into a working system:
• Telegram bot that captures user messages
• Send messages to OpenAI API for structured parsing (amount, recipient, timing)
• Return parsed response clearly to user
• Confirmation step before execution
• Store all requests in Google Sheets or simple database
• Basic scheduling logic (delayed payments)
• Webhook/API handling to connect services

⸻

Tech Stack (Preferred but flexible)
• Node.js or Python backend
• OpenAI API (GPT-4 or similar)
• Telegram Bot API
• Google Sheets / simple DB (Firebase, Supabase, etc.)
• Webhooks / Make.com / Zapier (optional but a plus)

⸻

Important Notes
• This is an MVP — speed and functionality matter more than perfection
• System should be built clean enough to expand later
• Payment execution can be simulated or simplified in this phase if needed
• Experience with Stripe, fintech, or wallet integrations is a plus

⸻

What I’m Looking For
• Someone who can actually connect systems end-to-end, not just write isolated code
• Clear communicator who can suggest improvements if something is overcomplicated
• Ability to build fast and iterate

⸻

Deliverable
A working MVP where a user can:
1. Send a payment request via Telegram
2. Have it parsed and confirmed
3. Logged and scheduled
4. Ready for execution (real or simulated)

⸻

Potential for Ongoing Work
If this phase goes well, there will be continued work expanding into full payment integration, wallet infrastructure, and scaling the system.

⸻

If you’ve built similar chatbot, AI, or payment-based systems, please include examples.

Deploy & Customize a React SaaS Assessment Tool (Next.js + Supabase + Stripe)

I have a fully built React application (single-file JSX, ~130KB of working code) that needs to be deployed as a production SaaS product. The app is a sales candidate assessment platform with AI-powered grading via the Anthropic API.

What's already built:
- Complete React UI with 115+ assessment questions, scoring system, AI grading, candidate forms, comparison views, and printable reports
- All business logic, state management, and component architecture
- Brand design and styling complete

What I need you to do:

1. Convert the single-file React app into a proper Next.js project structure
2. Set up Supabase for:
- User authentication (email/password)
- Database to persist assessments, candidates, responses, and scores
- Row-level security so each customer only sees their own data
3. Integrate Stripe for:
- $797/year subscription checkout
- Customer portal for billing management
- Webhook handling for subscription status
4. Add shareable candidate links (employer generates a unique URL, candidate fills out assessment at that URL without needing an account)
5. Deploy to Vercel with custom domain (app.wereallsalespeople.com)
6. Video embed placeholder (swap in a Vimeo or MP4 URL)
7. Client logo upload field in the assessment builder

I already have accounts set up for Stripe, Supabase, Vercel, and GitHub. I will provide complete source code, a detailed developer README with database schema, feature specs, and brand guidelines.

Ideal candidate:
- Has deployed at least 2-3 SaaS products with Next.js + Supabase + Stripe
- Familiar with the Vercel Next.js Subscription Payments starter template
- Experience with the Anthropic API or similar LLM APIs
- Can work from existing React code (not starting from scratch)
- Available to start this week

Budget: $1,000 estimated fixed price
Timeline: 7-10 business days

Please reply with:
1. A link to a SaaS product you've deployed with this stack
2. Your estimated timeline
3. Any questions about the scope

1) Consult on the billing/invoicing process
2) Offer chat support to clients on how to seek reimbursement from their insurance
3) Responsible for billing clients via Stripe, in-house EMR software, and more.
4) Responsible for issuing refunds, voiding invoices, etc.
5) Responsible for performing all activities within appropriate KPIS

Description:
Need a clean, conversion-focused website for a subscription-based audio romance story service.

What I need:
3 pages: Landing page, Checkout/Subscribe, About the Author
Audio player on landing page (plays sample chapter)
Recurring subscription setup
Mobile-responsive design
Email delivery integration (send audio links two times per weeks for different chapters)

Platform preference:
Open to recommendations. Considering Shopify, Ghost, or custom build. Must handle recurring billing seamlessly. Checkout must be very simple with differnt types of payment options.

Design:
I have mockups and brand colors. Modern, romantic, clean - think premium subscription service, not generic blog.

Must haves:
Experience with subscription/membership sites
Portfolio showing clean, modern designs
Can integrate Stripe or Shopify Payments
Knows how to set up automated email delivery

Include in your proposal: Platform recommendation and why, relevant portfolio examples, timeline estimate.

Redesign and optimize the website www.mariedargan.com

We're building AI SEO autopilot platform (outrank dot so competitor). Users connect their site, configure niche and brand voice, wake up to published articles and backlinks building. The core is built and working. You are finishing it and getting it to zero-bug production launch.

Do not apply if you want to greenfield. You need to read existing code before you write any.

What's already shipped:

Full autopilot pipeline, multi-step LLM article generation with QC gates, WordPress integration, Inngest background jobs, link partnership hub (verification, matching engine, fraud detection, dual approvals, immutable audit trail, backlink placement), 34 DB migrations, OpenAPI contract, unit and integration tests.

What you are completing:

- 6 remaining CMS integrations + unified Publisher Adapter interface with per-provider integration tests
- Stripe: checkout, production webhooks, cancel/upgrade flows, usage enforcement against subscription state
- Keyword discovery provider interface with at least one provider wired (DataForSEO or SEMrush)
- Existing content optimization v1: crawl/audit, suggestions payload, optional auto-apply
- CI/CD, system health endpoints, Vercel/Render deployment
- Two known bugs: anchor text extractor over-filters valid noun phrases; topical relevance filter scores title only, not body content
- Full QA to production-ready zero-bug launch

Stack (in use, non-negotiable): Next.js 16, TypeScript, Supabase, Inngest, Tailwind v4

Budget: $700 fixed. Timeline: 1 week.

To apply:

Start with X. Then: fixed-price confirmation, two relevant project links (SaaS with Stripe, AI/SEO tooling, or marketplace), biggest risks/unknowns on a project like this and how you'd de-risk them. Anything else gets skipped.

Here's the full job description:

---

**Full-Stack Integration Engineer – Lovable / Supabase / Claude AI**

**About the Role**

We're a growing digital health company building a suite of AI-powered wellness and clinical platforms. We work at the intersection of neuroscience, preventive medicine, and consumer health technology — and we move fast. We're looking for a hands-on full-stack integration engineer who can take ownership of building, operationalizing, and scaling our products from front-end to backend, with a strong command of modern AI-native development workflows.

This is an ongoing part-time engagement with room to grow. You'll be working across multiple live projects simultaneously, so the ability to context-switch, prioritize, and maintain clean architecture across codebases is essential.

---

**What You'll Be Doing**

- Building and iterating on web applications using **Lovable.dev** as the primary development environment, paired with **Claude (Anthropic API)** for AI-native feature development
- Taking Lovable-generated front-ends and making them fully production-ready — clean, scalable, and connected to robust backends
- Architecting and managing **Supabase** infrastructure: database schema, authentication, row-level security, edge functions, and real-time features
- Designing and implementing **HIPAA-compliant** data systems, including access controls, audit logging, encryption, and BAA-ready architecture
- Integrating third-party APIs, payment systems (Stripe), and automation tools (n8n or equivalent) into cohesive product workflows
- Building multi-step AI agent pipelines using the **Anthropic API**, including tool use, context management, and structured outputs
- Setting up webhook architecture and event-driven workflows across systems
- Collaborating closely with non-technical stakeholders — you'll need to translate product vision into working systems, not just execute tickets

---

**What We're Looking For**

- Demonstrated experience with **Lovable.dev** — this is non-negotiable. If you haven't shipped a project using Lovable, this role isn't the right fit
- Strong **React + TypeScript** proficiency (Lovable's output stack)
- Deep **Supabase** experience: not just basic queries, but RLS policies, edge functions, and production-grade schema design
- Solid **PostgreSQL** fundamentals
- Real experience integrating the **Anthropic API** (Claude) — tool use, multi-turn conversations, structured outputs, prompt engineering
- Familiarity with **HIPAA technical safeguards** — you don't need to be a compliance officer, but you need to know what PHI is and how to architect around it
- Experience with **Stripe** subscriptions, webhooks, and payment flow integration
- Comfort with **n8n, Make.com**, or similar automation platforms for building cross-tool AI workflows
- Strong communication skills — async-first, clear documentation, no hand-holding required

---

**Nice to Have**

- Experience building in health, wellness, or clinical tech environments
- Familiarity with freemium SaaS product architecture
- Experience with BAA vendor coordination (Supabase, AWS, etc.)
- Prior work on consumer-facing AI features (not just backend API calls)

---

**Engagement Details**

- **Type:** Part-time, ongoing
- **Hours:** Flexible, roughly 15–25 hrs/week depending on sprint priorities
- **Rate:** Competitive — commensurate with demonstrated Lovable + Supabase + Claude experience
- **Location:** Remote, global applicants welcome

---

**To Apply**

Please include in your proposal:

1. A specific example of a project where you connected a **Lovable front-end to a Supabase backend** and integrated an external API or automation tool — describe what you built, what broke, and how you fixed it
2. Your experience with the **Anthropic API** specifically (not just LLMs generally)
3. Any exposure to **HIPAA-compliant** system design

*Applications without a response to these three points will not be reviewed.*