The Whimsey Perch
Skip to content
TWP BUSINESS OS

Run Your Business as One Connected System.

TWP Business OS connects the people, processes, transactions, workflows and information that keep your business moving — giving teams a shared operating environment and management a clearer view of what is happening across the organisation.

IMAGE SPACE — EMPTY Future TWP Business OS Interface Reserved for the product interface visual.
One operating environment. Multiple business functions. Connected information.
People Processes Transactions Intelligence
02
THE BUSINESS FRAGMENTATION PROBLEM

Your Business Works as One. Your Systems Often Don't.

Growth creates complexity.

A growing business adds departments, employees, locations, customers, suppliers, transactions, projects, approvals, documents and applications.

Each addition creates another flow of information that needs to move through the organisation.

When business information becomes fragmented, coordination becomes harder.

SALES
HR
FINANCE
OPERATIONS
PROCUREMENT
PROJECTS
INVENTORY

Sales may maintain customer information in one place. Finance may manage billing and collections somewhere else. HR may maintain employee records separately. Operations may rely on task lists, spreadsheets or internal communication. Procurement may have its own supplier and purchasing workflows.

Management then has to bring these pieces together to understand the actual state of the business.

The challenge is not simply having more software. The challenge is keeping the business connected as it grows.

01

Repeated Information

The same business information gets entered, transferred or reconciled across different systems.

02

Disconnected Work

A process that begins in one department often requires manual coordination with another.

03

Delayed Visibility

Management information may arrive after the underlying business activity has already happened.

04

Follow-up Dependency

Important work can depend heavily on people remembering, communicating and following up manually.

03
THE TWP BUSINESS OS APPROACH

Bring the Operating Model Together

TWP Business OS is built around the way a business operates — not around isolated departments.

Instead of starting with individual applications, TWP starts with the underlying operating model.

PEOPLE + PROCESSES + TRANSACTIONS + WORK + DATA ↓ BUSINESS OPERATING ENVIRONMENT

Every business has people performing work.

That work follows processes.

Processes generate activities and transactions.

Transactions create information.

Information needs to be controlled, analysed and acted upon.

TWP Business OS brings these elements into a connected operating environment so that business activity does not have to remain isolated inside individual functions.

01

PEOPLE

Employees, managers, teams, customers, suppliers and other participants in the business.

02

WORK

Tasks, activities, projects, meetings, follow-ups and operational responsibilities.

03

PROCESSES

Workflows, approvals, SLAs, rules, escalations and recurring business procedures.

04

TRANSACTIONS

Sales, purchases, invoices, payments, inventory movements, expenses and other business events.

05

DATA

The information generated by people, work, processes and transactions.

People Work Processes Transactions Data
BUSINESS

When these elements are connected, the business becomes easier to operate, control and understand.

04
ONE BUSINESS, MANY FUNCTIONS

Connect Every Part of the Business Without Losing Its Role

A business may have different departments, responsibilities and specialised workflows. TWP Business OS does not remove those distinctions.

Instead, it provides a connected environment in which each business function can operate within its own domain while remaining connected to the broader organisation.

OPERATING ENVIRONMENT TWP BUSINESS OS Connected business layer
01

Sales & CRM

Customers, leads, opportunities, pipeline and sales activities.

02

HR & Workforce

Employees, attendance, workforce processes, performance and people operations.

03

Finance & Accounting

Financial transactions, receivables, payables, expenses, controls and reporting.

04

Inventory & Procurement

Suppliers, purchasing, stock, inventory movement and procurement workflows.

05

Operations

Everyday operational activities, responsibilities, processes and execution.

06

Project Management

Projects, milestones, tasks, teams, resources and delivery.

07

Central Business Layer

Shared information, workflows, permissions, reporting, automation and management visibility.

ARCHITECTURAL PRINCIPLE

These are not seven unrelated applications placed beside one another.

They represent different operating areas of the same organisation.

A CONNECTED BUSINESS JOURNEY
SALE→ CUSTOMER→ ORDER / CONTRACT→ OPERATIONS→ RESOURCE / PROCUREMENT→ FINANCE→ PAYMENT→ REPORTING
CROSS-FUNCTIONAL EXAMPLE

A customer order doesn't belong to Sales alone.

SalesCreates the opportunity and customer relationship.
↓
FinanceHandles commercial terms, invoicing and payment.
↓
OperationsCoordinates fulfilment or delivery.
↓
ProcurementSources required goods or services where necessary.
↓
ProjectsCoordinates structured delivery when the engagement requires project execution.
↓
ManagementMonitors the overall commercial and operational position.
TWP Business OS connects the journey instead of forcing every department to manage its part of the journey in isolation.
05
OPERATING LAYERS

