Build AI Email Automation MVP “BCcGuardDog”

Job Title: Low-Code/Backend Developer: Asynchronous AI Email Automation (Make.com + Node.js/APIs) Project Overview: I am looking for a talented automation and backend developer to build a lightweight MVP for an asynchronous, email-first administrative tool. Crucially, this system has no web portal, app dashboard, or frontend user interface. It operates 100% via email forwarding, BCC, and automated asynchronous workflows. The user interface is strictly the inbox. Our Core Tech Stack: * Workflow/Orchestration: Make.com (or lightweight custom backend where appropriate) * Email Routing & Parsing: Postmark or SendGrid (Inbound webhooks handling attachments) * AI Brain: OpenAI or Anthropic API (Factual extraction & classification, temperature 0.2) * Database & Billing: Stripe API + a lightweight database layer (PostgreSQL or secure Airtable base) The 3 Core Asynchronous Workflows Required: 1. Inbound Document Parsing: A webhook that catches forwarded emails, identifies user context, securely extracts text from an attached file (PDF/DOCX), passes it to an AI engine for analysis, and replies back to the user with a formatted report. 2. Contextual Email Comparison: A webhook that listens to BCC'ed email chains, retrieves historical project context from a database, uses AI to analyze if the new email conflicts with old parameters, and drafts an auto-generated reply script for the user. 3. Transactional Billing Automation: An inbound email listener that extracts key metadata (client details, amounts, line items), automatically triggers an invoice via the Stripe API, tracks payment status via webhooks, and manages an automated reminder drip sequence. Supporting System: * Referral Engine: A backend logic loop tracking successful attribution via Stripe checkout fields. Hitting specific milestones triggers automated Stripe API coupon updates on the user's active subscription tier. Screening Questions: 1. How do you plan to handle the inbound email attachments for the Document Parsing workflow? 2. Since this system doesn’t use a visual dashboard, how would you handle Stripe webhook failures securely if an active user’s email payment declines? 3. How would you structure the database logic to store historical project context so that the AI can quickly compare it against new incoming emails? 4. Have you built asynchronous, email-driven automation systems using Make.com or Node.js before? Please link to or describe one specific project. How to Apply: Please briefly detail your specific experience with Make.com, parsing inbound emails/attachments, and working with Stripe webhooks/customer APIs. Full context and branding materials will be shared under NDA during the interview stage. Budget: USD 250–750