Role Overview You are the Executive AI Enablement Lead at AIVC, the person whose job is to make the executives at AIVC’s client businesses true power users of Claude, Cowork, and code- and agent-driven workflows. AIVC partners with operator businesses to drive AI-led EBITDA growth, and part of that work is bringing each company’s most senior leaders up the AI curve. You’re the person who personally designs and runs that path on every engagement: assessing where a given client executive is today; curating the right materials, videos, and course content; running 1:1 coaching; building executive playbooks; and acting as their daily operator-in-the-loop until the new workflows stick. The first concrete instance is already lined up, a named client managing partner has explicitly asked for the fastest path to becoming a power user of Claude, Cowork, and Claude Code / Skills. From there you scale: same treatment to additional client executives across the portfolio, then a documented set of executive-grade playbooks and patterns that compound across every future engagement. You are bias-toward-results – a win is the client executive’s calendar-week looking different, not a beautifully written rubric nobody uses. What You’ll Own (Outcomes) • Within 30 days of pairing with the first client managing partner, they have a working daily routine in Claude, Cowork, and Code/Skills that’s already replacing or improving how they handle at least three recurring tasks • Within the first quarter of the engagement, the client executive is a true power user — running multi-step workflows, custom Skills/Projects, and agent-assisted tasks without needing coaching scaffolding for the basics • A documented set of executive playbooks (research, writing, analysis, synthesis, workflow automation, agent-assisted tasks) that compound across every client engagement, not one-offs • A curated, current library of learning materials, videos, example workflows, and Claude-native patterns — including a clear point of view on which external courses, tutors, or expert resources are worth plugging in • Observable change in how client executive cohorts use AI: from reactive chat to repeatable, structured, outcome-oriented workflows • A foundation of training assets and patterns that scales beyond executive coaching into broader client teams in year two • A reputation among AIVC’s clients as the trusted go-to for “how do I do this better in Claude” — measured by inbound demand and engagement expansion What You’ll Do (Responsibilities) • In the first weeks: build the first client managing partner’s tailored upskilling plan — assess current usage, identify the highest-leverage workflows for their day-to-day, curate the right mix of materials / videos / course content, and recommend any tutor or expert-guided support to fold in • Provide 1:1 coaching for client executives — managing partners, founders, C-suite leaders — on Claude, Cowork, and code- and agent-based workflows • Design tailored training plans per executive that go beyond basic onboarding into advanced usage, with explicit progression from chat → workflows → agents • Curate the best external materials (videos, courses, blog posts, example projects) and rewrap them into client-ready, AIVC-flavored learning paths • Teach practical, high-leverage use cases live: research, writing, analysis, synthesis, workflow automation, and agent-assisted tasks • Help client executives move from general chat usage into repeatable workflows — Claude Projects, Skills, scheduled Cowork tasks, MCP integrations, custom agents • Serve as a real-time tutor and expert resource for client executives — over Slack, in meetings, on-site, and in async written feedback • Run office hours, workshops, and informal Q&A sessions inside client teams to keep adoption sticky between coaching sessions What We’re Looking For (Required) • Deep hands-on expertise with Claude across every surface (Claude.ai, Claude Projects, Claude Code, Claude Skills, Claude API) — and an active habit of pushing the edges of each • Strong working fluency with Claude Cowork specifically, including scheduled tasks, connected apps / MCPs, and the broader workflow surface • Strong capability with code-enabled AI workflows: you can write Python and/or TypeScript, build agents, configure MCP integrations, and ship a working internal automation end-to-end without needing an engineer • Demonstrated ability to teach non-technical but highly demanding users — you’ve made executives, founders, or senior operators meaningfully better at something complicated, not just trained engineers • Strong workflow design instinct — you can translate messy business questions into clean prompts, workflows, and systems • Polished, discreet, and effective in high-touch client executive settings — high EQ, low ego, comfortable representing AIVC inside senior client environments and around senior decision-makers • Strong bias toward practical results over theoretical AI knowledge — the metric is the client executive’s behavior change, not the elegance of the explanation • Excellent written and verbal communication; you can write a playbook a client executive will actually read and use • Comfort with significant travel to client sites and embedded, on-site engagement work • 5+ years of professional experience across some mix of: applied AI / ML, technical training and enablement, developer relations, solutions engineering, executive coaching, management consulting, or chief of staff / senior operator roles to executives Helpful If You Have (Preferred) • Prior experience coaching or supporting C-level executives, founders, or managing partners as a client-facing professional — executive coach, principal solutions engineer to executive customers, chief of staff to a CXO, or partner-level consultant • Background that combines technical depth with people skills — developer relations, solutions engineering, technical training, or learning & development at a frontier AI or developer-tools company • Direct experience building executive-facing training programs or curricula that demonstrably moved adoption inside other organizations • Hands-on familiarity with the Anthropic product surface specifically: Claude Projects, Claude Skills, Claude Code, MCP server development, Claude API • Track record of getting non-technical users to genuinely adopt a technical tool — i.e., users who chose to keep using it after the training ended • Background in management consulting, professional services, executive coaching, or learning & development — especially in environments where the customer was a senior external client • An active personal portfolio of AI work (workflows, automations, blog posts, talks, open-source contributions) you can point to • Comfort building light tooling (a Notion playbook system, a Claude Skills catalog, a small dashboard) without needing engineering support • Familiarity with AIVC’s model — operator business engagements, EBITDA-led measurement, and the broader compounding intelligence layer — or eagerness to come up the curve quickly

