BookWise
One tool to manage them all.
One tool instead of three. Built for small businesses that don't need enterprise software, just something that actually works.
The Background
A friend of mine runs a law firm in Chile. He was paying for a website host, a scheduling tool, and trying to make sense of HubSpot — three separate subscriptions, three separate logins, none of them talking to each other properly — to do something pretty simple: have an online presence, let clients book appointments, and keep track of who he'd spoken to.
That felt like a solvable problem. So I started building BookWise.
The idea is straightforward: small businesses don't need Salesforce. They don't need a dedicated CMS with a developer on retainer. They need a digital presence, a way to take bookings, and somewhere to keep track of their clients — all in one place, without a monthly bill that assumes they're a medium-sized enterprise.
The Challenge
The tricky part wasn't building any one of these features — booking systems, CRMs and CMS builders all exist as standalone tools for good reason. The challenge was to build them as a coherent, single product, where each part makes the others more useful.
A booking that automatically creates or updates a client record. A calendar that syncs with Google Calendar, so nothing lives in isolation. A CMS that's simple enough that a lawyer in Santiago can update his own website without calling anyone. All of it under one login, one subscription, one place to look.
Building it as a multi-tenant system from the start added architectural complexity early on — every decision had to account for data isolation between organisations — but it was the right call. That's what makes it a product rather than just a bespoke solution for one person.
The Process
Built with Laravel and Filament PHP on the TALL stack. Multi-tenant architecture with full data isolation between organisations. Google Calendar sync handles two-way appointment management so clients and business owners are always looking at the same source of truth.
The app is also fully internationalised — currently English, Spanish and German — partly because the first real use case is Chile, and partly because if this is going to be a product, it should work for more than one market from day one.
My co-founder on this is the lawyer friend who inspired it. We're currently applying for a startup grant in Chile. The project has gone from "wouldn't it be funny if" to something I'm taking seriously.
Lessons Learned
Scope is the enemy of shipping. A tool that replaces three products has to resist the temptation to become four. Every feature decision has been a negotiation between "this would be useful" and "this would delay everything else." I'm still having that negotiation.
The other thing I keep coming back to: the hard part of building for small businesses isn't the technology — it's the abstraction. You're not building for developers who can read documentation and figure things out. You're building for someone who's also answering phones and doing the actual work of their business. Every unnecessary click is a real cost. That constraint makes you think more carefully about every decision, which I've found genuinely improves the product.