We are a growing tax and bookkeeping firm located in Central Florida, serving individuals, small businesses, entrepreneurs, and international clients. We are looking for an AI Automation & Local SEO Specialist to help us improve client acquisition, automate repetitive processes, strengthen our online presence, and identify growth opportunities. This is an initial 2–3 month project with the possibility of a longer-term relationship if results are achieved. Our goals include: • Improving local SEO and Google Business Profile performance • Identifying opportunities to generate qualified leads • Implementing practical AI automations for our operations • Improving website performance and user experience • Automating lead follow-up and client communication • Recommending tools, systems, and processes that can help us scale efficiently • Helping us leverage AI to improve productivity and customer experience Important: We are NOT looking for someone to create social media posts or manage Instagram accounts. We are looking for a problem solver who can help us build systems, improve visibility, automate processes, and generate measurable business results. Preferred Qualifications: • Experience with Local SEO and Google Business Profile optimization • Experience with WordPress websites • Experience with AI tools, ChatGPT, OpenAI, Claude, AI agents, or business automation • Experience with lead generation systems and marketing funnels • Experience with CRM platforms and workflow automation • Experience working with accounting, tax, legal, financial, or other professional service firms is a plus • Spanish is a strong plus, since many of our clients are Spanish-speaking. Candidates who can communicate in both English and Spanish will receive special consideration. When Applying, Please Answer: 1. What similar projects have you completed? 2. What would be the first three improvements you would recommend for a tax and bookkeeping firm like ours? 3. What AI, automation, or SEO tools do you typically use? 4. Please provide examples of measurable results you have achieved for previous clients. 5. Why do you believe you would be a good fit for this project? We are looking for someone who can think strategically, execute effectively, and help us build systems that support long-term growth.

I need someone to help me set up automation agents in Claude Cowork. My photo agency requires CoWork to watch a directory for new files and trigger a workflow. The ideal candidate will have experience in automation and workflow management, ensuring seamless integration with our directory to automate file processing.

We are seeking an experienced Automation & Integration Engineer to modernize and automate our CPA firm's operations. This role will be responsible for designing, building, and maintaining AI-driven workflows and integrations centered around CCH Axcess, Additive K-1, Microsoft 365, and other business systems. The ideal candidate combines software development, API integration, workflow automation, and AI implementation experience with deep knowledge of tax and accounting technology. This is a hands-on technical position. You will build production-grade automations, not just configure software. Responsibilities Design and develop integrations between CCH Axcess, Additive K-1, CRM, document management systems, and internal databases. Build AI-powered workflows to automate tax preparation, review, document processing, and client communication. Develop API integrations using the CCH Axcess Open Integration Platform. Automate repetitive tax workflows using APIs, webhooks, scripting, and workflow platforms. Create secure data synchronization between business applications. Build custom internal applications that improve CPA productivity. Implement OCR and AI document extraction for tax source documents. Build dashboards and reporting from tax software data. Create automation monitoring, logging, and alerting. Document all integrations and maintain technical architecture. Work directly with tax professionals to identify automation opportunities. Evaluate emerging AI tools and recommend practical implementations. Required Experience 5+ years building software integrations or business automations. Strong experience with: CCH Axcess CCH Axcess APIs REST APIs OAuth Webhooks JSON/XML Experience integrating accounting or tax software. Experience with AI APIs such as: OpenAI Anthropic Google Gemini Azure OpenAI Experience with automation platforms such as: n8n Power Automate Make Zapier Strong programming skills in one or more: Python C# JavaScript/TypeScript SQL database experience. Microsoft 365 integration experience. Git version control. Cloud experience (Azure or AWS). Preferred Qualifications Additive K-1 experience. CCH API development. CPA firm experience. Tax workflow automation. OCR and intelligent document processing. Experience with AI agents. Experience with document management systems. Power BI. SharePoint. Azure Functions or AWS Lambda. Docker. Technical Skills API Development REST OAuth JSON XML Python JavaScript SQL AI Integration Prompt Engineering Workflow Automation Microsoft Graph API SharePoint APIs Microsoft 365 Administration OCR RAG LLM Integration Git CI/CD What You'll Build Examples include: Automated K-1 ingestion into CCH. AI document classification and extraction. Tax return workflow automation. Client onboarding automation. Automated tax organizer processing. AI review assistants. Internal tax knowledge search. Automated email and task generation. Client portal integrations. Document routing. Workflow dashboards. Exception monitoring and alerts. Success Metrics Within the first 6–12 months, you will: Eliminate hundreds of hours of manual tax processing. Reduce duplicate data entry across systems. Build production-ready AI workflows. Create reusable integration frameworks. Improve tax workflow visibility through reporting and dashboards. Establish a scalable automation architecture for future growth. Nice-to-Have Certifications Microsoft Azure AI Engineer Microsoft Power Platform Developer AWS Developer Python certifications AI/LLM application development CPA technology consulting experience Ideal Background Candidates who have worked at firms or software vendors using: CCH Axcess Additive K-1 Thomson Reuters products Intuit products Wolters Kluwer tax software Tax technology consulting firms CPA firms with 100+ employees Tax automation consultancies