DESCRIPTION: I am an industry veteran with 40 years of service and marketing experience launching a specialized local vendor routing network. I am a solo operator looking for a certified, independent Zoho CRM specialist to execute a simple, highly targeted CRM setup. THIS IS A STRICTLY "DONE-WITH-YOU" (DWY) PROJECT. I do not want you to build this in isolation and hand me a finished product. We will collaborate live via Zoom screen-shares so you can execute the build while teaching me how the backend works, allowing me to take full operational control upon completion. PROJECT SCOPE & CORE REQUIREMENTS: 1. Module & Field Customization: Setup a single page layout using native Layout Rules to toggle among 15-20 Service Provider scopes based on a dropdown selection. 2. Account Subforms: Map out provider service areas and criteria matrices using standard Subform logic. 3. Telephony Integration: Configure Zoho Voice to match an existing, 40-year-old business line for outbound click-to-call recording mirroring our trusted Caller ID. 4. SMS Extension Setup: Connect a plug-and-play marketplace app (e.g., Smooth Messenger or Salesmsg) to text-enable our line for multi-channel customer photo logs. 5. Dual-Action Workflows: Program code-free Workflow Rules that simultaneously text the provider and customer the millisecond a lead is toggled to "Dispatched." 6. Invoicing & Automated Payment Setup (Native Zoho ACH Integration): • Native Processor Link: Connect Zoho Payments directly to the CRM environment to securely link and authorize providers' ACH bank accounts via the native Zoho Payments widget. • Pre-Paid Ledger Architecture: Build a custom numerical field on the Provider Account profile called "Available Lead Balance Credit." • The Conditional Payment Guardrail (Instant Balance Check Loop): Create a code-free Workflow Rule that checks the provider's credit ledger balance the exact millisecond a Lead Status is manually toggled to "Dispatched." - If Balance is Sufficient: Automatically subtract the flat lead fee from the "Available Lead Balance Credit" ledger, generate a timestamped invoice marked as "Paid," and allow the simultaneous text messages to fire. - If Balance is Insufficient: Instantly block the outbound text dispatches, halt the automation loop, and flip the Lead Status to a custom alert flag titled "On Hold - Account Replenish Required." • Low-Balance Auto-Replenishment: Integrate Zoho CRM with Zoho Billing/Books to automatically generate a recurring ACH pull to reload the contractor's escrow ledger whenever their balance drops below a specific monetary threshold.7. Zoho Contracts/Sign: Map checked CRM parameters into a Master Service Agreement template for seamless smartphone finger-signatures. PROJECT FRAMEWORK & CONSTRAINTS: • This project is estimated to take roughly 16 hours across 4 live sessions. • Every single screen-share session will be recorded so I have a custom training library. • STRICTLY NO CUSTOM DELUGE CODING. This system must rely 100% on out-of-the-box checkboxes, layout rules, and standard workflow rules so I can easily manage it moving forward. ANTI-BOT & ANTI-AGENCY MANDATORY RULES: 1. I am hiring an independent solo freelancer. If your past profile reviews contain the words “they” "them," "their team," "their developer," or "agency," do not apply. I will verify your identity on Zoom. 2. To prove you are a human who read this entire file, you must start your cover letter proposal with this exact sentence: "I am a solo freelancer and I have forty years experience with systems." Any application missing this exact sentence or using a standalone keyword line will be instantly declined and reported for automated bot application.

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.

