Before you apply read this first.: This is not a standard contract. We are not looking for someone to build something and disappear. We are looking for a developer who genuinely cares about people experiencing homelessness and wants to be part of something that actually changes lives. If that is not you, this post is not for you. If it is keep reading. What Is Operation Iron Gate: Operation Iron Gate is a physical intake hub in Vallejo, California built specifically for the unsheltered. Any homeless person can walk through our door and receive help no matter what barriers they are carrying, no matter what their documentation looks like, no matter how many times they have been turned away before. The rule is simple: nobody gets denied. We call it Yes by Default. Instead of looking for reasons to say no, we look for the next valid move. Every single time.When someone walks in, a case gets opened immediately. Every barrier they are facing gets documented. A next step gets started before they leave the building. And the system tracks every single movement of that case every action, every referral, every handoff until they actually receive the resource they need. Not a phone number on a piece of paper. The actual resource. It sounds too good to be true. That is exactly why we built the technology to make it real. What You Are Building — Phase 1 Only: We are currently hiring for Phase 1 only. This is the core platform build. We are keeping it focused. Once the pilot launches in Vallejo and the system is proven in the real world, we will move into the AI layer and long-term development. But right now we need Phase 1 built right. The platform is called DSAS the Digital Steward Authorization System. It is the brain of Operation Iron Gate. Here is what Phase 1 covers: * Case creation engine when someone walks through the door, a case opens immediately. One screen, one submit. * Barrier capture system every barrier the person is facing gets documented and connected to a next action. * Yes by Default enforcement a denial without a legal reason code is blocked by the system itself at the database level. * Three-tier triage system urgent cases get a 2-hour movement deadline with auto-calculated countdown. * Steward escalation queue hard cases route instantly to senior reviewers who make binding decisions. * MDO Live View: real-time monitoring screen showing every active case, who owns it, where it is stuck, how long it has been sitting. * Automated alert engine fires when a case stalls, when a deadline is missed, when a partner does not respond. * Glass Dashboard public-facing transparency layer showing the community how the system is performing in real time. * All data feeds automatically from the system. No manual entry ever. * IGAC credential system when someone arrives without ID, a credential is issued immediately on Day 1 so the case can keep moving. * 7-role permission matrix enforced at the API level on every endpoint. * Append-only audit trail tamper-evidence logging. Nothing gets deleted or edited after it is written.. The full technical specification is already built: * Every database field is named. * Every logic rule is written. * Every automated alert is defined. * Every role permission is mapped. You are not figuring out what to build. You are building something that is completely designed and ready to be coded. Technical Requirements Required: * Strong backend / full-stack development 3+ years building complex platforms * Relational database expertise PostgreSQL or MySQL complex logic enforced at the database level * Role-based access control enforced at the API level * Automated alert engines time-based and condition-based triggers * Append-only audit logging with tamper evidence * Real-time data feeds * REST API development Strongly preferred: React or similar framework for front-end interfaces. Mobile-responsive design Access Points may operate from tablets and phones. Civic tech, social services, healthcare, or government platform experience. We are open to your stack recommendation. Tell us what you would use and why. Who We Are Looking For: We need someone who is technically strong. But more than that we need someone who reads about Operation Iron Gate and feels something. Someone who understands that every field in this database is a real person's life. Someone who will flag a problem in the spec before building it wrong. Someone who stays when things get hard. Someone who wants to be part of this mission not just compensated for it. If you are only here for the money, this is not the right fit. If you want to build something that matters we want to talk to you. Compensation: Read This Carefully: This is a fixed-price contract via Upwork with milestone-based payments. Here is exactly how it works and why we structured it this way. We are paying in four milestones. Every single payment is tied to something real being delivered and confirmed not just promised. * 25% on project start you have skin in the game from day one and so do we. * 25% when the database and core logic is confirmed complete confirmed by the developer handoff checklist, not by your word alone. * 25% when the full intake flow and MDO Live View is confirmed complete again, confirmed by the checklist. * 25% at final sign-off when every single item on every Tier 1 handoff checklist is confirmed complete Nobody gets paid until something real is delivered and confirmed. The checklist is the protection for both of us. You cannot say something is done and collect payment if the checklist says otherwise. That is not a lack of trust that is how professional projects get built correctly. There is one more thing we need in this contract and we want to be upfront about it. The contract will include a scope change clause. That means if we ask you to build something that was not in the original specification something we did not think of, something new that becomes a change order and gets priced separately. It does not get quietly absorbed into the fixed price and it does not become a source of resentment on either side. You build what is specified. Anything beyond that gets negotiated openly and fairly. Fixed rate. Milestone payments. Handoff checklist as the payment trigger. Scope change clause in the contract. That is how we protect Pathfinders for Hope's mission funding and make sure you get treated fairly too. Additional terms: * NDA required before any specifications are shared * Work-for-Hire Agreement required before development begins all code belongs to Pathfinders for Hope * Rate is negotiable based on experience To Apply: Submit your proposal with your answers to all eight questions, a description of your most relevant project, your recommended stack, your honest Phase 1 timeline estimate, and your rate. We are building the operating system that proves homelessness can be solved one city at a time. If that is the kind of work you have been waiting for, we want to hear from you.

