Why the most consequential decisions in business lack a structured operating layer.
A private executive operating layer, deployed with leadership teams by experienced operators.
The executive operating gap
The gap between executive judgment and organisational execution is structural. Strategy, hiring, pricing, board narrative, and customer direction all run through the CEO. Yet the operating layer supporting those decisions is weaker than the systems supporting any other function in the business.
4%
Porter and Nohria tracked 27 CEOs in 15-minute increments for 13 weeks. Meetings absorbed 72%. The thinking that shapes the company gets the least protected time.
5.7x
Bain found top-quintile decision effectiveness produced 5.7x total shareholder return over five years, alongside 3.2x revenue growth and 3.6x earnings growth.
67%
Not because the strategy was wrong. Because execution was unstructured. The gap between decision and action is where most value dies.
The gap is not between good strategy and bad strategy. It is between decisions made and decisions executed.
Sources: Porter and Nohria, "How CEOs Manage Time," HBR, 2018. Bain & Company, "Measuring decision effectiveness." McKinsey, "Decision making in the age of urgency," 2019. Kaplan & Norton.
The limitation
General-purpose AI is strong at generating options, answering questions, and synthesising information. It is weak at preserving the operating record that makes executive decisions compound over time.
Strong at: Generating options, synthesising research, drafting communications.
Stops at: Every conversation starts from zero. No persistent decision record, no follow-through tracking, no connection between what was decided and what happened next.
Strong at: Broad organisational productivity, document generation, meeting summaries.
Stops at: Built for the organisation, not the decision-maker. No private reasoning space, no executive-specific data model, no governance over who sees what.
Strong at: Capturing what was said, surfacing action items, searchable records.
Stops at: Transcripts record conversation, not conviction. They do not track whether the commitment was kept, whether the reasoning held, or whether customer signal changed the picture.
The problem is not the model. It is the absence of structure around the model that turns a single conversation into a compounding operating record.
The implementation gap
McKinsey estimates that 70% of large-scale transformation programmes fail to reach their stated goals. The failure is rarely the software. It is the operating-model change required to use it. The executive operating layer is no different.
Who sees what. Who decides what. How decisions flow from private reasoning to shared execution to board narrative. Without defined governance, the system cannot hold candour and alignment simultaneously.
New cadences, new artifacts, new review points. A weekly brief changes nothing if no one reads it. Deployment means configuring the rhythm, not just the software.
The CEO and leadership team need guided practice with structured AI counsel. Fluency with the system is built through use on real decisions, with an operator present.
If the CEO does not use the system, the leadership team will not adopt it. Deployment starts with the CEO's actual decisions, not a training session.
This is why Lucumo is deployed, not installed. A fixed-scope diagnostic identifies where decisions stall. A guided implementation configures the system around how leadership actually operates. The first cadence cycles run with operator support. The product earns adoption through use, not rollout decks.
Sources: McKinsey & Company, transformation programme failure rates. SHRM, executive hire failure research. Kaplan & Norton, strategy execution gap.
The operating layer
Tools solve moments. The operating layer persists. A serious product in this category holds private judgment, durable execution, customer truth, and user control together across time.
A place to think out loud before socialising a view to the board, team, or market.
Options, conviction, and outcomes attached to the call, not lost inside chat history.
Conversations become tasks and notes that still carry their source reasoning weeks later.
Customer, investor, and team signal native to the operating record. It reaches the next decision, not a separate inbox.
Briefs, nudges, and review points that keep the loop alive without asking the CEO to rebuild it each week.
Export, deletion, retention, and access boundaries. Memory compounds without becoming a trap.
What gets deployed
Deliberation is private. Direction is shared. The CEO controls which decisions, commitments, and narratives move from counsel to cadence to board. Five connected components make this work.
Decisions, commitments, signal items, notes, and org context. The persistent layer that gives every conversation a memory.
Monday brief and mid-week nudge. The rhythm that turns a tool into a discipline.
Customer, investor, and team signal captured and fed back into executive decisions. Truth reaches the next call, not a separate report.
Narrative assembled from the operating record. Board preparation becomes exhaust from the system. Shareable via secure link.
What stays private and what gets published is governed by the CEO. Candid reasoning stays in counsel. Aligned decisions and board narrative flow outward on the CEO's terms.
Inside the operating layer
Private Counsel
Sessions, reasoning, memory
Operating Record
Cadence
Mon brief · Mid-week nudge
Board
Narrative · Share link
Signal
Themes · Patterns
Controls
Export · Delete · Audit
The operating record
The same pricing decision, made by the same CEO, in the same week. The difference is whether the reasoning, commitments, signal, and board narrative stay connected or scatter.
Before: fragmented across tools
Slack thread
Pricing rationale discussed
Reasoning lost after 48 hours
Google Doc
Options drafted
Never revisited after the call
Mental note
Conviction level: high
Unrecorded. Unfalsifiable.
Email to VP Sales
15% increase confirmed
Commitment made, no tracking
Spreadsheet
Customer reactions logged
Disconnected from the decision
Board deck
Narrative section drafted
Reconstructed from memory, two months later
After: connected inside the operating record
Conviction
Source
Decision session, 14 Mar
Options weighed
Hold · 10% · 15% with transition
Reasoning: Competitive positioning, margin pressure, Q3 expansion target. Existing customers transitioned over 90 days to protect retention.
Linked commitments
Customer signal
Acme Corp: positive reception, wants annual lock
Beta Ltd: concerned about budget cycle timing
Board output
Pricing narrative, commitment status, and signal summary assembled into board report. Status: Shared.
The reasoning persists. The commitments link to their source. The signal reaches the next call. The board narrative is assembled, not reconstructed.
In practice
Diagnostic
Wk 1–2
Configure
Wk 3–4
First cadence
Wk 5–8
Board output
Wk 9–12
Weeks 1–2
Map decision flows, alignment drag, signal sources, and board cadence. Identify three to five decisions where the gap costs the most.
Weeks 3–4
Configure Lucumo around actual decision patterns. Prime context. Define permissions: private, team, board.
Weeks 5–8
Real decisions through the system with operator support. Weekly brief activates. First commitments tracked against source reasoning.
Weeks 9–12
Operating record produces its first board narrative. Quarterly review measures decision throughput, context retention, follow-through.
Decision example: "Should we raise enterprise pricing?"
Private reasoning
CEO explores rationale, competitive data, churn risk. AI pressure-tests assumptions.
Decision record
15% increase committed. Existing customers transitioned over 90 days. Reasoning documented.
Follow-through
Commitments created from the session. Customer signal captured alongside the decision. Board narrative assembled from the full operating record.
Competitive reality
Each tool below does real work. The question is whether any of them hold the full executive thread: private reasoning, decision record, linked commitments, customer truth, operating cadence, and board-ready narrative with permission boundaries at every stage.
Carries well: Reasoning, option generation, synthesis. Strong at the moment of thought.
Thread breaks: No persistence. No decision record. No follow-through. Every session starts from zero.
Carries well: Capturing what was said, searchable records, extracting action items.
Thread breaks: Transcripts record conversation, not conviction. No link between what was recorded and whether the commitment held.
Carries well: Task tracking, project status, team coordination. Strong at commitments.
Thread breaks: Strong at status, weak at judgment. Tracks what needs to happen but not why it was decided or what tradeoff produced it.
Carries well: Customer records, signal aggregation, research repositories.
Thread breaks: Signal stays in the CRM. It rarely reaches the CEO at the moment of the next executive call.
Carries well: Board materials, governance compliance, operating frameworks.
Thread breaks: Board reporting starts at the board. These tools do not start at the executive decision that feeds it.
Carries well: Reflective practice, coaching sessions, personal development.
Thread breaks: Coaching stays private. It does not produce an operating record, tracked commitments, or board-ready output.
The question is not whether your tools work. It is whether anything holds the executive thread: from private reasoning, through decision and commitment, past customer truth, into board-ready narrative, with permission boundaries at every stage.
Trust architecture
The executive operating layer only works if the CEO can say what they actually think. Here is what we control today, what we configure during deployment, and what is on the roadmap.
Current controls
Deployment controls
Customer rights
Roadmap controls
Encryption
TLS 1.2+ in transit. AES-256 at rest via infrastructure.
Enforced by default. Not configurable off.
Active on every account. No opt-out.
Application-level field encryption. Zero-knowledge mode.
Data isolation
Per-user query scoping on every data access path.
Row-level ownership checks on all queries.
Your data is never mixed with another user's.
Database-layer RLS enforcement.
No model training
Data never enters training pipelines.
Architectural constraint, not a policy toggle.
Permanent by design. Not an opt-in you might miss.
Independent third-party verification.
Export
Full JSON export of all account data.
Available from first session.
Self-service. No approval required.
Additional export formats.
Deletion
Full account deletion with cascade.
Blob, auth, and billing cleanup included.
One action. Self-service.
Configurable retention schedules.
Access boundaries
Authentication on every route. Admin gating.
Two-factor authentication available.
Manage sign-in methods. Enable 2FA.
SSO/SAML. Role-based access control.
Auditability
In-app actions logged: creation, updates, deletion, export, AI tool use.
Admin-wide audit trail.
View and export your activity log.
Exportable compliance reports. SOC 2 readiness.
Support access
Admin access gated by email allowlist. No impersonation.
Admin boundary documented.
No one accesses your workspace without your knowledge.
Explicit support access controls with consent and audit trail.
Data residency
EU/US infrastructure. Jurisdiction disclosed.
Region stated before signup.
Know where your data is stored.
Customer-selectable region.
Encryption
Current controls
TLS 1.2+ in transit. AES-256 at rest via infrastructure.
Deployment controls
Enforced by default. Not configurable off.
Customer rights
Active on every account. No opt-out.
Roadmap controls
Application-level field encryption. Zero-knowledge mode.
Data isolation
Current controls
Per-user query scoping on every data access path.
Deployment controls
Row-level ownership checks on all queries.
Customer rights
Your data is never mixed with another user's.
Roadmap controls
Database-layer RLS enforcement.
No model training
Current controls
Data never enters training pipelines.
Deployment controls
Architectural constraint, not a policy toggle.
Customer rights
Permanent by design. Not an opt-in you might miss.
Roadmap controls
Independent third-party verification.
Export
Current controls
Full JSON export of all account data.
Deployment controls
Available from first session.
Customer rights
Self-service. No approval required.
Roadmap controls
Additional export formats.
Deletion
Current controls
Full account deletion with cascade.
Deployment controls
Blob, auth, and billing cleanup included.
Customer rights
One action. Self-service.
Roadmap controls
Configurable retention schedules.
Access boundaries
Current controls
Authentication on every route. Admin gating.
Deployment controls
Two-factor authentication available.
Customer rights
Manage sign-in methods. Enable 2FA.
Roadmap controls
SSO/SAML. Role-based access control.
Auditability
Current controls
In-app actions logged: creation, updates, deletion, export, AI tool use.
Deployment controls
Admin-wide audit trail.
Customer rights
View and export your activity log.
Roadmap controls
Exportable compliance reports. SOC 2 readiness.
Support access
Current controls
Admin access gated by email allowlist. No impersonation.
Deployment controls
Admin boundary documented.
Customer rights
No one accesses your workspace without your knowledge.
Roadmap controls
Explicit support access controls with consent and audit trail.
Data residency
Current controls
EU/US infrastructure. Jurisdiction disclosed.
Deployment controls
Region stated before signup.
Customer rights
Know where your data is stored.
Roadmap controls
Customer-selectable region.
Proof standard
Any product claiming to improve executive decision quality should be held to an explicit proof standard. Here is ours. These are the metrics we track from day one.
Do executives process more consequential decisions per quarter without sacrificing quality?
Measured by count of recorded decisions with documented reasoning, tracked from deployment baseline. Compared against pre-deployment cadence established during the diagnostic.
Does the reasoning behind a decision remain accessible and useful weeks after the call was made?
Measured by proportion of follow-up decisions that reference prior context from the operating record, versus starting from scratch. Assessed at 30, 60, and 90 days.
Are commitments completed at a higher rate when linked to their source reasoning and tracked against a cadence?
Measured by commitment completion rate for context-linked tasks versus standalone tasks. Tracked across the first two cadence cycles.
Our commitment: External research (Bain, McKinsey, Porter and Nohria) establishes the structural case. Product-specific evidence will be published from the deployment programme with methodology, sample size, and limitations disclosed. Every deployment measures these three metrics from baseline. We will not cite internal benchmarks without published methodology.
Fit
Lucumo is deployed with a specific profile of company and leader. The product is designed for this context and is honest about where it does not belong.
B2B software or tech-enabled services, 25 to 300 employees.
Leadership team of 4 to 12 people making pricing, hiring, org design, product, and board narrative decisions.
Active board or investor cadence with regular accountability rhythms.
High customer-signal volume across calls, Slack, CRM, support, and ad hoc notes.
CEO still personally involved in the calls that shape company direction.
Solo founder without a leadership team. The deployment model requires a team context.
No board or investor cadence. The operating record produces governance output that requires governance input.
Looking for a chatbot or an executive coach. Lucumo is an operating layer, not a conversation partner.
Looking for consulting hours, not a product deployment. The services component is fixed-scope, not open-ended.
Not willing to use the system on real decisions. Lucumo earns its value through use, not through installation.
Commercial model
Fixed-scope assessment of decision flows, alignment drag, signal sources, and board cadence.
Fixed-fee implementation: configure, prime context, define permissions, set cadence, roll out first use cases.
Annual contract with clear support terms. Scoped during the diagnostic to the leadership team's size, signal sources, and deployment complexity.
Optional advisory retainer. Measures what changed, adjusts configuration, identifies the next highest-leverage decisions.
Selected references
How CEOs Manage Time
Michael E. Porter and Nitin Nohria. Harvard Business Review, 2018.
Measuring decision effectiveness
Bain & Company. Decision effectiveness and financial results research.
Decision making in the age of urgency
McKinsey & Company. Decision speed and revenue growth, 2019.
AI Business Survey
PwC. Executive data privacy and AI adoption barriers, 2024.
Strategy execution failure
Kaplan and Norton. ClearPoint Strategy. Harvard Business Review.
Think clearly. Lead decisively.
Book an executive operating diagnostic.