Looking for a full-stack developer or product designer to help scope, wireframe, and build an MVP for a real estate responsiveness tracking platform. Phase 1 will strictly be a paid discovery/wireframing phase to map out user flows from scratch." Job Posting Template Title: Product Designer / Full-Stack Developer needed for MVP Discovery & Wireframing (Real Estate Platform) Description: I am looking for a talented Product Designer, Technical Product Manager, or Full-Stack Developer to help map out, wireframe, and scope the Minimum Viable Product (MVP) for a new real estate responsiveness tracking platform called Showing-Score. The platform’s core focus is holding buyers' agents accountable by tracking and scoring how quickly they provide feedback to listing agents after showing a property. Note: This is strictly for Phase 1: Discovery & Wireframing. I am looking for a blueprint before any coding begins. A signed Mutual NDA will be required before deep-dive project details are shared. Note: This is strictly for Phase 1: Discovery & Wireframing. I am looking for a blueprint before any coding begins. A signed Mutual NDA will be required before deep-dive project details are shared. Phase 1 Deliverables: 1. User Persona Flows: Clear step-by-step mapping for three distinct user journeys: o The Listing Agent: How they log in, input a showing, and track scores. o The Buyer's Agent: The low-friction flow of receiving an automated text/email link and submitting quick feedback without needing a clunky account setup. o The Admin Panel: How I will manage the backend database. 2. Interactive Wireframes: Low-to-medium fidelity clickable mockups (Figma preferred) showing the complete layout of every essential screen. 3. Technical Specification Document: A comprehensive spec sheet outlining the recommended tech stack, database architecture, and required API integrations (e.g., SMS/Email delivery systems like Twilio). Requirements: • Proven experience in UI/UX design, product discovery, and scoping software applications from scratch. • Strong background mapping out marketplace, directory, or rating systems. • Excellent communication skills to help translate business logic into clean technical requirements. • Experience with real estate tech or automated communication workflows is a major plus. To Apply: Please share examples of wireframes, user flows, or technical spec sheets you have built for previous software projects. Let me know your estimated fixed price or hourly rate for a 1-to-2 week discovery phase. Important note: To prove you read this entire description, please start your proposal with the word 'SCORE'."

