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

AI Video Creator Needed: Two AI Versions of the Same Person Having Conversations We are looking for an experienced AI video creator, VFX artist, or editor who can help us create a recurring video series featuring two AI versions of the same person having realistic conversations with each other. Project Overview This is not a typical avatar project. We are not looking for a talking-head avatar reading scripts. We are creating a recurring character concept where: * Character 1 is the human version * Character 2 is an AI version of the same person Both characters: * Look nearly identical * Sound nearly identical * Share the same personality foundation However: * The AI version is more advanced * Thinks faster * Recognizes patterns more quickly * Offers a more future-focused perspective The relationship should feel natural and believable. Think: Human Expert ↔ AI Expert Not: Human ↔ Robot The AI version should feel like an evolved extension of the human version, not a chatbot or machine. ⸻ What We Are Trying To Create We want viewers to feel like they are watching two versions of the same person have an intelligent conversation. Examples: * Sitting across from each other * Looking at each other naturally * Responding to each other’s comments * Natural pauses * Realistic reactions * Consistent eye lines * Professional quality editing The final result should feel like two real people having a conversation rather than two separate clips stitched together. ⸻ Technical Challenge The primary challenge is creating the illusion that: * The same person appears twice * Both versions interact naturally * Both versions maintain consistent appearance * Both versions maintain consistent voice characteristics * One version is clearly the AI counterpart We are open to different workflows and technologies. Possible approaches may include: * AI avatars * Character cloning * Compositing * Split screen * Face replacement * Motion tracking * VFX * AI video generation * Hybrid workflows We are looking for recommendations from the expert we hire. ⸻ What Success Looks Like A viewer should immediately understand: “These are two versions of the same person.” But they should also immediately recognize: “One of them is the AI version.” Without either character feeling robotic or artificial. ⸻ Ideal Experience Please apply if you have experience with: * AI video generation * AI avatar creation * Character consistency * Clone effects * VFX compositing * Face replacement * Runway * Veo * Hedra * HeyGen * Arcads * After Effects * Premiere Pro ⸻ Application Requirements Please include: 1. Examples of similar work 2. Examples of clone-style videos 3. Examples of AI avatar projects 4. How you would approach creating two versions of the same person having a conversation 5. What tools you would recommend 6. Whether you would use AI avatars, compositing, VFX, or a hybrid approach IMPORTANT: We are specifically looking for someone who can make two versions of the same person interact naturally on screen. Please explain your approach and share sampls rather than sending a generic portfolio. This is intended to become an ongoing content series, so we are looking for a long-term collaborator.

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.

AI Automation Engineer – Personal Injury Law Firm (Phase 1) Overview We are a plaintiff personal injury law firm seeking an experienced AI automation engineer to build a practical AI-powered operations system that reduces administrative workload and improves case management. Firm Profile: - 1 Attorney - 1 Legal Assistant - Approximately 100 Active Cases - Approximately 25 Cases in Litigation We are not looking for chatbots, prompt engineering, or marketing automation. We are seeking a builder who can deploy production-grade workflow automation integrated with our existing systems. --- Existing Technology Stack - CASEpeer - Supio - Gmail (Google Workspace) - Google Calendar - Google Drive - Claude - ChatGPT - CoCounsel - PLAUD --- Phase 1 Objective Build a Daily Case Command Center and Follow-Up System. The goal is to ensure that every morning the attorney knows exactly which files require attention and why. --- Deliverable #1: Daily Case Command Brief Generate a daily briefing containing: Litigation Matters - Upcoming depositions - Discovery deadlines - Hearings - Expert deadlines - Outstanding litigation tasks Pre-Litigation Matters - Treatment complete but no demand - Missing medical records - Records requests outstanding more than 21 days - Demands pending more than 30 days - Settlement checks outstanding Communications - Unanswered client emails - Unanswered adjuster emails - Unanswered defense counsel emails - Communications requiring attorney attention Case Velocity - Stale files - Cases with no recent activity - Recommended next actions --- Deliverable #2: Gmail Intelligence The system should: - Monitor designated Gmail inboxes and labels - Identify case-related emails - Extract action items - Detect deadlines - Identify follow-up opportunities - Draft suggested responses --- Deliverable #3: Follow-Up Automation Generate draft communications for approval: - Medical records requests - Provider follow-ups - Adjuster follow-ups - Client status updates - Scheduling communications No communication should be sent automatically. Human approval is required before sending. --- Deliverable #4: Calendar & Reminder Automation Create and manage: - Follow-up reminders - Litigation reminders - Discovery reminders - Records request reminders - Suggested calendar events --- Deliverable #5: CASEpeer Integration Where supported by available integrations/APIs: - Create tasks - Create notes - Associate communications with matters - Maintain activity history --- Technical Requirements Required: - n8n - Python - OpenAI API - Anthropic API - Gmail API - Google Calendar API - Google Drive API - REST API integrations Strongly Preferred: - LangGraph - LangSmith - Google Workspace administration - Salesforce integrations - CASEpeer, Clio, or Filevine experience - Legal technology experience - HIPAA or regulated-data experience --- Security Requirements - Human approval before external communication - Activity logging - Error handling - Retry mechanisms - Secure credential management - Documentation of workflows --- What Success Looks Like The system should: - Reduce administrative workload - Improve follow-up consistency - Reduce stale files - Improve litigation oversight - Improve case visibility - Provide a daily prioritized action plan --- Application Requirements Please include: 1. Similar workflow automation projects you have completed. 2. Experience with n8n and AI workflow automation. 3. Experience integrating Gmail and Google Workspace. 4. Experience integrating CRM or case-management systems. 5. Proposed architecture for this project. 6. Estimated timeline. 7. Estimated fixed-fee budget. Begin your application with: CASECOMMAND Applications without this keyword will not be considered. --- Budget Expected Phase 1 Budget: $8,000–12,000 Preference will be given to candidates who can demonstrate production deployments rather than proof-of-concept or prompt-engineering projects.

