Skip to content

For teams running several companies, SOVHELM shows where each task, approval, file and deadline belongs.

Know which company owns every commitment.

SOVHELM gives founder-led groups one private workspace where tasks, approvals, files, deadlines and access rules stay tied to the right company, legal entity and owner.

  • Separated demo
  • Five role views
  • Reference IDs
  • Audit trail
Built for Founder-led groups Holding companies Family businesses Service operators Micro-portfolios Ecommerce and property teams
SOVHELM / PRIVATE CONTROL Founder view
GR-1018

Supplier quote cannot move until payment terms are confirmed.

Venture
Verde Kitchen
Entity
Verde Kitchen Ltd
Function
Operations
Approval
Founder required
Task Evidence Decision Audit
Internal target
09 May
Review
12 May
Final risk
16 May

Why not a task board?

Tasks show work. SOVHELM shows the business context around the work.

Use a task board when the sentence is enough. Use SOVHELM when the company, approval rule, file, deadline, access boundary and audit trail matter.

Loose task text

Pay supplier.

A normal task board stores the sentence. The company, approval rule, visibility and supporting files have to be remembered elsewhere.

SOVHELM operating record PP-2047

Pay supplier for PurePack Home Ltd.

Venture
PurePack Home
Legal entity
PurePack Home Ltd
Function
Finance
Project
Amazon UK launch
Approval
Founder required
Evidence
VAT file and invoice proof

Search, comments, notifications and audit history stay tied to this structure.

01 Loose work

A task, date, comment or file enters the workspace.

02 Business context

Company, venture, function, legal entity and owner are attached.

03 Access boundary

Only the right roles can see, search, comment, approve or open files.

04 Traceable outcome

Decisions, evidence, audit history and next actions stay connected.

Record anatomy

A task becomes a governed record.

A record is a task with its business context attached: company, owner, proof, deadline and permission boundary.

In SOVHELM, a task is not just a line item. It carries the company, legal entity, owner, approval rule, evidence, deadline and visibility boundary with it.

SOVHELM does not ask the team to reconstruct context from chat. Each item carries its company scope, legal context, accountable people, evidence requirement, visibility rule and audit trail.

Control rule If the record moves, the boundary moves with it.
VK-2042 / Supplier quote record Locked until evidence is attached
Context locked
Company
Verde Kitchen Ltd
Venture
Verde Kitchen
Function
Operations
Project
Supplier launch path
Action rules
Owner
Operations lead
Approver
Founder required
Evidence
Dated quote and payment terms
Visibility
Founder, finance, operations only
Audit trail
  1. 09 May Internal target missed
  2. 12 May Approval held for evidence
  3. 16 May Final risk escalates if unresolved

Product evidence

Real product surfaces, not schematic claims.

Open the separated demo and inspect the current app: operating map, task queue, legal dates, alerts and mobile views. Each screen shows work with company, person, deadline and access context attached.

Evidence packet Current product screens Public demo workspace. No live customer records involved.
Workspace
Separated demo
Coverage
Map, tasks, dates, alerts, phone
Inspect
Open full-size product shots
Visual proofLive app screens, not concept panels
ContextVenture, function and people stay attached
ControlApprovals, due pressure and evidence state are visible
MobileDaily queue and alerts work on phone
Primary exhibit Operating map Venture, OKR, project, task state and owner context remain visible together before a record is opened. Open full-size screenshot
SOVHELM map with ventures, OKRs, projects and tasks
PathVenture to OKR to project to task
FocusDetail panel keeps the selected record in context
ScopeBranches follow the viewer's permitted access
SOVHELM mobile My Work queue with assigned work, approvals and due pressure
Daily queue My Work on mobile

Assigned work, approvals, reply-needed comments and scheduled pressure are grouped into the operator's daily plan on phone.

Useful for: founders and operators who need the next move without opening every board. Open full-size screenshot
SOVHELM task list with assignee, execution state, priority and due context
Execution Tasks with business context

