Licensed modules. Three layers. One closed loop.

Structured communication — indexed by engagement, not by time.

Pain: Separate chat workspaces per client mean separate logins, separate billing, and context that fragments the moment a team member switches engagements.

• Dedicated spaces per client engagement — one workspace, zero workspace-hopping.
• Files, links, and decisions stay pinned beside the conversation your PM monitors daily.
• Controlled guest flows: invite client stakeholders into scoped channels without exposing other engagements.
• Scheduled meetings attach to calendar events — join links live in-thread, not orphaned in separate apps.
• Recordings land in object storage you document and control.

The source of truth — always current, always in-context.

Pain: SOWs on shared drives, runbooks in external wiki tools, architecture decisions buried in email threads — no single source of truth, and none of it lives beside the actual delivery work.

• Long-lived reference material — SOWs, runbooks, handover docs — in the same tenant as delivery.
• Real-time collaborative editing so specs evolve with the engagement, not behind it.
• Permissions inherit from your workspace model — no separate docs tool to administer.
• Docs link directly from channel threads and agile tickets — no context switching.
• Search stays inside the tenant boundary you define and sell to clients.

Real-time budget vs. actual — before scope creep becomes an invoice problem.In product

Pain: External time sheets require consultants to reconstruct their day from memory at month-end. Billable hours slip, invoices run late, and no one can see utilisation against delivery scope until it is already too late.

• Log hours against the channel, ticket, or doc you are actively working on — no context switch.
• Budget vs. actual updates live as hours accrue — not at month-end when the damage is done.
• Project leads see utilisation against scope and get alerts before overruns happen.
• Invoices built from approved, billable time for the engagement — with optional agile task context on line items.
• Time data stays in your tenant alongside delivery artefacts — not in a third-party service.

Project secrets — encrypted and scoped, not passed around in messages.In product

The vault ships as a first-class module; exact policies, rotation UX, and compliance mapping depend on your plan and deployment — confirm with sales for procurement packets.

Pain: API keys, environment configs, and client credentials travel through chat messages, shared spreadsheets, and email. Every consultant who has ever forwarded a staging password knows the security exposure this creates.

• Encrypted storage for project secrets: API keys, credentials, environment configs — scoped to each workspace.
• Access control inherits from your workspace permissions — no separate secrets tool to administer.
• Audit log for every secret read or rotation — evidence for client security reviews.
• Searchable via Unified Search — find a credential as fast as you find a message.

What clients see — under your brand, not ours.Expanding

Pain: Clients chase status updates by email. Consultancies spend time writing update decks that are outdated the moment they are sent. Neither side has a shared, reliable view of where the engagement stands.

• A client portal experience ships in the product; fully custom domains and end-to-end white-label polish vary by roadmap and plan — confirm before you promise in a client SOW.
• Clients see a curated view: sprint progress, approved documents, and budget health.
• Scoped access — client A sees client A's portal only. No cross-engagement exposure.
• No KernelWork branding visible to your clients — you own the relationship.

Intelligence that understands the SOW.Roadmap

Today: the stack includes targeted assist hooks (for example staff-approved weekly engagement summaries where enabled), alongside deterministic risk and forecast signals in reporting. Roadmap: broader “SOW health” panels, spec-from-notes acceleration, and deeper cross-module automation — scope varies by release; treat the mock below as the north star, not a guarantee for every tenant on day one.

Pain: Delivery health is reactive — problems surface in retrospectives or client escalations, not before they affect the engagement. No tool connects the agreed scope to the actual work happening day by day.

• Roadmap emphasis: full “SOW health” panels, faster spec drafting from meetings, and tighter assistive overrun narratives — building on deterministic risk and forecast data you already get in reports today.
• Designed to enhance every module over time — intelligence embedded where the work happens, not a bolt-on chatbot.