Operate. Control. Understand. Act.

A business operating system should do more than record activity. It should help the organisation move from everyday execution to management action.

01
OPERATE

Run the everyday work.

Tasks, activities, customers, transactions, projects, requests and operational work are captured in the system.

Activity
02
CONTROL

Keep work within business rules.

Workflows, approvals, permissions, SLAs, targets and exception handling create structure around execution.

Governance
03
UNDERSTAND

Turn activity into visibility.

Dashboards, reports, KPIs, trends and performance views help teams and management understand the business.

Insight
04
ACT

Turn understanding into action.

Assign, approve, escalate, reallocate, follow up and improve based on what the business is actually showing.

Decision
OPERATE→ CONTROL→ UNDERSTAND→ ACT↺
The operating model becomes a continuous management loop — not a collection of disconnected screens.
06
WORKFLOW ENGINE

Make Every Process Visible, Structured and Accountable.

FROM REQUEST TO COMPLETION

Every process should have a beginning, an owner, a decision path and an outcome.

TWP Business OS turns business processes into structured workflows so that work does not depend only on memory, messages or manual follow-up.

01STARTTrigger or request enters the process.
→
02REQUESTRequired information and context are captured.
→
03ASSIGNResponsibility is given to a person or team.
→
04WORKExecution happens against defined requirements.
→
05REVIEWWork is checked before the next decision.
→
06APPROVEA decision gate controls progression.
→
07COMPLETEThe outcome is recorded and the process closes.
WORKFLOW ANATOMY

What makes a process operationally reliable?

TriggerWhat starts the process?
OwnerWho is responsible?
DeadlineWhen must it move?
DecisionWhat controls progression?
ExceptionWhat happens when the normal path fails?
OutcomeWhat proves the process is complete?
STRUCTURED EXCEPTIONS
Missing information Approval delay SLA risk Rejected request Threshold breach Rework required
07
BUSINESS ACTIVITY

Every Important Activity Has an Owner, a Status and a Next Step.

Business work becomes easier to manage when important activity is visible in a common operating language — what happened, who owns it, what its status is and what needs to happen next.

WHOOwner or responsible team
WHATActivity, request or transaction
WHENCreated, due and completed time
WHYBusiness context and purpose
STATUSCurrent stage or state
NEXTRequired next action
ACTIVITY TIMELINE Customer implementation
09:15Task createdImplementation checklist assigned to Operations.
11:40Work in progressOperations updated the required information and attached the document.
14:10Review pendingManager review is required before the next stage.
NEXTApprove & proceedThe next owner receives the action after approval.
BUSINESS ACTIVITY TYPES
Tasks Follow-ups Meetings Approvals Requests Transactions Exceptions Milestones
When responsibility and next action are visible, management spends less time asking what is happening and more time moving the business forward.
08
MANAGEMENT CONTROL

See the Business Without Chasing the Business.

Management visibility should not depend on collecting updates from multiple people, applications and spreadsheets. The operating environment should surface the business position directly.

BUSINESS CONTROL CENTRE Organisation Overview
TODAY / CURRENT CYCLE
ACTIVE WORK248Across business functions
PENDING DECISIONS31Awaiting action or approval
AT-RISK ITEMS12Require attention
OVERDUE07Past defined deadline
WHAT IS HAPPENING?
Sales Operations Projects Finance
WHERE IS ATTENTION NEEDED?
  • 03Approvals approaching SLA
  • 04Customer follow-ups pending
  • 02Project milestones delayed
  • 03Operational exceptions open
MANAGEMENT VISIBILITY
BUSINESS→ LOCATIONS→ DEPARTMENTS→ TEAMS→ EMPLOYEES / PROCESSES
01

What is happening?

Current business activity and operational position.

02

What is pending?

Work, decisions, approvals and follow-ups waiting for action.

03

What is delayed?

Items outside expected timelines or service levels.

04

What needs attention?

Exceptions and priorities requiring management intervention.

05

What happens next?

Assigned actions and decisions required to keep the business moving.

09
CENTRAL BUSINESS DATA

Connect the Information Behind Every Business Activity.

ONE CONTEXTUAL BUSINESS RECORD

Information becomes more useful when it stays connected to the activity that created it.

Customers, people, suppliers, transactions, projects, documents and activities should not exist as isolated records. They should form a connected business context that can be used across functions.

