Projects, tasks, project accounting
For businesses that sell work rather than goods: a project with stages and tasks, assignees and dependencies — moving a date recomputes the plan instead of silently breaking it. Customer orders, purchases and people's hours attach to the project, so margin is built from real documents, not a side spreadsheet. You see what is ready to bill, what is not accepted yet and which task holds the whole project. Turn it on for services and project work; trade without projects does not need it.
/projectsThey read the same documents as your team, prepare the next action, surface exceptions and keep the decision trail inside the process.
You set the authority. External messages, money and irreversible actions remain approval-gated until verified evidence earns a wider mode.
Choose an industry preset and start with realistic demo data; the team sees the target flow before migration.
Import or connect source data. Digital employees observe, draft and expose gaps while people confirm decisions.
For a typical 50-person company, the target is four weeks. Source quality, integrations and legal requirements can change it.
A module is more than screens. Digital employees work behind them: they prepare the decision and bring it to you instead of waiting for you to type everything in. Below — who exactly, what they do, and where their authority stops.
Keeps the plan alive and ties the work to the project's money
It does not change dates or money — it shows the consequences
Every capability below is tied to an implemented product route. A reviewed product screenshot is shown when it exists in this language; otherwise the route is explained as a transparent work loop, never as invented UI.
A project with phases, tasks and dates; assignees, dependencies and rescheduling that recalculates the plan.
/projectsStages and tasks with assignees and dependencies; moving a date recomputes the plan instead of silently breaking it. You see which task holds the whole project.
/projectsCustomer orders, purchases and hours attach to the project — its margin is built from real documents, not a side spreadsheet.
/projectsProject accounting: what was spent, what was billed, what is left in the budget. The figures are visible only with the project-money permission, enforced server-side.
/finance/projectsYes. Start with one workflow and the data it needs. Add adjacent modules only when the operating process calls for them.
Digital employees watch product records, prepare the next action, surface exceptions and keep the decision trail. Their exact actions and authority gates are shown on this page.
Your team sets the authority. External messages, money and irreversible actions stay approval-gated until you deliberately expand the operating mode.
You can review the target flow with realistic demo data on day one and connect real evidence during the first week. For a typical company of up to 50 people, four weeks is the target for moving one operating loop; source quality, integrations and legal requirements can change it.