Applications
Projects, assets and compliance, kept on schedule by agents that never forget a date
Planned. This suite is not available to install yet; the tables, agents, apps and connectors below are its design, not a running system.
Operations is the function that keeps promises: the project ships on the date, the van is serviced before it fails, the certificate is renewed before the inspection, the new starter's laptop is on the desk. Every one of those is a date someone has to remember, a status someone has to chase, and a record someone has to keep. In a small company those someones are busy.
The Operations Supercube installs the remembering, chasing and record-keeping. It seeds tables for projects, milestones, tasks, timesheets, capacity, assets, maintenance schedules, compliance obligations, incidents and IT requests. It declares agents that plan and re-plan projects when things move, keep the capacity view honest from timesheets and leave, schedule maintenance and chase it, track every obligation and certificate to its date, log and follow incidents, and handle the IT administration of accounts and equipment. It publishes apps for the project board, the capacity plan, the asset register, the compliance calendar and the service desk.
After installation, a project's milestone slips because a dependency is late. The Delivery Manager agent re-plans the downstream tasks, shows the effect on the end date and on two other projects that share the same people, and asks the project lead which of three options to take. The Asset Steward agent notices a vehicle's service is due in three weeks, books it with the garage on approval and tells the driver. The Compliance Officer agent lists the insurance renewal, the fire risk assessment and two staff certifications due next quarter, with owners. The IT Administrator agent provisions a new starter's accounts from the People Supercube's start plan and orders the laptop against the equipment standard.
Companies that deliver work or run physical things: services firms delivering projects, contractors, facilities and property managers, manufacturers with plant, and any company of 20 or more people that needs someone to own IT and compliance. Roles that use it are the operations manager, project leads, everyone who fills a timesheet, whoever owns assets and compliance, and the person who gets asked for a laptop.
| Agent | Role | Owns | Harness preference |
|---|---|---|---|
| Delivery Manager | general | Project plans, milestones, dependencies, re-planning, status reports | Claude Code |
| Resource Planner | analyst | Capacity and utilisation from timesheets, leave and plans; hiring signals | Claude Code |
| Asset Steward | general | The asset register, maintenance schedules, bookings, disposal | Claude Code, then Hermes |
| Compliance Officer | general | Obligations, certificates, inspections, policies, evidence, audits | Claude Code |
| IT Administrator | general | Accounts, equipment, access requests, joiner and leaver provisioning, the service desk | Claude Code, then pi |
| Table | Purpose | Key fields |
|---|---|---|
projects | Projects and engagements, shared with General Management | name, client, lead, start, end, budget, status, health |
milestones | Dated commitments within a project | project, title, due, status, dependencies |
tasks | Work items, mirrored from a tracker if one is used | project, milestone, title, assignee, estimate, status, due, tracker_ref |
timesheets | Hours by person, project and day | person, project, task, date, hours, billable, approved |
capacity | Planned availability per person per week | person, week, available_hours, planned_hours, leave |
assets | Equipment, vehicles, property, licences, devices | tag, kind, model, serial, location, custodian, purchased, value, status |
maintenance | Scheduled and completed maintenance per asset | asset, kind, due, done_at, supplier, cost, evidence |
obligations | Everything the company must renew, file, inspect or certify | title, kind, owner, due, frequency, evidence_required, status |
certificates | Certificates and licences with expiry, for people and assets | holder, kind, issued, expires, file |
incidents | Safety, security and operational incidents | at, kind, severity, description, actions, closed_at |
policies | Company policies, versions and acknowledgements | title, version, owner, review_by, acknowledged_by |
it_requests | Service desk tickets: access, equipment, problems | requester, kind, detail, approver, status, resolved_at |
| Group | Target systems | Flows in | Flows out |
|---|---|---|---|
| Work tracking | Jira, Linear, Asana, Monday.com | Tasks, status, assignees | Tasks and milestones created on approval, status notes |
| Time | Harvest, Toggl | Time entries | Projects and tasks to log against |
| Calendar and documents | Google Workspace, Microsoft 365 | Events, documents | Bookings, deadline reminders, evidence folders |
| Identity | Okta, Google Workspace, Microsoft 365 | Account and group status | Provisioning and deprovisioning on approval |
| Finance | Xero, QuickBooks, via the Finance Supercube | Project costs, asset purchases | Timesheet totals for billing, maintenance costs |
| People | Via the People Supercube | Starters, leavers, leave | Equipment and access status |
| Chat | Slack, Microsoft Teams | Incident reports, requests | Reminders, status reports, expiry alerts |
Re-plan on change Trigger: a task's due date, estimate or assignee changes, or a milestone slips. Steps: the Delivery Manager recalculates dependent tasks and milestones, checks the affected people's capacity, computes the effect on the end date and on other projects, and proposes up to three options. Checkpoint: the project lead picks an option or edits the plan. Output: the plan is current and the trade-off was explicit.
Weekly status Trigger: routine, Friday 15:00. Steps: the Delivery Manager writes a status note per project from task movement, timesheets against budget and milestone health, and lists risks and decisions needed. Checkpoint: the project lead edits before it goes to the client or to General Management. Output: consistent status across every project without a status meeting.
Capacity forecast Trigger: routine, Monday 07:00. Steps: the Resource Planner rolls capacity forward twelve weeks from plans, leave and timesheets, flags people over 100% or under 60%, and tells the Sales Supercube how much capacity is free for new work. Checkpoint: none. Output: staffing and hiring decisions made on numbers.
Maintenance scheduling Trigger: routine, daily. Steps: the Asset Steward lists maintenance due within 30 days, books with the usual supplier, tells the custodian, and after completion records the evidence and cost. Checkpoint: the operations manager approves bookings above a cost. Output: nothing fails for want of a service.
Compliance chasing Trigger: routine, weekly. Steps: the Compliance Officer lists obligations and certificates due within 90 days, reminds owners, collects evidence into the obligation's folder, and escalates overdue items. Ahead of an audit or inspection it assembles the evidence pack. Checkpoint: the owner confirms completion with evidence. Output: an audit is a folder, not a scramble.
Joiner, mover, leaver Trigger: a start, role change or leaving date from the People Supercube. Steps: the IT Administrator proposes the accounts, groups and equipment from the role's standard, requests approval, provisions through the identity connector, and orders or reassigns equipment in the asset register; on leaving it reverses everything and records returns. Checkpoint: the manager approves access; an admin approves privileged access. Output: right access on day one, no access on day last.
Incident follow-up Trigger: an incident is reported. Steps: the Compliance Officer classifies it, checks whether it is reportable under the company's obligations, opens actions with owners and dates, and chases them to closure. Checkpoint: the operations manager confirms classification and any external report. Output: incidents closed with actions done, and a trend report each quarter.
Professional services firm. Engagements are projects with budgets from Sales; timesheets drive billing in Finance; utilisation is the headline metric. The Resource Planner tells Sales how much capacity exists before a proposal promises it.
Construction contractor. Projects are sites with phases and subcontractor dependencies; assets are plant and vehicles with inspection certificates; obligations include site-specific safety documentation. The Compliance Officer assembles the health and safety file per site. Incidents are reportable by law and the routine knows the timescales.
Facilities management company. Assets belong to clients' buildings; maintenance schedules are contractual; the Asset Steward proves compliance per building per month. The service desk is the tenants' front door.
Manufacturer. Plant maintenance is preventive and condition-based; downtime is an incident category; the Delivery Manager plans production changeovers as projects. Calibration certificates on instruments expire and are chased.
Technology company. The IT Administrator is the main user: identity, devices, software licences as assets with renewal dates, and access reviews as a quarterly obligation. Security incidents follow a defined playbook.
Healthcare provider. Clinical equipment with servicing and calibration obligations, registrations and inspections as obligations, and the incident log structured for the regulator's categories.
write on its tables, read on People's non-sensitive tables and Finance's
project costs. Identity connectors run under tool profiles with only the operations the company allows.Suites share tables and compose, so the ones next to this one are the ones it works with.
The operating rhythm of the company, run by agents, owned by the leadership team
Goals, KPIs, meeting cadence and decisions in one place, with agents that prepare every review and chase every action so leaders spend their time deciding, not collecting.
Books that close themselves, cash you can see, approvals that stay with people
Accounts payable, receivable, month-end close, cash forecasting and management reporting run by agents against your own ledger data, with every payment and every journal approved by a person.
A pipeline that works itself while your people talk to customers
Lead qualification, CRM hygiene, quoting, follow-up and forecasting handled by agents in your own customer tables, so salespeople sell and managers see a forecast they can trust.