Real Estate Acquisitions Coach — Test & Refine AI Voice Agents We have AI voice agents (inbound, outbound, and speed-to-lead for web leads) that handle motivated seller calls for a real estate investment company. They work — but we need them to sound like a real acquisitions rep, not a bot. **You'll:** - Call into and receive calls from our agents as different seller personas - Try to break them, then tell us what's off - Rewrite robotic lines with language a real rep would use - Flag missing discovery questions and weak objection handling **You are:** - A real estate acquisitions rep / ISA / wholesaler with thousands of seller calls under your belt - Experienced across inbound, outbound, and web lead follow-up - Able to explain *why* a line lands or doesn't **Start:** Paid test / 5 mock calls with Video feedback. Ongoing work if it's a fit. **To apply, send:** 1. How many seller calls have you personally handled? 2. Your best opening line for a 60-day-old lead 3. Your hourly rate Not looking for prompt engineers or copywriters — looking for an operator who's lived in these calls.

I'm a retired entrepreneur and active investor looking for a skilled Claude AI practitioner to serve as a private tutor and advisor. I use Claude regularly and have a working Microsoft 365 integration in place, but I want an experienced guide to help me unlock advanced capabilities and build efficient, reusable workflows tailored to my work. This is not a beginner engagement. I learn quickly, prefer direct feedback over hand-holding, and want sessions focused on my actual use cases — not generic training. Topics to Cover - Claude Projects — structure and strategy for ongoing, organized work - Investment and general research — synthesizing company, market, and topic information efficiently - Correspondence — drafting polished emails in Outlook that match my voice with minimal editing - Document analysis — extracting key information from legal, financial, and fund documents - Microsoft 365 add-ins — what's available and genuinely useful for Word, Excel, and PowerPoint - Voice input and dictation — getting started and optimizing as a primary input method - Workflow building — creating persistent, reusable tools rather than starting from scratch each session - Agents, skills, and connected tools — connecting external tools, leveraging agentic capabilities, and building autonomous workflows - Prompt craft — advanced techniques applicable across all of the above Ideal Candidate - Hands-on experience with Claude (not just ChatGPT or general AI) - Background working with business operators, investors, or executives — not primarily developers or academics - Can demonstrate real-world applications, not just theoretical knowledge - Comfortable moving at a fast pace and adapting sessions to my priorities Format Virtual sessions via video call, 60–90 minutes each. Frequency to be determined based on fit and progress. Looking to begin with 4–6 sessions and reassess. To Apply Please include: 1. A brief description of your hands-on experience with Claude specifically 2. One or two examples of business or executive use cases you've worked on 3. Your availability and hourly rate A short introductory call before committing to paid sessions is expected.

