I Samuel 28:24-30:24

Hook

Let's cut the fluff. You're a founder. You live in a pressure cooker. The market's a battlefield, investors are circling, and your burn rate keeps you up at night. You've poured your soul into this, and now, suddenly, the path forward isn't clear. Your best ideas are hitting walls, your trusted mentors are giving conflicting advice, and the "whispers" of desperation start to sound like legitimate strategies. You feel cornered, isolated. Maybe you're even contemplating a move that, deep down, feels a little…off. A shortcut. A "growth hack" that skirts the edges of what's truly ethical. An acquisition target that feels right, but the internal data is murky, or the way you'd have to spin it to your team or the public would stretch the truth.

This isn't hypothetical. This is the founder's existential crisis. It’s the moment when the market rejects your brilliant pivot, your key hire jumps ship, or a competitor unveils the exact feature you were banking on. You’ve done everything “right” – talked to users, built the MVP, raised the seed. But now, the machine is sputtering. You’ve consulted your board, your advisors, your co-founders. You’ve run the numbers. You’ve prayed (or meditated, or journaled). And still, no clear answer. Just a growing dread.

This is exactly where we find King Saul in our text. He's facing an existential threat – the Philistines are mustered for war, an enemy he's failed to decisively defeat before. He's tried all the sanctioned channels: "And Saul inquired of G-D, but G-D did not answer him, either by dreams or by Urim or by prophets." (I Samuel 28:6). Every legitimate avenue for guidance is closed. The fear is palpable: "When Saul saw the Philistine force, his heart trembled with fear." (I Samuel 28:5). What do you do when your "Urim" (your data science, your market research) goes silent, your "prophets" (your most insightful advisors) have no answers, and your "dreams" (your vision, your gut instinct) are clouded by terror?

Saul, in his desperation, makes a catastrophic choice. He bans "ghosts and familiar spirits" (I Samuel 28:3), yet when all else fails, he actively seeks out a woman who consults them, disguising himself to bypass his own law. He’s not looking for truth; he’s looking for a way out, a magic bullet, even if it means sacrificing his principles, his integrity, and ultimately, his kingship. This isn't just a moral failing; it's a profound leadership error, born of fear and a refusal to confront uncomfortable truths. It’s the ultimate founder trap: believing that a desperate situation justifies desperate, unethical means.

But this text also gives us David. David, who is simultaneously navigating impossible loyalties, forced into a position of appearing to fight against his own people, then returning to find his home sacked and his people ready to stone him. He, too, is in dire straits: "David was in great danger, for the troops threatened to stone him; for all the troops were embittered on account of their sons and daughters." (I Samuel 30:6). Yet, his response is fundamentally different: "But David sought strength in the Eternal his God." (I Samuel 30:6). He then consults the legitimate channel ("Bring the ephod up to me," I Samuel 30:7) and, when given an answer, acts decisively and ethically, even in the distribution of unexpected spoils.

The dilemma for you, the modern founder, is stark: When the chips are down, will you be Saul, chasing a desperate shortcut that compromises your values and ultimately leads to ruin? Or will you be David, facing adversity head-on, seeking legitimate guidance, and leading with integrity, even when it feels like the whole world is against you? This text isn't just ancient history; it's a blueprint for navigating the inevitable crises of startup life with an eye on both your bottom line and your soul.

Text Snapshot

The narrative opens with David reluctantly preparing to march with the Philistines against Israel, only to be dismissed by their suspicious lords. Meanwhile, King Saul, abandoned by divine counsel, consults the Witch of En-dor, who conjures Samuel. Samuel delivers a grim prophecy: Saul's kingdom will fall, and he and his sons will die. David returns to find his home, Ziklag, burned and his family captive; he pursues the raiders, recovers all, and then establishes a radical rule for sharing the spoil equally between those who fought and those who guarded the baggage.

Analysis

Insight 1: Fairness - The "Shared Sacrifice, Shared Reward" Principle

The startup world often celebrates the "warriors" – the coders pulling all-nighters, the sales team closing mega-deals, the founder hustling for funding. But what about the "baggage guard"? The unsung heroes who keep the lights on, the HR person managing payroll, the admin assistant streamlining operations, the customer support rep deflecting complaints, the cleaning crew ensuring a functional office space? David's ruling in I Samuel 30:24 is a masterclass in foundational fairness: "The share of those who remain with the baggage shall be the same as the share of those who go down to battle; they shall share alike." This isn't just a nice sentiment; it’s a hard-nosed, ROI-driven principle for building a resilient, high-performing team.

