/ Architecture / · Mar 12, 2026 · 6 min
A website is not a system. Stop treating it like one.
Marketing sites, CRMs, and warehouses solve different jobs. Bundling them into one ‘portal’ is how projects stall.
Companies often ask for ‘a website with a cabinet’ and mean: catalog, CRM, warehouse, and reporting. That is four products. One URL does not make them one system.
We start by naming the jobs. Public pages need SEO, speed, and editors. Sales needs a pipeline. Operations needs stock and status. If those share a database, they still need different interfaces and permissions.
The practical move is a thin public site, a real CMS, and systems behind APIs. Integrations are cheaper than a monolith nobody can change without breaking the homepage.
If you are scoping a build this year, write the jobs on one page before you pick a stack. The stack is the easy part.
/ Contact /
If this is a live brief, send the jobs.
A website, a system, or a workflow where AI should sit. We reply with a next step.