DESCRIPTION; I'm building a data infrastructure product for ontology-driven AI context: object types, properties, and relationships materialized ahead of query time, so AI systems retrieve connected context fast instead of rebuilding it from raw sources on every request. I need experienced eyes on the ingestion foundation before anything gets built on top of it. The deliverables are fixed (below); hours are flexible — propose what you think the work honestly takes. Rate: my budget is $50–75/hr. That's a hard ceiling — proposals above that range can't be afforded and won't be considered, regardless of quality __________________________________________________________________________ WHO SHOULD APPLY A data engineer / data infrastructure engineer who understands what an ontology and a knowledge graph are and why they matter for AI systems — connected entities and relationships as first-class context, not just tables. You don't need graph database experience; you need to get why pre-materialized, relationship-aware data beats rebuilding context from raw sources on every query. If that framing clicks for you, you're the right kind of applicant. __________________________________________________________________________ THE PRODUCT, HIGH LEVEL: The platform deploys on a client's own infrastructure — we never see their data. Clients connect their data sources, define an ontology (object types, properties, relationships), and the platform materializes it across tiered storage. Later phases add a binary serve layer, SSD/RAM caching, and GPU-parallel query execution so AI systems and data applications retrieve connected context at very low latency. Target customers: companies running AI on complex connected data (security operations, healthcare, financial services) where privacy demands private deployment and speed matters. Storage note: the current prototype uses Iceberg on GCS for development convenience, but the architecture is intentionally built for any S3-compatible storage (on-prem S3, private cloud VPC, MinIO, etc.). Portability is a design requirement, not an afterthought — the platform must never be tied to a single cloud provider. __________________________________________________________________________ WHAT EXISTS TODAY: A working Python prototype: FastAPI, PyIceberg, PyArrow, Postgres, Supabase (metadata + sync ledger), GCS as the Iceberg warehouse. Architecture and design docs are provided for orientation. The cold path is functional and tested: a 31-test production suite ran against live infrastructure at 1M–5M row scale — core correctness, concurrency, failure injection (kill mid-sync, storage outages, lease expiry), idempotency/replay, rollback, a 50-sync soak, and audit checks. All passing, with a written sign-off document you'll receive. That's exactly why I'm hiring you: tests confirm behavior I anticipated. You're here for what I didn't anticipate — structural weaknesses, hidden risks, and edge cases that a test suite written by the same mind that wrote the pipeline can't catch. I'm strong on product and systems design, not low-level data engineering. The codebase is AI-assisted, and I want a professional to find what that typically accumulates. This is a prototype built from the ground up — no live client today. The goal: ensure the ingestion foundation is genuinely solid (data coming in from source correctly, at scale, repeatedly) so a scoped MVP pilot and beta release won't break under real usage. You are validating the foundation before anything gets built on top. __________________________________________________________________________ YOUR SCOPE — THE COLD PATH, END TO END Data source → validation → identity merge → materialized ontology in Iceberg on S3-compatible storage. The data connectors are in scope — they ARE Milestone 1. The platform supports exactly three ways data comes in, and your job includes confirming each one is genuinely production-grade, not just demo-grade: Postgres — full refresh and incremental watermark sync S3-compatible object storage (CSV) — currently GCS via S3 interop, but must work against any S3-compatible store (on-prem, MinIO, private VPC) Manual CSV upload — primarily for testing/onboarding For each connector, production-grade means: real error handling (bad credentials, unreachable source, permission failures, malformed/garbage data, schema drift), clear failure messages that tell a user what broke, no silent partial ingests, and sane retry/recovery behavior. If a connector swallows errors, loses rows quietly, or fails confusingly — that's exactly the finding I'm paying for. No other connectors are planned for this milestone. Three connectors that work correctly under stress beats ten that mostly work. Focus areas across the pipeline: Connectors — production-readiness and error handling as described above Identity & matching — entities staying consistent across syncs (PK merge, fingerprint mode, composite keys) Sync semantics — full refresh vs incremental watermark sync, replay idempotency, delete behavior Relationships — FK→PK edge materialization, rebuild triggers, orphan handling, stable node identity Versioning & audit — Iceberg snapshots, rollback, schema change lineage, sync ledger completeness Reliability — failure modes, partial writes, lock/lease behavior, silent wrong-data risks Code structure — dead code, duplication, coupling, fragility; source-specific logic must stay contained in each connector and never leak into the shared pipeline Explicitly out of scope: GPU execution, query kernels, binary serve formats, caching layers, query-time serving, and any new connector types — all future phases. Your scope ends at correct, versioned, audited data in Iceberg. __________________________________________________________________________ DELIVERABLES (in priority order) Prioritized written assessment — what's pilot-ready as-is, what must be fixed before a real pilot customer (with specific recommendations), and what the existing test suite missed (edge cases, risks, gaps). Active code changes — implement fixes for the highest-priority issues you find, directly in the repo. You'll have full repo access. I'm open to architecture changes and refinements as long as they're clearly explained with reasoning. A change log that teaches — for every change: what you changed, why it mattered, what it fixes or prevents, and what to watch for going forward. This isn't paperwork — I'm making a local engineering hire for the next milestone, and your write-ups become the onboarding record. Everyone who touches this codebase after you should learn from what you found. Fixes go deepest-risk-first. What you get from me: repo access, architecture/design docs, the test suite + sign-off report, and async availability for questions. __________________________________________________________________________ ***REQUIRED EXPERIENCE: 1)Production Python data pipelines 2)Apache Iceberg, Delta Lake, or Hudi (or strong Parquet/data-lake work) 3)Postgres 4)Merge/upsert, idempotency, watermark/CDC patterns Building or hardening data connectors that real users depend on************* __________________________________________________________________________ WHERE THIS CAN GO: This starts as a fixed-scope review. Separately, I plan to make my first part-time/full-time engineering hire locally (Dallas) to build Milestone 2 and beyond — SSD caching, serve layers, containerization, and microservices as the platform scales. For the right freelancer, there's opportunity to stay engaged on recurring scoped work — reviewing the foundation as it evolves and working in conjunction with that future hire. Not required, not promised — but the door is open if the work is strong. __________________________________________________________________________ *********HOW TO APPLY — READ CAREFULLY***** Answer this one question in your proposal, briefly and in your own words: "You're building a pipeline that ingests from Postgres and S3-compatible storage and materializes a connected ontology (entities + relationships) into Iceberg. How do you design the sync process to be reliable and idempotent — especially around watermarking, commits, and failure handling between steps?" Include your proposed hour estimate for the deliverables above. Get creative — attachments and notes welcome. Note on AI-generated proposals: I use AI heavily myself — but if your proposal or screening answer is clearly AI-generated boilerplate, you will be automatically rejected without consideration. I'm hiring your judgment and experience, not your ability to paste a prompt. Short, direct, human answers. __________________________________________________________________________ A NOTE ON TECHNOLOGY BOUNDARIES: ***QUICK EXAMPLE*** FastAPI and Iceberg are what the platform uses today, not permanent decisions. As the product scales, we may want to run FastAPI alongside a second framework, replace it entirely, or eventually move away from Iceberg toward a custom storage format optimized for the GPU serve layer. Those should be engineering decisions made on merit, not decisions we're forced into because the current code makes swapping painful. What I need confirmed: is the codebase modular enough that a change like that stays contained? Core business logic (validate, merge, materialize, version) should never be tangled directly with infrastructure. API routes should be thin entry points that hand off to service logic, not where business logic lives. Iceberg writes should be isolated behind a single abstraction. If those boundaries are clean, replacing or extending a technology layer is a focused engineering effort. If they're not, it touches everything and becomes a mess under deadline pressure with a full team. Flag anywhere that boundary is broken. That's a priority finding. __________________________________________________________________________ FINAL REMARKS: NDA & IP protections This engagement requires signing an NDA and IP assignments agreement before work begins; standard protections given you'll have full repo access to a pre-launch product. Documents are provided on day one; nothing unusual in them. If that's a dealbreaker, please don't apply.