In the immediate aftermath of recovering the spoil from the Amalekites, some of David's men – the "mean and churlish ones" (I Samuel 30:22) – argued against sharing with the two hundred who were "too faint to cross the Wadi Besor" (I Samuel 30:10). Their logic was simple: no direct participation, no direct reward. But David, understanding the deeper dynamics of communal success and long-term stability, shut them down. He recognized that the "baggage guard" played a critical, albeit less glamorous, role. They protected the assets, maintained the base, and allowed the fighting force to operate without concern for their rear. Their contribution was enabling. Without them, the entire operation would have been vulnerable.

This principle extends far beyond just a single battle's spoils. It became "a fixed rule for Israel, continuing to the present day" (I Samuel 30:25). It's a recognition that collective success is never solely the product of individual heroics. It's the sum of all contributions, visible and invisible, direct and indirect. When a founder creates a culture where only the "rockstar" engineers or the "quota-crushing" sales reps are celebrated and richly rewarded, while the operations team or junior developers are treated as interchangeable cogs, they sow seeds of resentment and disengagement. This leads to attrition, lack of innovation in critical support functions, and ultimately, a weaker organizational fabric.

Real-world startup application: Consider a SaaS startup that just landed a monumental enterprise client, securing a major funding round. The immediate impulse might be to lavish bonuses and equity on the sales team and the senior engineers who built the core product features for this client. But what about the product manager who spent months meticulously gathering requirements and defining the roadmap, the customer success manager who cultivated the relationship for a year before the deal was even on the table, the legal team that hammered out the complex contract, or the IT support staff who ensured the internal systems were robust enough to handle the new scale?

If these "baggage guard" roles feel undervalued in the moments of triumph, their motivation for future contributions will wane. They might perform their duties adequately, but they won't go the extra mile. They won't innovate in their own domains, seeing no direct reward for doing so. David’s rule isn't about charity; it's about strategic alignment. It says: "We are all in this together. Your role, however far from the 'front lines' of combat, is vital to our collective survival and success, and your reward will reflect that." This fosters a sense of shared ownership, mutual respect, and internal equity, which are powerful drivers of long-term organizational health and innovation.

KPI Proxy: Internal Equity Satisfaction Score (IESS). This could be measured via anonymous surveys asking employees across different departments and seniority levels about their perception of fairness in compensation, equity distribution, recognition, and promotional opportunities relative to their peers and overall company success. A low IESS, particularly among "support" functions, indicates a "mean and churlish" internal culture, signaling future attrition and reduced discretionary effort.

Insight 2: Truth & Transparency - The Peril of Self-Deception and the Cost of Evasion

Saul's journey in this text is a tragic descent born of self-deception and a desperate flight from truth. He begins by acknowledging, "I am greatly troubled. The Philistines are attacking me and G-D has turned away from me—and no longer answers me, either by prophets or in dreams. So I have called you to tell me what I am to do." (I Samuel 28:15). He knows G-D has turned away, but he still seeks a convenient answer, a shortcut, a magic bullet, rather than confronting the underlying reasons for his predicament.

Samuel's brutal response leaves no room for ambiguity: "Why do you ask me, seeing that G-D has turned away from you and has become your adversary? G-D has done what was foretold through me: G-D has torn the kingship out of your hands and has given it to your fellow, to David, because you did not obey G-D and did not execute [God’s] wrath upon the Amalekites. That is why G-D has done this to you today." (I Samuel 28:16-18). Samuel doesn't offer a quick fix; he reiterates the truth of Saul's past failures and their inevitable consequences. Saul's desperation led him to bypass legitimate channels and his own prohibitions, seeking a "ghost" to tell him what he wanted to hear, but instead, he got the harsh reality he had been avoiding.

