- Hourly: $30.00 - $75.00
- Expert
- Est. time: More than 6 months, Less than 30 hrs/week
*Please read this full post before applying as it's not for everyone * I am not looking for a canned proposal. I won't respond to obviously AI responses * Potential dealbreakers below I am looking for a long-term Google Ads and social media ads specialist who understands small business budgets, local service businesses, hourly work, and clear reporting. I have been in the website and marketing industry for 20+ years. Over time, I have focused my work on WordPress websites, SEO, and marketing support for American small businesses. Most of my clients are local, service-based businesses, no e-commerce. My clients include general contractors, excavators, concrete companies, fence builders, deck builders, dog walkers, therapists, nonprofit consultants, tree farms, and other small business owners. I am looking for someone who can help manage simple paid ad campaigns for some of these clients. This may include Google, Facebook, Instagram, Reddit, and maybe even ChatGPT ads, or a mix depending on the client. Some campaigns may be ongoing. Others may be short-term campaigns for a specific service, event, season, promotion, or business need. I need someone who is comfortable with both. This would be a small team relationship. I want someone reliable, practical, honest, and easy to communicate with. *Possibly dealbreaker for you* Important pricing and workflow note: I do not work on large monthly retainers or project-based pricing. My company bills clients based on real time worked. I know most ad specialists have a monthly minimum per client with package deals starting at $500-1,000/month. That just doesn't work for my clients who are small, local businesses with tight budgets. Each invoice to my client is broken down by: Client Task Time worked If a task takes 10 minutes, I bill 10 minutes. If it takes 47 minutes, I bill 47 minutes. I need someone who is willing to work the same way. Please do not apply if you require a monthly minimum per client. Some clients may only have $100 per month available for ad management. Some may have more. The work will vary by client and by month. This is very important. I work with small businesses that need honest, practical marketing help without being forced into large retainers they cannot afford. Time tracking and payment: You will need to use my FreshBooks Contractor account to track your time. Time must be tracked by client and task. I invoice clients and pay contractors around the first of each month. Honest time tracking is required. Inflated time, padded hours, vague time entries, or time clock theft are dealbreakers. I am loyal to good people, and I want this to become a long-term working relationship. But honesty, integrity, clear communication, and accurate time tracking are non-negotiable. The work may include: - Setting up basic Google and social media campaigns from scratch - Some ad accounts have already been started so will need to give you access. After which, you're welcome to work your magic with the data I've got and create new campaigns. - I'll need you to take lead on guiding me to get you the right access to accounts and to share with me. - Generating New Ads: Doing basic keyword research, writing ad copy, setting location targeting based on client direction and current website, reviewing landing pages if necessary, etc. - Maintaining Ads: Checking search terms, pausing poor-performing items, adjusting keywords or targeting, updating ad copy, reviewing spend, etc. - Monthly Reporting: Send a monthly report via email to me that I will forward to the client after review. You can include any notable highlights they should know or questions to ask. Most campaigns will be simple. I am not looking for overly complicated agency-style campaign builds. I need clean, organized, practical campaigns for local service businesses. You should be comfortable communicating with me directly. Over time, if needed, you can communicate directly with my clients after I make an introduction. Please have: - Well-written communication - Strong customer service skills - A positive attitude - Patience with small budgets Tools You'll Use: - Asana for project management - FreshBooks for time tracking - Search Atlas - I use for SEO but you can use whatever tool you prefer This may be a good fit if: - You intimately understand the back end of the Google ecosystem (Ads, Analytics, Search Console, Tags, etc.) - You've been doing this long enough that you don't need much direction. - You don't just go through the motions of running ads but actually use your brain and help these small businesses get leads and survive. - You're completely comfortable with small budgets, small business owners, and sometimes fickle budgets. - You don't require monthly minimums and have no problem working hourly and even prefer it that way for transparency and honesty. - You're interested in long-term work. This is not a good fit if you: - Only work with large ad budgets - Require a monthly minimum per client - Require large retainers - Only work on project-based pricing - Do not want detailed hourly tracking - Do not want to use FreshBooks for time tracking - Do not want to work with small local businesses I am looking for someone for the long haul. If I find the right fit, I believe this can grow over time. I already have a solid base of about 40 clients, and I am confident I will bring in more work once I have the right person helping with paid ads.
- Hourly
- Intermediate
- Est. time: Less than 1 month, Less than 30 hrs/week
I'm a debt and equity analyst and I need a clean, reliable Excel tool to track my deal pipeline. I want something simple that just works — the macros must be fully built in and working on delivery (I don't want to import any code myself), and the file must open without any corruption errors. Environment: Excel on Windows (desktop). Outlook desktop is available for any email features. MUST-HAVE - Pipeline tab — a table with these columns: Deal Name, Borrower/Sponsor, Type (Debt/Equity/Mezz), Size ($), Status (Chasing / In Market / Quoted / Closed), Date Uploaded (manually editable), Follow-Up Date (auto-calculated as Date Uploaded + 2 days, but overrideable), Notes, and an ID. Type and Status must be dropdowns. Overdue follow-up dates should highlight automatically. - Add/Edit Deal form tab — a simple intake form to add a new deal or edit an existing one. Saving pushes the entry straight into the Pipeline tab. I also need to be able to edit deals directly in the Pipeline. - Dashboard tab — auto-updating summary: deal counts by status, total pipeline volume, volume by type, and a count of overdue follow-ups. - Working buttons for Add, Edit, Delete, and Export to CSV. - Follow-up reminders on open — when I open the file, it shows me a list of deals with follow-ups due today or overdue, so nothing slips through. - Status-change timestamps — when a deal's status changes, auto-record the date so I can see how long a deal has been at its current stage. NICE-TO-HAVE (please quote these separately so I can decide) - Auto-archive — when a deal is marked Closed or Dead, move it to a separate Archive tab to keep the active pipeline clean while preserving history. - Aging / conversion analytics — average days at each stage, time from Chasing to Quoted, and win rate by lender. - Quick filter buttons — one-click views like "In Market only" or "follow-ups due this week." Deliverables: One working .xlsm file with all macros pre-installed and tested end to end, plus brief instructions on enabling macros. This is a small, well-defined project. Please share an example of a similar Excel/VBA tool you've built, and confirm you've tested macro-enabled files on Windows Excel.
- Hourly: $40.00 - $128.00
- Expert
- Est. time: 3 to 6 months, Hours to be determined
Type: Hourly, ongoing (part-time to full-time, room to grow) Stack you'll work in: Notion, Slack, HubSpot, Google Workspace/Gmail, Claude + other LLM APIs, Zapier/Make/n8n About us We're a fast-moving sports and fan-engagement startup. We're small, we ship quickly, and we want AI woven into how the whole company operates, not as a side experiment, but as the default way we work. You'd be the person who makes that real. What you'll do Map our current workflows across sales, marketing, ops, and content, then find the highest-leverage places to automate. Build automations and agent workflows that connect our tools (Notion, Slack, HubSpot, Gmail/Google Workspace) using platforms like Zapier, Make, or n8n plus LLM APIs. Design and ship AI agents for real jobs: lead routing and CRM enrichment, content drafting, customer/fan response triage, internal knowledge search, reporting digests. Stand up the connective tissue (prompts, integrations, guardrails, and monitoring) so automations are reliable, not brittle demos. Train and enable our team: build SOPs, run working sessions, and create lightweight docs so non-technical people actually adopt what you build. Help set our AI strategy and roadmap as we scale. You're a strong fit if you Have shipped real automations and AI agent workflows in production (not just prototypes). Are fluent with Zapier / Make / n8n and at least one major LLM API (Anthropic/Claude, OpenAI). Know your way around HubSpot, Notion, Slack, and Google Workspace integrations and APIs. Can write clean prompts and think in systems: edge cases, error handling, human-in-the-loop checkpoints. Can explain technical work to non-technical people and get them to adopt it. Communicate proactively and move fast without breaking trust on things that touch customers or revenue. Nice to have Experience taking a small company "AI-native" end to end. Background in sports and/or blockchain. Comfort with light scripting (Python/JS) when no-code hits its limits. How to apply In your proposal, please: Describe one AI agent or automation you built, the tools involved, and the measurable result. Tell us how you'd approach training a non-technical team to actually use what you build. This part matters as much as the build. Share your hourly rate and weekly availability. Proposals that skip these will be passed over. We're looking to start with a small paid task and grow the engagement from there.
- Hourly: $70.00 - $85.00
- Expert
- Est. time: Less than 1 month, Less than 30 hrs/week
We need a developer to build a simple AI chatbot MVP using Next.js and the OpenAI API. The chatbot should allow a business owner to enter FAQ or support content, then let users ask questions through a chat interface. The AI should answer based only on the provided content.
- Hourly
- Intermediate
- Est. time: 1 to 3 months, Less than 30 hrs/week
Looking to build digital workflows to cover common tasks, such as responding to leasing inquiries, ingesting and analyzing bills from emails, proactively managing maintenance requests with self-service type questions, etc. Need someone who is proficient with building with LLMs, harnesses, and can demonstrate that they have build reliably operating systems Goal would be to reliably measure efficacy on each task, such that we could promote away from HITL into auto-act capabilities when confidence is sufficiently high Opportunity for much more work if can prove excellence here.
- Hourly: $35.00 - $65.00
- Intermediate
- Est. time: 1 to 3 months, Not sure
### Job Description: AI Chatbot Developer We are excited to announce an opening for an experienced and innovative developer to join our dynamic team in the pursuit of creating an advanced AI Chatbot. This chatbot will be designed to perform essential business functions, including but not limited to lead generation, quoting, and providing exceptional customer support. Our ideal candidate will possess a robust background in AI technologies, particularly in the realm of chatbot development, and will be equipped with outstanding problem-solving skills that enable them to tackle complex challenges with creativity and efficiency. As a key member of our development team, you will collaborate closely with various departments to gain a comprehensive understanding of our specific operational needs and requirements. Your ability to translate these needs into a functional and user-friendly chatbot solution will be critical to enhancing our overall operational efficiency. We are looking for someone who is not just technically proficient but also possesses a keen sense of business acumen to ensure that the chatbot aligns with our strategic goals. In this role, you will be responsible for various aspects of the chatbot development lifecycle, including but not limited to: - Designing and developing the conversation flow and user interface of the chatbot, ensuring it is intuitive and engaging for users. - Implementing natural language processing (NLP) capabilities to enable the chatbot to understand and respond to user inquiries accurately. - Integrating the chatbot with existing systems and databases to facilitate seamless access to information necessary for lead generation, quoting, and customer support functions. - Conducting rigorous testing and quality assurance to ensure the chatbot performs reliably and meets user expectations. - Analyzing user interactions and feedback to continuously improve the chatbot's performance and expand its capabilities over time. - Staying current with the latest advancements in AI technologies and chatbot development to incorporate best practices and innovative solutions. You will also play a crucial role in training team members on how to utilize the chatbot effectively and will be expected to provide ongoing support and maintenance to ensure the chatbot remains up-to-date and functional. If you have a passion for artificial intelligence, a deep understanding of customer engagement strategies, and a desire to make a significant impact within our organization, we would love to hear from you! Join us in revolutionizing the way we interact with our customers and streamline our business processes through cutting-edge technology. This is a fantastic opportunity for someone looking to advance their career in a fast-paced, forward-thinking environment. Apply today and be part of our exciting journey towards enhancing our customer experience through AI!
- Hourly: $25.00 - $70.00
- Intermediate
- Est. time: 1 to 3 months, Less than 30 hrs/week
I am a partner at a recruiting firm seeking a conversational AI tool to enhance our communication with candidates and clients. Our business is highly conversational, and we primarily use LinkedIn and Loxo. We need a tool that can efficiently manage and personalize our interactions, potentially integrating with our existing platforms.
- Hourly: $50.00 - $60.00
- Intermediate
- Est. time: 3 to 6 months, Less than 30 hrs/week
Looking for general help building out a platform for an AI saas.
- Hourly
- Expert
- Est. time: 3 to 6 months, 30+ hrs/week
I am working through a design agency on an application for their end client. I think the agency will need you to contract with them directly, but I will manage the project for them. I have scoped out the project already, and our plan is to internally perform a design phase with the client to produce a prototype with Lovable. There may be minor changes to scope after that design phase. The purpose of the app is to create bespoke wedding gown concept images for potential customers of an online wedding dress store. I have provided the details below and attached as a PDF 1. Customer opens an AI dress/gown design experience from a link in their separate e-commerce site. - This can be presented in its own page, we don't want a chat window to be present on any other page - This will be a chat-based interface built into the content area of the page, instead of a popup - The design must be elegant, and match the theme of the e-commerce site - The top navbar and footer don't need to be exactly recreated in this subdomain site, but should look similar enough to create a seamless experience - There will be no integration with the e-commerce site, we need to keep these web apps completely separate 2. The customer must sign up for an account and purchase one credit to begin the AI session - We will need to set up the subdomain site with its own payment processing system and login system - The payment integrations are Stripe to facilitate credit card and Apple pay, and a basic Paypal integration 3. The customers should be able to use a magic link to sign into their accounts, instead of having to remember a password - The account should automatically remember the browser to reduce friction for future access to the app 4. When an AI session begins, we will ask the customer a series of questions programmatically to prime the AI agent so that it can deliver better results - The questions will need to use conditional logic, such that the first question which determines one of 3 main conditional tracks: What type of gown are you looking for? Wedding Gown, Evening Gown, Cocktail Dress - If Wedding Gown is selected, the AI should suggest for the customer to take go to a bridal store and pictures of themselves in different dresses they like and upload the pictures, and describe what they do and don’t like about each dress. It can ask this in the freeform chat, since it may make the most sense to let them fill out the entire questionnaire to stay engaged, and we should reduce the costs of development for the questionnaire by omitting any unnecessary UI that the freeform chat can provide. - It may be best to always just prompt for them to upload the inspirational image at the beginning of the freeform chat so we can omit unnecessary programmatic UI, but in the case of the Wedding Gown it will specifically ask the customer to peform the above task. - We may have other specific questions to add to the questionnaire depending on what conditional track the customer chooses, though only the 3 main branches of conditional logic based on dress type will be required. - Examples of general questions it will need to ask are as follows: -- silhouette -- neckline -- sleeves -- fabric -- embellishments -- color -- train -- length -- closure -- lining -- structure -- inspiration -- event type -- I didn’t get the exact list of questions yet from my client that we should ask in the initial questionnaire. Let me know if you will need this information to accurately provide a price for the development of this application 5. We should not display a concept image after the programmatic questionnaire, the customer will be taken directly into the freeform chat from the questionnaire. - The AI agent may start with an overview of the selected choices from the questionnaire, then can generate concept images at its discretion. 6. The AI should guide the customer through a freeform conversation - The conversation should begin with the AI asking the customer to subjectively describe their dream dress 7. The AI should also make a suggestion near the beginning of the conversation for the customer to upload at least one inspirational photo, but photo upload is optional - If the customer uploads an initial inspiration image, the AI agent should not attempt to figure out body type, measurements, or any other information that we can gather programmatically. - It should treat the inspirational image the same way it would treat any image the customer uploads during the freeform chat, to reduce the cost of development as much as possible. 8. Customer can proceed with a freeform conversation description - The customer should have the option to type in a chat and to upload images - The purpose of the conversation is for the customer to describe the desired dress or gown in an open-ended way 9. AI generates one or more concept images based on the conversation, as soon as it can once it has enough information - The AI model we select should be very good at generating these types of images, this is probably the most important quality the AI model needs to have - The concept images should have the same quality as the final image 10. It is acceptable to generate the gown on a mannequin or a real human model, however the dress must be photorealistic, not a sketch or cartoonish rendering. 11. The concept images that the AI generates and the final image should portray the body type and skin color which the customer specifies - It is very important for us to render the image of the garment on the correct body type - ex. Hourglass, pear-shaped, thin, plus sized, etc. -- Specific body measurements do not need to be factored into the rendering of the body type, it just generally needs to be able to render the garment on different body types. - It is also very important for us to render the garment on a human model or mannequin which has the same or similar skin color as the customer inquiring -- This is important for the customer to judge the garment color and fabric type that will look best on them -- This is also important to make the app inclusive for people of all racial backgrounds who might use the app -- It may be best not to display the face, or if human models are used, to use pictures of models with different racial backgrounds, to avoid bizarre mismatches between facial characteristics and skin tone - The AI agent should ideally prioritize pictures of garments from our client’s website to use as inspiration when it generates renderings in the freeform conversation, along with the customer’s description of what they want. However this is not a hard requirement, so it could be eliminated from the requirements if it greatly increases devlopment effort. - The requirement for the quality of the images that are generated will be somewhat subjective and so we will need to budget time for our client to request revisions to this based on their review of the system. - We need to build the image generation part upfront to ensure the quality is acceptable before we spend time on other parts of the application. 12. AI asks whether the generated concept is generally what the customer wants - Customer can revise the concept conversationally 13. AI can regenerate or refine images after customer feedback 14. The tone of the conversation the AI has with the customer is important. - We will want it to speak like a friendly expert seamstress. - This requirement will be somewhat subjective and so we will need to budget time for our client to request revisions to this tone based on their review of the system. 16. We ideally want the agent (both chat and image generation) to have deep expertise about fabrics and these types of garments in general, so it can guide the user through prompts, and render the chosen fabrics correctly - I think freeform chat will be necessary for the customer to explain which fabrics should be used where on the garment, instead of gathering this informaton in the programmatic questionnaire - The customer will likely revise the fabric selections after they see the initial renderings of the garment - We would like to avoid the costs of training an AI for this, so ideally we should use commercially available AI models which have been trained for this purpose, instead of having to train our own model. Prompting the AI with this information might be a cost-effective way to teach it this expertise 17. There will be certain restrictions on what types of colors or fabrics can be used in the dress designs - So, the agent should know these restrictions when it has the freeform conversation with the customer. - For example, the store owner will not be able to produce dresses with neon colors, tie dye colors, etc. - Our client will articulate a list of restrictions for us before we begin the project. 18. AI should never display links to other websites, or suggest for the customer to navigate to other websites 19. This AI might not need to be trained specifically for this industry, but we should at least use prompting to direct it to gather this kind of information, and to give it some background about what each of these things mean, so it can describe them to the customer. We basically need to make it as knowledgable as possble while keeping costs low. 20. The AI system the system should remember their active conversation - Since the customer will be required to have an account to use the AI system we can use that to automatically save the AI conversation - The saved conversation should preserve all the information that the customer input since the beginning of the AI session - A customer can only have one active AI session at a time - The customer cannot resume an AI session that has been completed - We don't need to provide a way for the customer to see the details of completed AI sessions 21. AI should have a fallback/human-help option if the customer gets stuck or the AI fails. - The fallback should collect enough information for an admin to follow up manually, so it should present a form in order to ensure that all the necessary information gets collected - A message should be displayed above the form, or somewhere on the page, to inform the customer that the entire conversation will be sent along with the form submission, so they know that they do not have to type all the details of the AI conversation - The app must present a button outside of the chat prompts after 3 - 5 chat messages have been sent, so the customer knows they have the option to terminate the AI conversation and manually ask for help. - That button would display the form - We don't want to display the button before any conversation has happened because we don't want customers to skip the chat altogether. -- One of the business goals of this app is to allow custom inquiries without overwhelming the support staff - Site admins must have the ability to adjust how many messages the button will display after, so they can control this threshold after they observe the results of real conversations - After the button initially displays, it should remain present in the view so the customer can easily access it at any point in the conversation 22. The freeform chat must be limited to something like 50 to 75 messages, in order to avoid excessive charges from the 3rd party AI services - This threshold should be adjustable from an admin portal - If this threshold is reached during the conversation, then we should force the customer to use the fallback form from requirement #21 to submit their inquiry 23. Customer can submit the completed design inquiry when satisfied. - During the submission process, the chat must ask for the following information, and present the following pre-written messages. This doesn't actually need to be executed by the AI model, but it can just be programmatically presented to the customer: - Ask for customer contact info, including name, email, and phone number. - Ask for requested event/date, while making clear the date is not guaranteed. - Ask for seamstress-relevant measurements, including bust, waist, hips, hollow-to-hem, shoulder width, bust point, underbust, waist-to-floor, arm length, bicep, wrist, back width, torso length, height, shoe height, and preferred fit. -- I still have to refine this list with the client, I am not sure if it needs to ask for all these things, or if there are some different things that I haven't listed here which it needs to ask for -- When it asks for this information it should display links under each measurement type to articles which describe how to produce each of the measurements. We can hardcode these links or allow the admin to specify each, they don't need to be generated by AI. - Prewritten disclaimer text should display. 24. The final submission should notify a list of email addresses set by a site admin. 25. The final submission will completely consume the credit used to purchase this AI session - The AI conversation cannot be resumed after the final submission - Another credit must be purchased to start a new AI conversation - New AI conversations will not have any memory of the previous conversations, any new AI conversations will start from a clean slate 26. Admins must have the ability to manually reset a credit, or assign a credit for free and cancel a current session, so the customer can start a new AI conversation. - This doesn't need to be very user friendly for the admin. If a session is reset this way, no knowledge of the previous conversation needs to be preserved. 27. Admins should be able to review partial, or completed conversations within a list in the admin portal - Each line item should display a status indicator to show if the conversation has been submitted yet, if an admin has began the review process, or if the item has been handled: Ex. In Progress, Submitted, In Review, Awaiting Payment, Handling, Ready To Ship, Closed - Admin should be able to see the answers to the programmatic questionnaire - Admin should be able to review the full conversation history - Admin should be able to review all uploaded photos/files - Admin should be able to review all AI-generated images, and the final one should be clear to them - Admin should be able to see the collected technical design details and measurements 28. Pricing of the garment remains manual and is handled by after review, the AI should not give any quote or present any pricing even if asked by the customer. 29. If the customer asks for pricing, the AI should display a prewritten script like this: "Pricing will be determined by the store owner after this conversation has been reviewed." 30. Invoices and payment will be handled manually through native WooCommerce custom order/invoice functionality which is already present in the e-commerce site, the AI system doesn't need to handle this at all. I mentioned this above on the requirements, but I want to reiterate since it is important and a hard requirement for how the development milestones must be structured: - The requirement for the quality of the images that are generated will be somewhat subjective and so we will need to budget time for our client to request revisions to this based on their review of the system. - We need to do the image generation part upfront to ensure the quality is acceptable before we spend time on other parts of the application As an optional add-on to the scope of this project, can you give a separate estimate to enhance the AI such that it understands which kinds of modifications will increase or decrease the cost of producing the gown, so it can guide the customer in case they are asking for very expensive things. - It shouldn’t give any specific price numbers, but should give the customer guidance if additions or alterations will significantly increase or decrease the cost of production. - This will be to prevent the customer from being surprised when the store owner manually follows up with them with the price of the garment they designed. This client did agree to adhere to a strict schedule to provide feedback after each round of development, given that we complete each round of development on the schedule we agreed to. - However, this client has deviated from agreed schedules multiple times in the past on other projects I did with them, so you should factor that into your timeline and cost estimations - We cannot increase the development cost mid-way through the project, however we can adjust the development timeline if the client deviates from the schedule In your proposal, please also include a quote or estimate for the cost of hosting and ongoing maintenance after the app has launched - Our client can pay for the hosting directly - We will need at least ongoing updates to patch security vulnerabilities and ensure uptime of the app and all its features which will be defined by the scope of this project - We don't need a 100% 24/7 uptime SLA, but basically just keeping everything up to date so it stays stable, and we'd need someone to respond to outages within 24 hours - Outage response can consist of simple rollbacks, if necessary, as long as all the chat session info is at least provided to the client as a CSV or similar, along with all graphic assets from any conversations, so they don't lose any data from an outage - I would set the expectation with my client that we would treat any future support or enhancement requests to be additionally charged for on an as-needed basis
- Fixed price
- Expert
- Est. budget: $2,000.00
Build Private AI Chat Tool Using Anthropic Claude API — Law Firm Budget: $1,500–$3,000 fixed price Description: I'm a managing attorney at a small law firm in New York. I need a private, secure web application that gives my 4-person team access to Claude AI for document summarization and legal drafting — using the Anthropic API with Zero Data Retention so no client data is stored externally. What I need built: Browser-based chat interface (works like claude.ai but private) Per-user login (4 users) PDF upload — user uploads a document, selects a task (summarize medical records, extract key facts, etc.), Claude returns structured output Conversation history saved to our own encrypted database, tagged by case number Admin view where I can see all conversations across all users Hosted on a private server with HTTPS/SSL No data logged or stored outside our own database Clean, simple UI — non-technical staff must be able to use it Tech requirements: Anthropic Messages API (claude-sonnet-4-6) Zero Data Retention configured on the API account PostgreSQL or similar database for history Per-user authentication (JWT or similar) PDF text extraction before sending to API Encrypted database at rest You must have: Prior experience with the Anthropic Claude API specifically Experience building secure web apps with user auth and databases Portfolio or examples of similar builds Please answer this in your proposal: have you configured Zero Data Retention on the Anthropic API before? This is a fixed-price project. I own all code upon final payment.