The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Available for new freelance projects.
I help with Python/FastAPI backend development, REST API integrations, PostgreSQL, webhooks, automation, data workflows, scraping, and OpenAI/LLM integrations.
I’m especially open to:
small backend features;
API/integration work;
automation of manual processes;
data processing pipelines;
backend fixes and production issues;
small AI-enabled workflows.
I can start immediately and I’m happy to begin with one clearly scoped paid milestone. If you have a task that needs to get shipped, send me the scope and expected result.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
JARVIS
Title: JARVIS: Voice-First Autonomous AI Assistant
Description:
A locally hosted AI assistant that listens, reasons, and acts on my computer with human approval where it matters.
What I built:
Voice interface with a "Hey Jarvis" wake word, speech-to-text and text-to-speech
Autonomous coding agent that locates, patches, tests, and fixes its own code
Multi-provider LLM routing (Gemini, Groq, OpenRouter, Ollama, OpenAI) with automatic fallback
13 tools, approval gates, and an audit trail for safety
n8n workflow automation and a REST/WebSocket API
Tools: Python, FastAPI, LangChain, PostgreSQL, Redis, ChromaDB, Ollama, Docker, n8n
Having automatic fallback across multiple LLM providers keeps the assistant running smoothly even when one service drops.
The problem
AI tools changed how fast good work gets made, but hiring still looks like 2015: long specs, hourly guesses, and no clear line between a prompt and a finished product. Clients want the result. Skilled people who build with AI want to be paid for outcomes, not hours.
What we built
VibeBay is a two-sided marketplace for finished AI work. A client posts what they need in plain words. Matched talent reply with a price, a delivery date and real samples. The client picks one, pays into escrow, and the money is released when they approve the work, or 7 days after delivery.
Inside the product:
Explore and search across six kinds of work, with talent profiles, portfolios, levels and reviews
Task posting, proposals with milestones, and checkout with escrow through Stripe
Real-time messaging between clients and talent
An AI assistant that helps clients describe the work and find the right person
Skill tests graded by AI, and profile import that turns an existing portfolio into a VibeBay profile
A full admin panel: approvals, moderation, support, orders and live campaign numbers
A pre-launch system with founding seats per country, referral codes and a countdown to opening day
How it's built
Next.js on Netlify, Supabase for the database, sign-in and file storage, Stripe for payments and escrow, Claude for the AI features, and Resend for email. Every page is checked automatically on each change at four screen sizes, from a small phone to a wide desktop, for accessibility and for broken buttons and links.
Where it is now
Founding seats are opening country by country, and the full marketplace opens on 31 October 2026.
Designed and built by Dreamec Studios.:
The question I ask before automating anything: "What does this look like on a Tuesday in month four?"
Not the demo. Not launch day. Month four, when the person who championed it has moved on, the data has drifted, and the model has quietly started doing something slightly different.
The automations that survive month four have three things: a human somewhere in the loop, a log a non-engineer can read, and a kill switch that doesn't need me. The PO intake agent I posted last week is built that way on purpose. It registers and notifies, people decide, and every email in and out is logged.
If yours has all three, you're fine. If it has none, I'd love to hear how it's going. I collect these stories.
the month four test is so spot on zahid. everyone designs for the launch demo, but silent prompt drift kills more workflows than actual broken APIS.