Answered directly, including the awkward ones.

A construction ERP: one workspace holding projects, tasks, clients, documents, finance, HR, sales, contracts, procurement, inventory, QA/QC, HSE and company administration. Not a project tool bolted to an accounting package — one system with one database behind all of it.

It is built for it. The module set is a construction company's: procurement with RFQs and tenders, inventory with site movements, QA/QC with NCRs and punch lists, HSE with permits and incidents. A company outside construction would be paying for a shape it does not need.

All seventeen, on every plan. There is no edition that withholds a module until you upgrade, because a company that cannot afford the quality module is exactly the company that needs it.

Yes, per company, from Settings. A module switched off is unreachable rather than merely hidden: it leaves the sidebar and the router refuses its routes.

It replaces the operational side — budgets, invoices, payments, expenses and cost against value per project. Statutory accounting and filing stay with your accountant. NESTO is where the numbers are produced, not where they are audited.

The whole application is responsive down to a phone. Below tablet width the navigation moves into a drawer and the layout narrows to a single column — the same screens, not a reduced mobile version.

Your administrator provisions them inside your company workspace and assigns the role. There is no public sign-up: a construction company's workspace is not something anyone should be able to join.

One role per company membership. A person can belong to several companies with a different role in each — useful for group structures and joint ventures.

See, and nothing else. Read-only roles have every create, edit and delete grant stripped when their permissions are built, so a create route is refused even if the URL is typed by hand.

Yes. A role is configuration — its navigation, dashboard and permissions are declared in one place, and it then appears in the sidebar, the roles screen and the access checks without a screen being written.

In your company workspace, scoped to your company record. The role that grants access is held on the membership joining a person to that company, so nothing is visible across a boundary it was not granted across.

Twice. Middleware checks the session and the role configuration at the edge before a page is reached, and the page checks the permission again itself. A route added without a middleware rule fails closed.

One eight-hour working day, then sign-in is required again.

No. V0.1 has no AI features and your data is not used to train anything, by us or anyone else.

Nothing at runtime. No analytics, no tag managers, no embedded widgets. The page you are reading loads no images and no external scripts.

Per company, per month, with every module included and a user ceiling per plan. Pricing is on the pricing page — no quote required to see a number.

Yes. Ask for a walkthrough and we will take you through a working workspace as any of the sixteen roles, so you can see what your own people would see.

Your company workspace, your roles, your users and the modules you want switched on. Company plans include guided setup; the workspace is not billed while it is being prepared.

Completely. V0.1 is the structural foundation — every module has its route, navigation, header and dashboard, and functionality is being built onto that, module by module. If a feature you need is not built, we will tell you when it will be rather than show you a mockup.