CUSTOMERAccount · Contact · History
PEOPLEEmployee · Role · Responsibility
SUPPLIERVendor · Contract · Purchase
TRANSACTIONOrder · Invoice · Payment
PROJECTMilestone · Task · Resource
DOCUMENTRecord · Version · Approval
ACTIVITYTask · Follow-up · Decision
CONNECTEDBUSINESS
CONTEXT
Shared operating information
IMAGE SPACE 02 Connected Data / Relationship Interface Reserved for a future TWP Business OS data relationship visual.
01

Shared records

Important business information can be referenced by multiple functions without recreating the same context.

02

Connected activity

Actions and transactions remain linked to the customer, employee, project or process they belong to.

03

Better visibility

Management views can use connected information instead of isolated departmental snapshots.

10
INTELLIGENCE & PERFORMANCE

Understand What Is Happening Across the Business.

Once business activity is consistently captured and connected, the organisation can move from raw activity to measurement, comparison and management insight.

01ACTIVITYWork happens
→
02RECORDED DATABusiness events are captured
→
03MEASUREMENTKPIs and indicators are calculated
→
04MANAGEMENT INSIGHTPatterns, trends and priorities become visible
PERFORMANCE VIEW Business intelligence by dimension
REVENUESales, orders, collections and commercial movement.
PIPELINEOpportunities, stages, conversion and follow-up.
PRODUCTIVITYWorkload, activity, completion and turnaround.
WORKFORCEPeople, attendance, capacity and performance.
OPERATIONSExecution, SLA, exceptions and continuity.
PROJECTSMilestones, delivery, resources and risks.
FINANCEReceivables, payables, expenses and controls.
EXCEPTIONSDelays, breaches, unresolved issues and escalation.
Activity becomes data. Data becomes measurement. Measurement becomes management insight. The goal is not more dashboards. The goal is clearer understanding of the business.
11
COLLABORATION

Communication Should Stay Connected to the Work.

Move conversations closer to the business activity they belong to.

Important decisions should not disappear inside disconnected chats. TWP Business OS connects communication with customers, projects, tasks, approvals and management work.

CONTEXTCustomer / Project / Task The conversation starts with a real business object.
→
CONVERSATIONDiscuss & clarify People communicate with the relevant context visible.
→
DECISIONRecord the outcome The important decision becomes part of the record.
→
ACTIONOwner + due date The discussion becomes accountable work.
→
COMPLETIONClose the loop The result remains connected to the original context.
COLLABORATION SPACES
TeamDepartmentTaskProject CustomerManagement
CONTEXTUAL

Conversation stays with the work.

Relevant discussions can be attached to the business object they concern.

ACCOUNTABLE

Decisions create responsibility.

A discussion can become an assigned action, deadline or approval.

TRACEABLE

Important decisions remain visible.

The business can retain a record of what was decided and what happened next.

12
DOCUMENTS

Every Important Document Has a Business Context.

DOCUMENT LIFECYCLE

Documents should be managed as business records, not just files.

Connect documents to customers, employees, suppliers, finance, projects and operations so the record stays useful throughout its lifecycle.

CREATE→UPLOAD→CLASSIFY→ REVIEW→APPROVE→USE→ STORE→ARCHIVE
DOCUMENT CONTROLCustomer Agreement
VERSION 04
LINKED TOCustomer / Contract
OWNERLegal & Commercial
STATUSApproved
LAST UPDATED20 Sep 2026
v04Final agreementApproved
v03Commercial revisionSuperseded
v02Legal reviewSuperseded
v01Initial draftArchived
13
APPROVALS & DECISION CONTROL

Make Business Decisions Structured, Traceable and Accountable.

Important decisions need more than a message saying “approved”.

TWP Business OS can structure requests, validation, decision gates, approvals, returns and execution so the organisation knows who decided what, when and under which process.

REQUEST→VALIDATION→DECISION GATE→ APPROVE / RETURN→EXECUTE / CORRECT→COMPLETE
DECISION OBJECTS
Purchase requestsExpensesDiscountsQuotations ProposalsVendor onboardingEmployee requestsLeave Project changesBudget requestsFinancial transactionsOperational exceptions
DECISION HISTORY
01SubmittedRequest created by Operations
02ValidatedRequired information confirmed
03ApprovedManager decision recorded
04ExecutedApproved action completed
Multi-level approvals can follow defined authority, value, department or business-rule conditions.
14
TARGETS, PERFORMANCE & ACCOUNTABILITY

Turn Business Objectives Into Measurable Responsibility.