Overview Curiel Homes is looking for a highly skilled freelance specialist to help transform our website into a true lead conversion machine. We are a modern real estate and mortgage brand focused on growth, automation, local authority, and scalable systems. We want someone who understands: Real estate lead generation SEO and local search strategy AI integrations and automation Google PPC CRM workflows and follow-up systems Website performance optimization Conversion-focused design This is NOT just a website design project. We are looking for someone strategic who can help build long-term systems and automation that drive leads and conversions. Current Goals We want to improve and/or implement: Website + SEO Neighborhood-focused SEO landing pages Local authority content strategy Faster mobile page speed ADA/screen reader optimization Structured blog strategy based on real search queries Mortgage and down payment assistance pages Google Business Profile integration AI + Automation AI chat follow-up and lead nurturing CRM automation and workflow optimization Retargeting audience setup Review scraping/integration tools (ex: Birdeye.ai) AI-assisted content generation Smart lead capture systems Data + Content Add/edit videos throughout website Fed-related market data integrations Content hub/blog strategy Automated market insights and reporting ideas Ideal Candidate We are looking for someone who has: Experience working with lead-gen businesses Strong understanding of SEO and technical SEO Experience with Google PPC Experience with AI tools and automation Experience integrating CRMs and lead funnels Strong communication and strategic thinking Ability to recommend scalable systems Portfolio of websites or funnels that generated measurable results Bonus if you have experience with: IDX websites Sierra Interactive, Follow Up Boss, KVCore, or similar CRMs AI chat systems Local SEO domination strategies Conversion rate optimization What We Need From You When applying, please include: AI/automation experience What platforms/tools you recommend Your approach to improving conversion rates Estimated timeline Your preferred pricing structure Project Scope We are open to: Hourly consulting Fixed project pricing Ongoing monthly partnership Potential for long-term work if it is a strong fit.