Univium (small-business consultancy) is hiring a part-time Consulting Lead to own client problems end-to-end: lead discovery calls, scope and design solutions, write dev briefs (Jira), review deliverables, and draft proposals. Start 5 hrs/week, scale to 10 then 20. Hire needed within 3–4 weeks. Hours & Rate - Start: 5 hrs/week; scale to 10 → 20 as proven - Rate: $90–$110/hr (final rate based on experience/fit) - Location: US-based only (required) - Timeline: must be available to start within 3–4 weeks Key responsibilities - Lead or co-lead 1–3 client discovery/consultation calls weekly - Scope client problems, design fit‑for‑purpose solutions, write clear Jira cards/dev briefs - Review dev output, manage handoffs, and communicate results to clients - Draft proposals with hourly estimates and confidence levels for owner review - Self-onboard to new clients by mining notes, recordings, existing systems - Flag high-risk/low-confidence work proactively What this role is NOT - Not responsible for writing production code (in-house devs implement) - Not responsible for owning sales or managing other consultants initially Success outcomes (first 6 months) - Help scale active clients from 3 → 5–6 without increasing owner hours - Independently move 1–2 projects/week from scope → dev handoff or run 2–3 consultations/proposals weekly - Owner spends time on risk-review/high‑stakes oversight, not solution generation - Minimal hand‑holding required for onboarding; interactions are net relief for owner - Documented process to onboard a second consultant by month 6–9 Required qualifications - US-based with flexible scheduling for client calls - 5+ years working with small businesses (SMB experience required) - Hands-on familiarity with at least 4 of: Airtable, Notion, Zapier / N8N / Make, Google Apps Script, Lovable / Replit - Strong client-facing experience (leading discovery, managing expectations) - Proven portfolio of end-to-end SMB projects (scoping → solution → handoff) - Excellent at writing dev briefs / Jira tickets and delegating execution - Strong strategic problem-solving and calibrated risk awareness - Available to ramp to 10 hrs/week on 1–2 weeks' notice Screening filters (what we’ll prioritize) - Clear portfolio of solved SMB problems, ability to justify tool choices - Evidence of self-directed initiative and minimal ramp-time hires - Comfortable working via Upwork (time tracker), available within 3–4 weeks - NOT a pure executor, enterprise-only consultant, or non-US-based How to apply Submit via Upwork with: - Relevant hourly rate expectation within $90–$120/hr - Short cover note (1–2 paragraphs) summarizing why you fit this role - 2–3 portfolio examples of SMB problems you’ve solved end-to-end (links or brief case studies) - Your earliest availability to start - We’ll screen on Upwork, present finalists to the owner. Owner will interview top candidates (30–45 min). Selected candidate starts at 5 hrs/week. Owner note to candidates: We need someone who makes the owner’s life easier from week one — minimal hand‑holding, strong judgment, clear communication. If that sounds like you, please apply.

