We have an existing application that includes several AI-powered features and integrations. Some features are currently not functioning as expected, and we are looking for an experienced developer to review the codebase, identify the root causes, and implement reliable fixes. The ideal candidate should be comfortable working with AI/LLM integrations, debugging complex systems, and improving existing functionality without disrupting the overall application.

AI Developer Needed – Build Us a Marketing AI Agent We need a skilled developer to build an AI-powered Marketing Assistant for our business. **Core Tasks the Agent Will Handle:** - Appointment setting & lead qualification - Copywriting (emails, ads, social content) - Automated follow-up sequences - Lead research and CRM updates **Requirements:** - Experience with AI agent frameworks (LangChain, CrewAI, AutoGen, etc.) - Strong prompt engineering skills - Ability to integrate with our existing tools (CRM, calendar, email) - Past projects to show us – links or demos preferred **Budget:** Open to discussion based on scope **Timeline:** Looking to kick off within 1–2 weeks

We’re a strategic investor relations firm looking to bring on an AI automation specialist to help us build and maintain internal workflows across key deliverables. This is not a one-off project. We’re looking for someone who can work with us ongoing, think in systems, and help us implement a structured AI-driven operating model. We already have a clear roadmap and initial strategy in place. Your role is to help bring it to life. What We’re Building We are focused on three core workflows: 1. AI-Assisted Drafting (Priority) Build Custom GPTs for client deliverables (earnings materials, summaries, etc.) Structure inputs (transcripts, historical materials, models) Standardize outputs (tone, format, consistency) 2. Analyst Consensus Automation Pull data from Excel / SharePoint (NOT third-party APIs) Use Make.com (or similar) to automate workflows Feed structured data into ChatGPT for report generation 3. Fund Profile Workflows (Later Phase) Work with semi-manual datasets (exports from IR platforms) Build hybrid workflows (automation + human input) What We Need From You We are looking for someone who can: Build Custom GPT workflows (not just prompts) Work with Make.com (or similar tools like n8n / Zapier) Integrate with Microsoft 365 (SharePoint, Excel, Outlook) Structure messy workflows into repeatable systems Think critically about data accuracy and validation Build with human-in-the-loop review processes Important Context We work in investor relations → accuracy matters more than speed We are not looking for “full automation” → we want controlled, reliable workflows Many processes today involve manual copy/paste and disconnected tools Goal is to reduce friction and standardize output, not cut corners Engagement Details Type: Ongoing (starting with a pilot project) Initial Focus: Build Phase 1 (AI drafting workflow) Hours: Flexible (will grow over time) Start: ASAP How We’ll Evaluate Candidates We’re less concerned with resumes and more interested in how you think. Please include: Examples of automation workflows you’ve built (especially with GPT + Make/Zapier) A short explanation of how you would: Take a transcript + prior materials → generate a structured draft Tools you prefer and why Nice to Have (Not Required) Experience in finance, IR, or data-heavy environments Experience working with structured Excel models API experience What This Can Turn Into If this goes well, this becomes a long-term role helping us build and maintain our internal AI infrastructure. We’re not looking for a task-doer—we’re looking for someone who can grow with us and own this function over time.

We are a small AI consulting practice that helps financial services firms put AI to work inside their business. Our clients are owner-led firms like accountants, business appraisers, financial advisors, and insurance agents. We do not sell one-off scripts or disposable projects. We build practical AI systems that take real work off these firms' plates, delivered through ongoing monthly work. Demand is growing and the bottleneck is delivery. We are looking for one delivery partner to own that side of the work with us. How it works: we handle marketing, sales, and the paid advisory session that starts each client. Once a client moves to ongoing work, you take the lead on delivery. You build the systems against the priorities we set each month, and you run the weekly client meeting as their main point of contact. We stay in for support, to translate the client's business context, and to own the relationship at the top, but week to week the client works with you. What you would own: -Building AI and agentic systems for clients -Running the weekly client meeting and being the client's day-to-day contact -Taking each engagement from kickoff through delivery on the month's agreed hours, to a standard we can stand behind Compensation is $100/hour for your hours, which include both build time and client meetings. Straightforward and paid against tracked hours. As our client book grows, so do the hours available. Who we are looking for: -Genuinely fluent building real systems with modern AI tools. -Not just familiar with them. You should be comfortable architecting and shipping working systems for non-technical business owners. -Client-ready. You can run a working session, explain technical things plainly to a non-technical owner, and hold a client relationship week to week. -Native or fluent English. You are in front of clients every week, so clear, natural communication is non-negotiable. -Strong general technical judgment. The specific stack matters less than the ability to find the right solution and build it. -Reliable. We scope the work and stand behind it, so we need to count on what you deliver and how you handle the client. Who this is not for: anyone looking to own sales or pricing, anyone who only wants to build quietly and never talk to a client, and anyone new to this work hoping to learn on the job. To apply, tell us briefly: the most relevant AI system you have built and what it did for the business, how comfortable you are leading client calls, and how you approach building these systems. Start your reply with the word "Agentic" so we know you read this in full. Applications without it will not be reviewed. We will move quickly with the right person.

