Not a website with an app bolted on. One design language, one build process, one relationship. Your website finds new clients, your app keeps them, and the two talk to each other.
Sign-ups, bookings and purchases sync automatically between website and app. No manual imports, no copy-pasting between platforms, no "why isn't this showing up" at 9am on a Monday. One system that behaves like one system.
When a cobbled-together stack breaks, everyone points at someone else. With Oak there is one person responsible for the whole thing. One monthly conversation, one point of contact, one invoice. And when something breaks at an inconvenient time, you know exactly who to message.
Delivery runs in sequence: the website is designed and built first, then the app. Eight to twelve weeks in total, and the site goes live while the app is still in build and testing. Something real is working within weeks, not unveiled at the end.
A client finds you on Google, lands on your website, signs up, and appears in your CRM automatically. They book an appointment and loyalty points accrue without anyone pressing anything. They refer a friend and it shows in the data. That's what "integrated" means. Not two things that technically coexist.
Worth knowing before you decide. Root can grow into Oak later, but designing the site and the app together from the start is cleaner than retrofitting an app around a finished website. If you're on the fence, the call is where to settle it.
Copy drafted from conversation as standard. Integrations scoped on the discovery call. One relationship, one monthly arrangement, both platforms looked after.
Someone signs up on your website, they appear in your CRM. They book online, loyalty points accrue. You want a report on the whole thing, it's already there.
You could stitch this together yourself using three different tools and a lot of determination. People do. They also spend about six hours a month keeping it all working. Your call.
Genuinely integrated. The two systems are built to talk to each other from the ground up, not two separate products sharing a login. Sign-ups on the website appear in the app CRM automatically. Bookings made through either route sync to the same place. It behaves like one system because it is one system.
Depends what's in it. No two Oaks are the same, so there's no figure on this page. Scope is agreed on the discovery call and everything is quoted before anything is signed.
That's fine, and Root is the right starting point. The site gets built so an app can join it later without ripping anything up. If you already suspect an app is coming, say so on the call: designing both from the start keeps the design language consistent and the joins cleaner.
Eight to twelve weeks, delivered in sequence: website first, then app. The site goes live early while the app is still in build and testing, so you're not waiting three months to have something real online.
No. The app is a Progressive Web App: accessible via a link or QR code, no App Store required. Clients can add it to their home screen if they want, or just use the link.
Hosting, SSL, monitoring and day-to-day changes for both the website and the app. Text, images, prices, hours: covered, no time cap. New features and new integrations are a new conversation, quoted before anything is agreed. One arrangement, one invoice, both platforms looked after.
You own everything. The domain is yours, the website code sits in your own Git repository, and your customer data, in the app and out of it, is yours. Verdant runs everything, you own everything.
Yes, on a case-by-case basis. Mention it on the discovery call.
Tell me what's broken, or what's missing. You'll get a straight answer on whether it's worth fixing and roughly what it would take. No pitch deck, no follow-up sequence.
Forms not your thing? Email George directly. It lands in the same place.