1. PROJECT OVERVIEW Applied Communications Group is soliciting proposals from qualified Illinois-licensed architectural firms to provide architectural design, code review, permit documentation, and coordinated Mechanical, Electrical, Plumbing, and Fire Protection modifications for the renovation of our newly acquired office and warehouse facility. The intent of this project is to renovate an existing commercial building and convert portions of the facility into corporate office space while maintaining warehouse operations. This project is a renovation and modification of an existing building and existing infrastructure. The design team shall adapt and extend existing systems as required and avoid unnecessary redesign of existing building systems. Additional Project Notes & Clarifications A little background on the project and my thinking behind the RFP. The original RFP was put together with the help of ChatGPT as a way to organize the project and make sure all of the major trades were addressed. Now that I've had more time to think through the scope, I wanted to provide some additional context. General Thoughts The building is located in Addison, Illinois. I grew up in Addison and am very familiar with the community and the local permitting process. This property has been somewhat neglected over the years, and one of my goals is to improve both the building and its appearance. The local inspectors are generally practical and reasonable to work with. My intent is to submit a professional and complete permit package that demonstrates a quality renovation, but I don't anticipate an overly difficult review process or excessive scrutiny on items that are clearly existing conditions. Many of the requirements listed in the RFP are intended to ensure the project presents well and leaves a good impression with the Village, rather than driving unnecessary engineering effort. Architectural A floor plan has already been developed and will be provided to the selected Architect in AutoCAD (.DWG) format. The Architect shall use this drawing as the basis for the permit drawings and verify field dimensions and existing conditions as required. The office renovation is intended to have an open ceiling concept. Existing structural steel, roof deck, ductwork, conduit, sprinkler piping, and other overhead systems shall remain exposed where practical. The Architect shall coordinate the architectural design with the Mechanical, Electrical, Fire Protection, and Fire Alarm drawings to ensure a clean, coordinated layout suitable for permit approval. The Architect shall prepare complete architectural permit drawings, including floor plans, demolition plans, door schedules, finish plans, life safety plans, ADA compliance, and any other information required by the Village of Addison for permit approval. My primary goal is to obtain a clean, professional permit set that clearly communicates the scope of work. Electrical The majority of the electrical infrastructure is already in place. The building currently has: • Existing 200A service distribution. • Existing 100A subpanel serving each floor. • Existing branch circuit infrastructure. For the most part, the electrical design should consist of extending conduit and wiring from the nearest existing junction boxes and panels to support the new office layout. The primary open design item is lighting. I have not finalized whether the space will have a traditional suspended ceiling or an exposed/open ceiling concept. At the moment, I am leaning toward an exposed ceiling design. HVAC Most of the HVAC backbone infrastructure already exists. The main duct trunks are installed and in good condition. The primary HVAC work will consist of extending branch ducts to serve the renovated office areas. We are planning to install new rooftop units, so that information should be incorporated into the design documents. The building is essentially divided into four similar zones, with each side of each floor functioning as its own zone. Because the layouts are very similar, I would expect a representative airflow calculation or design approach to be applicable across multiple areas. The only significant exception is a portion of the first floor where additional office space was added previously. I will handle the field investigation and documentation of existing conditions and will provide as much information as possible to support the design effort. Fire Protection The building is fully sprinklered. Because I am leaning toward an exposed ceiling concept, I believe some sprinkler head modifications may be required. My understanding is that existing heads may need to be adjusted or converted to accommodate the open ceiling design. A typical detail or general note showing the intended approach would be helpful, but I do not anticipate a complete sprinkler system redesign being necessary. Plumbing The plumbing system is essentially existing and will remain in place. The scope is limited primarily to fixtures and restroom layouts. Much of this information is already reflected on the existing drawings. At this time, I do not anticipate significant plumbing design beyond documenting fixture locations and any minor modifications required for the renovated spaces. Fire Alarm An existing fire alarm system is already installed and operational but will require a few modifications to support the renovation and maintain code compliance. Because the building is fully sprinklered, I anticipate only a limited amount of new fire alarm work, including: • Notification appliance near the stairway. • Visual notification appliance in each restroom. • Manual pull station and notification appliance at required exits. • Minor modifications to support existing monitoring, relays, and sprinkler interfaces. Overall, I view this as a modification of the existing fire alarm system rather than a complete redesign. Final Thoughts My goal is to work with a design team that understands this is primarily an adaptation of existing building systems rather than a ground-up design. I am looking for practical, permit-ready documents that accurately reflect the renovation while avoiding unnecessary redesign of infrastructure that is already in place and functioning properly. Owner-Provided Information The Owner will provide the following information and documentation to reduce the Architect's design effort and minimize time spent documenting existing conditions: • Completed Floor Plan in PDF and AutoCAD (.DWG) format. • Existing Exit Plan requiring only minor modifications. • Electrical Outlet / Power Drawing in AutoCAD (.DWG) format. • Low-Voltage Drawing in AutoCAD (.DWG) format. • Interior and exterior photographs documenting existing conditions. • Field measurements and verification of existing conditions. • Existing room layout, door locations, and space planning information. • Existing equipment locations and documentation where applicable. • Ongoing support throughout the design process, including additional measurements, photographs, and field verification as requested. Owner Support and Project Intent The Owner has invested considerable time documenting the existing building and preparing the base drawings to reduce the Architect's effort. The intent is to minimize time spent recreating existing conditions so the design team can focus on code compliance, permit documentation, and the modifications required for this renovation. Proposals should reflect that a substantial amount of the existing conditions documentation has already been completed by the Owner. The Owner intends to remain actively involved throughout the project and will promptly answer questions, perform additional field verification, provide photographs, and update background drawings as needed to reduce engineering hours and expedite completion of the permit documents. This is not a building design project. It is primarily the preparation of permit drawings for an already-developed floor plan using existing building systems. The Architect's primary responsibility is to coordinate the disciplines, verify code compliance, and prepare a complete permit-ready drawing package.