Radak's commentary on I Samuel 28:24, which delves into the nature of the "witch of En-dor" and whether Samuel truly appeared or if it was a deception, highlights this theme. Radak notes that some Sages believe the witch merely created an illusion, using tricks to make it seem like Samuel spoke, predicting things that were already known or easily guessed (e.g., David being anointed, the general fear of the Philistines). Even if the appearance was real (as other Sages argue, stating G-D intervened to make Samuel appear), the core lesson remains: Saul was trying to circumvent the natural, ethical order. He wasn't seeking genuine repentance or a change of course, but a hack to escape his fate. He was trying to find a loophole in reality.

Real-world startup application: How many founders, facing a plateau in user growth or a failing product, desperately cling to their initial vision, ignoring brutal market feedback? They might launch a new feature without proper validation, pour money into a marketing campaign that doesn't resonate, or pivot wildly based on a single conversation with an angel investor, rather than truly understanding the core issues. This is the modern equivalent of consulting the witch of En-dor. It's seeking a "magic answer" from an illegitimate source (or an unvalidated one) because the legitimate channels (data, customer feedback, honest self-assessment) are delivering an uncomfortable truth.

Consider a founder who consistently misrepresents their user engagement numbers to investors or potential acquirers. They might inflate daily active users, selectively highlight positive metrics, or obscure churn rates. This is a Saul-like evasion of truth. While they might secure a bridge round or an initial term sheet, this foundation of deception is inherently unstable. When the real numbers eventually surface (and they always do, whether through due diligence, market performance, or internal leaks), the trust is irrevocably broken. The "Samuel" of reality will eventually deliver the grim prophecy, just as it did for Saul.

Transparency isn't just a buzzword; it's a strategic imperative. Founders who cultivate a culture of radical candor – both internally and externally – are better equipped to navigate challenges. They can admit when a product launch failed, when a strategy needs adjusting, or when the company is facing difficult times. This honest communication might be painful in the short term, but it builds resilience and allows for genuine course correction. Saul’s refusal to accept responsibility for his past actions (the Amalekite incident) led him to the witch, where he was forced to confront the truth without any power to change it. A founder who repeatedly dodges uncomfortable truths will find themselves in a similar position, facing an inevitable downfall with no viable path forward.

KPI Proxy: Transparency Index (TI). This could be a composite metric including: frequency of all-hands meetings with Q&A (openness to challenge), anonymous feedback platform usage, clarity and accessibility of company goals/financials (where appropriate), and employee perception of leadership honesty (survey-based). A low TI indicates a high risk of "Saul-like" self-deception and evasion.

Insight 3: Competition & Loyalty - Navigating Conflicting Obligations

David’s position with Achish, the Philistine king, is a masterclass in navigating deeply conflicted loyalties and competitive dynamics. He's a refugee, essentially a mercenary, serving a king who is a sworn enemy of his own people. Achish, in a moment of trust (or perhaps naivete), declares: "As G-D lives, you have been honest, and I would like to have you serve in my forces; for I have found no fault with you from the day you joined me until now. But you are not acceptable to the other lords." (I Samuel 29:6-7). David has built a reputation for reliability, even though his ultimate loyalty is elsewhere.

When the Philistine lords object to David marching with them – fearing he might turn against them in battle, appeasing Saul "with the heads of those involved" (I Samuel 29:4) – David plays his role perfectly. He feigns indignation, asking Achish: "But what have I done, what fault have you found in your servant from the day I appeared before you to this day, that I should not go and fight against the enemies of my lord the king?" (I Samuel 29:8). This isn't a direct lie, but it's a strategic ambiguity. David's "lord the king" is ultimately G-D, and eventually, he himself will be king of Israel. But in that moment, he allows Achish to believe he means Achish. He maintains his cover without explicitly betraying his true allegiance.

Real-world startup application: This scenario is rife in the modern business landscape. Founders often face situations where they must navigate complex, sometimes conflicting, loyalties. This could be:

• Co-founder agreements: A co-founder might have a side project or a previous venture that could be seen as competing, or might have an obligation to a former employer (e.g., non-compete clauses, IP rights). How transparent and honest must they be? When does "strategic ambiguity" cross into outright deception?
• Strategic Partnerships: A startup might partner with a larger company that is also a competitor in certain market segments. How much information can be shared? How do you ensure your team's loyalty remains with your primary mission, even while collaborating with a "frenemy"?
• Investor Relations: An investor might sit on the board of multiple competing companies. While they have a fiduciary duty, founders must navigate the flow of information carefully, understanding where loyalties might be split.
• Employee Recruitment: Hiring talent from competitors often involves navigating non-compete clauses, intellectual property concerns, and the ethical implications of "poaching."