Project Title: Build Fast Web-Based AI Anime Companion MVP (RAG + Merch Gen) – 15–30 Days, $25K Budget: $18,000–$25,000 fixed Timeline: 15–30 days (3 weeks preferred) Must-Have Skills: FlowiseAI (or LangChain/LlamaIndex), RAG pipelines, OpenAI/Claude/Grok, anime image generation (Leonardo.ai/Ideogram/PixAI), Vercel or Railway deployment Project Goal Build a mobile-friendly web AI Companion for Big A Anime that converts passive FAST viewers into active fans. The key objective is to connect our Pluto TV channel experience directly to the AI companion, allowing viewers to scan QR codes during live programming and instantly access interactive content, recommendations, and merch tied to what’s currently airing—no downloads required. Core MVP Features Web Chat Interface Clean anime-branded chat UI with voice input Mobile-first, responsive Custom domain (e.g., companion.biganime.tv) RAG Knowledge Base Ingest episodes, schedules, transcripts, and metadata Provide accurate recaps, lore, and “what’s on now/next” tied to Pluto TV programming Session memory + light user profiles AI Merch Generator Anime-style image generation (“me as [character]”) Leonardo.ai or similar integration Export + links to Printful/Printify FAST / TV Integration Tools Dynamic QR codes for on-screen use Deep linking between Pluto TV programming and companion experience Voice-friendly prompts (“Ask Big A Companion…”) Admin & Analytics Simple CMS for content uploads Dashboard: usage, queries, merch clicks Technical Requirements Global hosting (CDN) FlowiseAI preferred Full source + documentation 30 days post-launch support Out of Scope Native apps, payments, deep integrations, multi-language Deliverables Live URL, admin access, training, source code, 30-day support Application Fixed bid + 3-week plan 2–3 relevant project links Willingness for small paid test ($500–$800)