ElevenLabs Conversational AI Expert — Long, Multi-Node Voice Agents with Tool Calls Project type: Hourly Experience level: Expert Duration: Short-term engagement with potential for ongoing work About the project We're building voice agents on ElevenLabs Conversational AI (Agents Platform) that run long, complex calls of 20+ nodes in the workflow builder, with multiple tool/function calls along the way. The agent is embedded directly into our app (using the ElevenLabs SDK) rather than the ElevenLabs widget. The agents work, but we're fighting duplicate questions/answers. The agent re-asks questions it already asked, or repeats information it already gave, at different points in the call. We need someone who has actually built and shipped long-running ElevenLabs voice agents (not just simple single-prompt bots) to help us fix the structural setup so calls stay coherent end to end. That covers workflow/node architecture, state handling, prompt design, tool orchestration, and our client-side integration. What you'll do ● Audit our current agent: workflow node structure, system/node prompts, tool definitions, and conversation flow. ● Audit our client-side integration (the ElevenLabs SDK embedded in our app): session/connection handling, event handling, client tools, and how local app state stays in sync with the conversation. Reconnects, double-fired events, or repeated client-tool calls can also cause re-asks. ● Diagnose the root causes of the duplicate question/answer behavior. Possible culprits include context/state not being tracked across nodes, overlapping node responsibilities, prompt ambiguity, retrieval/knowledge-base issues, or client-side state/event problems. ● Redesign the node graph and transitions so each node has a clear, non-overlapping job and the conversation can't loop or re-ask. ● Improve state/variable management across nodes: dynamic variables, captured data, and how it's passed forward so the agent "remembers" within a call. ● Tighten tool/function calling: when tools fire, how results are handled, error/timeout handling, and avoiding redundant calls. ● Address context-window and long-call degradation, plus turn-taking behavior that causes drift. ● Recommend the right structural patterns for flows this long (single agent vs. multi-agent/agent transfer, sub-agents, branching). ● Document the fixes and the patterns so our team can maintain and extend the setup. You're a strong fit if you have ● Demonstrable hands-on experience with ElevenLabs Conversational AI / Agents Platform. Please reference specific agents or projects you've built. ● Experience with the workflow/node builder for branching, multi-step calls, not just a single system prompt. ● Experience embedding ElevenLabs in a custom app via the SDK (React/JS, WebRTC/WebSocket), not just the drop-in widget. ● Solid grasp of tool/function calling (client tools and server tools/webhooks), including error handling. ● Strong prompt engineering for voice, plus understanding of LLM context windows, state, and conversation memory. ● Experience debugging long conversations for looping and repetition, including intermittent, hard-to-reproduce cases. ● Bonus: knowledge base / RAG, dynamic variables, multi-agent transfer, post-call analysis, and the ElevenLabs API/SDK. To apply, please include 1. A short description of a long, multi-node ElevenLabs agent you built: how many nodes, what tools, and what it did. 2. How you'd approach diagnosing duplicate question/answer issues in a 20+ node flow (a quick paragraph, since we want to see how you think). 3. Your availability and rate. Applications that just say "I'm an AI expert" without specific ElevenLabs experience will be skipped. We're looking for someone who has lived in this platform.

Description: We are a New York personal injury and employment law firm looking to build a Spanish-language AI voice agent inside GoHighLevel to qualify inbound leads from Facebook Lead Ads. What we need: Inbound and Outbound Voice AI agent in GHL that speaks fluent, natural Spanish Qualifies leads based on a script we provide (5-7 questions) Routes qualified leads to our call center via live transfer, SMS alert or GHL pipeline action Conversation AI SMS follow-up integrated into the same workflow Clean handoff between Voice AI and human intake staff Requirements to apply: Must have built at least one Spanish-language GHL Voice AI agent previously Submit a recorded demo (Loom or video) of a prior Spanish GHL Voice AI build — no demo, no consideration GHL certified or power user preferred Must be available for a 20-minute Zoom before project start Project scope: Fixed price. Build + testing + one round of revisions. To apply: Send your demo recording and a one-paragraph description of the prior build (industry, use case, how the voice performed).

We are seeking a skilled cold calling sales expert to promote our digital marketing services, focusing on voice AI agents and SEO. The ideal candidate will have experience in telemarketing and lead generation, with a strong ability to engage potential clients and convert leads into sales. This role requires excellent communication skills and the ability to work independently. If you have a passion for digital marketing and a proven track record in sales, we would love to hear from you.

We are a fast-growing telecom / AI-First CPaaS serving sms and voice API's. We are building the first AI-first communications platform (SMS, Voice, RCS, AI agents) designed for speed, simplicity, and real-world business outcomes. We are not looking for a “task completer.” We are looking for a true senior engineer who: thinks in systems moves fast makes decisions independently writes clean, scalable code uses AI tools (Claude, etc.) as a force multiplier ⚠️ Read This First *DO NOT APPLY IF YOU ARE PRETENDING TO BE IN A DIFFERENT COUNTRY. PROOF OF RESIDENCY IS REQUIRED. Most applicants will not be a fit. If you need: detailed tickets hand-holding constant direction This is NOT the role for you. If you are the type of engineer who: sees a problem and solves it end-to-end improves architecture without being asked ships quickly without sacrificing quality You will thrive here. What You’ll Do Build and ship full-stack features across our platform (messaging, voice, AI workflows) Make architectural decisions (not just implement) Improve system performance, reliability, and scalability Work directly with founders (no PM layers) Move from idea → production very quickly What We Expect (Non-Negotiable) 5+ years real full-stack experience (not just titles) Strong backend experience (Node.js / APIs / infra) Strong frontend experience (React or similar) Experience building production systems at scale Ability to work autonomously with minimal direction High ownership mentality Bonus (but highly valuable) Experience with telecom / CPaaS / messaging Experience with AI integrations (LLMs, agents, workflows) Experience optimizing performance at scale Startup experience (especially early-stage or fast growth) How We Work Small, high-output team Very fast iteration cycles No unnecessary meetings High trust, high expectations We use AI tools heavily (Claude, etc.) — you should too What We Care About Most Not your resume. We care about: How you think How you build How fast you execute The quality of your code To Apply Please include: Links to projects you’ve built (real production work) A short explanation of: a system you designed end-to-end a difficult technical decision you made independently Your GitHub Optional (but strong signal): Share how you use AI (Claude, etc.) in your workflow Compensation Competitive (based on experience) Long-term opportunity with a fast-growing, profitable company If you are truly senior, this will feel obvious. If not, this role will be very uncomfortable. **THIS IS A FT, HOURLY ROLE. PROVIDE YOUR REQUESTED HOURLY RATE IN PROPOSAL**