David's situation highlights that loyalty is rarely black and white in high-stakes environments. He wasn't explicitly deceptive to Achish, but he allowed Achish to draw favorable, albeit incorrect, conclusions about his ultimate allegiance. This strategic ambiguity allowed him to survive and eventually thrive. The key is to understand the line: when does ambiguity become active misrepresentation? When does protecting your own interests cross into undermining someone else's trust in a way that is fundamentally unfair or unethical?

The commentary on David's "honesty" with Achish is minimal, suggesting the text implicitly acknowledges the complexity. Achish believed David was honest, and David’s actions (not directly harming Philistine interests during his service) supported that belief, even if his ultimate loyalty was hidden. This is a precarious ethical tightrope. The lesson for founders is that while integrity is paramount, the world is complex. There are times when full, unvarnished disclosure of all intentions is not feasible or strategically wise. However, this must always be balanced against the risk of creating a reputation for untrustworthiness. David's track record with Achish was strong enough that Achish lamented his departure, even calling him "as acceptable to me as an angel of God" (I Samuel 29:9). This indicates that David had managed his complex loyalties without burning bridges, at least with his direct patron.

KPI Proxy: Partner Trust Score (PTS). This could be an aggregated score from surveys or qualitative feedback collected from key strategic partners (investors, large clients, collaborators) about their perception of the company's reliability, transparency, and fairness in dealings. A high PTS suggests effective navigation of complex relationships, while a low score indicates potential trust breaches or perceived disloyalty.

Policy Move

Policy: The Ziklag Spoil Distribution Principle for Equity and Recognition

Objective: To codify a fair and transparent system for distributing significant company-wide rewards (e.g., equity bonuses, profit-sharing, or project success bonuses) that recognizes the critical contributions of all team members, regardless of their direct involvement in "front-line" achievements, thereby fostering a culture of shared ownership, mutual respect, and long-term organizational cohesion. This policy is directly inspired by David's decree in I Samuel 30:24: "The share of those who remain with the baggage shall be the same as the share of those who go down to battle; they shall share alike."

Sample Draft: [Company Name] Shared Success & Equity Policy

1. Preamble: At [Company Name], we believe that our success is a collective endeavor, the result of every individual's dedication and contribution, both visible and behind-the-scenes. Just as the "baggage guard" was essential to David's victory, so too are all our team members vital to achieving our ambitious goals. This policy establishes a framework for equitable distribution of significant company-wide rewards, ensuring that all who contribute to our ecosystem share proportionally in our triumphs.

2. Scope: This policy applies to all full-time employees of [Company Name] and governs the distribution of: a. Discretionary equity grants tied to significant company milestones (e.g., successful funding rounds, major product launches, exceeding annual revenue targets). b. Company-wide profit-sharing initiatives or special performance bonuses. c. Any other substantial, non-standard financial recognition tied to collective company success. This policy does not supersede individual performance-based bonuses, commission structures, or standard annual compensation reviews.

3. Definitions: a. Direct Contributors ("Go Down to Battle"): Employees whose roles are directly and immediately responsible for achieving a specific, high-profile company milestone or success (e.g., core engineering team for a product launch, sales team for a major deal, executive leadership for a funding round). b. Indirect Contributors ("Remain with the Baggage"): Employees whose roles provide essential support, infrastructure, operational excellence, or long-term strategic value that enables Direct Contributors to succeed. This includes, but is not limited to, HR, IT, finance, legal, administrative support, customer support, and non-core R&D. c. Company Milestone/Success Event: A predefined achievement that triggers a distribution under this policy (e.g., Series A funding close, 1M ARR, successful launch of Product X).