01BUSINESS OBJECTIVEWhat the organisation needs to achieve
↓
02DEPARTMENT TARGETWhat each function contributes
↓
03TEAM TARGETWhat the team must deliver
↓
04INDIVIDUAL RESPONSIBILITYWho owns which outcome
↓
05MEASURED OUTCOMEWhat actually happened
TARGET TYPES
CommercialOperationalFinancial WorkforceProjectDepartmental
PERFORMANCE CYCLE
SET→PLAN→EXECUTE→ MEASURE→REVIEW→IMPROVE
RESPONSIBILITYWho owns the result?
MEASUREHow is progress tracked?
REVIEWWhen is performance discussed?
IMPROVEWhat changes next?
15
EXCEPTIONS, ALERTS & ESCALATIONS

Make Exceptions Visible Before They Become Bigger Problems.

Normal work can be automated. Exceptions need attention.

The operating system should identify when work moves outside expected rules, timelines or thresholds — then direct the issue to the right owner.

DETECTED→ALERT→RESPONSIBLE OWNER→ RESOLVE→ESCALATE IF UNRESOLVED→MANAGEMENT→RESOLUTION
SLA

Approaching or breached

Surface work that is close to or outside its defined service level.

APPROVAL

Decision pending

Identify approvals that are waiting beyond expected timelines.

TASK

Overdue work

Highlight tasks that have passed their expected completion date.

PAYMENT

Payment overdue

Bring collection or payment exceptions into management visibility.

PROJECT

Milestone delay

Identify delivery movement that may affect project outcomes.

THRESHOLD

Rule exceeded

Trigger attention when a business metric crosses a defined threshold.

ESCALATION LOGIC Exception → Owner → Deadline → Reminder → Escalation → Management Resolution
16
BUSINESS CONTINUITY & OPERATIONAL RHYTHM

Turn Business Operations Into a Repeatable Operating Rhythm.

Strong operations are not only about individual tasks. They depend on recurring management rhythms that make planning, execution, review and improvement repeatable.

DAILYExecute

Work, priorities, customers, tasks, approvals and exceptions.

WEEKLYReview

Team performance, pipeline, workload, blockers and upcoming commitments.

MONTHLYMeasure

Business results, finance, targets, productivity and operational performance.

QUARTERLYImprove

Objectives, capacity, strategy, process changes and business priorities.

PLAN→EXECUTE→MEASURE→ REVIEW→CORRECT→IMPROVE↺
CONTINUITYKeep the operating model intact when people, locations or responsibilities change.

Processes, ownership, records, approvals and business history remain part of the system instead of living only with individuals.

17
BUSINESS AUTOMATION

Turn Business Rules Into Automatic Actions.

WHENTriggerEvent, time or business activity
→
CHECKConditionRule, threshold or status
→
DECIDEBusiness logicWhat should happen?
→
ACTIONAutomatic responseNotify, assign, update or escalate
→
RECORDResultExecution and audit history
SALES

New opportunity

Assign owner, create follow-up and update pipeline stage.

FINANCE

Payment condition

Trigger reminder, task or escalation based on receivable status.

PROCUREMENT

Threshold reached

Route a purchase request into the required approval path.

HR

Employee event

Create required onboarding, review or compliance actions.

PROJECTS

Milestone risk

Alert the owner and escalate if corrective action is not taken.

MANAGEMENT

Business exception

Surface important deviations into management visibility.

AUTOMATION GOVERNANCE
OwnerActivationConditionsHistoryExecution StatusError VisibilityPermissionsAudit
18
INTEGRATIONS

Your Business Does Not Operate in One Application. Neither Should Your Data.

CONNECTEDTWP
BUSINESS OS
CRM / SALES
ERP / FINANCE
PAYMENTS
HR / PAYROLL
ECOMMERCE
MESSAGING
API

System-to-system connectivity

Exchange structured business data with connected applications.

WEBHOOKS

Event-driven updates

React when important events occur in connected systems.

SYNCHRONISATION

Keep records aligned

Synchronise relevant records and business states.

IMPORT / EXPORT

Move business data

Support controlled migration, bulk updates and operational exchange.

MIDDLEWARE

Coordinate complex flows

Connect systems where direct integration is not practical.

INTEGRATION GOVERNANCE
AuthenticationPermissionsMappingSync RulesErrorsLogsMonitoringAccess
19
MOBILE OPERATIONS

Keep Business Moving Wherever Work Happens.

Business does not stop when people leave their desks. TWP Business OS brings important operational actions into a mobile-first experience for teams working in the field, on-site, in meetings or across locations.