The queue keeps reference ID, venture, function, assignee, status, due pressure and latest signal together.

Useful for: deciding what is blocked, overdue or waiting for approval. Open full-size screenshot
See more product surfaces
Entity date control Little Leaf Living Ltd
Next final26 JunPAYE control
Open now10VAT
At risk8deadline pressure
Accounts Prep Filing
VAT VAT VAT Return
Corporation tax CT Final
Legal dates Entity timeline

Internal target dates, preparation windows and final legal deadlines are shown in one view.

Useful for: annual accounts, VAT, filings, insurance and other obligations. Open full-size screenshot
SOVHELM mobile alerts and notification centre
Access signals Alerts on phone

Mentions, approvals, blocked work, scheduled pressure and sync issues are grouped for mobile triage.

Useful for: checking what needs attention without exposing unrelated records. Open full-size screenshot
Open demo Take the 2-minute guided tour See scenarios Demo data is separate from live workspaces.

Operating scenarios

Different businesses, same control problem.

SOVHELM is not limited to one sector. It is for teams where work crosses companies, people, approvals, evidence and visibility boundaries.

These examples show how ordinary operating pressure becomes a controlled record someone can own, search and audit. Ecommerce and property are useful examples, but they sit inside the broader founder-led multi-company pattern.

Holding company Subsidiary approval is blocked until the latest filing pack is reviewed.

Normal tools show a task. SOVHELM keeps the company, legal entity, approver, evidence file, final deadline and audit trail attached.

  • Company scope
  • Legal deadline
  • Evidence pack
  • Approver
Record path: entity date -> generated task -> approval -> audit history
Family business group A private founder decision needs assistant follow-up without exposing the private note.

SOVHELM separates the founder's private context from the delegated action while preserving who actually acted and who they acted for.

  • Private note
  • Delegated assistant
  • Real actor
  • Limited visibility
Record path: founder note -> assistant action -> comment -> audit trail
Service operator A client delivery risk crosses operations, finance and leadership before the due date.

The record holds the owner, decision needed, latest signal, due pressure and linked comments so the team does not manage the risk through scattered messages.

  • Project risk
  • Owner
  • Decision
  • Latest signal
Record path: project -> risk -> task -> decision -> notification
Micro-portfolio An investor update needs visibility without exposing supplier notes or internal blockers.

SOVHELM can keep portfolio pressure visible while restricted records disappear from search, files, comments and approval actions.

  • Investor-safe view
  • Hidden records
  • Search boundary
  • Linked work
Record path: portfolio summary -> linked task -> restricted evidence -> access decision

Built for sensitive work

Every sensitive record carries its access decision.

When several companies share one workspace, SOVHELM keeps the daily operating view useful without making every record visible to every person.

Access proof Switch roles to see what disappears from search, files, comments and approval actions.

Use this when investors, assistants, suppliers or different company teams need different views of the same operating workspace.

Record Supplier quote
Can see + act Founder, Operations, Finance
Limited action Assistant acting for founder
Hidden Investor, other venture team
Trust center Demo/live separation Private records by role
Access decision receipt VK-2042 / Verde Kitchen supplier quote
Record scope Verde Kitchen Ltd / Operations / supplier quote evidence
Action requested Open file, comment, approve payment terms, appear in search

Founder view: visible, actionable, approvable and searchable.

Can see recordYes
Can comment or actYes
Can approveYes
Can open filesYes
Appears in searchYes
Audit visibilityFull
PersonSeeActApproveSearch
FounderYesYesYesYes
Operations leadYesYesNoYes
Finance partnerYesCommentYesYes
Assistant acting for founderLimitedDelegatedNoLimited
InvestorNoNoNoNo result
Other venture teamNoNoNoNo result
Denied surfaces Search result, file preview, comment thread, notification, audit detail
Audit result Real actor and on-behalf-of person remain visible where delegated action is used.

