I build the system, then I hand you the keys.

This page is the long version. The rest of the site is concrete and outcome-shaped on purpose. Read this one and then go book a call, or don't. It's the same offer either way.

I spent years learning to build software. Real software. Not prompts, not wrappers. The kind of code that runs at 3am while everyone is asleep and doesn't fall over. Then the agents arrived and the work changed.

Now one operator can do what a five-person team did last year. I watched this happen in my own work first. The same week's worth of code took an afternoon. The thing I would have hired a junior for, I built between meetings. The cost of bespoke software dropped by an order of magnitude and most of the world hasn't caught up to the price yet.

§ 01This studio is that practice.

Pulp AI Studio is one operator setting up and running AI for small and mid-sized businesses, and writing custom systems for the ones that outgrow it. The kind of operators who answer their own phone. Used car dealers. Independent service shops. Clinics, contractors, local agencies. People who run things and know exactly where the hours are leaking.

They don't need another platform to learn. They've been pitched plenty. They need one specific thing done well, by someone who runs it for them. Catches the leads. Books the call. Pings the customer on day thirty. Sources the inventory. Whatever it is.

§ 02Start managed. Grow into a rig.

Every AI plan out there has the same fine print: the software is the cheap part, and you are the labor. So most shops start with a plan run for them. We set up a hosted CRM with the AI built in (a voice AI receptionist, speed to lead, database reactivation, AI social replies), connect it to the tools you already run, and manage it. Live in about two weeks, at one flat monthly price in the same range as the AI receptionist plans you would run yourself. Your contacts, conversation history, and phone number are yours to export or port out if you leave.

When a shop outgrows that, we scope a custom build: hardware, software, integrations, and compliance setup, live in about 30 days, and the rig is yours. If it doesn't pay back on a working shop, the math is wrong somewhere and I want to know about it. Quoted before we start. No hourly. No "we'll see how it goes." If we estimate wrong, we eat it. Most shops start managed and grow into a rig. That's the whole deal.

§ 03One builder. The same one writing the code.

The person on the call is the person in the editor. No project manager, no junior associate, no offshore handoff. When the chatbot answers a customer at 9pm on a Tuesday, that answer was shaped by a conversation we had two weeks earlier on a 30-minute call.

That doesn't scale to ten clients at once. It's not supposed to. The bet this studio makes is that one builder with the agents is now enough to do good work for small operators at a price they can stand. If that bet is wrong I'll find out fast.

§ 04What I won't do.

I won't sell you a dashboard and call it the product. I won't quote you hourly. I won't hand you a login and leave you to run it. If you own a rig, the build stands on its own, and ongoing work is yours to opt into. If a plan you'd run yourself already does the job, I'll point you at it and we'll part on good terms.

§ 05The bet.

The bet is that the agents are doing the work now, and the right move is to put them on the smallest, most concrete jobs first. The ones where an operator can see the result the morning after we deploy. Not the five-year roadmap. Not the platform. The specific rig that catches the specific lead this Tuesday at six.

If you're an operator and you've read this far, the next step is the same as everywhere else on the site. Fifteen minutes. One workflow. One question: where is the phone going quiet?