Work
Early proof, described honestly.
ANOVA PROJECTS is a young company. Rather than decorate this page with percentages nobody measured, here is what we have actually built, what it does, and what we intend to be able to prove about it.
Our rule: a number appears on this site only when it was measured and can reasonably be attributed to something we did. Everything else is described as what it is.
Website, booking and reminders as one system
A business whose enquiries, appointments and reminders lived in three places that did not know about each other.
The problem
Customers found the salon, then had to work to become customers. Booking meant a phone call during opening hours. Appointments were confirmed manually. Reminders depended on somebody having time to send them, which on a busy day nobody did, and a missed appointment is a slot that cannot be sold twice.
What we built
A website designed around booking rather than around describing services; a booking path a customer can complete at eleven at night; an automated reminder system that runs without anyone starting it; and the cloud and automation infrastructure underneath, which we host and maintain.
What happens next
We are collecting the operating data needed to say something concrete about no-show rates and booking volume. When those numbers exist and can be attributed fairly, this becomes a full case study, with the method shown, not just the result.
Scope
- Website design and build
- Online booking infrastructure
- Automated appointment reminders
- Cloud hosting and infrastructure
- Automation between the moving parts
- Ongoing maintenance
What we are measuring
- Share of bookings made outside opening hours
- No-show rate before and after reminders
- Admin time spent per week on scheduling
A restaurant website built around atmosphere, menu and easy contact
A design study for a Greek taverna in Berlin-Wilmersdorf, built to find out what a restaurant site should actually do for the people who run it.
The problem
Most restaurant sites make a guest work. The room is hidden behind a stock photo, the menu is a PDF that will not open properly on a phone, and the way to get in touch is a phone number in the footer. The decision to walk in happens in about twenty seconds, and the site spends them on the wrong things.
What we built
A German-first site with a Greek version, opening on the room itself: the menu as real, readable pages rather than a download, the dishes photographed as they are served, and contact details that a phone can act on in one tap. Static output, so it loads on a weak connection in the street outside.
Being straight about it
This is our own concept, not commissioned work, and it is not published as the restaurant's website. The photographs in the build are placeholders, and the opening hours, prices and legal texts are unconfirmed. We are showing the design thinking, not claiming a client result. No reservation system has been built.
Scope
- Concept and art direction
- German and Greek content structure
- Menu as readable pages, not a PDF
- Static build, no tracking
Business Overview Dashboard
One screen for the numbers an owner checks on a Monday morning, built to show what a dashboard is for before anyone pays for one.
What we built
Enquiries and where they came from, bookings against free capacity, what is still open and who owes what, and the week against the one before it. Each panel is there because a business owner named the question, not because the chart library had one going spare.
Being straight about it
Every figure in it is invented. It is a demonstration of a layout and a way of thinking, not a report from a real company, and it will always say so on the screen. The interactive version is being prepared for demo.anova-projects.com and is not linked here until it is live.
Panels in the concept
- Enquiries and their source
- Bookings against free capacity
- Open items and who owes what
- This week against the last one
The systems we built for ourselves first
Not client work. The reason client work does not have to wait for a vendor.
Before selling anyone an AI agent or an internal tool, we built them for ourselves: small applications, agents connected to real tools rather than demo data, API and MCP integrations between systems that were never designed to talk, automations that run unattended, and infrastructure we host and operate ourselves.
It matters commercially for one reason. When a client problem needs something that does not exist as a product, we can build it instead of explaining why it is not possible.
What happens next
Patterns that keep recurring become reusable components. That is how delivery gets faster and how the eventual Business Operating System stops being a slogan.
Capability this demonstrates
- Building small applications end to end
- AI agents wired into real tools
- API and MCP integrations
- Unattended automation
- Self-hosted infrastructure and operations
- Choosing to build rather than pay for SaaS that nearly fits
Measurement
How we will report results.
Step six of our process is "measure", and it is the step most agencies quietly skip.
Agreed before we build
We decide together what should change, and how we would know. If we cannot name a measure, that is a signal about the project.
Measured after launch
A number before, a number after, and an honest note about everything else that was going on at the same time.
Published only with permission
Case studies appear here when the client agrees and the result is attributable. Never a rounded-up figure to fill a gap in a layout.
Want to be the next project on this page?
Early clients get unusual attention, and a company that badly wants the result to be worth writing about.
Running a content account as a system
Practical, hands-on experience producing and publishing content, stated for exactly what it is.
What we did
Built and ran a content account end to end: deciding what to make, producing it, editing it, publishing on a rhythm, and reading what the numbers said afterwards. The account reached roughly a thousand followers. One video reached about 150,000 views and around 6,000 likes.
Being straight about it
That is real experience, and it is why we can build content systems that survive a busy month rather than a content calendar nobody keeps. It is not yet evidence of a repeatable growth engine, and we will not present it as one. If you want followers guaranteed, we are the wrong company.
What happens next
The valuable part of this work is the system around it: profile structure, a consistent visual language, production that does not depend on inspiration. That is what we sell, and what we intend to measure on client accounts.
Figures we can stand behind
Own account, own content. Presented as experience, not as a client result.