Approach

How Primanza runs a product company.

Each product is built as a complete business, brought under Primanza ownership, and then operated. What follows is organised by what each decision is for; the technical detail sits underneath as evidence.

Product independence

A product should be able to serve its market without asking permission from another product. That is a commercial requirement before it is a technical one: pricing, packaging, release timing and positioning all have to be decidable for one product alone.

Its own codebase, built and released on its own schedule
Its own domain, brand and customer-facing surface
Its own accounts, billing and commercial terms

Risk isolation

A failure should cost what it costs and no more. Products share no runtime, so an outage, a bad release or a security incident reaches that product's customers and stops at that boundary rather than travelling across the portfolio.

Separate infrastructure and separate production environments
Separate databases; no customer record is shared between products
Separate credentials and configuration per product

Operational accountability

Someone has to be answerable for a product that is running, and a customer has to be able to find them. Accountability sits with the company that owns the product, and the routes to it are published rather than implied.

Named company, legal and security channels
A responsible-disclosure route for security researchers
Published terms for the company and, separately, for each product

Independent product identity

A product is judged on its own merits by the people who use it. It carries its own name and its own domain, and it does not need the parent company's brand to be credible — the relationship runs the other way.

Its own name, mark and product site
Its own documentation and support channel
Primanza ownership stated, not used as the product's identity

Long-term maintainability

The cost that decides whether a portfolio works is not the cost of building a product, it is the cost of still running it in five years. Products are therefore built to one standard, so that any of them can be picked up and maintained without relearning how it was made.

One engineering and security baseline across the portfolio
Tests, documentation and a rollback path as a condition of release
Dependencies kept current on a schedule rather than on incident

Clear ownership

Primanza owns each product outright, and ownership is the reason the rest holds. There is no shared control, no revenue split at the product level and no arrangement that would put a decision about a product outside the company.

Wholly owned by Primanza LLC
No external product owners or operating partners
Assets, domains and accounts held in the company's name

The division of responsibility

One owner, separate books — and it is worth being exact about which side of the line each thing falls on.

Held at company level

Ownership of each product and of its assets, domains and accounts
Capital, and the decision to fund, hold or stop a product
Engineering, security and release standards
Legal and commercial infrastructure
The corporate record, and accountability for it

Held by each product

Its name, brand and customer-facing surface
Its codebase, deployment and production environment
Its database and its customer records
Its accounts, billing and pricing
Its documentation, support and terms of service

How a product reaches the portfolio

Four stages. A product is publicly listed at the end of them and not before; the first product has been through them.

01
Chosen
A specific operational problem, a buyer who feels it, and a commercial model that works at the scale one product can reach. A candidate that fails any of the three does not proceed.
02
Built as a whole business
The application is developed in its own project and finished — interface, data, accounts, billing, support, legal terms, tests and a deployment that can be rolled back. It reaches production standard before anything else happens.
03
Brought under Primanza
The finished application moves onto Primanza's product infrastructure: its own repository, its own deployment, its own production environment and its own domain. It is never merged into another product or into this site.
04
Operated
It runs on its own domain, serves its own customers, and evolves on its own release cycle under the company's security and maintenance standard.

Where things live

Three addresses, three responsibilities

primanza.com publishes the company and an index of the products it owns. It does not publish a page about any product: each SaaS application operates independently on a dedicated Primanza-controlled subdomain such as product.primanza.com, and the index links straight to it.

Corporate: Address: primanza.com; The company: the ownership model, the standards and the published record. No accounts and no customer data are held here.
Product index: Address: primanza.com/en/products; The register of products Primanza owns — each one designated, named and linked to its own domain. It describes no product; it points to them.
Application: Address: product.primanza.com; The SaaS product itself, on its own Primanza-controlled subdomain, with its own accounts, billing, data, support and terms. Everything a customer needs to evaluate it is published here, by the product.

What is deliberately not shared

Across the portfolio there is no shared user account, no shared authentication, no shared database, no shared billing and no shared release cycle. Convenience is not a sufficient reason to connect two products; a shared system would only follow a real business case and an explicit architectural decision.

Contact

Independent products. One accountable owner.

Primanza LLC is established and operating its first product. Partnership, investment and general company conversations reach the company directly.

Contact Primanza