AI Engineer (RAG & Agentic Workflows). *LLM RESPONSES AUTOMATICALLY AVOIDED* We have already launched a production generative AI product that utilizes a custom Retrieval-Augmented Generation (RAG) architecture. We are now expanding the platform to include CRM intelligence, workflow automation, and agentic AI capabilities. This is **not** a prompt engineering role. Seeking an engineer with deep experience building and deploying production AI systems that combine LLMs with multiple structured and unstructured data sources. You should be comfortable walking into an existing, complex codebase, understanding the current architecture, and improving it. Existing AI Architecture Our current AI architecture consists of: * OpenAI embeddings * Embeddings stored in MongoDB * MongoDB Atlas Vector Search for retrieval * Retrieval from both structured SQL data and unstructured document collections * Existing tool/function-calling architecture **Please do not apply if you have not previously built or maintained production RAG systems using embeddings and vector search.** Experience specifically with **OpenAI embeddings and MongoDB Atlas Vector Search** is highly preferred. CRM Intelligence Layer We are currently building a CRM platform and need the AI to reason over CRM records, including the other records are RAG currently retrieves. You will be responsible for designing and implementing the AI integration layer that enables the LLM to intelligently retrieve and reason over CRM data. This work includes: * Designing AI tools/functions that expose CRM data to the LLM. * Implementing backend tool handlers that retrieve CRM records. * Defining tool schemas and instructions so the AI knows when and how to retrieve CRM information. * Building secure retrieval mechanisms that enforce strict user and organization-level access controls. * Transforming raw CRM records into structured, AI-ready context. The AI will need to reason across: * CRM contacts and organizations * client profiles * Deals and opportunities * Projects * Tasks and reminders * Notes * Email history * SMS and WhatsApp communications * Call transcripts * Meeting summaries * Documents and contracts * Workflow history Agentic AI & Workflow Automation * Build proactive AI agents that generate alerts, recommendations, follow-ups, reports, and suggested next actions. * Design systems capable of reasoning across both structured and unstructured data sources. * Architect and implement multi-step and multi-agent workflows. * Develop workflow intelligence that assists users in completing real-world business tasks. Required Experience * Demonstrated experience building and deploying production AI systems used by real customers. * Experience working with embeddings, vector databases, and retrieval pipelines. * Experience implementing LLM tool/function-calling architectures. * Experience integrating AI systems with business systems such as CRMs, ERPs, or other operational databases. * Experience combining structured and unstructured data within AI applications. * Strong backend engineering and systems architecture experience. * Demonstrated ability to quickly understand and improve existing codebases. * Ability to independently own and deliver complex technical initiatives. Strongly Preferred * Experience with OpenAI embeddings. * Experience with MongoDB Atlas Vector Search. * Experience building agentic AI systems and workflow automation. * Experience designing long-term memory architectures. * Experience building multi-tenant SaaS applications with strict authorization requirements. * Experience implementing evaluation and monitoring pipelines for production AI systems. What We Value * High accountability and ownership. * Strong communication skills. * Product thinking and user empathy. * Ability to understand user workflows before writing code. * Pragmatism and sound engineering judgment. PLEASE DO NOT WASTE OUR TIME IF YOU NOT MEET THE REQUIREMENTS 

EroFlow Intelligence is an enterprise-grade, autonomous AI orchestration pipeline designed to mitigate global supply chain disruptions for aerospace manufacturing. Built using a multi-agent framework, the system automates the entire lifecycle of risk detection, impact analysis, and procurement mitigation without requiring human intervention for standard operational anomalies. The architecture coordinates three specialized, asynchronous AI agents that communicate via a centralized event bus to solve complex logistical bottlenecks in real-time. Core Agent Architecture & Workflow 1. The Sentinel Agent (Data Ingestion & Extraction) Role: Continuous Global Monitoring. Function: Utilizes advanced LLM-driven web scraping and unstructured data extraction to monitor global news feeds, geopolitical shifts, weather anomalies, and shipping port telemetry. Trigger: If it detects a disruption (e.g., a port strike or critical mineral shortage), it extracts key entities (materials affected, estimated delay times) and passes a structured JSON payload to the orchestration layer. 2. The Impact Assessment Agent (Predictive Modeling) Role: Deep Cross-Referencing & Analytics. Function: Upon receiving a trigger, this agent cross-references the disrupted material with the company’s internal ERP (Enterprise Resource Planning) database and current inventory levels. Output: It runs a predictive analysis to determine exactly which production lines will stall and calculates the financial risk, assigning a high/medium/low priority score to the event. 3. The Mitigation & Logistics Agent (Autonomous Execution) Role: Operational Resolution. Function: If the risk score exceeds a specific threshold, this agent is authorized to take action. It autonomously queries pre-vetted alternative suppliers via APIs, negotiates standard volume pricing based on historical contract data, drafts a comprehensive procurement proposal, and queues the purchase order for final human sign-off (or executes it automatically if under a certain dollar cap). Technical Stack (The Blueprint) Frameworks: LangGraph / CrewAI (for multi-agent state management and deterministic routing). Core Language: Python 3.11+ Data Layer: PostgreSQL (for ERP syncing) & Pinecone / Qdrant (Vector database for storing and querying supplier contract PDFs and historical compliance documentation). LLM Orchestration: OpenAI GPT-4o / Anthropic Claude 3.5 Sonnet utilized via structured outputs (Pydantic parsing) to ensure strict API data integrity. Hosting & DevOps: Containerized via Docker, orchestrated via Kubernetes, and deployed on AWS with asynchronous task queues managed by Celery and Redis. Quantifiable Business Results (The Hook) 92% Reduction in supply chain anomaly response time (from 48 hours down to 14 minutes). Automated Recovery: Successfully mitigated over 140 potential production line stalls autonomously in simulated stress tests. Cost Efficiency: Saved an estimated $1.2M in expedited shipping fees by predicting bottlenecks 10 days before they impacted manufacturing floors.