4. Distribution Principles: a. Equitable Allocation: For each Company Milestone/Success Event, a predetermined pool of equity or funds will be set aside for distribution under this policy. b. Shared Percentage: A fixed percentage of this pool (e.g., 60%) will be allocated to Direct Contributors, and the remaining percentage (e.g., 40%) will be allocated to Indirect Contributors. The exact percentages will be reviewed and approved by the Board of Directors annually or prior to a major event. c. Proportional Within Groups: Within each group (Direct and Indirect), individual allocations will be determined based on a transparent formula that considers: i. Tenure: Length of service to the company during the period leading to the milestone. ii. Role Impact: The strategic importance and scope of the individual's role, as defined by their job description and leadership assessment. iii. Performance: Individual performance during the relevant period, as documented in performance reviews. d. Transparency: The overall pool size, the split between Direct and Indirect Contributors, and the general formula for individual allocation will be communicated clearly and proactively to all employees. Specific individual allocations will remain confidential.

5. Implementation Steps:

1. Board Approval & Executive Sponsorship: This policy must be formally approved by the Board of Directors and championed by the CEO and executive leadership team. Their visible commitment is crucial for its success.
2. Define Trigger Events: Clearly articulate what constitutes a "Company Milestone/Success Event" that activates this policy. This could be tied to specific revenue targets, product launches, funding rounds, or strategic exits.
3. Establish Allocation Framework: Before any event, the leadership team, with HR and Finance, will define the exact percentages for Direct vs. Indirect Contributors and the specific criteria (tenure, role impact, performance) for proportional distribution within each group. This framework should be documented.
4. Communication & Education: Conduct company-wide meetings to introduce and explain the policy. Emphasize the "Ziklag Spoil Distribution Principle" – how every role contributes to the collective victory. Address common questions and concerns transparently.
5. Role Classification Matrix: Develop a living document that categorizes common roles within the company as either primarily "Direct" or "Indirect" contributors for various types of milestones. This ensures consistency and reduces ambiguity.
6. Review and Adjustment Cycle: Annually, or after each major distribution event, review the policy's effectiveness. Gather feedback from employees (e.g., via anonymous surveys on fairness perception) and adjust the percentages or criteria as needed to ensure ongoing equity and alignment with company values.

6. Potential Pushback & How to Address It:

• "Why should someone who wasn't 'on the front lines' get the same share?"
  • Response: This is the "mean and churlish" argument David faced. The answer is that no "front line" exists in a vacuum. The "baggage guard" – whether IT infrastructure, HR support, legal counsel, or administrative efficiency – creates the stable, secure environment that enables the front-line team to focus and succeed. Without that foundational support, the "warriors" would be distracted, less effective, and ultimately, vulnerable. David's wisdom was that true, lasting success requires a united front, where everyone feels valued and invested. This policy reinforces that systemic interdependence. The goal isn't just one win, but building a company that can endure many "battles."
• "This will dilute the rewards for the highest performers/most critical roles."
  • Response: This policy is about equitable company-wide distribution, not necessarily equal distribution for individuals. The framework still allows for differentiation based on role impact and individual performance within the Direct and Indirect categories. However, it ensures a baseline recognition for all vital contributions. Furthermore, by fostering higher morale, lower attrition, and greater cross-functional collaboration, the overall "spoil" (company success) is likely to be larger, benefiting everyone in the long run. It's an investment in organizational health that pays dividends.
• "It's too complex to implement and manage."
  • Response: While any new policy requires effort, the long-term benefits of a fair and transparent system outweigh the initial complexity. The framework (percentages, criteria) can be established once and then adapted. The alternative – ad-hoc, opaque, or perceived unfair distribution – leads to far greater complexity in managing employee disengagement, turnover, and internal politics. This policy provides a clear, defensible structure.

By implementing the Ziklag Spoil Distribution Principle, [Company Name] commits to building a resilient and deeply unified team, recognizing that true victory is a shared accomplishment, and that fair reward is the bedrock of lasting loyalty and peak performance.

Board-Level Question

"Given our current market pressures and competitive landscape, how are we ensuring that our pursuit of growth and innovation doesn't inadvertently lead us down a 'Saul-like' path of desperate, short-sighted decisions that compromise our long-term integrity and core values, particularly regarding transparency with our stakeholders and ethical considerations in competitive strategy?"

