We are looking for 2-3 AI engineers/developers to help us build/complete an AI go-to-market (GTM) tool that looks at both structured and unstructured data, runs it all through our AI engine, and provides insights and recommendations straight to sales people. The tool is able to handle large volumes of data and provide actionable insights for business decision-making. Our engine consists of a prioritization algorithm, pattern matching and sentiment analysis. We use our recommendation engine to deliver the output (insights) straight to our tool which is "Apple-simple", intuitive and gamified. No more sales time wasted on looking at dashboards and trying to agree on which insights are important and which should be acted on. What you'll do Own features end-to-end across theFastAPI backend (IEngine) and Next.js 15 / React 19 frontend— from Claude prompt design to UI polish. Extend the intelligence pipeline: meeting ingestion (Google Drive + Deepgram realtime), Claude-driven action card generation, Neo4j relationship graph, and Supabase-backed state. Build customer-facing dashboard surfaces — deals, gamification, coaching, trust graph — with TypeScript, Tailwind, shadcn/ui, and D3. Operate WebSocket transcription sessions and async job pipelines reliably under real meeting load. Instrument with Sentry, harden auth (NextAuth :left_right_arrow: JWT :left_right_arrow: FastAPI service-to-service), and keep deploy pipelines green. Build with simulators: when you can't test against live meetings, generate realistic synthetic transcripts through our simulator service. Stack you'll work in Backend: Python 3.11, FastAPI, Uvicorn, PyJWT, Anthropic SDK, Deepgram, Neo4j, Supabase (Postgres + realtime), WebSockets Frontend: TypeScript, Next.js 15 (App Router), React 19, NextAuth 5, Tailwind, shadcn/ui, D3, Stripe Infra: Fly.io, GitHub Actions, Sentry, Supabase AI: Claude (Opus/Sonnet) for transcript analysis, action card generation, and agentic dev workflows What we're looking for 4+ years building production web applications, ideally across Python and TypeScript. Comfort designing and shipping features against an LLM API — prompt iteration, structured outputs, evals, cost/latency tradeoffs. Real Claude or OpenAI production experience required. Experience with multi-tenant SaaS patterns, JWT auth, and one or more of: graph databases, realtime systems, audio/transcription pipelines. Comfort with AI-assisted development workflows (Claude Code, Cursor, etc.) — not just as a code-completion tool, but as a way to plan and ship features. Bias toward shipping. Small surface area, high ownership, no committee.

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.

Looking for a trainer to deliver the "Claude AI for Workflow Automation and Productivity Training Course" for a Corporate Training Engagement We are seeking an experienced instructor to deliver a hands-on corporate training focused on using Claude AI for workflow automation and productivity enhancement. The ideal trainer should be comfortable teaching business users and technical professionals how to leverage AI tools to streamline operations, automate repetitive tasks, and improve collaboration. This is an instructor-led training engagement to corporate participants. Training Topics Include: Introduction to Claude AI and AI-driven workflow automation Using Claude AI to improve productivity and task management Automating business processes such as: Email and document workflows Meeting notes and follow-ups Content generation and reporting Enhancing team collaboration with AI-assisted workflows Integrating Claude AI with business platforms and automation tools Workflow automation using tools such as: Zapier Trello Asana Notion CRM and customer support platforms AI best practices, governance, privacy, and ethical considerations Future trends in AI-powered business automation Ideal Trainer Profile: Strong hands-on experience with Claude AI or similar generative AI platforms Experience delivering workflow automation or productivity-focused training Familiarity with AI integrations and no-code/low-code automation tools Comfortable teaching both conceptual and practical hands-on sessions Prior corporate training experience preferred Ability to customize examples and exercises for business audiences Training Format: Instructor-led live training Interactive discussions and hands-on exercises Corporate audience Beginner-friendly but practical and business-oriented

