Concepts
Access to AI is not yet operational use
Why giving people an AI chat interface does not by itself change how an organisation works, remembers, or decides.
Resources for building operating intelligence.
Practical notes on orchestration, ontology, review cadence, spend context, and practice-specific operating systems.
Proximity primer · 10 parts
What can AI actually do?
A ten-part Proximity primer on moving from individual assistance to systems that can participate responsibly in professional work.
Latest resources
Read resource
Methodology
Authority has to be clear before AI can act
Why action readiness depends on knowing which source, rule, and person can authorise a consequential step.
Methodology
Automation requests often begin with the output
Why a requested output is only the visible edge of the judgement, evidence, exceptions, and ownership that make automation work.
Concepts
Individual assistance does not create organisational memory
Why useful personal AI interactions disappear unless evidence, decisions, and commitments return to a shared operating system.
Methodology
Undocumented exceptions are part of the workflow
Why the work people most want to automate often depends on exceptions that have never been represented as part of the process.
Industries
Why Better Writing Cannot Fix Broken Management Reporting
Why polished property reports still fail when project evidence, definitions, cut-offs, and ownership break before the writing begins.
AI readiness and governance
How teams decide whether AI can answer, prepare, recommend, escalate, or act with accountability.
Methodology
The model is not the risky part
Why AI risk often comes from access, permissions, tools, memory, and review paths surrounding the model.
Concepts
From scattered context to a review packet
Why review packets are one of the most useful AI artifacts for professional teams working across scattered sources, owners, and decisions.
Methodology
What the first month of a Proximity deployment can establish
One possible first-month shape for defining a business outcome, auditing data and access, designing the connected model, testing an early workflow, and scoping the path to production.
Methodology
The First Draft
Why teams should build AI trust by using agents for internal preparation before delegating forward-facing work.
Methodology
What a good AI handoff looks like
A practical guide to AI handoffs that preserve sources, assumptions, missing context, ownership, next steps, and approval boundaries.
Concepts
Why AI needs source grounding
A concise guide to connecting AI outputs to inspectable evidence, provenance, freshness, and explicit gaps.
Operating intelligence and organisational context
The operating model behind useful AI: context, digital twins, shared memory, sources, cadence, and tools.
Methodology
Why Interfaces Need Operating Boundaries
A practical argument for designing AI and professional work interfaces as operating boundaries and worldviews: connected enough to share context, separate enough to preserve role, authority, focus, and review.
Concepts
Context is not hiding in your database
Why professional context is not just stored data, and why AI needs more than searchable records to support serious work.
Concepts
A tool helps you work. A system changes how work happens.
The difference between a personal AI tool that improves one task and a shared system that changes how work is captured, reviewed, handed over, and remembered.
Concepts
Most organisations forget their own promises
Why professional trust depends on whether a firm can remember what it said it would do.
Concepts
From scattered context to a review packet
Why review packets are one of the most useful AI artifacts for professional teams working across scattered sources, owners, and decisions.
Methodology
What the first month of a Proximity deployment can establish
One possible first-month shape for defining a business outcome, auditing data and access, designing the connected model, testing an early workflow, and scoping the path to production.
Automation vs human judgment
Where AI should automate, prepare, delegate, escalate, or leave responsibility with people.
Methodology
AI adoption fails when it becomes a launch event
Why durable AI adoption grows through repeated work, review, correction, and trust rather than a one-off launch.
Methodology
The model is not the risky part
Why AI risk often comes from access, permissions, tools, memory, and review paths surrounding the model.
Concepts
From scattered context to a review packet
Why review packets are one of the most useful AI artifacts for professional teams working across scattered sources, owners, and decisions.
Methodology
How to choose the first AI workflow
A practical decision framework for selecting a first AI pilot by recurrence, source coverage, reviewability, operating pain, and bounded consequence.
Methodology
The First Draft
Why teams should build AI trust by using agents for internal preparation before delegating forward-facing work.
Concepts
What makes AI useful in professional work
A practical framework for useful AI in professional services: better judgment, preparation, coordination, source review, and follow-through.
Industry operating context
Example walkthroughs of Proximity systems for manufacturing, food and beverage, hospitality, property and the built environment, architecture and design studios, and trading and sourcing.
Industries
Why Better Writing Cannot Fix Broken Management Reporting
Why polished property reports still fail when project evidence, definitions, cut-offs, and ownership break before the writing begins.
Industries
International Architecture Starts Before the Opportunity Arrives
How architecture studios cultivate overseas opportunity networks, then activate trusted local partners after a project is won.
Industries
The Hard Part of WhatsApp Ordering Starts After the Message
How conversational food orders can become clear preparation work without forcing customers and operators into an unfamiliar channel.
Industries
How Operating Judgement Survives Growth
Why operating judgement scales through reusable questions, conditions, and exceptions rather than a library of old answers.
Industries
A New Revision Does Not Carry Its Own Rationale
Why property-project changes become ambiguous when the revision travels further than its reason, owner, and acknowledgement.
Industries
Why Better Review Packets Do Not Solve Every Founder Bottleneck
The difference between design-review time lost to poor preparation and design authority that remains concentrated at the top.
Looking for deployment notes, security details, or a sector-specific operating model?
Contact