Not a build with extras. George joins the business as a consultant a few days a month: design, build, and finding the friction points nobody has had time to fix.
George comes in a few days a month and works where the work is: design decisions, build priorities, the processes everyone quietly routes around. Not a supplier emailing deliverables from a distance. Someone in the room who knows how the place runs.
There's a build in the partnership: a hand-coded website on fast global hosting, a custom app that runs in any browser with no app store in the way, integrations with the systems you already use. No page builders, no templates. The person building it is the same person who scoped it, in the room where it'll be used.
Every business has them: the spreadsheet that's secretly load-bearing, the process with three workarounds, the report nobody trusts. Part of the arrangement is hunting these down and deciding, together, which are worth fixing and which are fine as they are.
Before Verdant, George was a Product Owner at MetLife, deciding what got built, in what order, and what didn't get built at all. That's the discipline Canopy runs on. Sometimes the most valuable sentence in a partnership is "that isn't worth building".
Everything built under Canopy is looked after as part of the arrangement. Hosting, monitoring, fixes, the small changes that keep things current. There's no separate care contract to manage, because the partnership is the contract.
Canopy is scoped from the conversation, quoted before anything is agreed, and never the same twice. The discovery call is where yours takes shape.
Most agencies build the thing, invoice the thing and move on. Fine, if the thing was ever the problem. Usually the real problem is the dozen small ways the business fights its own tools, and nobody stays around long enough to notice.
Canopy is for businesses that want someone in it with them. A consultant a few days a month, working through design and build, finding the friction points, and staying accountable for whether any of it made a difference.
No two arrangements are alike, which is why this page has no spec sheet. Everything is scoped from the conversation, and the conversation starts with a discovery call.
It's scoped from the conversation. No two Canopy arrangements are alike, so there's no standard price to publish. The discovery call is where scope, shape and investment get worked out, and everything is quoted before anything is agreed.
A conversation about your business: what's working, what isn't, and where the friction sits. No pitch, no pressure. By the end you'll have a clear sense of whether a partnership makes sense and what working together would involve.
Builds inside the partnership run to agreed timelines, and an agreed timeline holds, or you hear about it in advance rather than after the fact. The partnership itself is ongoing: a few days a month, for as long as it keeps earning its place.
The partnership carries on. The build is one part of the arrangement, not the point of it. George stays in the business a few days a month, and everything built is looked after as part of the arrangement. Nobody gets handed to a support queue.
You do. Your domain is registered to you, the code sits in your own Git repository, and your customer data is yours. Verdant runs everything, you own everything. No licensing arrangements, no lock-in, no 'you can only host this with us'.
They will. That's rather the point of having a consultant inside the business. Changes get discussed in the room, assessed, agreed, then built. Because the arrangement is ongoing, a change of direction is a conversation, not a crisis, and never an invoice that appears from nowhere.
Yes. Integrations with your existing software are part of what Canopy is for, and working out where your current systems fight each other is usually where the friction-hunting starts.
Book a discovery call. If Oak would do the job, you'll be told so. Selling a partnership where a straightforward build would do isn't good for either of us.
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.