We are looking for a hands-on Forward Deployed AI Engineer to help build practical AI systems This is not a pure backend role and not a strategy-only consulting role. You will work close to end users, understand how their workflows actually operate, and then build AI-enabled tools that solve specific business problems. The ideal person is a strong software engineer who is comfortable with ambiguity, can communicate clearly with non-technical stakeholders, and can take an AI prototype from idea to something reliable and usable. What you will do - Learn the business workflows, systems, data, and constraints. - Build AI applications using Claude or similar large language models. - Use the right mix of prompting, retrieval, tool use, agents, and workflow automation. - Own delivery from scoping through prototype, testing, hardening, and handoff. - Create evaluations to determine whether the system is accurate, reliable, and safe enough to use. - Translate between domain experts and technical implementation. - Work carefully with sensitive or regulated data. - Document what you build so it can be maintained and reused. What we are looking for - Strong Python engineering skills. - Hands-on experience building with LLMs, preferably Claude or the Anthropic API. - Experience with RAG, structured prompting, tool use, evaluation, or agentic workflows. - Ability to operate independently in a messy, ambiguous environment. - Strong communication skills with both technical and non-technical stakeholders. - Track record of shipping working software, not just demos. - Comfort working with real-world data, integrations, and imperfect requirements. Helpful but not required - Prior forward deployed engineering, solutions engineering, or technical consulting experience. - Experience building AI tools for enterprise customers. - Experience in regulated or sensitive-data environments. - Familiarity with validation, auditability, traceability, or compliance-oriented workflows.

Overview We’re looking for an experienced AI engineer or AI systems builder to help us design and build an internal intelligence layer that turns fragmented customer data into actionable growth opportunities. Right now, customer insights live across multiple disconnected systems — CRM notes, product usage data, emails, support tickets, and spreadsheets. While the data exists, it is not structured in a way that helps us proactively identify expansion opportunities, churn risks, or account-level next steps. We want to build an AI-driven system that continuously synthesizes this information and helps our team understand: * What is happening inside each account * Where expansion or upsell opportunities exist * Which accounts are at risk and why * What the next best action should be for each customer ⸻ What You’ll Build You will design and implement an AI system that can: * Ingest structured and unstructured data (CRM, emails, notes, product signals) * Build dynamic “account intelligence profiles” for each customer * Identify patterns across accounts (usage drops, feature gaps, expansion signals) * Generate clear, human-readable account summaries * Recommend next-best-actions for sales, customer success, or leadership * Surface expansion opportunities based on behavioral and contextual signals * Flag risk signals early with supporting reasoning ⸻ Ideal Output For each account, the system should be able to generate: * A concise account narrative (“what’s going on here”) * Key signals and anomalies * Expansion opportunities (with rationale) * Risk factors (churn or stagnation indicators) * Suggested actions for the team this week * Confidence level and supporting evidence ⸻ Why This Matters We are sitting on a large amount of customer data, but most of it is passive. The goal is to turn it into an active intelligence system that helps our team: * Prioritize the right accounts * Increase expansion revenue * Reduce churn risk * Spend time on the highest-impact opportunities This becomes a core internal system that directly impacts revenue efficiency and customer outcomes. ⸻ Ideal Candidate We’re looking for someone with experience in: * LLM-based systems and agentic workflows * Data pipelines and multi-source data ingestion * Prompt engineering + structured reasoning systems * CRM systems (Salesforce, HubSpot, etc.) * Customer analytics / product analytics * Building internal AI tools or copilots * Backend + API integration work Bonus if you’ve worked on: * RevOps tooling * Customer success platforms * Data enrichment or account intelligence systems * SaaS growth analytics ⸻ Deliverables * System architecture for AI customer intelligence layer * Data ingestion and normalization approach * Prompting / reasoning framework for account analysis * Prototype system (or working MVP) * Output format for account intelligence reports * Documentation for internal expansion and scaling * Recommendations for tooling (build vs buy decisions) ⸻ Engagement This starts as a project-based build, but could expand into a long-term role as we scale the system across our entire customer base and additional workflows. ⸻ To Apply Please include: * Examples of AI systems or agentic workflows you’ve built * Experience integrating LLMs with real business data * Your recommended architecture for a system like this * Any clarifying questions you’d want answered before starting

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

### 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!

We are a small residential real estate investment company seeking an AI Solutions Architect to enhance our acquisition platform. The role involves designing and implementing AI solutions to improve data analysis and decision-making processes. The ideal candidate will have experience in AI architecture and a strong understanding of real estate data analysis.