Context, Boundaries, and Scale: How CoAmi Workspaces Are Being Designed

Software should adapt to how an organisation operates, rather than forcing a business to change its processes around rigid, off-the-shelf tools.

That is the core philosophy behind CoAmi, the AI platform currently in development to help businesses and individuals create, maintain, and improve custom software.

When designing the system, our objective extended beyond allowing users to build software through conversation with our AI companion, Ami. We needed to solve an underlying architectural challenge: how do you manage context, data isolation, and governance when AI writes code and executes workflows across multiple projects?

The planned framework relies on two dedicated workspace environments: Business Workspaces and Personal Workspaces.

What is a CoAmi Workspace?

A workspace is being designed as the isolated home for a specific business or individual within CoAmi. It brings together software projects, connected systems, documentation, and the operational rules governing what Ami is permitted to do.

Instead of fragmenting your stack across separate platforms, one account will access multiple workspaces while keeping information and permissions separate. Whether you manage multiple companies or build a private side project, data remains isolated. A single workspace can also house several software projects, eliminating the need for a new workspace for every individual tool.

Business Workspaces: Software Built Around Your Business

Business Workspaces are being designed for sole traders, small businesses, and larger organisations requiring software suited to how they operate.

The starting point might be a specific requirement - such as a customer portal, a reporting dashboard, or an enquiry system. It could also address recurring operational friction, like staff entering identical information across tools or relying on spreadsheets only one person understands.

Ami’s intended role is to evaluate the challenge, ask targeted questions, and help establish what should change. With authorised access to relevant documents, spreadsheets, and connected systems, Ami will build a clearer picture of the business to inform the software it proposes and builds.

Potential project examples a service business might run in a Business Workspace include:

• Customer Portals: Secure hubs for managing requests, updates, and documentation.

• Internal Operations Systems: Customised tools for assigning and tracking work.

• Performance Dashboards: Dashboards displaying real-time metrics against targets.

• Workflow Automations: Integrations connecting existing platforms to reduce repetitive administration.

(These reflect potential project examples currently under development rather than ready-made, off-the-shelf products available today.)

Personal Workspaces: Turning Ideas into Blueprints

Personal Workspaces are being developed to support individuals with a project idea, hobby, community initiative, or personal software requirement.

That might mean exploring an app idea before forming a company, building a tool for a local club, or organising personal collections.

The experience is being designed around conversation. You explain your goals, and Ami works through the questions required to define the project scope. The initial output will be an Ami Blueprint - a plain-English summary outlining the project's scope, open decisions, and expected development costs where available.

Personal users will access the same core AI build capability as business users, but the interface will display only relevant controls, keeping team administration out of a clean personal setup.

Business vs. Personal Workspaces: Key Differences

Governance, Isolation, and Future Growth

Separation and security are fundamental to the workspace design. Access to one business will not grant access to another, and information will not be shared across contexts.

Within a Business Workspace, role-based permissions will govern project access. Company membership alone will not grant open access to every project, and workspace ownership will not expose a team member's private inbox or notes. Each workspace will also feature an Ami Policy covering operational rules such as spending limits, external communications, and actions requiring explicit human approval.

If a personal project transitions into a commercial enterprise, CoAmi is being designed to support converting a Personal Workspace directly into a Business Workspace - preserving its code, history, and Ami knowledge.

As AI makes custom development more accessible, more businesses will choose to build tailored software rather than conforming to rigid SaaS products. CoAmi Workspaces provide the structural foundation required to drive that shift.

CoAmi is currently in active development. You can learn more about the platform vision on the main CoAmi overview page or get in touch to discuss the project.