WorkCustomersApprovalsCommunication DocumentsUpdatesNotifications
NOT DESKTOP ON A PHONE.Mobile should prioritise the actions, information and decisions people need while they are away from the full workspace.
09:42TWP●●●
MY WORK

Good morning, Team

03Approvals pendingReview
07Tasks due todayOpen
04Customer follow-upsView
02ExceptionsResolve
IMAGE SPACE 03 Future TWP Business OS Mobile Interface Reserved for the final mobile product visual.
20
TWP INTELLIGENCE

From Business Data to Business Intelligence.

INTELLIGENCEWhat should we understand?
ANALYTICSWhat does the data show?
BUSINESS DATAWhat has happened?
BUSINESS ACTIVITYWhat is happening?
SUMMARISATION

Turn large amounts of business activity into concise management briefings.

DISCOVERY

Find relevant information across connected business records.

PATTERNS

Surface recurring trends, anomalies and relationships for review.

BRIEFING

Prepare role-specific business updates and priority views.

WORKFLOW ASSISTANCE

Support teams while they work through structured processes.

NATURAL LANGUAGE

Allow people to ask questions about authorised business information.

AI ASSISTS. PEOPLE REMAIN ACCOUNTABLE.
PermissionsApprovalsBusiness RulesHuman ReviewAuditability
21
ROLE-BASED EXPERIENCE

Give Every Role the Business View It Needs.

EMPLOYEE

My Work

Tasks, responsibilities, targets, deadlines, communication and personal performance.

EXECUTE
MANAGER

My Team

Workload, progress, priorities, exceptions, approvals and team performance.

CONTROL
DEPARTMENT HEAD

My Department

Department performance, cross-team dependencies, resources and operational health.

COORDINATE
EXECUTIVE

My Business

Business position, trends, risks, targets, exceptions and management priorities.

DIRECT
ONE SYSTEMDifferent role. Different responsibility. Connected business context.
22
SECURITY, GOVERNANCE & AUDITABILITY

Control Access, Action, Approval and Audit.

01ORGANISATIONBusiness boundary
→
02DEPARTMENTFunctional boundary
→
03ROLEResponsibility
→
04USERIndividual access
→
05PERMISSIONSAllowed actions
ACCESS

Who can see it?

Control information visibility according to organisational responsibility.

ACTION

Who can change it?

Define which users or roles can perform business actions.

APPROVAL

Who can decide?

Route decisions through defined authority and approval rules.

AUDIT

What happened?

Retain relevant history of important business actions and decisions.

AUDIT EXAMPLE
14:32Discount approvedManager · Customer Account · Approval workflow
14:35Quotation updatedSales · Commercial record · System action
14:36Customer notifiedAutomation · Communication workflow · Completed
23
SCALE

Start. Grow. Scale. Coordinate.

01START

Establish a connected operating foundation for core business activity.

→
02GROW

Add teams, functions, workflows, transactions and business complexity.

→
03SCALE

Standardise processes and visibility across more people and locations.

→
04COORDINATE

Connect the wider organisation through common operating information.

IMAGE SPACE 04 Future Enterprise Architecture Visual Reserved for the final scale / multi-location architecture graphic.
PEOPLEMore users without losing responsibility.
LOCATIONSMore locations without fragmenting visibility.
FUNCTIONSMore business systems without isolated operations.
DATAMore information with a connected business context.
24
IMPLEMENTATION

Understand the Business. Structure the Process. Then Operate It Digitally.

Don't digitise chaos.

Start with how the business actually operates. Then structure the process, define responsibility, configure the system and continuously improve it.

01DISCOVERUnderstand people, processes, transactions and business requirements.
→
02DESIGNDefine the operating model, workflows, roles and information.
→
03CONFIGUREBuild business rules, permissions, workflows and operating views.
→
04CONNECTIntegrate relevant systems and business data.
→
05TESTValidate processes, controls, roles and business scenarios.
→
06DEPLOYLaunch the operating environment and onboard users.
→
07IMPROVEMeasure adoption, performance and process improvement opportunities.
IMAGE SPACE 05 Future Implementation / Transformation Visual Reserved for a future implementation methodology visual.
Implementation is an operating-model transformation — not simply a software installation.
TWP BUSINESS OS

Run the Business.
Understand the Business.
Improve the Business.

TWP Business OS brings people, work, processes, transactions, information and intelligence into one connected operating environment — so the organisation can operate, control, understand and improve as one system.

PLAN→OPERATE→CONTROL→ MEASURE→UNDERSTAND→IMPROVE↺