Trust posture

Built for sensitive operating work.

Use the public demo without moving real records. When a live workspace is created, records, files, comments and search follow the same scoped access model.

Review security and data posture
Demo separation Demo and live workspaces stay separate.

The public demo is for product inspection. Real operating records belong in authenticated workspaces.

Access scope Records follow venture, role and private-record rules.

Search, comments, files, notifications and linked work use the same visibility boundary.

Private records Founders can restrict sensitive items to selected people.

Restricted work disappears from normal lists and search for people outside the access set.

Audit history Important changes keep a record of who acted.

Delegated assistant actions preserve both the real actor and the on-behalf-of person.

Persistence Live workspaces use Supabase-backed persistence.

Operational saves, comments, files and generated work are designed around a database-backed source of truth.

First review Initial review does not require sensitive records.

Prospects can inspect workflows, mobile views and access behavior before importing live business data.

OperatorSOVHELM LLC
Live persistenceSupabase-backed workspaces
Transport securityHTTPS/TLS for app traffic
Data boundaryDemo and live records stay separate
Operational requestsExport, deletion, backup and hosting questions handled through privacy/security contacts
Review Trust Center

Pricing

Simple plans by operating scale.

Priced by companies, not seats. Investor, supplier and assistant viewers stay free.

Choose the plan by how many companies or ventures need shared control, access rules, files and deadlines in one workspace.

Buying rule Start with the smallest boundary that reflects how your group actually operates.
Pricing Monthly workspace plans
Core included Team members, role-scoped records, search, comments, files, notifications, audit history and demo/live workspace separation.
Scoped separately External viewers, specialist workflow packs, custom workflow models and larger portfolio boundaries.
Plan 01

Founder

£149/month Best for: one company or venture

For one operating company that needs controlled tasks, approvals, sensitive records and supporting files.

  • 1 company or venture
  • Founder queue, private records and files
  • Approval, comments, search and audit trail
Plan 03

Portfolio

£599/month Best for: up to 10 companies or ventures

For portfolio-level control where delegated assistants, external visibility and multiple ventures need one governed place.

  • Up to 10 companies or ventures
  • Portfolio operating map and assistant delegation
  • External viewer and investor boundaries
Rollout discipline Start narrow, prove the operating record model with real work, then extend the workspace boundary deliberately.

Before you open the demo

Common buyer questions.

Use the public demo to inspect the product immediately. Request a private walkthrough when you want SOVHELM mapped to your own companies, people, recurring work and access boundaries.

Who is SOVHELM built for?

Founder-led groups, holding companies, family business groups, service operators and investor-backed micro-portfolios that need work, approvals, legal dates and access control in one place. Ecommerce and property operators are common examples, not the only fit.

What is an operating record?

A task with its business context attached: reference ID, venture, legal entity, function, owner, approval state, evidence, comments, linked work and audit history.

Is the demo separated from live data?

Yes. The public demo uses separated sample records and role views. Live customer records only enter after a workspace is set up.

How do access boundaries work?

Roles, ventures, private records and delegated assistant mode decide what each person can see, act on, approve and find in search.

Private walkthrough Map SOVHELM to your operating structure.

No sensitive records are needed for the first review.

Direct email: sales@sovhelm.com

Public demo

Inspect the product before real work moves in.

Pick one record, change the viewing role, follow its linked work and check whether the boundary still holds.

Public demo Separated workspace
  1. 01Open the demoConfirm the workspace is separated from live customer records.
  2. 02Search a reference IDCheck venture, function, owner, approver, due pressure and evidence context.
  3. 03Follow the branchMove from task into project, OKR, legal entity dates, comments, files and audit.
  4. 04Change roleCompare founder, partner, manager, team member and investor visibility.
  5. 05Boundary holdsThe same record remains traceable, while restricted records disappear from search, files and comments.