We’re hiring an extraordinary developer to own and grow our Base44 apps and sales products. around the future of AI discovery 1. Future of AI Discovery Core Demo – https://pull-discovery-core.base44.app/ You’ll evolve https://pull-discovery-core.base44.app/ into a beautiful, fluid, high‑performance, full-functional future of AI discovery demo following our advanced and sophisticated technical blueprint Integrate and orchestrate AI models incorporating LLM's, Search and World Models into a seamless experience with no visible seams between UX and intelligence. Own front‑end performance, responsiveness, and micro‑interactions—animations, transitions, and state changes should feel intentional and “alive,” not bolted on. Implement robust logging and analytics to understand how users explore, where they get stuck, and how the discovery engine can adapt dynamically. 2. Book Sales Engine – Six‑Channel Publishing System The second current Base44 project is a system that operationalizes our comprehensive sales plan across six channels. SEE THE COMPREHENSIVE BOOKSALES PLAN ATTACHMENT UNDERNEATH THIS POSTING You will: Translate a detailed multi‑channel publishing strategy (KDP optimization, physical bookstores via IngramSpark, other digital platforms, libraries, bulk institutional sales, and authority‑engine content marketing) into concrete workflows, tools, and dashboards. Build internal interfaces and automations to: Track metadata, pricing, and promotions across Amazon KDP and other platforms. Monitor campaigns across TikTok, Meta, LinkedIn, YouTube, newsletters, and partnerships. Surface KPIs like BSR, review velocity, ad spend, email growth, library adoptions, and bulk orders in a single, coherent view. Design light internal UIs that make it easy for non‑technical team members to update copy, add titles, trigger campaigns, and view performance without breaking anything. Implement robust, testable integrations between Base44, external APIs, and data sources to keep everything in sync as we scale from 8 to 22+ titles and beyond. Who You Are We’re not looking for a generic “full‑stack dev.” We’re looking for an unusual combination of visionary and doer: Creative technologist mindset – You think in systems and interfaces at the same time. You care deeply about how a product feels as well as how it works. Obsessed with execution – You’re disciplined, structured, and relentless about shipping. You break ambiguity into sprints, reduce complexity into tickets, and never let projects stall. Proactive owner – You don’t wait for instructions. You propose better ways to do things, flag risks early, and bring options—not problems—to every conversation. Strong product sense – You can balance ideal UX with realistic constraints and understand when to ship v1 vs. when to invest in polish. Comfortable with complexity – Multi‑channel distribution, layered data flows, and evolving requirements don’t scare you; they energize you. Ideal Skills & Experience You don’t need all of these, but you should recognize yourself in most: 5+ years building production web applications, ideally with a strong front‑end/UI focus. Deep experience with modern web stacks (React/Vue/Svelte or similar) and TypeScript, plus comfort with Node or comparable back‑end runtimes. Strong visual/UI instincts: experience collaborating with designers or owning design yourself for data‑rich interfaces and dashboards. Experience integrating AI/LLM APIs and retrieval systems into real products (RAG flows, multi‑step tool use, chat‑like interfaces, recommendation engines). Experience with analytics and experimentation: event tracking, funnel analysis, A/B testing. Familiarity with publishing, ecommerce, or multi‑channel marketing systems is a plus (KDP, IngramSpark, email platforms, ad platforms, analytics). Prior work in environments like Base44 or other low‑code/agentic platforms is a strong plus, but not required if you learn fast.

