We have a half vibe coded, half bubble web app. (interface and some backend wf’s are vibecoded).
its functioning well. but we are looking for a team member (part-time or freelancer is okey).
Hi, I’m interested. I’m a Full-Stack Bubble Developer with 3+ years of experience building scalable web applications, API integrations, and automation workflows. I also have experience with AI agents, n8n, Make, Zapier, and UX-focused product development. I’d be happy to contribute part-time or as a freelancer.
Hi, my name is Christian. I have nearly two years of experience developing websites and automations in Bubble, and I recently developed a custom ERP. I’d like to know more about your proposal.
I specialize in building complex, end-to-end applications as both a designer and no-code developer. My expertise spans the full project lifecycle, from high-fidelity Figma prototyping to full-stack development with the Bubble platform. I engineer advanced backend workflows and integrate external services to enhance platform functionality. By bridging intuitive UI/UX design with robust logic, I deliver scalable, high-performance solutions ready to help you achieve your goals.
I build production Bubble apps. Not prototypes, live products with real payment infrastructure.
Most recently I launched ParkHavn at parkhavn.com, a two sided parking marketplace, solo: native iOS + Android, Stripe Connect payouts with multi party splits, real time booking with race condition safe double booking prevention, and push notifications. It’s live on the App Store now.
If you’re building something with payments, marketplaces, or native mobile, that’s my zone. The hard plumbing most Bubble freelancers avoid. Rate is $90 an hr.
Happy to hop on a quick call or take a look at your build.
Hi,
I’m writing because of your third line — BPA, RPA, agentic automation.
That’s the part I actually work in, not just Bubble.
What I do: Bubble on the front, automation layer behind it (Make / n8n),
including LLM steps — document processing, lead enrichment, internal agents
that complete a task instead of just calling an API once.
On a half vibe-coded / half Bubble app the pain is usually the seam between
the two: unclear which side owns the data, the same workflow existing in both
places, and no retry or error handling on the automation side. That’s the
first thing I’d audit.
Portfolio: https://portfolio-79s.pages.dev/
Part-time works for me.
Maksim Padleski
I work on exactly this: apps half built with AI tools, half Bubble. The problem is usually between the two parts, and usually in the data model. That’s where I would start.
Bubble and Xano, APIs, ex data analyst. Part-time works for me.
Half vibe coded, half Bubble is a specific situation: the app works, but nobody has the full picture of how the two halves talk to each other. That is fine until you need to change something that crosses the boundary, and then it costs three times what it should because the change has to be traced through both sides.
That boundary is where I work. Six years on Bubble before I moved to code, so I read the editor as a spec rather than guessing at the logic. On the code side, Next.js, TypeScript, Python, and I work with AI agents daily, but spec-first: the spec sets what the product does, the agent executes. Which also means I can read what your vibe coded parts actually do rather than what they were prompted to do.
On automation: I have built agent pipelines and tool-calling flows, and I care more about whether they fail safely than whether they demo well.
Part-time or freelance works for me. I am in Indonesia, so I overlap with European hours in the afternoon and Asian hours fully.
Happy to look at the app and tell you where the seams are before we talk about scope.