We're an AI agent development, business automation, and quality assurance agency. We help businesses scale by building custom AI agents, automating their operations, and ensuring everything ships reliably. We're hiring a results-driven SDR to own our outbound engine. Your job: find high-fit prospects, start real conversations, and book qualified discovery calls for our Lead Architect. What You'll Do Prospecting & list building — Build targeted lead lists against our ICP using Apollo.io, LinkedIn Sales Navigator, and specialized databases. Outbound outreach — Run multi-channel sequences: personalized LinkedIn, strategic email, and the occasional voice note. Qualification — Filter for prospects with the technical complexity and budget that fit our AI, automation, and QA services. Appointment setting — Own the top of the funnel and book 2–3 qualified discovery calls per week. CRM management — Keep meticulous records of outreach activity and lead status. What We're Looking For 2+ years of B2B sales — Proven outbound track record, ideally with technical agencies, SaaS, or professional services. Technical literacy — You can confidently discuss AI agents, APIs, CRM workflows (HubSpot / ActiveCampaign), and business process automation (Zapier). Exceptional communication — You write concise, high-impact copy that cuts through the noise, and you lead with value instead of a hard sell. Tool proficiency — Hands-on experience with Apollo.io, LinkedIn Sales Navigator, and modern CRMs. Self-starter mentality — This is a remote, autonomous role. You'll manage your own volume and report on weekly KPIs. How to Apply Send a short note telling us: A recent outbound campaign you ran and the result. The tools you're fastest in. One line of cold outreach copy you'd send to a CTO at a mid-market company drowning in disconnected systems.