OVERVIEW We are a technical advisory firm that partners with VC-backed companies to design, build, and scale their engineering foundations. We embed with our clients as a core part of their technical team, not as outside consultants handing over a document, but as engineers who own the outcome alongside them. Our current client is a VC-backed company operating in the auto logistics space. They're at an exciting and critical stage: they have product-market fit, they have backing, and now they need to build the production infrastructure to match their ambitions. We've been brought in to lead that build, and we're looking for a senior full stack engineer to join us for it. This is a greenfield backend API platform built in TypeScript on Node.js with Express or Fastify, and you'd be involved from the very beginning. That means shaping the architecture, setting the patterns, and building something that will need to handle real production load in a fast-moving, operationally complex industry. The backend we're building needs to be reliable, well-structured, and built to grow. If you want to do meaningful backend work on a greenfield codebase, in a real industry with real complexity, working with a team that has high standards, this is the opportunity. WHAT YOU'LL BE BUILDING A production-grade backend API platform in TypeScript on Node.js, using Express or Fastify. Because we're starting from scratch, the early decisions carry significant weight and you'll be part of making them. API architecture, project structure, middleware conventions, authentication approach, error handling, observability, data access patterns: these are all on the table and we want engineers who have opinions about them informed by experience. Day-to-day you'll be writing and reviewing TypeScript, contributing to architecture and design discussions, collaborating with the team on Slack, and joining at least one Zoom sync per week with the broader team and client stakeholders. WHAT WE'RE LOOKING FOR - 5 to 10 years of professional software engineering experience with a strong backend or full stack background. Specifically: - Fluent in TypeScript with a solid working knowledge of the Node.js runtime, including async patterns, error propagation, and performance characteristics, not just the surface API - Hands-on Express and/or Fastify experience with real APIs built using them, a clear understanding of their trade-offs, and the ability to make informed structural decisions without needing to be guided - A track record of shipping and operating production systems, having been accountable for something running live, having handled production incidents, and thinking seriously about reliability, logging, and failure modes. - Comfort operating in a greenfield environment with some ambiguity, able to ask the right questions, help define what isn't yet defined, and take ownership of outcomes rather than waiting for a fully formed spec. - Strong English communication skills, written and spoken. We're a distributed team, async-first on Slack, and we interface directly with a client whose business is moving fast. Clear communication is as important as clean code US-based strongly preferred with meaningful overlap with US business hours required for team and client collaboration NICE TO HAVE - Cloud infrastructure experience (AWS, GCP, or Azure) - Familiarity with authentication protocols (OAuth 2.0, OIDC) - API versioning strategy experience - CI/CD pipeline experience - Domain familiarity with logistics, fleet management, or supply chain systems is a genuine bonus HOW WE WORK We are a tight team with high standards and low tolerance for vague communication or dropped balls. Slack is our primary channel, async-first with responsiveness expected during working hours. We sync on Zoom at least weekly, more often during active design and planning phases. We use Jira for our ticket management. You'll receive a Microsoft 365 account on hire for SSO access to all internal and client tooling from day one. We don't micromanage. What we do expect is proactive communication, early flagging of blockers, and the kind of ownership that comes naturally to engineers who treat a codebase as something worth getting right, not just getting done. On a greenfield project with a client at a pivotal growth stage, that distinction matters. HIRING PROCESS - Intro call (15 min) - the firm, the client, the project, your background, and your questions - Technical screen (if applicable, via Coderbyte) - Background check - standard criminal background check required for all hires, no exceptions - Offer and onboarding - Microsoft 365 account and full tooling access provisioned before day one HOW TO APPLY We read every proposal that makes a genuine effort. Please include: - A description of a production backend system you've built, including what it did, the scale it operated at, your specific contributions, and what decisions you made that you're proud of or would revisit today - Your honest assessment of your TypeScript and Node.js depth. We value specifics and self-awareness over a list of buzzwords Links to code, whether GitHub, open source contributions, a portfolio, or anything else that shows us how you think and work We work with companies at inflection points and we hold ourselves and the engineers we bring in to a high standard. If this project sounds like the kind of work you want to do, make that clear in your proposal and tell us why this domain, this stage, and this type of build appeals to you specifically.

