Sites & tasks — the execution core
Sites, tasks, execution stages, budgets and the daily progress journal. This is where day-to-day site execution lives. Wired into every other module for full context.
4construct.net →4construct isn't an island. It runs inside the same ecosystem as 4mystaff (teams), 4notify (messaging), 4mycontracts (documents) and 4invoices (billing). One account, unified permissions, flows that sync automatically.
In 4b2b every module is built to talk to the others. A site activity in 4construct can trigger a 4notify message, a contract signed in 4mycontracts auto-opens a site, and stage invoices fire from 4invoices without manual data copy. Below — how each ecosystem brand plugs into your sites.
Sites, tasks, execution stages, budgets and the daily progress journal. This is where day-to-day site execution lives. Wired into every other module for full context.
4construct.net →Team availability and shift planning (4mystaff), HR documents and payroll (4softhr). Site allocations respect real capacity.
4mystaff.net →Email, SMS, WhatsApp and push for deadlines, blockers and status changes. 4notify workflows trigger straight from site events.
4notify.net →Templates, approvals and digital signatures for site contracts and SLAs. Versions live next to deliverables — not lost in Drive.
4mycontracts.net →Stage billing, recurring invoices, Stripe payment links. Close a stage in 4construct and the invoice fires automatically through 4invoices.
4invoices.net →One 4b2b account, unified permissions, centralized billing. Add brands as you need them.
Each app solves a distinct need and works on its own too. Open any of them: