Description
Summary I’m the founder of a DFW-based general contracting company (Summit Signature Renovations) and a parallel AI services business (Summit Signature Solutions) that productizes AI ecosystems for other contractors. I’ve designed a multi-agent AI ecosystem using Claude + Obsidian + Git, and I need a technical implementer to turn the design into working automation over the next 20 weeks. What you’d be building: • n8n workflows connecting Claude API to Obsidian vault, Google Drive, PlanHub, QuickBooks • MCP integrations so Claude reads/writes to my Obsidian vault directly • Automated bidding pipeline (lead intake → qualification → estimate draft → two-version output → follow-up cadence) • Voice memo processing pipeline • A living methodology library in Obsidian that becomes the delivery IP for my productized service This isn’t a “build it and disappear” engagement. It’s guided implementation with knowledge transfer. You’ll produce recorded build walkthroughs and reusable SOP documentation as core deliverables, not afterthoughts. My technical partner will consume those as training to run future client deployments. Working model: • Async-friendly (you build independently on your end, deliver recorded walkthroughs + docs at natural checkpoints) • Questions consolidated in async batches • Upwork Time Tracker required on hourly work • All work done by you personally, no subcontracting Engagement structure: • ~20 weeks total, staged with off-ramps at end of week 4 and week 8 • Weekly hours average 7-10 (some weeks lighter, some heavier) • Starts with a paid one-hour prep engagement so both sides can evaluate fit before committing to Phase 1 What I need in candidates: • Proven n8n workflow experience (portfolio examples required) • Claude API integration experience specifically (not just “LLMs” broadly) • MCP protocol familiarity • Evidence of documentation discipline — please share a Loom walkthrough, YouTube tutorial, or blog post you’ve produced explaining HOW you built something • Fluent async written English • Willingness to work with Upwork Time Tracker on all hourly work Screening question: Please attach or reference one build walkthrough (Loom, YouTube, blog post) you’ve produced in the past that would give me confidence you can teach as you build. If you don’t have public work of that kind, describe how you’d approach producing it for this engagement. Full briefing attached. Please read it fully before applying. It contains the strategic framework, phased scope, current state, hard constraints, and paid-prep-hour process. Your rate quote should reflect the SOP/methodology depth described in Sections 7 and 12, not just workflow build hours. Serious inquiries only. Thank you. Quintin