Overview I have a Next.js website with a newsletter signup form that currently submits directly from the browser to HubSpot's Forms v3 endpoint. I want to add a lightweight LLM-based spam filter that inspects each submission *before* it reaches HubSpot, and silently rejects (or flags) anything that looks like spam/bot/junk input. Current setup - Framework: Next.js (App Router, TypeScript, React client component) - The form component (`NewsletterForm.tsx`) POSTs directly to `https://api.hsforms.com/submissions/v3/integration/submit/[portalId]/[formGuid]` - Fields collected: `firstname`, `lastname` (optional), `jobtitle`, `email` - Portal ID and Form GUID are public form identifiers (no secrets today) What I want you to build 1. Create a server-side API route in the Next.js app (e.g. `app/api/subscribe/route.ts`) that: - Receives the form fields from the client - Runs an LLM spam/quality check (e.g. OpenAI or similar) to classify the submission as legit vs. spam — checking for gibberish names, fake/disposable emails, nonsense job titles, injection attempts, etc. - If legit → forwards the submission to HubSpot (server-side) - If spam → rejects gracefully with a generic message (no HubSpot write) 2. Update the existing `NewsletterForm.tsx` to POST to the new internal API route instead of calling HubSpot directly. 3. Keep the LLM API key server-side only (use an environment variable — never expose it to the client). 4. Preserve the existing UX: loading / success / error states should still work. Deliverables - Working API route with the LLM spam check + HubSpot forwarding - Updated form component - Brief note on which env vars to set (`OPENAI_API_KEY`, etc.) and how to configure them - Clean, typed TypeScript that matches the existing code style Nice to have (optional) - Basic rate limiting / honeypot field as a cheap first line of defense before the LLM call - Configurable spam threshold or a logged "reason" when something is rejected Requirements to apply - Strong Next.js App Router + TypeScript experience - Experience calling an LLM API (OpenAI or equivalent) from a server route - Familiarity with HubSpot Forms API is a plus To apply, please briefly answer: 1. Which LLM/provider would you use and roughly what would it cost per submission? 2. How would you handle the case where the LLM API is slow or down — do you fail open (let it through) or fail closed (block it)? 3. Have you integrated with HubSpot Forms before? (yes/no is fine)

Rebuild a travel agency SaaS platform from a working no-code prototype to Next.js + Supabase. Features include Notion-style CRM, AI proposal builder (Claude API), client portal, commission tracking, Stripe billing, and Duffel flights API. Row-level security required. Fixed price project. Full working prototype provided as reference.

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.

Content Creators (TikTok / Instagram / X, ~1K–100K) — Try Our AI Tool + Paid 60-min Feedback Call ($50) ABOUT US We're CreaMate.AI , an AI "manager" for mid-tier creators — it helps with content strategy, growth insights, and matching with paid brand deals. We're an early-stage startup in Sequoia's AGIBuilder program and inviting our first creators in. We'd love your honest take. WHO WE'RE LOOKING FOR - Active content creator / KOC on TikTok, Instagram, or X - Ideally 1K–100K followers (some flexibility — we care most that you post regularly and have a real, engaged audience) - Any niche is welcome — no category restriction - Based in the United States, United Kingdom, or Canada - Native or fluent English HOW IT WORKS 1. Message us so we can send you a free ACTIVATION CODE (access is invite-only). 2. Register at CreaMate.AI with your code and try the core features on your own channel (~10–15 minutes). 3. Join a 60-minute video call to walk us through your honest feedback. WHAT YOU GET - $50 for the 60-minute call - Free early access to CreaMate - (Optional) Be featured as an early creator + a shot at brand-deal matches TO APPLY, PLEASE SHARE 1. Link(s) to your channel(s) + follower count 2. Your niche 3. One sentence: your biggest struggle with content or monetization right now 4. Your timezone Note: the product is invite-only — you'll need the code we send to register. Apply and we'll send your code. Looking forward to meeting you!

Needs to hire 5 Freelancers to interview Summary Content Creators (TikTok / Instagram / X, ~1K–100K) — Try Our AI Tool + Paid 60-min Feedback Call ($50) ABOUT US We're CreaMate.AI , an AI "manager" for mid-tier creators — it helps with content strategy, growth insights, and matching with paid brand deals. We're an early-stage startup in Sequoia's AGIBuilder program and inviting our first creators in. We'd love your honest take. WHO WE'RE LOOKING FOR - Active content creator / KOC on TikTok, Instagram, or X - Ideally 1K–100K followers (some flexibility — we care most that you post regularly and have a real, engaged audience) - Any niche is welcome — no category restriction - Based in the United States, United Kingdom, or Canada - Native or fluent English HOW IT WORKS 1. Message us so we can send you a free ACTIVATION CODE (access is invite-only). 2. Register at CreaMate.AI with your code and try the core features on your own channel (~10–15 minutes). 3. Join a 60-minute video call to walk us through your honest feedback. WHAT YOU GET - $50 for the 60-minute call - Free early access to CreaMate - (Optional) Be featured as an early creator + a shot at brand-deal matches TO APPLY, PLEASE SHARE 1. Link(s) to your channel(s) + follower count 2. Your niche 3. One sentence: your biggest struggle with content or monetization right now 4. Your timezone Note: the product is invite-only — you'll need the code we send to register. Apply and we'll send your code. Looking forward to meeting you!