Engagement Overview I am the CEO and principal attorney of a small law practice specializing in campaign finance, lobbying regulation, FARA, nonprofit law, and government ethics. My five-person team — a junior partner, two associates, and an executive assistant — recently integrated into a larger firm. I am looking for an experienced Claude/AI automation builder for a phased engagement to design, build, and deploy a suite of interconnected agents and automations. This brief covers three phases. Phase I (Inbox Triage) is the highest immediate priority and the natural starting point. Phases II and III follow sequentially. Strong candidates will be evaluated on Phase I but should demonstrate familiarity with the full roadmap. This is a paid engagement. Scope, timeline, and rate are open to discussion. Technology Stack Email: Gmail (personal Pro account — not firm infrastructure) AI: Claude (Anthropic) via MCP or API Task and project management: Notion (existing workspace; routing tables, matter tracking, and timesheet structure already in place) Calendar: Google Calendar Internal chat: Google Chat Document storage: Google Drive (primary); local hard drives on iMac and MacBook Pro (secondary) Matter management / DMS: iManage (larger firm system — integration via dedicated ingestion email address) Voice notes: Plaud (AI note-taker) Signing platform: TBD — candidates should ask during scoping Out of scope: Signal and iMessage — encrypted platforms with no API access; manual forwarding convention only Confidentiality Requirements This is a law practice. Attorney-client privilege and work product protection apply to all client communications and matter-related documents. These are not compliance checkboxes — they are professional obligations with real consequences. The successful candidate must: • Execute a non-disclosure agreement prior to engagement • Demonstrate genuine understanding of why data handling matters in a legal context — not just technically, but professionally • Never use client names, email content, routing data, or document content for training, testing, or demonstration purposes • Work exclusively within the client's authenticated accounts — no third-party data stores outside the approved stack • Design systems that minimize data exposure — process and route, do not store unnecessarily Generic proposals that do not address confidentiality specifically will not be considered.   Phase I — Inbox Triage Agent Real-time classification and routing of inbound Gmail, with a daily digest to the executive assistant. Objective The principal attorney's Gmail inbox receives high volumes of email across clients, matters, and categories of widely varying priority. The goal is an agent that processes every inbound message, classifies it, routes it to the correct person automatically, and ensures nothing drops — without overloading the executive assistant with triage work she should not be doing. Two-Stage Routing Logic Stage 1 — Sender Classification Every inbound email is classified against a tiered contact list maintained in a Notion database: MVC: Most Valuable Clients — 5 to 10 contacts. Highest priority. HVP: High Value People — 10 to 20 contacts. Some overlap with MVCs. Principal attorney, unless task-type rule applies All other clients: Roster managed in Notion with assigned attorney(s). Assigned attorney(s) per Notion client record Catch-All: Anyone not in the contact table — prospects, opposing counsel, vendors, bar association, etc. Generate executive assistant daily digest Stage 2 — Task-Type Classification (MVCs only) For MVC contacts, a second classification layer routes based on the nature of the request. Rules are client-specific. Examples: • Scheduling requests → Executive assistant • Contracts and approvals → Designated associate(s) per client record • Strategic and substantive legal matters → Principal attorney Task-type rules are defined per MVC client and must be configurable without developer involvement. Routing Table — Notion All contact and routing data lives in an existing Notion database. The agent reads from it at runtime. Required fields: • Contact name and/or email domain • Tier (MVC / HVP / Standard / Catch-All) • Assigned attorney(s) for Standard clients • Task-type override rules for MVCs The executive assistant must be able to add, edit, and re-tier contacts without touching code. This is a hard requirement. Routing Output Candidates should propose their recommended approach from among the following, based on current Gmail MCP capabilities: • Apply Gmail label and/or forward to assigned attorney's address • Create a pre-addressed draft for principal attorney review before sending • Log routing decision to Notion with email link and recommended assignee Please address this question directly in your proposal — it is a key evaluation criterion. Daily Executive Assistant Digest Once per day at a configurable time, the agent generates a digest delivered to a designated Notion page covering all catch-all emails from the prior 24 hours. Each entry includes: sender, subject, timestamp, and a one-line AI summary of the email's apparent purpose.   Phase II — 5 AM Daily Brief A structured morning brief delivered to Notion each day before 5 AM, aggregating schedule, tasks, workflow status, news, and forward-looking context. Objective The principal attorney starts each day across multiple locations and needs a single, consolidated view of what matters — professional and personal — without opening email. The brief is delivered to a dedicated Notion page and covers the sections below in the following order. Section 1 — Daily Schedule Full calendar for the day pulled from Google Calendar. All events, calls, and commitments in chronological order. Section 2 — Open Projects and Undone Tasks Two sub-sections: (a) MVC high-value work — open projects and incomplete tasks for Most Valuable Clients, filtered to substantive legal work only; and (b) Personal — all open personal projects and tasks without exception. Personal items are comprehensive by design: if it is not surfaced here, it will be forgotten. Source: Notion task and project database. Section 3 — Blocking What is the principal attorney specifically holding up? Items where others in the firm are waiting for a review, decision, approval, or action. Source: Notion matter and task records where assignee or status indicates the ball is in the principal attorney's court. Note to builder: this section requires careful logic design. The agent must infer from status fields and assignee data what is genuinely waiting on the principal attorney versus what is simply unresolved. Work with client during onboarding to define the exact field logic. Section 4 — News Digest Industry News Curated digest of overnight developments in: campaign finance law and FEC activity, election administration, lobbying regulation (federal and state), nonprofit political activity, and government ethics. Format: short summary of each item with a link to the full article. Aim for signal, not volume — 5 to 10 items maximum. US Political News 5 to 10 headlines with links covering: presidential politics, US Senate and House elections, and major gubernatorial races. Stories people are actually talking about, not wire service filler. Section 5 — Firm Workflow Matter-level status summary pulled from Notion, organized by client tier and activity: Status Definition Closed Completed yesterday Moving Action taken yesterday Paused No action yesterday Stuck No action in five or more days Client groupings: MVCs (non-high-value work), Standard clients (all work), and any other open matters. Section 6 — One Month Look Ahead Rolling 30-day forward view pulled from Google Calendar covering: regulatory filing dates and compliance deadlines, matter-level deadlines, client birthdays, holidays, and planned vacations or travel. Anything that requires preparation or awareness in the next 30 days. Section 7 — Personal Financial Summary (If Feasible) Summary of personal financial position pulled from Monarch Money, if an API or MCP connector is available. Candidates should investigate Monarch's API access and address feasibility in their proposal. If not currently feasible, this section is omitted without affecting the rest of the brief. Delivery Notion only — not email. A dedicated page refreshed each morning before 5 AM. Previous day's brief should be archived, not overwritten.   Phase III — Night Maintenance Three nightly agents that run after close of business: timesheet creation, document filing preparation, and Plaud note routing. All outputs are delivered to Notion for principal attorney review. Part 1 — Timesheet Creation Objective Each evening, the agent reviews the day's activity across three sources and populates a timesheet in an existing Notion template for the principal attorney's review and finalization. Sources • Google Calendar — all events and calls attended • Gmail sent items — emails sent that day, grouped by client/matter where inferable • Google Chat — internal messages sent, grouped by thread/matter where inferable Note to builder: Google Chat API access will need to be confirmed alongside Gmail and Calendar MCPs. Confirm availability and any OAuth scope requirements in your proposal. Output: Populated Notion timesheet using existing template structure. Principal attorney reviews each morning, adjusts entries as needed, and finalizes. The agent does not finalize — it drafts. Part 2 — Document Filing Objective Each evening, the agent surfaces documents created or edited that day for the principal attorney's review. The attorney flags finals, and the agent forwards them to the firm's iManage ingestion email address for filing. Sources • Google Drive — documents created or modified that day • Local hard drives — iMac and MacBook Pro Note to builder: local hard drive access requires a locally-running component (daemon, Claude Code instance, or folder-watching script) on each machine. Please address your proposed approach to this in your proposal. Alternative approach for consideration: a designated 'Ready to File' folder on each machine that syncs to Google Drive. The attorney drags filing-ready documents into this folder throughout the day; the agent watches the folder and processes from there. Simpler architecture, device-agnostic, and builds a consistent filing habit. Candidates should evaluate and recommend. Output: A Notion page listing all documents surfaced for that day, with document name, location, and last-modified time. Principal attorney marks finals. Agent forwards marked documents to the iManage ingestion email address. iManage filing is handled by firm IT from that point — no direct iManage API integration required. Part 3 — Plaud Note Routing and Archiving Objective: The principal attorney uses a Plaud AI note-taker on calls and meetings. Each evening, the agent pulls new Plaud summaries, routes them to the appropriate team members, archives a copy to Notion tagged to the relevant client matter, and deletes the underlying audio and transcript from Plaud's platform and the local device. Prerequisite — Plaud API Plaud API or webhook access is a prerequisite for this part. Candidates must investigate and confirm availability before scoping. If Plaud does not currently support programmatic access, this part will require a manual export step as a workaround — please address both scenarios in your proposal. Routing Logic: Similar in structure to Phase I inbox triage routing (MVC/HVP/Standard tiers with task-type overrides) but with distinct rules to be defined with the client during onboarding. Do not assume inbox triage rules apply directly. Archiving: One copy of each Plaud summary is saved to Notion as a note, tagged to the relevant client matter. Tagging logic to be defined during onboarding. Deletion: After successful routing and archiving, the agent deletes: (a) the audio and transcript from Plaud's platform via API, and (b) any local copies on the principal attorney's devices. Local deletion requires the same locally-running component described in Part 2. Candidates may propose a unified local agent that handles both Part 2 and Part 3 local operations.   What I'm Looking For Strong candidates will have: • Demonstrated experience building Claude-based automations or agents — not general AI experience • Hands-on experience with Gmail MCP, Google Calendar MCP, and Notion MCP (or equivalent API integrations) • Ability to build systems that non-technical users can maintain — editability and simplicity are as important as technical sophistication • Comfort with phased delivery — Phase I first, Phases II and III following sequentially based on performance • Experience with professional services clients (legal, financial, consulting) is a meaningful plus • Willingness to execute an NDA and work within a legally sensitive environment What to Include in Your Proposal Please address the following specifically. Proposals that do not engage with these questions will not be considered. • Your proposed technical architecture for Phase I — how you would connect Gmail, Claude, and Notion • Your answer to the Gmail MCP routing output question in Phase I (labeling vs. drafts vs. Notion logging) — what is actually supported and what do you recommend • Your assessment of Plaud API availability and your proposed approach for Phase III Part 3 • Your assessment of Monarch Money API feasibility for the Phase II financial summary section • Your proposed approach to local hard drive access for Phase III Parts 2 and 3 — daemon, sync folder, or other • A comparable project you have delivered — describe the client type, the stack, and what made it work • Your estimated timeline and rate for Phase I, and a rough order-of-magnitude estimate for Phases II and III • Confirmation that you are willing to execute an NDA prior to engagement I am looking for someone who has read this brief carefully and has a specific, informed point of view on how to build it. This is phase one of a longer automation roadmap and the right candidate will be a long-term partner, not a one-time contractor.

