What's been happening.

Ardesia is the product; Silica Systems is the company. We've acquired silica.systems as the domain and reorganised the website to reflect the split: Silica is the publisher, Ardesia is what we publish. The change is purely structural — the team, the product, and the work are all the same. Earlier, we ran everything under the Ardesia name and treated the company and product as one. With a defined scope on Ardesia and a horizon for what may come after, the company needed its own identity.

The pricing layer was restructured to support multiple tenants per company account, per-user permissions on price changes, and a full audit log on every price book modification. Price books also gained more case coverage: effective-dated overrides, contract-level rules, volume tier integrity checks, and per-product floors. Setting up pricing should now feel less like a workaround and more like the system it's meant to be.

Started building the marketing site: hero, platform walkthrough, Argo deep-dive, FAQ. The site is being built specifically around the product as it exists today, not as it might exist later. Aimed at office managers in manufacturing companies and the people who decide what software they use.

Spent a day with our first design partner walking through how their office actually runs — every email, every WhatsApp thread, every quote, every gap. Several of the choices Ardesia is built around — the daily ledger format, the customer-scoped Argo, the active-cycle scope — come directly from this conversation.

Two earlier tools: Corridor (office automation with AI) and LexVault (CRM and communication ledger); have been merged into a single product, Ardesia. The CRM and ledger work that lived in LexVault is now the foundation of Ardesia's customer-record view; Corridor's office-automation logic is now Argo, the AI working layer over everything. The merge was a pivot in scope: from "tools that help with parts of the office" to "one product that handles the office's active cycle."

One tool, one workflow, one place. The two previous products will not be developed further as separate offerings.

Ardesia begins as an idea: one workspace for the manufacturing office — invoices, orders, documents, and messages — with an assistant that runs on the customer's terms.

The premise is simple. Office managers in manufacturing companies don't need another tool to add to the stack. They need fewer windows, fewer tabs, and a place where the supplier email, the order it refers to, and the reply that goes back all live together.

From here, the work starts.