We’re a product-focused team developing an AI-driven SaaS platform aimed at improving how businesses handle information, workflows, and internal processes. We’re looking for a developer who can build a smart feature that allows users to interact with their data and documents in a more automated and intuitive way. The goal is to reduce manual effort and enable faster, more informed actions through AI. This role involves designing and implementing the core logic behind the feature, connecting AI capabilities into the product, and ensuring everything works smoothly within the existing system. You should be comfortable building end-to-end functionality, working with modern web applications, and integrating AI services into real user-facing features. Experience with AI-powered products, automation tools, or data-driven applications is highly relevant.

We're looking for an AI & Data Analysis expert to lead the integration of intelligent tools within the business platform. You'll connect Google Ads, marketing data files, and operational data sources to build AI agents via Claude that support business decision-making across our pet retail operations. Key Responsibilities Design and configure Claude-powered agents using tool use, structured prompts, and automated workflows for data analysis Integrate the Google Ads API to extract campaign metrics and feed decision-making dashboards Ingest, clean, and structure CSV, Excel, and other marketing data formats for agent processing Generate automated narrative reports and actionable visualizations for the executive and marketing teams Maintain and iterate on data pipelines connecting advertising, sales, and inventory data Required Technical Skills Claude API / Anthropic MCP (Model Context Protocol) Prompt engineering and LLM tool use / function calling Google Ads API Python or JavaScript (for pipelines and integrations) SQL / PostgreSQL / Supabase Pandas / NumPy or equivalent data libraries REST API consumption and integration Advanced Excel / Google Sheets Nice to have: Google Analytics, BigQuery, Looker, Power BI Ideal Profile Proven experience building data pipelines or LLM-powered tools in a production environment Hands-on familiarity with the Anthropic API and agent/tool-use patterns Ability to translate raw data into clear, actionable business recommendations Self-directed — can propose and build solutions without exhaustive specs Initial Projects Campaign ROI Agent — connects Google Ads + business sales data to generate automatic performance alerts and recommendations Marketing File Pipeline — ingests CSV/XLSX marketing files and produces AI-generated summaries and insights Executive Dashboard — decision-support interface with Claude-generated action recommendations based on live data

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 looking for an experienced Asana Automation & Integration Expert to build or fix a strict, sequential, 1-for-1 Round Robin routing system for incoming form submissions. We currently have an Asana project (Talent Pool Sourcing Requests) where new tasks land via an Asana Form. We need these incoming tasks to alternate strictly and instantly between two main assignees (Arhi and Nandini) without failing. Ideally, it's easy to modify if we need more assignees. I'm open to your suggestion on how to solve this, ideally it's done within asana natively, but open to using Zapier or Make.com or N8N if best.