We are a fast-growing telecom / AI-First CPaaS serving sms and voice API's. We are building the first AI-first communications platform (SMS, Voice, RCS, AI agents) designed for speed, simplicity, and real-world business outcomes. We are not looking for a “task completer.” We are looking for a true senior engineer who: thinks in systems moves fast makes decisions independently writes clean, scalable code uses AI tools (Claude, etc.) as a force multiplier ⚠️ Read This First *DO NOT APPLY IF YOU ARE PRETENDING TO BE IN A DIFFERENT COUNTRY. PROOF OF RESIDENCY IS REQUIRED. Most applicants will not be a fit. If you need: detailed tickets hand-holding constant direction This is NOT the role for you. If you are the type of engineer who: sees a problem and solves it end-to-end improves architecture without being asked ships quickly without sacrificing quality You will thrive here. What You’ll Do Build and ship full-stack features across our platform (messaging, voice, AI workflows) Make architectural decisions (not just implement) Improve system performance, reliability, and scalability Work directly with founders (no PM layers) Move from idea → production very quickly What We Expect (Non-Negotiable) 5+ years real full-stack experience (not just titles) Strong backend experience (Node.js / APIs / infra) Strong frontend experience (React or similar) Experience building production systems at scale Ability to work autonomously with minimal direction High ownership mentality Bonus (but highly valuable) Experience with telecom / CPaaS / messaging Experience with AI integrations (LLMs, agents, workflows) Experience optimizing performance at scale Startup experience (especially early-stage or fast growth) How We Work Small, high-output team Very fast iteration cycles No unnecessary meetings High trust, high expectations We use AI tools heavily (Claude, etc.) — you should too What We Care About Most Not your resume. We care about: How you think How you build How fast you execute The quality of your code To Apply Please include: Links to projects you’ve built (real production work) A short explanation of: a system you designed end-to-end a difficult technical decision you made independently Your GitHub Optional (but strong signal): Share how you use AI (Claude, etc.) in your workflow Compensation Competitive (based on experience) Long-term opportunity with a fast-growing, profitable company If you are truly senior, this will feel obvious. If not, this role will be very uncomfortable. **THIS IS A FT, HOURLY ROLE. PROVIDE YOUR REQUESTED HOURLY RATE IN PROPOSAL**

We're looking for an experienced Go High Level specialist to finalize and connect the components of our missed call text back, voice AI agent, and booking funnel — and confirm everything is working seamlessly end to end. What's already done: - Voice AI configured - Conversations AI configured - Booking system connected with staff member created - A2P 10DLC verified (text and voice) - Funnel built What we need: Everything connected and fully operational — missed calls triggering the text back workflow, the voice AI engaging callers correctly, and the booking funnel capturing and routing leads without issues. We want this running as a complete, seamless system, not just individual pieces. Timeline: We need this done as soon as possible. Access: We will provide full access to everything you need and are available to assist with anything that comes up along the way. Deliverable: Once fully operational, we require screen-recorded video proof of the entire system working correctly from start to finish. If you've done this type of GHL build-out before and can hit the ground running, we'd love to hear from you. Please share relevant experience or examples when applying.