Resources
Everwood publishes practical business and technology guides, product guidance for getting the most out of the platform, and transparent development notes — all aimed at appointment-based, local service businesses.
Featured guides
Plain-English guides on the technology and decisions service businesses actually face.
A website is often the first place a potential customer learns about a business — long before they call, visit, or buy. This guide explains why a website generally matters for modern businesses, the common types of business websites, and the kinds of things a website can do beyond just looking nice.
How AI booking assistants connect to your calendar and customer data is changing — from custom, one-off API integrations toward a newer open standard called MCP. This guide explains both approaches in plain terms and what actually matters when evaluating an AI-powered booking feature.
Zapier and similar platforms are a great starting point for automating a growing service business — until the number of Zaps, their cost, and the risk of silent failures start to outpace what they're worth. This guide covers the signs a business has outgrown point-to-point automation and the two paths forward.
Browse by topic
Practical automation guides for small business owners and teams.
Practical web development guides for small business owners and teams.
Practical marketing guides for small business owners and teams.
Practical wifi guides for small business owners and teams.
Practical pc guides for small business owners and teams.
Product help
Dedicated help articles for setting up Booking, services, workers, availability, and reviews are still being written. For now, the best way to learn the platform is to explore the products or try the live demo — and our team can walk you through setup directly.
Product guides are growing — this section will expand as the platform does.Building in the open
Build Notes are field reports on product decisions, features shipped, problems solved, bugs and lessons, and development progress.
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.
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.
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.
What's here
Practical, customer-facing education for running, marketing, and improving a service business.
Transparent updates about how Everwood is designed and developed.
Instructions for using Everwood, growing over time. For now, explore the products or ask our team.