**Part-Time Media Buyer – Home Services Lead Generation** **About Us** Bold Acquire is a B2B lead generation company that connects home service contractors (roofing, HVAC, plumbing, and similar trades) with exclusive, high-quality consumer leads. Our tagline: *We Do Leads. You Do Business.* We're growing fast and looking for a media buyer who knows how to generate home services leads at a low cost per lead using Facebook and Google. **What You'll Do** - Set up and manage Facebook Lead Ad campaigns targeting homeowners in specific zip codes - Set up and manage Google Local Services Ads (LSA) for home service verticals - Monitor performance daily and optimize for cost per lead - Provide a simple weekly report (leads generated, CPL, spend, recommendations) - Coordinate with us on landing page tweaks and ad creative **You're a Great Fit If You:** - Have hands-on experience running lead gen campaigns specifically for home services (roofing, HVAC, plumbing, remodeling, etc.) - Can show examples of CPL results from past home services campaigns - Are comfortable managing a modest monthly ad budget ($400–600 to start, scaling up) - Communicate clearly and proactively — no ghost acts - Work independently without hand-holding **Nice to Have** - Experience with GoHighLevel or similar CRM - Familiarity with Google LSA specifically - Experience building or optimizing landing pages **Engagement Details** - Part-time: approx. 8–12 hours/month to start - Fixed monthly retainer preferred (open to hourly for the right candidate) - Long-term relationship if results are strong - Remote, flexible schedule **To Apply, Please Answer These 3 Questions:** 1. What home services vertical have you generated leads for, and what was your average CPL? 2. Do you have experience with Google Local Services Ads specifically? 3. What monthly ad budget have you managed in the past? Applications without answers to these questions will not be reviewed.

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.