DESCRIPTION We're a small applied AI lab running a live, production-track AI product for an institutional financial services client. The work is technical, fast-moving, and high-stakes. We need to fill a critical infrastructure role with someone senior, collaborative, and genuinely excited about building in the current AI tooling ecosystem. THE ROLE You'll own the data infrastructure layer for an AI-powered intelligence platform built on the Microsoft Azure ecosystem. This is a hands-on engineering position — you're responsible for designing, building, and maintaining the pipelines that feed a live AI scoring engine. The environment is agentic. Data moves from 15+ heterogeneous external sources (APIs, PDFs, regulatory filings, web) through Bronze, Silver, and Gold layers into a scoring and inference system. The hard problems are extraction quality, schema normalization, pipeline reliability, and getting the right data to the scoring engine in the right shape. You'll work directly with the technical lead and engagement lead. No layers. Fast decisions. WHAT YOU'LL OWN + Data pipeline architecture and delivery across Bronze (raw ingestion), Silver (normalization, NLP extraction, entity resolution), and Gold (unified output, scoring-ready) layers + Microsoft Fabric lakehouse implementation — OneLake, Data Pipelines, Dataflows Gen2, Warehouse, and downstream system integration + Microsoft Foundry (formerly Azure AI Studio) — agent orchestration, prompt pipelines, and AI model integration within a secure Azure tenancy + Azure Data Factory orchestration for structured source ingestion +Salesforce integration via Snowflake native connector — field mapping, custom object schemas, sync reliability Extraction pipelines for unstructured sources (PDFs, regulatory filings, web content), coordinating with Azure OpenAI-based extraction agents +Data governance and security posture — all data stays within the client's Azure tenancy; data residency is non-negotiable REQUIRED: Technical Skills + Microsoft Fabric — production experience, not sandbox. You should be able to speak to Lakehouse vs. Warehouse tradeoffs, OneLake architecture, and real pipeline implementation. Microsoft Foundry / Azure AI Studio — hands-on with agent deployments, prompt flow, model endpoints, and Azure OpenAI integration within an enterprise Azure tenancy + Azure Data Factory — pipeline authoring, trigger management, connector configuration, monitoring +Snowflake — Gold layer data warehousing, schema design, query optimization, native connector usage (specifically Salesforce) + Python — data engineering contexts: pandas, PySpark, API clients, extraction scripts + SQL — complex joins, window functions, schema design; SQL Server preferred + Azure Blob Storage / ADLS Gen2 — Parquet/Delta format, access control, lifecycle management REQUIRED: AI-Augmented Development This is a hard requirement. You should be actively using AI coding tools to multiply your output — fluency with Claude Code, Cursor, and OpenAI Codex as part of your daily development workflow. If these aren't already in your stack, this isn't the right fit. We hire for multiplied output, not raw hours. REQUIRED: Demonstrable Work We don't evaluate resumes alone. Bring something — a GitHub repo, a deployed pipeline, an architecture document you authored, a case study with real numbers. We should be able to look at your work and understand what you built, what decisions you made, and why. Work under NDA is fine if you can describe it in enough detail to convey complexity and ownership. ATTITUDE & WORK STYLE Comfortable with Agile Scrum and its accompanying ceremonies. You raise issues early and help solve them. You communicate tradeoffs clearly without over-explaining. You're comfortable with evolving specs and don't need to win the architecture argument — just build the right thing within the approved stack. We're a small, senior team with low friction and direct communication. That's the environment; it works if you work with it. THE STACK The client environment has specific technology approvals. Production work runs on Azure OpenAI (client-hosted), Microsoft Fabric, Microsoft Foundry, Snowflake, Azure Data Factory, ADLS Gen2, Salesforce via Snowflake native connector, and SQL Server. LangChain, DeepSeek, and the external Claude API are not approved for this environment. NICE TO HAVES Experience with financial services or institutional investment data (SEC EDGAR, public pension filings, regulatory documents), familiarity with InvestorFlow or Salesforce Financial Services Cloud, unstructured document extraction at scale, or Azure Purview.

