Build Notes

Building Everwood in the open

A working journal of how the platform is made — what shipped, the decisions behind it, the problems solved, and what each experiment taught us.

Browse Build NotesExplore Products

Latest update

LearningEverwood Booking

Our Booking Widget Is Guarded by the Website It Sits On. A QR Code Does Not Have One.

I asked for research on giving every business one permanent booking link, and got back a careful answer about names, redirects and printed codes. Then I read our own booking code and found the thing the research never mentions. What actually protects a booking today is not the key in the page. It is the website address the request comes from, and not one of the new places we want customers to book from has an address we could check.

Read the update →Related: Booking

The archive

Every Build Note, newest first

LearningEverwood Booking

The Cancel Button Is the Easy Half. We Have No Rules to Put Behind It.

I expected this research to be about proving a customer owns their booking. Then I found that our customers can already cancel and reschedule, by talking to the booking assistant, while the account they sign into can only show them their appointments. The capability exists and the button does not. What is missing is smaller to describe and harder to skip: a business cannot set a cancellation rule anywhere in Everwood, so a cancel button today could only ever say yes.

LearningEverwood Booking

Nine People Get the Email. One Gets the Slot.

I set out to design a waitlist and spent most of the research on a question I thought was already answered: what exactly happens when someone cancels. Our booking system already refuses to double book, so the danger was never two people in one chair. The danger is nine people opening an email about an appointment one of them can have. The part I now think has to be built first is the part nobody demos.

LearningEverwood Booking

Our Reschedule Email Says Update. The File It Sends Cannot.

I went into this research expecting to scope Apple and Google Wallet passes. What I found first was a promise we were already making and could not keep. When an appointment moves, we email the customer a button that says update your calendar, and the file behind that button has no way to say it replaces anything. A wallet pass would not fix that. It would make the same promise louder, and put a service we have to keep running behind it.

LearningEverwood Platform

Making Booking Agent-Accessible Is Not an API Problem. It Is a Trust Problem.

I spent a research cycle on what it would take for an AI agent, not a person, to book an appointment through Everwood. I went in thinking the answer was to publish some endpoints. The research pushed back. An agent is a probabilistic client that retries, caches, and occasionally invents availability. Reads are cheap to expose. Writes are where the trust boundary actually lives.

ExperimentingEverwood Platform

The Hard Part Is Not Building the App. It Is Making It Usable Without You.

Every local app has the same hidden problem. It works perfectly for the person who built it. The builder knows where everything is, why it is set up that way, and what to do when something looks broken. The real test is whether a business owner can use it on their own.

ExperimentingEverwood Platform

The Dashboard Change That Made My SaaS Feel Like a Platform

My dashboard was a Booking dashboard with Everwood branding. When I clicked "All Products," the sidebar disappeared and it felt like a different app. The fix was not a redesign. It was a shift in who owns the shell.

See the products these updates are shaping

Explore ProductsStart free

The information on this website is provided for general educational purposes only and may not apply to your specific setup or environment. It should not be considered professional advice. Always consult a qualified technician when appropriate.