The Claude architecture
you can build on yourself.
It starts with a paid discovery and architecture phase. Before proposing anything, I map how your property, serviced accommodation, and advisory arms actually run, then design a clear Claude architecture of Projects, knowledge bases, and custom instructions with one shared knowledge foundation at the center. Your business logic lives in that foundation, independent of any single tool, so you never get locked in. We prove value on a few high-impact workflows first, then scale cleanly from a structure simple enough for you to understand and own, and robust enough to carry every automation that comes later.
The potential is clear. The architecture isn't.
You can see what Claude could do across your businesses. Getting there without creating a tangle is an architecture problem, and architecture is exactly what most AI setups skip.
Potential you can see but can't build
You already know where AI could remove friction and unlock time. The gap is bandwidth and structure: without the right foundation in the right order, the potential just sits there.
AI setups become a tangle
Bolt Projects and prompts together ad hoc and six months later it is a mess nobody understands. Scale is what exposes the shortcuts taken at the start.
Tool lock in quietly traps you
When your business logic lives inside one tool's features, expanding or switching means rebuilding from scratch. A foundation tied to a vendor is a foundation you do not really own.
Understand first. Then architect for scale.
The engagement opens with a paid discovery and architecture phase, and you own the blueprint whether or not we continue. I spend that phase understanding each arm of the business, property, serviced accommodation, and advisory, and mapping the processes where AI actually removes friction. From there I design a clear Claude architecture: Projects, knowledge bases, and custom instructions, all organized around one central knowledge foundation that holds your business logic in a single place. That foundation is deliberately tool-agnostic, so Claude and any automation tools connect to it rather than trapping your logic inside one vendor's features. We build in a sensible order, foundations first, proving value on two or three high-impact workflows before anything ambitious, so it scales cleanly instead of becoming a tangle. Everything is documented with a recorded walkthrough, your NDA is signed up front and access stays scoped, and the whole point is that you can understand the logic and extend it yourself without depending on me.
What you get. Phase by phase.
A low-risk phased engagement. Paid discovery first, then a tool-agnostic foundation, then proven workflows, then clean scale.
- Working sessions to understand your property, serviced accommodation, and advisory arms
- Key processes mapped, with the friction points where AI unlocks the most time
- A clear Claude architecture: Projects, knowledge bases, custom instructions, and how they fit
- A prioritized build order and blueprint you own whether or not we continue
- One central knowledge base holding your business logic, context, and SOPs
- Structured so Claude Projects draw from it instead of duplicating instructions
- Kept independent of any single tool or vendor, so you never get locked in
- Simple enough to understand at a glance, robust enough to extend for years
- The two or three highest-leverage workflows automated first
- Claude Projects and custom instructions built on the shared foundation
- Connected to the tools you already use where it genuinely makes sense
- Value proven on real work before anything ambitious gets built
- Additional workflows added cleanly on the same architecture
- Connectors and automation tools like Zapier where they earn their place
- Full documentation of how everything is structured and why
- A recorded walkthrough so you learn the approach and extend it yourself
- New arms and workflows added as the business grows, always with scale in mind
- Periodic architecture reviews so the system stays clean instead of tangling
- NDA respected, access scoped rather than handed over wholesale
- You stay independent: extend it yourself, with no dependency on me to maintain it
Foundations first. Then it scales.
A phased path where each stage proves itself before the next. Click any stage to see what it delivers.
What this stage delivers
- Working sessions across property, serviced accommodation, and advisory arms
- Key processes mapped with the highest-value friction points identified
- A clear Claude architecture of Projects, knowledge bases, and custom instructions
- A prioritized build order and blueprint you own either way
What this stage delivers
- Central knowledge base holding business logic, context, and SOPs
- Claude Projects structured to draw from it, not duplicate it
- Kept independent of any single tool so you never get locked in
- Simple to understand at a glance, robust enough to grow on
What this stage delivers
- The highest-leverage workflows automated first
- Claude Projects and custom instructions on the shared foundation
- Connected to the tools you already use where it makes sense
- Value proven on real work before anything ambitious is built
What this stage delivers
- Additional workflows added cleanly on the same architecture
- Connectors and automation tools like Zapier where they earn their place
- Full documentation of how it is structured and why
- A recorded walkthrough so you learn the approach and extend it yourself
Let's start with discovery.
A short call to talk through the discovery and architecture phase, how I'd decide what to build first, and how I handle a scoped-access NDA before touching anything sensitive. It is a low-risk way for both of us to see how we work together, and you own the blueprint either way. Happy to walk through commercials on the call.