I need a full stack developer to build a simple web application called WriteTheDeal. The frontend design is already 100% complete — I have fully designed HTML files ready to hand over. You are building the backend and making everything functional. This is Phase 1 of a larger project — if this phase goes well, there is a strong chance of continued paid work for Phase 2 with additional features. Here is exactly what needs to be built: 1. An embeddable JavaScript widget that dealers paste on their website with one line of code. When a buyer clicks Make an Offer a modal opens with a form collecting the following information from the buyer: offer amount, first name, last name, email address, phone number, and card details via Stripe. 2. Payment intent question — the offer form must ask the buyer how they intend to pay for the vehicle, with three options presented as selectable buttons: Finance through the dealership, Cash, or Outside lending. This is a required field and must be completed before the offer can be submitted. The dealer must see this answer clearly displayed alongside the rest of the offer details in their dashboard. 3. Trade-in question — the offer form must ask the buyer “Do you have a trade-in?” with a Yes or No option. If the buyer selects Yes, the following additional fields must appear: Vin Number - Year, Make, Model, Trim, Mileage, and Condition. Condition must be a dropdown with exactly these three options: “Showroom condition,” “Good — some scratches here and there, may need new tires,” and “Poor — needs a lot of TLC.” All trade-in details must be clearly visible to the dealer in their dashboard alongside the rest of the offer. 4. Notes field — both the buyer and the dealer must be able to add a note at any point in the process. The buyer can add a note when submitting their original offer. The dealer can add a note when responding to an offer. All notes must be stored and visible in the full offer history so both sides can see the complete conversation thread at any time. 5. A Stripe integration using Stripe Connect — when a dealer accepts an offer, the $1,500 deposit must go directly into the dealer’s own connected bank account, not mine. I must never receive the buyer’s deposit money in my account at any point. I earn only a separate platform fee automatically deducted at the time of each transaction. The buyer’s card must be authorized but not charged at the time of offer submission — it is only captured when the dealer accepts. If the dealer declines, the hold must be released immediately and the buyer is never charged. 6. ADF/XML lead delivery — when a buyer submits an offer, the system must automatically send a correctly formatted ADF/XML lead email to the dealer’s CRM intake email address. This must work with all major automotive CRMs including VinSolutions, ELEAD, DealerSocket, DriveCentric, ProMax, and AutoRaptor. The lead email must include all offer details — offer amount, buyer contact info, payment intent, trade-in details, and any notes. 7. Instant dealer notifications — the moment a buyer submits an offer, the dealer must automatically receive both an email notification and a text message notification containing the buyer’s name, offer amount, and a direct link to view the full offer in their dashboard. Text messages must be sent using Twilio. 8. Dealer dashboard — a secure, password-protected login page where dealers can see all of their incoming offers. Each dealer must only ever see their own offers and their own buyers — no dealer should ever be able to see another dealer’s data. The dashboard must clearly display for each offer: buyer name, email, phone, offer amount, payment intent, trade-in details if applicable, notes, and the full offer history. Each offer must have three action buttons: Accept, Decline, and Counter Offer. 9. Counter-offer functionality — in addition to Accept and Decline, the dealer must be able to send a counter-offer back to the buyer with a revised amount and an optional note. The buyer must receive an email and text notification when a counter-offer is sent. The buyer must be able to accept the counter, decline it, or send their own counter back. This back-and-forth negotiation must be able to continue for multiple rounds until one side accepts or declines. Every round of the negotiation must be stored and visible in the offer history for both the buyer and the dealer. 10. Maximum discount threshold with automatic decline — each dealer must be able to set a maximum percentage off MSRP they are willing to consider, for example 5%. If a buyer submits an offer that falls below this threshold — meaning the discount requested is greater than the dealer’s set maximum — the system must automatically decline the offer immediately without the dealer needing to take any action. The buyer’s card must never be charged on an auto-declined offer. This threshold setting must be adjustable by the dealer at any time from their dashboard settings, and must be settable as both a store-wide default and on a per-vehicle basis. 11. Salesperson send-link tool — inside the dealer dashboard there must be a tool where a salesperson can enter a customer’s name, email, phone number, offer amount, and vehicle details, and the system generates a unique pre-filled link. When the customer opens this link the offer form loads with all their details already filled in — they only need to add their card to submit. The salesperson must be able to send this link via email or text directly from within the dashboard. 12. Admin panel for me — I need a completely separate and private admin login at a secure URL. From this panel I must be able to: add a new dealer by entering their basic info, automatically generate their unique dealer ID, automatically generate their dashboard login credentials, automatically generate the exact widget code snippet ready to send to their webmaster, and view all dealers and all offers across the entire platform. I must never need to contact the developer to add a new dealer after launch. 13. Individual dealer login accounts — each dealer must have their own unique username and password to access their dashboard. When they log in they must only see their own data. No dealer should ever be able to access or view another dealer’s offers, buyers, or settings. 14. Public website — I have a fully designed landing page and pricing page already built as HTML files. I need these deployed and made live at writethedeal.com as the public-facing marketing website for the product. 15. All accounts must be created under my ownership — please set up all hosting, database, Twilio, and any other third-party service accounts using my email address and my payment method from day one. Even though you will be handling the technical setup, I must own every account. I must be able to access, manage, and if necessary transfer every account without needing your involvement after the project is complete. Please use Node.js for backend and PostgreSQL for the database, deployed on Render or Railway. If you strongly prefer a different approach please explain why in your proposal, but I would like to stick with widely used tech so I can easily find another developer to maintain or update the product in the future if needed. Deliverables: — Fully working embeddable widget with all form fields described above — Payment intent question (finance with dealer, cash, or outside lending) — Trade-in question with year, make, model, trim, mileage, and condition dropdown — Notes field on every offer visible to both buyer and dealer — Stripe Connect integration with deposits going directly to dealer accounts — ADF/XML lead delivery to dealer CRM intake email — Email and SMS notifications to dealers via Twilio — Dealer dashboard with accept, decline, and counter-offer functionality — Full negotiation history stored and visible on every offer — Maximum discount threshold settings with automatic decline per dealer and per vehicle — Salesperson send-link tool with pre-filled customer links — Admin panel where I can add new dealers and generate widget codes myself — Individual dealer logins with complete data separation between dealers — Public marketing website deployed at writethedeal.com using my existing designs — All third-party accounts created under my ownership — Fully deployed and live on a real URL — A 20 minute Loom video walkthrough of the entire system — A simple plain-English document explaining how to add a new dealer from start to finish Timeline: 4 to 6 weeks Budget: $3000-$4000 fixed price for everything listed above, paid across 6 milestones Note on hiring: Before I hire anyone I will ask all candidates to explain in plain English how they would set up Stripe Connect so that the $1,500 deposit goes directly to the dealer’s bank account and never passes through my account. The clarity and accuracy of your answer to this question will be a significant factor in my hiring decision.

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