I need an expert senior software engineer that can provide consulting services around implementation best practices of LLM's and AI into existing application workflows. i.e. leveraging AI to extract data from a document as part of an ingestion pipeline.

This project is a continuation of the existing SMOX audit and production readiness review currently in progress. The objective is to continue working with the current auditor and transition from audit findings into implementation planning and execution. Current priorities include: • Review completed audit findings • Verify repository structure and production readiness • Implement 30-Day Smox Pro Trial functionality • Review Stripe Connect subscription management • Review Stripe webhook handling and payment events • Resolve subscription and payment-related issues • Correct booking timeline and client visibility issues • Resolve calendar history and scrolling issues • Improve notification reliability • Address production-impacting defects identified during the audit • Establish a milestone-based implementation roadmap Existing repositories, AWS access, Stripe access, audit documentation, and project assets will be provided as needed. This is not a new application build. The project already exists and is currently deployed. The goal is to continue the audit engagement and execute the highest-priority production readiness improvements identified during the review process.

We are looking to do a new build of our patch bay label designer tool. Customers are currently able to pick their model of patch bay, add text labels, colorize, and group. They can then checkout and it creates print ready artwork for our team to produce. The UI is a bit clunky and there are some features we want to add such as an admin tool to add and edit labels. You can see the current tool here: https://create.traceaudio.com/

Forum Intelligence: Project Brief & Initial Rollout 1. Executive Summary & Objective Forum Intelligence is a beginning as a localized data retrieval, processing, and archiving system designed to scrape public municipal records and state legislative data for public oversight. The immediate objective is to build a functional, highly resilient prototype focused on the Tri-Cities region (Burbank, Glendale, and Pasadena, California). The system will autonomously ingest messy, unstructured municipal data (City Council meeting minutes, agendas, public notices, and legislative PDF text, recorded mp4), clean it, and make it fully searchable and queryable via a localized AI agentic framework. 2. Phase 1 Scope: The Tri-Cities Rollout Th engineer will be responsible for building two primary pillars: A. Resilient Scraper Bots • Target Ingestion: Monitor and pull data from Burbank, Glendale, and Pasadena municipal portals and California legislative feeds. • Data Types: Brittle HTML sites, heavily nested tables, public notices, legislative drafts, and massive unstructured PDF archives. • Requirements: The scraping architecture must be exceptionally robust, utilizing intelligent error handling, retry semantics, and pagination tracking to handle frequent municipal website layout changes without breaking the pipeline. B. Ingestion & Vector Pipeline • Parsing: Extracting clean text from poorly formatted documents and scanned PDFs. • Local RAG (Retrieval-Augmented Generation): Chunking and embedding the data locally into a vector database (e.g., pgvector, Chroma, or Milvus) to enable semantically accurate entity linking and contextual search. 3. Targeted Hardware Stack To ensure maximum data security, strict public oversight integrity, and predictable operational costs, Forum Intelligence is skipping commercial cloud APIs in favor of an on-premise, localized NVIDIA enterprise deployment. The production roadmap aligns precisely with the new computing patterns detailed in NVIDIA’s latest hardware roadmap: • Inference & Token Generation: Running local open-weight frontier models (e.g., Neotron 3 Ultra or Claude/Llama equivalents) optimized for reasoning and long-context tool use. • Compute & Orchestration: The backend infrastructure is architected around NVIDIA’s dedicated agentic architecture, utilizing high-instructions-per-clock (IPC) Vera CPUs paired with Vera Rubin GPUs. • Memory & Storage Processing: Utilizing NVIDIA’s unified memory fabric and data processing units (DPUs) for ultra-low latency context management, KV caching, and fast vector database retrieval. 4. Immediate Milestones for the Engineer 1. Architecture Design: Map out the database schema and local inference ingestion loop. 2. Tri-Cities Scraper Deployment: Write and deploy the initial automated bots for Burbank, Glendale, and Pasadena. 3. Local MVP Pipeline: Demonstrate a local RAG pipeline where a user can query the Tri-Cities scraped records and receive grounded answers with exact source attributions. The above was AI generated from months long conversations with Gemini. The goal is to prove the concept then roll out to LA County, state of CA, and then the country.