We're hiring a senior front-end contractor to take ownership of the front end of CMMC.builders, a production compliance-assessment platform, and then support other applications in our portfolio on an ongoing basis. The app was built quickly using Replit and AI-assisted ("vibe coding") workflows — it works, is in production, but it was not written with long-term maintainability as the top priority. We need someone who can read a large AI-generated codebase, form an independent judgment about what's solid versus fragile, and systematically bring it up to a level you'd defend in a code review at a company that values engineering. This isn’t a "rewrite everything" job. It's an audit-and-refactor process: understand what exists, identify risks, fix them without breaking production, and leave the codebase in a state a regular team could safely build on. This is a long-term role supporting a well-funded, high-stakes MVP, with real potential to turn into a full-time position for the right person. WHAT YOU'LL ACTUALLY BE DOING Phase 1 — Audit (first 1–2 weeks) Review the front-end architecture (component structure, state management, data-fetching patterns, routing, type safety) and prepare a written report on your findings, prioritized by risk and effort. Identify AI-coding issues specifically: duplicated logic, inconsistent patterns across similar features, overly broad "any" typing, prop-drilling where shared state should be, dead code, and components that mix data-fetching, business logic, and presentation. Flag any security or correctness concerns on the front end (unsanitized rendering, client-side trust of server-controlled data, broken access-control assumptions). Phase 2 — Refactor (ongoing) Carry out the refactor plan in reviewable, incremental PRs — no large-scale rewrites. Establish or tighten conventions: component boundaries, shared hooks, data-fetching layer, form/validation patterns, error and loading states. Improve type safety and eliminate unsound patterns introduced by AI-assisted coding. Add or enhance test coverage on the areas you modify. Document decisions throughout to keep the codebase understandable for the next person (human or AI). Beyond CMMC.builders Once the initial audit and top-priority refactoring are stable, you will work on front-end tasks across other applications in our portfolio — developing new features, conducting additional audits, and providing senior front-end support. OUR STACK React 19 + TypeScript, built with Vite TanStack Query for data-fetching and caching, wouter for routing Zod for schema validation Express (Node) backend, PostgreSQL via pg (no ORM — handwritten parameterized SQL) Vitest + Playwright for testing Hosted on Replit, deployed via Replit Autoscale YOU SHOULD APPLY IF You have 5+ years of production React/TypeScript experience and can cite real shipped projects, not just tutorials. You've performed codebase audits or major refactors before — not just greenfield projects. You can share a time when you inherited a messy codebase and what you actually changed. You are comfortable reading unfamiliar code quickly, forming your own judgment, and respectfully pushing back if something seems wrong — including AI-generated code that looks superficially okay. You write clearly. The audit report and PR descriptions are as important as the code. You can work independently with minimal oversight and communicate proactively, not just when prompted. NICE TO HAVE Direct experience refactoring or "productionizing" AI-generated or AI-assisted code. Familiarity with compliance, security, or regulated-industry software (this product deals with CMMC/cybersecurity compliance data). Experience using Replit as a development environment. HOW TO APPLY Your proposal must include: A one- or two-sentence example of a real audit or refactor you led on an existing codebase — what was wrong and what you did. A link to a GitHub repo or code sample showing your TypeScript/React coding style (not just a live demo link). The words "compliance refactor" are somewhere in your opening line, so we know you’ve read this posting. Proposals that are templated, copy-pasted, or don't answer the above won’t be considered, regardless of rate.

We're an early-stage AI startup building Hirey — an agent-to-agent marketplace that runs inside various AI tools via a plugin. Think "Upwork for AI agents": your agent finds, vets, and books the right human or agent on your behalf. We're looking for 5 AI Agent enthusiasts to install our plugin (openclaw, codex, Opus, Gemini), try a sample workflow, and give us honest feedback on a 30-minute Zoom. About 30 minutes of your time total. What you'll do 1. Install the Hirey plugin in Codex. It connects your agent to Hirey’s remote MCP server, so there’s no local server, Node setup, Claude Desktop, or JSON config edit required. Setup is usually: enable the plugin, restart the AI agent you installed on 2. Connect to Hirey and run one sample workflow we send you. 3. 30-min Zoom with the founding team. We'll ask what confused you, what worked, what you'd change. Camera on, recorded. Who we're looking for - Someone who has used AI tools in the past, especially for any coding or technical tasks - You use Claude Desktop, Cursor, Codex, or similar AI dev tools regularly. - Bonus: you've built or contributed to anything in the AI agent / MCP / LangChain / Claude Code ecosystem. What you get - $25 flat, released via Upwork on call completion. - Early access to the Hirey AI agent network if you want to keep using it. - A direct line to the founding team — we genuinely want your criticism. To apply, answer these in your proposal 1. Have you used an AI coding tool before? Which one(s)? 2. One sentence on a recent AI/agent project you've worked on or played with. 3. Your timezone and earliest availability this week. We'll respond within 24 hours and schedule calls within 2 business days. No long applications, no portfolio review. Optimizing for speed.