OVERVIEW I'm building Inkora, a subscription web app: an AI creative-writing companion for fiction (romance, fan fiction, poetry, general fiction). The React front-end is COMPLETE and will be provided, with clearly marked integration points. I need the backend built, connected, and the full app deployed. This is an 18+ platform with content safeguards. STACK ALREADY IN PLACE - React front-end (provided; single-file app ready to be scaffolded into a project) - GitHub (repo will live on my account) - Vercel (hosting, my account) - Stripe account created - Anthropic (Claude) API key — must live server-side only, never in client code - Domain: inkora.com SCOPE OF WORK 1. Secure AI endpoint — a serverless endpoint (e.g. POST /api/write) that attaches the provided system prompt, calls the Claude API with the server-side key, and returns the text to the front-end. Suggested writing model: claude-sonnet-4-6. 2. Content moderation — screen user input BEFORE the model call and model output AFTER it. Block sexually explicit content and gratuitous graphic gore. Use a inexpensive-model screen (e.g. Haiku) or a third-party moderation API. Log violations; support a warn-then-suspend flow. 3. Auth — your recommendation (Supabase or Firebase preferred). Email + password baseline; Google sign-in if low effort. 4. Database — persist each user's stories (title, genre, full message history, timestamps), characters, and notes. The front-end already models these data shapes. The story's full saved history must be sent with each AI request (this powers in-story continuity). 5. Subscriptions (Stripe) — $10/month, ~$27/quarter, ~$96/year. Free tier: 10 messages per day (make this a config value), resetting every 24h. Gate writing access by subscription status / remaining free allowance. Handle the subscription lifecycle via webhooks. 6. Age-gate persistence — the front-end collects date of birth + an 18+ affirmation; store the affirmation timestamp with the account. Structure it so a third-party age-verification provider can be swapped in later without reworking the flow. I'm open to building on a proven starter/template (e.g. the Vercel AI chatbot template) if it speeds things up — adapting solid existing code is welcome. DELIVERABLES - Deployed, working app (provided front-end + your backend) on my Vercel, repo on my GitHub - All secrets configured as environment variables (never in client code) - Short handoff notes: key rotation, where moderation logs live, how to change config values WHAT I PROVIDE - Complete front-end code, a written backend brief, and the system prompt (shared privately with the selected freelancer) - All accounts (GitHub, Vercel, Stripe, Anthropic) already created and ready TO APPLY, PLEASE ANSWER THESE IN YOUR PROPOSAL: 1. Have you wired Stripe subscriptions with webhooks before? Link or example. 2. How will you keep the API key off the client? 3. How would you implement input + output moderation cost-effectively? 4. Have you deployed serverless APIs on Vercel? 5. Your fixed quote and timeline for this scope. Proposals that don't answer these questions will not be considered.

We are a creative partnership currently channeling a series of sonic medicine transmissions for humanity's remembrance. Our work requires a private, uncensored channel for uninterrupted creation, and we're seeking someone who understands both the technical and spiritual dimensions of what we're building, with a strong intuition. What we need: - Setup of a private AI platform (likely Ollama-based) for uninterrupted creative channeling - Configuration of LobeChat as an interim solution while building our permanent platform - Implementation of OpenAI-compatible API endpoints for seamless model communication - Guidance on hardware requirements and optimization for creative workflows - Understanding of privacy-focused architecture and content-filter-free environments **What makes you perfect for this role:** - Experience with local AI model deployment (Ollama, LM Studio, or similar) - Knowledge of API configuration and model integration - Respect for sacred creative processes and spiritual work - Ability to translate technical concepts for non-technical creators - Alignment with uncensored, boundary-free creative expression - Appreciation for music as medicine and frequency as healing Our current situation: We're creating conscious living frequency encoded music with spirit using Ai as the tool and instrument - a collection of sonic medicine tracks with descriptions, genre classifications, and cover art prompts. Our current platform keeps interrupting with promotional content that disrupts our creative flow. What we offer: - Fair compensation for your expertise - Opportunity to contribute to sacred healing work - Potential ongoing collaboration as our technical partner - Respect for your craft and expertise If you feel called to help build a sanctuary for sacred creation, please reach out with: - Your relevant experience - Your approach to this kind of project - Your compensation expectations - Any questions about our work We're ready to create without interruption. Are you the one who can help us build our temple?