We are looking for an expert backend developer and automation engineer to extend an existing, production-grade Model Context Protocol (MCP) server and overhaul its orchestration layer. The headline correction for this project: the existing Lawfather MCP is to be retained and extended, not rebuilt. It already exposes deterministic, parameterized Playwright tools for every required county portal (District Clerk, HCSO, HCDAO) and a client database. Those backend tools are the reliable layer and are not the source of the instability this project exists to fix. The instability lives entirely in the orchestration layer — the model-driven layer that decides when and how to call the tools. The fix is to move deterministic control out of model-followed prose and into code, and to host the agent on an always-on machine with persistent memory. Core Project Principles • Extend, Don't Rebuild: Retain and extend the existing MCP; do not re-implement portal scrapers from scratch. • Code Over Prompts: Deterministic logic lives strictly in tool code, never in instructions the model must remember each session. • No Caller Loops: Batch operations must run to completion server-side. No operation may require the caller (model) to loop. • Agnostic Architecture: The system must remain model-agnostic and host-agnostic. No single provider — Anthropic, OpenAI, Z.ai/GLM, or Nous — may be a hard dependency. • Privilege First: Client data stays on owned hardware; the model is never the gatekeeper of which case a file belongs to. Existing Tool Inventory (To Be Inherited As-Is) The following tools already exist on the production MCP (containerized on a local Synology NAS) and are in daily use. Re-deriving their behavior is completely out of scope: • hcdc_get_docket: Court settings by date range + bar number (District Clerk). • hcdc_check_filings: Per case: standard defense filings present vs. missing. • hcdc_download_filings: Images-tab documents: bulk OR selective by filters; dest_subfolder; dry_run. Note: The parameterized download tools already cover most retrieval requests. "All filings," "this filing," "all subpoenas," "all resets," and "everything filed that day" are argument combinations on this tool, not separate features. • hcso_locate: Defendant custody location (facility / floor / pod) by SPN. • hcdao_grab_file: Download a single named file from the DA portal Files tab. • hcdao_download_discovery: Batch / delta discovery download from the DA portal. • hcdao_download_media_alert: Batch-download files listed in a 'New Media Available' portal email. • hcdao_case_summary: Scrape the Case Jacket quick summary / DAO narrative. • hcdao_plea_offer: Scrape current plea offer + full offer history. • hcdao_assigned_ada: Assigned ADA name / email / phone on a case. • lookup_client / list_clients: Resolve / list clients from the shared client database. Scoped Work (Paid Deliverables) 1. County Case Resolver (New Tool): Find a case from partial identifiers — any subset of (name, SPN, DOB, court, cause). Searches county systems (not just the local client DB). MUST return a ranked candidate list for the user to choose from; MUST NEVER auto-select. Wrong-defendant selection is a privilege failure, not a cosmetic bug. 2. Latest-Version Retrieval: Add scope=latest to hcdao_grab_file so 'most recent' selects the newest among supplements instead of the first match. 3. Async Transcribe Tool (Skill to Tool Promotion): Build a deterministic MCP tool using Gemini 3.1 Pro Preview for transcription, followed by a second pass that sends the transcript back with case context for cleanup (speaker mapping, defense-moment preamble). Long-running: implement as an async job (submit to job id to poll to fetch), NOT a synchronous call. 4. OCR Tool (Skill to Tool Promotion): Implement a readability check on ingest. If a document is not cleanly readable, FLAG it and ASK before sending to Gemini 3.1 Pro Preview for OCR. OCR must be gated and confirmed, never automatic. 5. Server-Side Batch Jobs: Move all chunk, loop, delta, and throttle logic OFF the caller and INTO the tool code. One call runs the batch to completion. 6. Queued HCDAO Fixes: For hcdao_download_discovery, add a portal_ids filter for targeted single-file pulls and a custom output-path / Drive-folder destination feature. Known Portal Quirks to Handle from Day One • hcdc_get_docket returns a broader date range than requested; results must be filtered to the requested window. • hcdao_download_discovery delta detection is blind to files organized into dated subfolders and must be explicitly handled. • Court DG7 does not surface through standard bar-number docket lookup and requires separate handling. • The Playwright Node.js driver subprocess can die silently while database tools respond; you must health-check the driver proactively. Orchestration, Host Layer, & Deployment Topology • Target Host: Hermes Agent (Nous Research) running as the persistent shell, providing persistent memory, the scheduler, and messaging surfaces. The MCP server will plug directly into it. • Agnostic LLM Routing: Default the agent/dispatch role to the most reliable tool-calling model (currently Claude Opus). Route bulk, non-critical generations (draft summaries, transcript cleanup) to a cheaper model (e.g., GLM-5.2). No provider may be hard-wired. Per-tool pins are allowed strictly for transcription/OCR tasks (pinned to Gemini 3.1 Pro Preview). • Memory Fencing: Hermes's persistent memory and learning loops must remain enabled to accumulate facts and user preferences. However, the agent must be strictly fenced from self-editing or rewriting its own mechanical execution paths (portals, downloads, filings), which must remain frozen in MCP tool code. • Hardware Deployment Infrastructure: • Always-on Brain: M1 Pro MacBook Pro (16 GB, mains-powered, lid open) running the Hermes gateway, Messages.app, and a BlueBubbles iMessage bridge. Must be fully automated via launchd services to handle headless crash recovery, auto-login, and sleep prevention (pmset autorestart / caffeinate). • Tools and Storage: Synology NAS (10.0.0.149) hosting the Lawfather MCP container, local client folders, and Drive sync. • Private Network: Tailscale mesh across all devices for secure remote access without open inbound ports. Acceptance Criteria for Sign-Off • No batch operation requires the caller to iterate. • The case resolver returns ranked candidates and never auto-selects. • Transcription runs seamlessly as an async two-stage job surviving multi-hour files without timing out. • OCR never fires automatically on low-readability files without gated confirmation. • Zero regressions on the existing MCP tool inventory. • The Resiliency Test: The full stack successfully restarts completely unattended after a host reboot or simulated power loss, and is reachable via iMessage/SMS immediately after. • Self-editing is fenced on mechanical download/filing paths. Hard Guardrails • Privilege: Downloads route strictly to the correct client folder; a wrong-case match is treated as a severe defect, not a warning. Privileged audio/discovery data stays on owned hardware where the chosen model allows. • Determinism: Repeatable steps live entirely in tool code, never in prompts. • Agnosticism: Model and host layers must remain fully swappable without modifying the core MCP tools. Before quoting "done," you will be expected to confirm live portal behaviors regarding District Clerk document labels, DA portal stable identifiers, and county search surfaces. How to Apply Please submit a proposal detailing your specific experience with MCP architectures, Playwright browser automation, and macOS/Docker DevOps automation. Anti-Bot Filtering: To prove you read this entire scope, please start your application with the phrase "PROTECT THE LAW" in all caps. Automated or generic copy-paste applications will be instantly rejected.

Frontend: React Native (Expo SDK 54), TypeScript Backend: Firebase — Firestore, Cloud Functions (Node, v1), Firebase Auth, Firebase Storage Architecture: Multi-tenant data model (multiple client organizations sharing one Firestore database, isolated by security rules) Auth: Email/password via Firebase Auth, role-based access (general contractor / subcontractor roles) Firebase / React Native SaaS (Contract, with potential for ongoing work)

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.

Seeking an experienced tutor/consultant to guide in learning Azure, .NET, and Angular, microsoft sql server. Responsibilities include creating showing me how to do work, consulting during meetings sessions, and providing feedback. The ideal candidate will have strong communication skills and the ability to adapt to individual learning styles. Work schedule. Just need to be available 4-6 or more daily between hrs 8am est -6pm somewhere in between that time frame 4-6 hrs daily Attending meeting just to consult, teach me enough I can do work, and do tasks daily.