What I need: I want a custom-built, fully working physical Skylanders portal that I can place real figures and traps on, that works with the Cemu emulator on my Windows PC. It must be detected by my computer as a genuine Skylanders portal (USB Vendor ID 0x1430, Product ID 0x0150) so the game treats it as real hardware. I am not interested in software-only emulation — I want real hardware with real, placeable figures. This is a recreation of the Skylanders: Trap Team "Traptanium" portal. It's a known, documented build (Raspberry Pi Pico + NFC reader + open-source firmware), so this is execution work, not research from scratch — I'll provide a detailed technical reference doc with the exact firmware repos, wiring, and USB protocol once we connect. The finished portal must include, like the original: An open surface to place multiple figures at once A separate trap slot Color (RGB) LEDs lighting the portal area A dedicated LED for the trap slot A working speaker for in-game audio A housing that can be opened to access the internal components for future repairs or upgrades (e.g., screwed or otherwise removable panel — not glued or permanently sealed shut) Suggested approach (you're welcome to propose better): Raspberry Pi Pico running TinyUSB-based portal firmware (e.g., the open-source PicoWPortal project), an MFRC522 reader for the main figure area, a second NFC reader for the trap slot, addressable RGB LEDs, a white trap-slot LED, and a small speaker + amp — all in a custom 3D-printed/fabricated housing. Deliverables: A working, assembled portal in a custom housing with all five features above functioning in-game. Proof it works — a short video showing a real figure and a trap being placed and recognized in Trap Team running in Cemu on Windows, plus the LEDs and speaker responding. A brief written note of the firmware/version used and how to re-flash it, so I can maintain it myself. What I'll provide: My real Skylanders figures/traps for testing (or I can dump and send the data — your call). My broken original portal as a layout/feel reference (photos or shipped). A detailed technical reference document (firmware, wiring, protocol, part numbers). Two things to be aware of before you bid (please address these in your proposal): The trap slot (second reader) and the speaker (USB audio passthrough) may require extending the firmware beyond a stock flash. Tell me whether you'll use existing firmware that supports these or whether you'll be writing/extending code, and price accordingly. The multi-figure read area needs a larger or custom-tuned 13.56 MHz antenna (a stock MFRC522 antenna only reads one small spot). Tell me how you'll handle reliable reads across the surface. Logistics: Tell me if you work remotely (I ship parts/figures) or are local to South Florida (Homestead/Miami). Please quote parts cost, labor, and turnaround separately. MILESTONES: Design sign-off — parts list, wiring plan, housing concept, and confirmation of trap-slot + audio approach. (small upfront %) Working electronics (no housing) — Pico enumerates as 1430:0150, main reader + trap reader recognized in Cemu, LEDs and speaker responding on the bench. (largest %) Final assembly + housing — everything integrated in the custom enclosure, acceptance test passed, proof video + re-flash notes delivered. (final %) Acceptance criteria With Trap Team running in Cemu on Windows: a real figure on the main surface appears in-game; a trap in the trap slot is recognized; portal RGB LEDs respond to in-game color/fades; the trap-slot LED lights when expected; the speaker produces in-game audio. Proof captured on video. I have conducted research and sourced the firmware and software needed. Just need someone to source and assemble the hardware.

We have three businesses — Tallow (a tallow skincare brand), The Lady May (a Southern food and hospitality brand), and Glory Bound (a Mediterranean restaurant). All three of our Facebook Pages, Instagram accounts, and ad accounts are currently tied to our founder’s personal Facebook account. This is causing major operational issues — team members are constantly locked out, two-factor codes route to one person, reporting is mixed across brands, and we have no clean separation between businesses. We need an expert to migrate everything into one properly structured Meta Business Manager owned by a company email address. The full scope of work includes: • Create one central Meta Business Manager under a company email we will provide • Claim and transfer all three Facebook Pages (Tallow, The Lady May, Glory Bound) from the personal account into the Business Manager • Connect all three Instagram accounts to their corresponding Facebook Pages inside Business Manager • Set up three separate ad accounts inside Business Manager — one per brand — for clean, independent reporting and billing • Transfer or set up a Meta Pixel for each brand, properly connected to its respective ad account and owned by the Business Manager • Add our team members with the correct permission levels (Admin, Advertiser, Editor) so everyone can log in independently using their own Facebook accounts — no shared passwords • Verify everything is fully functional before the job is closed Important: This must be done without asking for anyone’s personal Facebook password. All access should be handled through standard Meta permission requests and partner access. We also have active ads running and cannot afford to lose ad history, pixel data, or audiences during the migration.

## About the project We are building a private, members-only virtual platform designed as an elegant residence — a "house" whose interior rooms members visit and move through on web and mobile. The aesthetic is warm luxury residential: golden hour light, rich natural materials, deep greens and warm neutrals, the feeling of a beautiful private home in the early evening. Think quiet wealth and warmth — never clinical, never corporate, never game-like. This is not flat illustration work. Each room must be painted as a **layered environment scene built for parallax and camera movement** — our developer will assemble your layers into scenes that subtly shift, drift, and transition as members move through the house. ## Scope — Phase 1 (5 scenes) - The entry hallway (the anchor scene — this one sets the visual DNA for everything) - Four interior rooms, each with its own character and function Additional rooms (9 more) will follow for the right artist, making this a substantial ongoing relationship — Phase 1 is how we choose that artist. ## What you'll receive from us - A complete art direction bible: palette (hex codes), typography, lighting direction, mood, and a page per room describing its function, furniture, and emotional temperature - Concept reference images for each room conveying composition and atmosphere - Direct feedback from the founder — the vision holder — at sketch, color, and final stages ## Technical deliverables (per scene) - Full scene painted in **separated layers** (background, midground elements, foreground framing, light effects), delivered as layered source files (PSD or equivalent) with clean alpha/transparency per layer — typically 5–8 layers per scene - Backgrounds and mid layers painted **beyond the visible frame** (bleed on all sides) so edges never show during camera drift - **Door states** for each doorway: closed, ajar, and open (doors are our transitions between rooms) - Web-optimized exports (PNG per layer) at resolution suitable for desktop and mobile - Source files included; full rights transfer on payment ## Required experience — please only apply if this describes you - You have shipped **layered environment/background art for interactive use**: visual novels, point-and-click adventure games, animated explainers, parallax web experiences, or 2.5D game environments - Your portfolio shows **painted interiors with atmospheric lighting** — warmth, light pools, believable materials - You understand painting for parallax: layer separation, bleed, and how a scene reads when the camera moves ## Style keywords Warm luxury residential interiors · golden hour · painterly realism or refined stylization (no cartoon, no anime, no vector-flat) · rich wood, velvet, brass, linen · quiet, unhurried, inviting ## Process and terms - **Paid test scene first:** we begin with the hallway as a standalone paid milestone. If the collaboration works, you're awarded the remaining Phase 1 rooms, with Phase 2 (9 rooms) to follow. - NDA required before receiving the full art direction bible (the platform is pre-launch). - Please include in your proposal: (1) 2–3 portfolio pieces showing layered environment work — links to the specific pieces, not just your profile, (2) a one-line description of how you'd technically structure the hallway's layers, and (3) your per-scene rate and turnaround time. Applications that don't address item (2) will not be considered — it's how we know you read this.

About ZeremAI ZeremAI is a premier AI and Automation implementation consultancy that future-proofs businesses. We specialize in cutting-edge AI agents, intelligent systems automation, and real-time AI-assisted KPI dashboards across all business departments. Our "Align–Automate–Achieve" methodology bridges the gap between technology and measurable impact, helping teams reclaim up to five days of productivity weekly per employee, allowing organizations to focus on their core mission. Position Overview: We are looking for an AI Technical Account Manager who thrives at the intersection of systems architecture and client partnership. This role is for a high-presence communicator who takes pride and care about Customer Success and can translate complex AI and automation workflows into clear, actionable business wins and communicate them with the AI Development team. You are an AI Technical Account Manager at heart—someone who possesses the technical depth to design sophisticated systems but whose real superpower is leading the client relationship. You’ll be the face of our delivery team, ensuring our clients don't just get a tool, but a transformed business process they actually enjoy using. Key Performance Indicators (Success Metrics): -100% successful deployment rate of AI and automation solutions. -Ensure systems adoption success scores reach 95%+ -Increase customer productivity by 20% to 100%+ through AI automation. -Increase customer KPI achievement rate by 2x through intelligent dashboards. -Maintain 97% or higher customer satisfaction rating for solution delivery. Core Client Responsibilities: Strategic Client Leadership: - Relationship Management: Act as the primary technical point of contact, managing expectations and leading clients through the "Align–Automate–Achieve" journey with confidence. - High-Impact Communication: Lead discovery calls and project updates with clarity and brevity. You are the concise expert—getting to the point quickly and making complex concepts clear and simple to non-technical customers. - Client Success Orientation: Prioritize the "human" side of the implementation, ensuring the solution solves the client’s actual pain points rather than just being technically correct. Solution Architecture & Discovery: - Workflow Mapping: Conduct process audits to identify gaps and translate messy business problems into clean system requirements. - High-Level Design: Architect automation ecosystems using Make, Zapier, Airtable, HubSpot, and other systems, ensuring all pieces of the tech stack talk to each other seamlessly. - AI Integration: Leverage LLMs (OpenAI, Claude, etc.) to enhance productivity and build smarter business logic for clients. Delivery & Adoption: - Implementation Oversight: Work with the internal dev team to ensure the blueprints you designed are built to spec and delivered on time. - The Final 10%: Lead the hands-on training and documentation phase, ensuring the client’s team feels empowered and capable, not overwhelmed. - Iterative Optimization: Monitor performance post-launch and proactively suggest enhancements to deepen the client relationship. Key ZeremAI Operations Responsibilities: - Collaborate with the Chief AI Officer and Strategy Officer to evolve ZeremAI’s systems playbook. - Lead the evaluation and adoption of new AI technologies and platforms. - Ensure solution designs align with the Align–Automate–Achieve methodology. - Create internal system frameworks, templates, and automation best practices. - Mentor and collaborate with AI Systems Developers to maintain high-quality standards. - Analyze reporting on architecture performance, ROI metrics, and adoption rates. The Ideal Profile: Technical Fluency (The "How It Works" Knowledge): - Systems Thinker: You understand the Big Picture of how APIs, CRMs, and databases interact. You don’t need to be the world’s fastest coder, but you must be a world-class architect. - Automation Stack: Deep familiarity with CRM, Project Management, Integration, and AI tools. - AI Expert: A solid grasp of how to practically apply AI/LLMs to business workflows. The Superpowers (Client & Communication): - Professional Presence: You carry yourself with a demeanor that builds immediate trust. You are concise, articulate, and mindful of the client’s time. - Concise Communicator: You avoid the Solution Architect Trap of over-explaining. You know how to give a "Yes/No" or a "Bottom Line Up Front" (BLUF). - Leadership: You can guide, educate, and—when necessary—firmly pivot a client toward a better strategic path. Qualifications: Required Skills & Experience - 5+ years of experience in systems consulting, operations, business automation, or a similar role. - 2+ years of AI expertise in a business context - Strong hands-on experience with automation tools (JSON, Zapier, Make, Airtable, etc.) and system integrations. - Working knowledge of project management and CRM platforms (e.g., Monday.com, HubSpot, Salesforce). - Familiarity with API usage, data flows, and basic scripting or logic-based automation. - Excellent problem-solving and process-mapping skills. - Clear written and verbal communication, especially with non-technical stakeholders. - Strong client-facing presence with the ability to guide, educate, and influence clients. Preferred Qualifications: - Experience in a fast-paced startup or agency environment. - Exposure to AI tools and understanding of their application in business settings. - Technical certifications in automation platforms (Zapier Expert, Make Partner, etc.). - Understanding of business functions like marketing, sales, operations, and finance. Soft Skills: - Demonstrate creativity in problem-solving by identifying innovative solutions to client challenges and operational obstacles. - Systems thinker with a knack for breaking down complex problems. - Highly organized, self-motivated, and able to manage multiple client projects simultaneously. - Collaborative team player who thrives in a remote-first work environment. - Passionate about technology, continuous improvement, and client success.

We run a marketing agency, and we need a senior Klaviyo person to take over the cleanup of one client's account and own it through to fixed. Here's the situation. The client is an established ecommerce brand with a list of around 350,000 contacts. Earlier this year they moved off Listrak onto Klaviyo. Since the migration, orders attributed to email have dropped from roughly 1,500–2,000 per month to about 500. We've already run a full audit against the live account, so we know most of what's wrong. We need someone to confirm it, fix it, and talk about it confidently with a sharp technical contact on the client's side. The hard part is the website. The client's site is custom-coded, not Shopify or WooCommerce. The Placed Order event feeds Klaviyo through a custom API integration, and we believe it's double-firing (one transactional flow shows about 4,700 conversions from only 254 buyers). You need to be comfortable reading how events post through an API, spotting duplication, and telling the client's developer exactly what to change. This is not a template-design gig. What you'll do: 1. Work with the client's developer to validate the Placed Order API payload: one event per order, a unique event ID, no per-line-item or status-change duplication. 2. Fix attribution. Exclude or relabel transactional flows (order, shipping, delivery confirmations) so they stop inflating revenue, set proper conversion windows, and reconcile Klaviyo-attributed revenue against UTM/GA4 revenue. 3. Clean up the flow architecture. Remove a duplicate Welcome Series, de-conflict overlapping "Added to List" flows, and rebuild thin cart flows (abandoned checkout and add-to-cart) with the right exclusions between them. 4. Turn on and standardize UTM tracking across every flow and campaign email. 5. Set a warming and deliverability plan for the 350k list: engaged-segment sending, sender-reputation rebuild, and a clear rule for when full-list sends are safe. 6. Hand us a point-by-point issue log we can take into a Klaviyo support call. Please answer in your proposal: How do you tell real incremental email revenue from inflated transactional-flow attribution in Klaviyo? What do you turn off or relabel?

Developer needed to launch a family organizer app (backend + accounts) Short version I’ve already built a working prototype of a family management app. It looks and behaves the way I want. What it can’t do yet is the “behind the scenes” part: save information in one shared place so every family member sees the same thing on their own phone, let each person log in, and send reminder notifications. I need a developer to build that part and get the app live so my family can actually use it on our phones. One thing that matters a lot to me, please read carefully: after you finish, I need to be able to keep changing and improving the app myself, working with an AI assistant — without having to hire or contact anyone again. So everything you build has to be handed over to me completely, written cleanly and simply, and explained well enough that an AI assistant can understand it and help me make future edits. No locked-down systems, no “only I can touch this” setups, no surprise dependencies. I own all of it. What the app is It’s a private organizer for my household (two parents, six kids). It has five sections: • Today — a daily summary for each person (their schedule, their tasks, family meal/afternoon plans). • Schedule — a weekly calendar: who’s driving which kid to which school, each parent’s work day and hours, kids’ activities, meal and afternoon plans. • Chores — daily and weekly tasks you can assign to specific people, and check off when done. • Lists — grocery and supply lists. • Tonight — an evening summary of chores that still aren’t finished. The look, layout, colors, and how everything behaves are already done. I’m not asking you to design anything. I’m asking you to make it real and shared. What I need you to build 1. One shared place to store our information (the part it’s missing most). Right now, anything I type only saves on the device I typed it on. My wife’s phone and the kids’ devices don’t see it. I need all our information kept in one shared online location so that when anyone makes a change, everyone else’s device updates too, within a few seconds. 2. A login for each family member. Simple and family-friendly: you open the app, tap your name from a list, and type a PIN. Once you’ve logged in on your own phone, it should keep you logged in so you don’t have to do it every time. Every person — both parents and all six kids — gets their own login. Parents can edit everything; kids mainly see their own stuff and check off their own chores. The app already has a built-in “who’s using this” concept; your login system just needs to drive it for real. 3. Notifications to people’s phones. • Every morning, each person gets a notification with their summary for the day. • Every evening at 8:00 PM, each person gets a reminder of any chores they haven’t finished that day. The app already knows exactly what each of those messages should say — I just need them actually delivered to phones on schedule. 4. Shared photo proof for kids’ chores. When a kid marks a chore done, the app already makes them take a photo as proof. Right now that photo is stuck on the kid’s device. I need those photos saved in our shared location so my wife and I can see them from our own phones. What “done” looks like • My family can install or open the app on our phones and each log in with our name and PIN. • A change one person makes shows up on everyone else’s device. • Morning summaries and 8:00 PM chore reminders arrive as phone notifications. • Kids’ chore photos are visible to the parents on their own devices. • It runs reliably without me needing to babysit it. Very important: I need to be able to maintain it myself afterward I work on this app with an AI assistant, and I plan to keep improving it that way for a long time. So I’m asking that you: • Hand over everything — all the code, all the accounts and passwords, all the settings — in my name, owned by me. Nothing stays under your account. • Write it cleanly and simply. Please don’t over-complicate it or add tools and layers that aren’t truly needed. The simpler and more standard it is, the easier it is for me and an AI assistant to understand and change later. • Comment and document it in plain terms: what each part does, where things live, and how to make common changes (like adding a person, changing a notification time, or adjusting a list). • Write a short “how it works” guide for a non-developer — how to find things, how to change them safely, and how to undo a mistake. • Avoid lock-in. Use widely used, well-known building blocks (the kind an AI assistant will already understand), not anything obscure or proprietary that only you would know how to maintain. • Do a handoff call or video walking me through it so I’m comfortable taking it from there. If anything about how it’s built would make it hard for me to edit later on my own, please tell me up front. To apply, please tell me • A short note, in plain English, on how you’d approach this — especially how you’ll keep it simple and easy for me to maintain myself afterward. • Whether you’d build it so it works on iPhones and Android (and whether that’s a website-style app or an installable app — explain the trade-offs simply). • A rough estimate of cost and timeline. • One or two examples of similar things you’ve built. A few notes • This is a private app for my family only — not something I’m selling. It doesn’t need to handle thousands of users, just the eight of us. • Privacy matters: it includes my kids’ photos and our daily whereabouts, so it needs to be kept private and secure. • I already have the full working front end (the part you see and tap). I’ll share it with the right person. You’re building the engine behind it and getting it onto our phones.

WordPress Website Redesign – Boutique Finance Recruiting Firm (Astra + Elementor Pro) We are Hire Point Recruiting, a boutique Accounting & Finance recruiting firm based in Sparta, NJ serving the NY/NJ market. We’ve been in business for 15+ years and have grown significantly — our website needs to better reflect where we are today as a firm. We already have a clear vision, homepage concepts, sitemap direction, branding direction, and content structure prepared. This is not a “blank slate” project — the direction is decided. We’re looking for someone who can execute it cleanly and professionally. Current Setup WordPress website Astra theme Currently using Beaver Builder (open to transitioning to Elementor Pro) Domain and hosting already owned Existing live website: hirepointrecruiting.com Scope of Work Redesign homepage to align closely with approved reference direction (shared upon engagement) Redesign 4–5 inner pages: For Employers For Candidates About Us Contact One Discipline/Industry page template Create reusable templates for future service, discipline, and industry pages Set up global styles: fonts colors buttons spacing Build modern navigation / dropdown structure Ensure site is polished and fully responsive across desktop, tablet, and mobile All work completed in a staging environment first — no edits made directly to the live site Migrate completed site to WP Engine upon approval Provide short Loom walkthrough video after launch showing us how to make basic edits internally What We Are NOT Looking For Full custom-coded rebuild Complex backend development Custom plugin development SEO services or copywriting (already handled) A full rebranding project We are looking for practical execution within the existing WordPress ecosystem. Ideal Candidate Strong portfolio of clean, modern WordPress websites Experience with professional services, recruiting, finance, staffing, advisory, or B2B websites preferred Proven experience with Astra + Elementor Pro Strong eye for spacing, typography, and polished modern design Comfortable working within staging environments Clear communicator who hits deadlines Experienced enough that this project feels straightforward to execute Budget $3,000–$4,500 fixed price (Open to milestone-based payments) Timeline Target launch within approximately 5–6 weeks Location Remote is fine — NY/NJ based is a plus but not required To Apply — Please Include 2–3 live portfolio examples of similar professional services or B2B websites you’ve built Brief overview of how you would approach the project (staging, process, timeline, handoff) Your fixed-price quote for this scope ⚠️ Applications without relevant portfolio examples will not be considered. We are serious about this project and looking for someone equally professional and detail-oriented.