auditroom.ch: uploads and Stripe, taken over in conversation

The Audit Room is run by Fabian Bürgy and his company BUERGY GmbH: independent second opinions from a human being on pitch decks, brands, digital products and strategic decisions. Fabian Bürgy brings more than 25 years of experience in brand building, digital products and creative leadership. His clients send him material that nobody else should see, and pay for the audit when they order.

The website already existed. Fabian Bürgy moved it to MADLAB // Publishing with Claude and carried on building it there. It went quickly, and two things that make people hesitate when they hear “website without a CMS” have worked without a hitch ever since: the secure upload of client files and payment with Stripe.

The starting point

A second opinion depends on trust. Anyone who has a pitch deck reviewed before a funding round, or a brand strategy before a launch, is handing over something that isn’t public yet. So the website has to do more than look good. It accepts files, links them to an order, takes the payment and makes sure the material isn’t lying around anywhere it shouldn’t be.

Then there’s the audience: founders, leadership teams, agencies and investors, not only in Switzerland. That’s why the website is written in five languages.

What the website does

• Ordering in a few steps: drop a file on the home page or select it, choose the audit, add the details, pay. Anyone who would rather share a link can start without a file.
• Three packages at fixed prices: Essential Audit for CHF 200.– within 24 hours, Deep-Dive Audit for CHF 800.– within 48 hours and Executive Audit for CHF 2’400.– within 72 hours, all including VAT.
• Secure upload: PDF, PowerPoint, Keynote, Word or ZIP, up to 50 MB per file.
• Payment with Stripe: the amount is paid when ordering, and the order is then complete.
• Five languages: English, German, French, Spanish and Portuguese, plus dedicated pages for each audit area, from pitch decks to AI-generated work.

How it works on MADLAB // Publishing

Taken over rather than rebuilt. Fabian Bürgy brought the existing website across with the import. MADLAB // Publishing pulls the published pages, together with images, fonts and scripts, into the workspace. From there it carried on in conversation with Claude: adjusting copy, adding pages, building in the order form. How the import works is explained on Take over an existing website.

The files don’t sit in the web root. For uploads and payment the website needs a little PHP, which comes with the “PHP” add-on. Uploaded files land in the website’s data area. It sits outside the public pages, can’t be reached at any address and isn’t touched by a new publish. Only the website’s own PHP can get at it.

The Stripe keys never go through the chat. Fabian Bürgy stored the Stripe secret key in the portal under “Data”, separately for the preview and the live website. Claude never sees it. The PHP reads it from the data area at runtime. That way you can try things in the preview with Stripe’s test mode while real payments run on the live site.

Testing happens in the preview. PHP runs in the preview even before the add-on is booked. So Fabian Bürgy could go through the whole flow, from upload to test payment, before the website went live. What to keep in mind is explained in PHP and the data area.

What we learned

• No CMS doesn’t mean no features. An upload for confidential material and a payment are exactly the things you used to install a CMS and plugins for. Here it’s a few PHP files written by Claude and a data area built for the job.
• Secrets belong in the portal. Keys and client files never appearing in the chat isn’t a minor detail for a service like The Audit Room. It’s the precondition.
• A takeover is a beginning, not an end. The old website was up in no time. Since then Fabian Bürgy has kept developing it in conversation, with every change saved as its own version.

What else you can build is covered in What you can build with MADLAB // Publishing. How an owner looks after his website by voice is shown in the oceya.ch case study.

Frequently asked questions

Can a website without a CMS accept files from clients?

Yes. With the “PHP” add-on the website accepts files and stores them in the data area. It sits outside the public pages and can’t be reached from outside.

How does Stripe get onto the website?

The website’s PHP talks to Stripe. You store the secret key in the portal under “Data”, not in the chat. For the preview you can enter a test key and try the whole flow before real payments run.

Does my AI assistant see my clients’ data?

No. There is deliberately no tool for the data area. You manage what’s in it in the portal. Your assistant writes the code that accepts the files, but it doesn’t read them.

Can I take over my existing website like this?

Yes. If you have the files, upload them as a ZIP. Otherwise the import takes over the published pages, as with auditroom.ch. After that, everything carries on in conversation.