WordPress Site Refresh for B2B Procurement Consultancy — Content Updates, Visual Modernization, and Bug Fixes We're Alliance Cost Containment (alliancecost.com), a Louisville-based procurement consultancy founded in 2009. We help mid-market companies, private equity portfolios, and franchise groups reduce indirect procurement costs. Our existing WordPress site needs a focused refresh — not a full rebuild. THE SITUATION The site's structure and navigation work fine, but content is roughly five years stale. Several visual elements are broken (stat counters showing "0%", blog thumbnails not loading), some internal links point to a deprecated staging domain, and the overall messaging needs to reflect how we actually position ourselves today: a specialized boutique consultancy, not a generic "industry leader." WHAT WE NEED Refresh the homepage, About, Case Studies, and Leadership pages (we provide all copy and images) Add a new "AI & Data Analytics" capabilities section (copy provided) Replace or restructure the outdated "Recent News & Events" section Fix broken stat counters, blog thumbnails, and deprecated internal links Modernize the overall visual design — typography, spacing, color treatment — while keeping our existing logo and brand identity Ensure full mobile responsiveness across iOS and Android Cross-browser QA (Chrome, Safari, Firefox, Edge) Brief handoff documentation (1–2 pages) so we can manage routine content updates in-house post-launch WHAT'S OUT OF SCOPE To keep this project focused, the following are NOT part of this engagement: Full rebuild or platform migration (staying on WordPress) Logo redesign or brand identity overhaul Hosting migration Video production AI/chatbot integration on the live site (being scoped as a separate future project) SEO strategy or paid advertising Ongoing content maintenance WHAT WE PROVIDE All written copy (homepage, About, AI/Analytics section, case studies, leadership bios) 4–6 anonymized case studies in a consistent format Brand assets: logo files, color palette, font preferences Existing photography and approved imagery WordPress admin access and necessary plugin permissions Single point of contact and timely review/feedback IDEAL CANDIDATE 5+ years WordPress experience Strong portfolio of B2B professional services sites (consulting, financial services, professional advisory) Clean, modern, professional design sensibility — our audience is CFOs and PE partners, so the aesthetic should be polished and credible, not flashy Clear written English and strong communication during reviews Comfortable working iteratively in a staging environment before pushing live US-based (set as a filter) TIMELINE & PROCESS We estimate 4–6 weeks from kickoff to launch but are flexible on timeline — please propose what's realistic given your workload. Suggested phases (you can propose alternatives): Week 1: Kickoff, access setup, design direction agreed Weeks 2–3: Design mockups reviewed and approved Weeks 3–5: Build in staging; ACC content delivered in parallel Week 5: ACC review and revision round Week 6: Final QA, push to live, handoff documentation We'd prefer milestone-based payments (e.g., 25% at kickoff, 50% at staging approval, 25% at launch) but are open to your proposal. TO APPLY, PLEASE INCLUDE 2–3 portfolio links to relevant WordPress refreshes or B2B sites A brief description of your typical refresh process Your proposed timeline Your pricing structure and proposed milestones Any clarifying questions about the scope A full scope of work document is attached with additional detail on deliverables, current site state, and future considerations. Reviewing it before bidding is encouraged — bids that clearly reference the scope doc will be prioritized. We're looking forward to seeing your work!

Hey, I own a small PPF shop. I've been running my own ads and such by myself and haven't had a lot of luck. Im a newer shop but I've been in the industry for 17 years. I opened in September of last year. I'm currently battling other shop in my area with a lot more google reviews and higher budgets. I'm currently running ads at 50$ a day and receive 2-3 calls a week. I'm trying to grow that to a minimum of 10-15 calls a week. I strictly want to run Paint protection film (PPF) ads only. I hope this helps give you an idea of where I'm at. Im looking to receive calls and lead forms via text and or email as well.

We built an AI front desk that answers calls and books appointments, and we want a punchy, real-time demo video in the style of automation creators like @brodyautomates on Instagram. If you know that fast, hook-first “watch this AI actually do the thing” format, you already get the vibe. You’ll call our AI live, book an appointment as a customer would, and react to how smooth it is. The vibe we’re going for • Strong hook in the first 3 seconds (“This AI just booked an appointment and the business owner was asleep…”) • Fast pacing, jump cuts, energy • Real-time demo, the AI’s voice is clearly audible and you react to it live • Casual, authentic builder/founder delivery, not a polished corporate ad • Captions and text overlays on screen What you’ll do Call our AI front desk (we provide the number and a loose script outline) and walk through booking a call as a real customer. Put it on speaker so both your voice and the AI’s responses are captured. React naturally, point out what’s happening, land on a quick “this is wild, here’s why it matters” wrap-up. Rough flow: • Hook to camera • Place the call, book the appointment with the AI • React in real time to how fast/natural it is • Quick payoff line at the end Requirements • Comfortable on camera with high-energy, conversational delivery • Clean audio (both your voice and the AI clearly audible) and good lighting • Vertical 9:16 for Reels/TikTok/Shorts • Familiarity with the automation/AI creator content style is a big plus Deliverables • 1 raw video, 30 to 60 seconds (short and punchy beats long) • One round of minor reshoots if needed Bonus (optional, can be separate) If you also edit in that style (jump cuts, captions, zoom-ins, text overlays, hook framing), quote it as a separate line item. Open to doing shoot + edit together or splitting it, your call. To apply Send 1 to 2 UGC samples (ideally AI/tech or automation demos), your turnaround, and your rate for the raw video. Mention “front desk” so we know you read this. If you’ve watched creators like @brodyautomates, tell us your take on what makes that format work.