01
Imagination and discovery
Identify repeated problems, hidden context, trust concerns, and workflow moments where AI could create surplus value with the right operating context.
/~
Operating intelligence for professional practice.
A forward-deployed platform that makes your work observable, your decisions grounded, and your actions governed around how your team actually works.
Acme LLP
ActorMONOidWyrdOSPilfer
CM
Client Matters
~/Practice/client-matters
Client files, meeting prep, follow-ups, and approved drafts.
DocsCalendarTasks
6 sessions
PO
Practice Operations
~/Practice/operations
Admin workflows, billing cleanup, templates, and internal notes.
TasksSpending
3 sessions
CD
Compliance Deadlines
~/Practice/compliance
Filing dates, renewal reminders, evidence packs, and review history.
CalendarDocsTasks
4 sessions
RN
Referral Network
~/Practice/referrals
Partner outreach, referral notes, and follow-up drafts.
Messaging
2 sessions
World-state ontology
Mon 8
16° Rain
Daily Note
Tue 9
18° Drizzle
Daily Note
Wed 10
17° Drizzle
Daily Note
Thu 11
16° Rain
Daily Note
Fri 12
21° Cloudy
Daily Note
Sat 13
21° Cloudy
Daily Note
Sun 14
21° Cloudy
Daily Note
09:26
Ritual
Practice review
- Open files and deadlines
Ritual
Client consultations
- Intake calls
Ritual
Case preparation
- Evidence and notes
Ritual
Client sessions
- Booked appointments
Ritual
Documentation
- Notes and records
Ritual
Advisory work
- Recommendations
Ritual
File triage
- Urgent items
Ritual
Client preparation
- Meeting packets
Ritual
Professional analysis
- Research
Ritual
Compliance review
- Requirements and risk
Ritual
Client meetings
- Decision support
Ritual
Document drafting
- Deliverables
Ritual
Accounts admin
- Payments and expenses
Ritual
Client follow-ups
- Open questions
Ritual
Records cleanup
- Files
Ritual
Continuing education
- Reading and updates
Ritual
Deep file work
- Complex matter
Ritual
Light planning
- Calendar and priorities
Ritual
Week setup
- Deadlines and prep
/ Use cases
Built for work where context is hard to hold.
Each use case begins with a focused operating area where the work already happens, then helps the team see what needs attention, what is missing, and what should move next.
The examples here show where that operating layer can be applied across different teams, workflows, and review rhythms.
Legal and advisory practices
For firms where client work depends on evidence, deadlines, judgment, and review. The system can be configured to keep matter context together: what changed, what is missing, which documents support the current position, and what needs approval before anything moves forward.
Read use caseAccounting and financial control
For teams managing receipts, approvals, renewals, spend, owners, and review cycles. This can be configured to make the control context visible: what needs attention, what evidence exists, who owns the decision, and what should be escalated before action.
Read use caseArchitecture and design studios
For studios where work moves through references, options, client conversations, consultant input, and review notes. For this kind of practice, the system can keep the project story together: why decisions were made, what changed after critique, and what needs preparing before the next review.
Read use caseEngineering and surveying teams
For teams working across site evidence, drawings, inspections, constraints, contractors, and formal approvals. In this setting, it can keep the technical record clear: what changed, what supports it, which issues remain open, and who owns the next step.
Read use caseTherapy and care practices
For teams where continuity, sensitivity, and handover context matter. The system can be configured to prepare reviews and follow-ups from the approved record while keeping sensitive decisions and client-facing actions behind human judgment.
Read use caseRelationship-led businesses
For galleries, hospitality, media, partnerships, and founder-led teams where trust lives across conversations and follow-through. For relationship-led work, it can keep relationship memory visible: what was promised, who owns the next step, what context matters, and what needs a careful follow-up.
Read use case/ How It Works
Built with your team.
We embed an engineer with your team to understand the systems, workflows, decisions, and review habits already in motion, then keep working alongside you as the operating layer is deployed, adopted, and expanded across the business.
02
Scoping
Define the operating area: the source systems, evidence, language, approvals, data boundaries, and review rhythm needed to make the workflow loop useful and visible.
03
Prototyping + Testing
Build a prototype layer around the chosen workflow and test it with the team, using real materials, real decisions, and real review conditions to understand what the system needs to support.
04
Deployment
Turn the proven prototype into an adopted workflow, establishing the ownership, controls, feedback rhythms, and operating habits needed for it to run reliably and shape the next loop.
/ Operating Platform
Clear infrastructure for complex work
Starting from a three-layer model of professional work, this gives every deployment a common structure while still allowing the system to be configured around the language, workflows, systems, and constraints of each practice.
Ontology
The shared model of how the practice thinks: principles, terminology, goals, standards, and the reasons decisions are made a certain way.
Rituals
The repeated operating rhythm of the practice: reviews, handovers, follow-ups, ownership, deadlines, and moments where judgment is required.
Spend
The resource context behind the practice: subscriptions, vendors, tools, and commitments understood by what they support and who owns them.
/ Orchestration layer
Orchestrate across every domain
Actor is a minimal-setup custom agent harness connected directly to your operating twin. It can answer questions, complete bounded tasks, set up workflows, prepare summaries and follow-ups, and queue actions for human review before anything important is written or sent.
/ Trust and control
Keep judgment in the hands of the practice.
Proximity is built for environments where expertise, accountability, and professional discretion matter. The system can prepare context, surface patterns, draft next steps, and organize review queues, but sensitive decisions and external actions remain governed by the people responsible for the work.
Approval boundaries
/ Deployment and data control
Built for existing enterprise boundaries.
Proximity does not require every practice to adopt the same hosting, model, or data posture. Each deployment can be configured around the organization's infrastructure requirements, approved model providers, existing subscriptions, and internal governance policies.
Custom deployment
Run Proximity in a managed tenant or self-host it within the organization's own environment.
Model compliance and flexibility
Use approved model providers and existing subscriptions instead of being locked into a single model stack.
Workspace control
Keep operating context, permissions, and access scoped to the teams, workflows, tenants, and environments defined for the deployment.
/ Start
Start with one operating area. Expand from there.
Begin with a focused review rhythm, workflow, or team where better operating context would immediately change the quality of preparation and judgment.