Inside a company that researches, builds and creates ventures, it is easy for things to drift. A client project starts to be called a product. A product idea starts to be called a company. A promising concept starts to be talked about as if it already exists.
We keep six distinctions on purpose:
| Not the same | Why it matters |
|---|---|
| Project ≠ company | A delivery for one client is not a business of its own |
| Product ≠ company | A product can live inside OceanBlu for years |
| Brand ≠ company | A name on a page is not a legal or operating entity |
| Venture ≠ automatically a company | A venture candidate becomes a company only when it is formed |
| Capability ≠ company | Research & Innovation, Technology, AI and Concord are operating areas, not subsidiaries |
| Industry ≠ organizational structure | We work across sectors without building a division for each |
Where an opportunity can go
Once an opportunity is validated, it can take one of several routes: a research project, a client project, an institutional project, a product, a platform or reusable component, a partnership, a Concord venture — or a pause, or a stop.
Each route needs different people, contracts and economics. That is why the route is chosen deliberately, at a gate, with the evidence on the table.
Nothing changes category on its own.
A project does not become a product, and a product does not become a company, until a decision is recorded. It sounds bureaucratic. In practice it is what keeps a young company honest about what it has actually built.