This isn't a soft, touchy-feely question. It’s a direct challenge to the board’s strategic oversight, demanding an honest assessment of risk and value alignment. The "Saul-like path" refers to the desperation that leads to abandoning principles, seeking shortcuts, and ultimately, self-destruction. Saul, facing an overwhelming enemy and divine silence, chose to consult the Witch of En-dor, a practice he himself had outlawed. This was a desperate, short-sighted move, driven by fear and a refusal to confront the consequences of his past actions. It compromised his integrity, violated his own edicts, and delivered not a solution, but a confirmation of his impending doom.

For a startup, this translates directly to the pressures of hyper-growth, investor demands, and the relentless pursuit of market share. The "Philistines" could be a well-funded competitor, a sudden market shift, or a looming funding cliff. In such moments, the temptation to engage in "growth hacking" that blurs ethical lines, to make misleading statements to secure a deal, to cut corners on data privacy, or to engage in aggressive, potentially anti-competitive tactics becomes immense. The board's role is not just to scrutinize financial performance, but to safeguard the company's long-term viability by ensuring its ethical foundation remains solid. A company built on integrity is more resilient, attracts better talent, retains customer trust, and ultimately generates more sustainable value.

Different answers to this question reveal distinct strategic postures:

• "We have clear ethical guidelines and internal controls": This is a good starting point, but it's not enough. It prompts follow-up questions: How are those guidelines enforced? Are they merely boilerplate, or are they actively integrated into decision-making processes? Who is accountable for upholding them, beyond legal and compliance? What mechanisms exist for employees to report potential breaches without fear of retribution? A robust answer would detail specific training, anonymous reporting channels, regular ethical audits, and clear consequences for violations. It would also highlight how ethical considerations are built into product development, sales processes, and marketing campaigns from the outset.
• "Growth is paramount; we'll course-correct any ethical missteps later": This response signals a high-risk, "move fast and break things" mentality that can be devastating in the long run. It implicitly accepts that ethical compromises might be necessary for short-term gains, effectively adopting Saul's desperate approach. While agility is crucial, sacrificing integrity for speed often leads to reputational damage, legal battles, employee disillusionment, and eventual market rejection. This path is rarely sustainable and almost always results in a more painful "course correction" down the line, often too late to save the company's core value or reputation. It’s a bet that the market's forgiveness will outpace the damage done, a bet that rarely pays off.
• "We prioritize sustainable, ethical growth, and integrate these values into our strategic decision-making": This answer aligns with a David-like leadership. It implies a commitment to transparent communication with all stakeholders – employees, customers, investors, and the public. This means being honest about challenges, data, and intentions, even when it's uncomfortable. It also means approaching competitive strategy with an awareness of long-term impact, focusing on innovation and customer value rather than predatory tactics. This posture requires proactive measures, such as:
  • Ethical Review Boards: For new products or marketing campaigns, an internal committee specifically reviews ethical implications.
  • Transparency Metrics: Tracking and regularly reporting on internal transparency (e.g., employee feedback on leadership honesty) and external transparency (e.g., clear data privacy policies, honest marketing claims).
  • Values-Based Decision Frameworks: Explicitly incorporating core values into strategic planning and project approval processes, ensuring that growth objectives are always balanced against ethical considerations.

This question forces leadership to articulate not just what they are doing to grow, but how they are doing it, and what principles they are unwilling to compromise, even under extreme pressure. It's about preventing a "Saul moment" before desperation sets in, ensuring that the company's foundation of trust and integrity is strong enough to withstand any "Philistine" invasion. The board's responsibility is to ensure the company builds an enduring kingdom, not just a fleeting victory.

Takeaway

The ancient narratives of Saul and David offer a stark, ROI-minded lesson for the modern founder: Desperation is a potent accelerant for ethical compromise, but true leadership builds enduring value through integrity. Saul's tragic arc demonstrates the catastrophic cost of seeking desperate shortcuts and evading uncomfortable truths – a path that ultimately destroys trust and leads to ruin. Conversely, David, facing his own profound crises, models resilient leadership: establishing radical fairness ("The share of those who remain with the baggage shall be the same as the share of those who go down to battle; they shall share alike," I Samuel 30:24), navigating complex loyalties with strategic integrity, and seeking legitimate guidance. Your startup's long-term resilience and market value depend not just on your hustle, but on the unwavering ethical framework you build. Prioritize transparency, embrace difficult truths, and ensure that every member of your "baggage guard" feels valued; these are not soft skills, but the bedrock of sustainable success.