I build websites and business automations for small teams. The first version runs in two weeks, and the code and accounts stay yours.
Pick a scenario. See what the system does at each step, and the screen it produces.
Example scenario, people are fictional. Timings from a typical setup.
Products still in daily use. As R&D team lead I owned their architecture and delivery.
Internal company OS
0+employees use it every day
Sales, CRM, bookings and WhatsApp for 250,000+ customers in one place. 45+ modules, 12+ integrations.
Architecture and development
SaaS for Etsy sellers
0+active users
Etsy sign-in, multi-currency and AI-generated designs.
Product development
Community for building with AI
0+students
A community of founders who map the process, build the system and sell the result. I built the library that walks members through real company automations with n8n, Vercel, Supabase and Resend.
Technical implementation library
Client work · site, webinars and CRM
0+leads captured
Website, webinar sign-up flow and booking tracking for the sales team. Every Calendly booking lands on the site, in the sheet and in the CRM automatically.
Site, integrations and CRM
Fixed price, fixed timeline. After the call you get a firm quote for your case. Prices exclude VAT.
A task you do by hand every day, run end to end by a system.
from €1,5002 weeks
A site that turns visitors into customers and answers their questions at night too.
from €1,9002 – 3 weeks
Work I've delivered, and systems I build often.
Client work · EU project website
Examples of how they work, without naming clients.
Example setup
Appointments are set by phone, and no-shows are noticed at the end of the day.
What changesA booking enters the calendar the moment the customer writes, and nobody has to call to remind them.
Example setup
The same price and opening-hours questions arrive all day, and after-hours ones go unanswered.
What changesCommon questions get answered at night too, and only the ones that need you reach you.
Example setup
Form requests get lost in the inbox, and it's unclear who should reply.
What changesEvery request is logged, you hear about it instantly, and no customer waits without a reply.
15 minutes. You walk me through the work, and I tell you plainly whether automation will help.
We start small and test with your real data. If it doesn't save time, we stop.
Code, documentation and every account stay with you. Nothing depends on me.
I live in Brussels and lead the R&D team of an education company: we built the systems the whole company runs on and the products its customers use.
With Coban Labs I do the same work for smaller teams, in English and Turkish.
You describe one process, and I tell you whether it suits automation and roughly how long it would take. No sales pitch.
I start with the tools you already use. Where needed I add tools like n8n, Supabase and Claude, all opened in your own accounts.
The number of processes and tools changes the price. After the call I send a fixed quote that doesn't change until the work is done.
Yes. Calls are online and invoices are in euro.
I fix bugs free for 30 days after handover. After that there's a monthly maintenance option.
Yes. Agents that answer questions, book appointments or create records in your CRM. An agent only reaches the tools you allow and waits for your approval on important steps.
In your own accounts. I prefer servers in Europe and never copy your data elsewhere.
Tell me about your work in two sentences, then pick a time that suits you. If it isn't a fit, I'll say so.
