Structured data
Knowledge base, records, documents, storage, wiki content, and permission-aware context.
Internal direction briefing
Sharpen the core.
Keep the capability.
vama is narrowing its centre of gravity around the two highest-value assets: vama Claw as the execution surface, and vama Enterprise Control as the governed control plane.
Product direction · Development alignmentClaw
+ Control
+ Control
Skills & SOPscentrally governed
Existing systemsstill connected
Minimal Packcore substrate
Auditvisibility by design
The message for the team
This is a focus pivot—not a restart.
The work already completed remains valuable. The change is where the product strategy places the strongest emphasis and how we sequence future capability.
Nothing important is being thrown away.
Existing platform, knowledge, desktop bridge, mobile, connector, and workplace work all support the broader harness. We are reducing unnecessary scope in the Workplace Pack and investing more deeply in Claw, Control, Skills, connectors, security, and observability.
What changed
From broad workspace ambition to a focused enterprise AI harness.
Previous emphasis
- Build a broad, unified workplace platform.
- Encourage people to depend on vama’s own functions.
- Expand workplace utilities toward feature coverage.
- Make the vama family the primary environment for work.
- Assume humans will navigate many product surfaces directly.
New emphasis
- Work alongside Google Workspace, Microsoft 365, CRM, ERP, and specialist systems.
- Make Control the governed AI access and visibility layer.
- Make Claw the primary natural-language interaction and execution surface.
- Keep the Workplace Pack minimal, structured, and agent-operable.
- Encode company SOPs as Skills and apply them during execution.
Product direction matrix
How to interpret the pivot across the product family.
| Area | Direction now | Team implication |
|---|---|---|
| vama Enterprise Control | Core focus Private control plane for identity, policy, model routing, MCP/API access, Skills, approvals, and audit. | Prioritise reliability, security, connector mediation, visibility, and administrative clarity. |
| vama Claw | Core focus Local agent and primary employee interface for outcomes, tools, Skills, and desktop work. | Prioritise local execution, enterprise sign-in, Skills, tool wrappers, policy projection, and resilient UX. |
| Skills and SOPs | Core focus Company operating procedures become governed, versioned, executable Skills. | Build Skill retrieval, eligibility, versioning, signing, distribution, invocation, approval, and audit into the core loop. |
| Private Workplace Pack | Deliberately minimal Structured data and general functions that Claw can operate. Email function: development discontinued; it no longer adds value under the revised direction. | Build dependable substrate functions. Avoid niche feature accumulation and unnecessary manual screens. |
| Existing systems | Keep connected Google Workspace, Microsoft 365, CRM, ERP, databases, and industry systems remain relevant. | Invest in connectors, permissions, data-flow policy, and stable interfaces rather than replacement modules. |
| Mobile and leadership | Extend the harness Mobile provides human oversight; Command/WorkOS provides leadership visibility as capability matures. | Keep these aligned to dispatch, approvals, results, governance events, and organisational visibility. |
The new priority stack
01Control
Govern external access, policy, identity, credentials, and visibility.
02Claw
Give employees one natural-language surface for governed execution.
03Skills
Turn company SOPs into executable, versioned operating procedures.
04Minimal Pack
Provide structured data and general functions—not a giant office suite.
System architecture
Control is the centre of governed external access.
Claw executes locally. Control decides what may happen outside the device, which Skill applies, which data route is permitted, and what must be recorded.
Employee deviceClaw · local files · desktop applications · local checks
Human oversightMobile dispatch · approval · intervention · results
vama Enterprise
ControlIdentity and device health
Policy and data classification
Skill registry and SOP orchestration
Credentials and model routing
MCP/API gateway
Audit, visibility, approvals
ControlIdentity and device health
Policy and data classification
Skill registry and SOP orchestration
Credentials and model routing
MCP/API gateway
Audit, visibility, approvals
Existing systemsGoogle Workspace · Microsoft 365 · CRM · ERP · databases
Approved endpointsLLMs · MCP servers · APIs · company services
The new execution loop
Every governed request follows the same mental model.
01Ask
Employee describes the desired outcome.
02Recognise
Claw detects the tools, data, and possible SOP.
03Resolve
Control returns the eligible Skill and context.
04Check
Policy validates identity, device, data, and action.
05Execute
Claw uses local functions, Pack functions, MCP, or APIs.
06Record
Skill, route, approval, and outcome are auditable.
Skills and SOPs
Employees ask for outcomes. The system applies the procedure.
The organisation’s operating discipline should be encoded in the system instead of relying on every employee to remember every manual step.
Marketing message
Apply approved tone, structure, required disclosures, and sign-off.
Client communication
Use permitted fields, correct template, routing, and review rules.
Quarterly report
Use approved data, calculations, disclosures, and publication approvals.
Expense claim
Extract evidence, apply coding rules, and route by threshold.
Skill ownership, version, eligibility, allowed data sources, permitted tools, output requirements, approval checkpoints, rollout scope, revocation, and execution evidence.
Interpret the user’s intent, request the relevant Skill, carry out the approved sequence, ask for clarification when needed, pause for approval when required, and present the result naturally.
A simple request-and-result interaction. The complexity of the SOP is absorbed by the harness, while the employee retains visibility and authority at the points the organisation defines.
Private Workplace Pack
Small substrate. Broad agentic usefulness.
The Pack should support Claw with reliable, structured data and general functions. It should not become a feature-count competition with mature office or industry suites.
General functions
Read, search, create, update, classify, compare, calculate, route, notify, and request approval.
Agent-operated workflows
Claw composes the functions into outcomes while retaining Skill, tool, approval, and data-flow traceability.
Scope discipline rule
If a capability is already available in the customer’s current systems, or can be expressed through a general function and a governed Skill, it does not automatically justify a new specialist module in the Workplace Pack.
The relationship evolves with use
As staff increasingly use Claw for daily work, Claw can build a richer, permission-aware understanding of their working context, preferences, recurring tasks, and interaction patterns. This should be used to make the working relationship more effective—not as unrestricted surveillance. Within the controls defined by the organisation, aggregated and interpreted knowledge about workflows and staff behaviour can improve recommendations, Skills, routing, and organisational capability.
When the company subscribes to the Private Workplace Pack, staff may gradually rely less on third-party office tools because Claw can use the Pack’s private functions on their behalf. Employees can still review and approve the resulting records, documents, and outputs, but they need not manually operate a word processor, spreadsheet, or specialist screen for every task.
What stays valuable
Existing work remains part of the harness.
Continue investing in
- Private deployment and server foundations
- Knowledge ingestion, retrieval, and permission-aware context
- Companion local bridge and device-side processing
- Connector patterns, APIs, and existing-system interoperability
- Mobile dispatch, capture, approvals, and human oversight
Increase emphasis on
- Claw enterprise sign-in and Control connectivity
- Control-side policy, routing, credential, and audit systems
- Skills Registry, SOP orchestration, signing, versioning, and distribution
- Aggregation and interpretation of permitted institutional knowledge and staff behavioural data within Control for analysis, organisational insight, and deeper capability
- Tool wrappers and policy enforcement independent of prompts
- Observable, reliable end-to-end execution
Keep deliberately narrow
- Niche office-suite feature parity
- Specialist modules already covered by customer systems
- Manual screens that Claw can operate through general functions
- Functions without a clear role in the control, knowledge, or execution loop
Definition of done
The pivot succeeds when the system feels simple to the employee and rigorous to the organisation.
For employees
- Ask Claw for an outcome in natural language.
- Receive a useful result without memorising every SOP.
- Understand when an action needs approval.
- Work across local apps, existing systems, and private vama functions.
For the organisation
- Know which agent, user, device, Skill, and connector acted.
- Change an SOP centrally and distribute it systematically.
- Control data routes, tools, models, and credentials.
- Investigate outcomes through reliable audit and observability.
One-sentence internal direction
vama is not trying to rebuild every business application; it is building a private, governed AI harness in which Claw becomes the employee-facing executor, Control becomes the enterprise source of policy and visibility, Skills encode SOPs, and the Workplace Pack provides only the minimal structured functions the harness needs.