# Two founders, one company: can this partnership handle the next stage? **FICTIONAL EXAMPLE · COMPLETED ASSESSMENT SCENARIO.** Every person, organisation, quotation, assessment response, document, observation and event in this report is invented. It demonstrates the proposed reporting approach, not a real engagement, validated prediction or client outcome. No real participant data or test scores are used. The conclusions are illustrative human advisory views; the client retains its decision. **Founder Dynamics · Maya Ellis, CEO · Luca Hart, CTO/Product · 36-person B2B software company · Growth-capital scenario** ## 2-minute brief **Compatibility view:** Maya and Luca can build together. They are not yet ready to give the incoming leadership team the independence assumed in the growth plan. Describing them only as a “strong complementary team” would hide that gap. **What works:** Maya creates commercial momentum; Luca challenges assumptions and protects product quality. Both have put the company ahead of personal preference in specific decisions. Their differences improve judgement when there is one agreed decision owner. **What could fail:** Maya protects important relationships by bypassing process. Luca protects standards by pulling decisions back to himself. New commercial and product leaders could become responsible for results without being allowed to lead. More capital would fund more activity around the same control problem. **The uncomfortable finding:** status matters to both, in different ways. Maya wants to remain the person who opens the decisive door. Luca wants his technical judgement to remain the reference point. Those motives become costly when someone else's authority threatens that identity. **What daily life could feel like:** energy, access and fast progress when they agree. When they do not, managers may hear two answers, soften bad news and seek permission through personal relationships. **For the investment team:** the people evidence does not support assuming two senior hires will remove founder dependence. Change that assumption in the operating plan. This is a people-diligence conclusion, not a recommendation to invest or determine transaction terms. ## The investment context came first This assessment started with the investment team's plan and the company as it exists today. There is no future manager to interview first in this founder engagement. The equivalent first step is understanding the business, current team and demands the next stage will place on its leaders. The company has 36 people and sells B2B software. New capital would fund a larger commercial team, two experienced functional leaders and a second market over 18 months. Three assumptions matter: the founders want the same growth path; senior hires will receive real authority; and difficult news will reach the board early enough to change a decision. Both founders received full assessments. Three colleagues supplied agreed contextual accounts; their own personalities were not assessed. Commercial projections supplied context rather than independently verified financial evidence. The question is how each founder's values, motives, pressure responses and relationship habits support or undermine the plan. Strong individuals are not automatically a compatible partnership for every stage of a company. ## What the engagement covered Each founder completed Alma-supported assessment work and two MindFrame conversations. The engagement included a joint prioritisation exercise, reconstruction of a disputed customer promise, operating-decision records and colleague accounts. Separate debriefs preceded the shared discussion. MindFrame draws on psychology, organisational psychology and applied neuroscience relevant to people management. That foundation helps us ask better questions and compare explanations; it does not turn an interview conclusion into a proven prediction of company success. We tested what it is like to disagree with each founder, who receives credit, what happens after a mistake and whether delegated authority survives an unwelcome answer. Motives were explored through choices and trade-offs, not asserted from a persuasive story. Self-report and interview answers can repeat the same self-image. Where available, records and another person's account were used to challenge it. Work-relevant interpretation stays separate from speculation about private life or a claim to know hidden thoughts. ## Maya Ellis — individual behavioural portrait ### What she wants, and what she does not want to lose Maya wants the company to matter beyond its early customers. She becomes animated describing a category the business could shape and opportunities employees could gain. She also enjoys being the person who makes an important connection happen. The first motive is supported by a deal she declined because its delivery demands would have harmed the product. The second appeared when she described a future commercial leader mainly as someone who would make her own selling more scalable. She initially struggled to name a high-profile decision that would stop coming to her. The concern is not ambition. It is hiring expertise while reserving the visible, consequential parts of the job. A strong hire could feel valued for capacity and credibility, but not trusted with leadership. ### The everyday experience: access, energy and shifting commitments Maya listens closely to customers, notices hesitation and turns discussion into action. One colleague described her making an anxious new manager feel able to approach her. She gives a team a concrete reason to care. The cost is that a helpful conversation can become a promise before the people doing the work have agreed it. The commitment reconstruction found a real difference between enthusiasm for the opportunity and permission to announce a date. This was not simply poor documentation. A team needs to distinguish an idea, a possible exception and an authorised commitment. Otherwise, people leave an encouraging meeting with different accounts of what they now owe. ### Vanity, credit and being seen In a senior review, Maya described a customer recovery as something “I got over the line.” The decision record and two accounts showed substantial work by the customer team. When challenged, she named their contribution and corrected the account in the next review. One compressed phrase could be ordinary shorthand. It warranted attention because a colleague described a similar pattern when external attention was high. The counterexample was a failed negotiation for which Maya publicly accepted responsibility rather than blaming delivery. This supports a specific status-sensitive pattern, not a conclusion that she always takes credit or has a personality disorder. Around visible wins, she may overstate her part. Around a clear failure, she can own it. Team-first leadership needs accurate recognition when there is praise to collect. ### Criticism, pressure and loyalty Maya examined the specific feedback that a promised date had removed product's negotiating room. The broad claim “you always overpromise” produced immediate defence. Specificity helped her examine the event; a global judgement shifted attention towards protecting her identity. During public challenge in the exercise, she interrupted Luca to explain the customer consequence, then let him finish after the interruption was named. A colleague described a similar rush to answer when momentum was being questioned. The material reviewed showed no retaliation after that disagreement, but quieter people may stop objecting if they must fight for airtime. Maya shows loyalty by facing a disappointed customer herself. She can also protect the closest relationship at everyone else's expense. Care for a customer is not automatically care for the team asked to absorb an impossible date. ### The compatibility implication Maya can make a cautious company more ambitious. She is less compatible with an experienced commercial leader expected to own customer priorities while she keeps a private exception route. That boundary needs changing before the role is offered. Asking the hire to “manage the founder relationship” would conceal the real problem. Her success also depends on colleagues offering a credible route forward, not merely a list of objections. The team needs both commercial courage and an honest limit on commitments. ## Luca Hart — individual behavioural portrait ### What he wants, and why control matters Luca wants a product whose logic remains sound as it grows. He enjoys simplifying a difficult design so others can use it. He is not simply risk-averse: he proposed a major workflow change before customers requested it and tested it through a bounded experiment. He also values being the person who understands the whole system. In the role-change discussion, he accepted a product leader's authority, then added reviews for anything touching connected parts of the product. That covered almost every important choice. Two motives may coexist: protecting a system for which he feels accountable, and protecting his place as its final authority. Luca acknowledged that a sound decision made without him could feel like a loss of relevance, even when good for the company. ### What it is like to bring him an idea Luca finds dependencies others miss. A proposal receives serious attention and a strong argument can change his view. That is valuable when commercial enthusiasm is hiding a real cost. He may give six objections before saying what he would support. In the exercise, he produced a usable alternative only after being asked to choose within the available time. To him, questions improve the decision. To a colleague, they can feel like a test that never ends. A confident peer may welcome this challenge. A junior manager may decide it is safer to ask permission than make a recommendation. Compatibility depends on how Luca uses authority, not simply whether someone enjoys analytical discussion. ### Public challenge and psychological safety A colleague described Luca calling a proposal “basic thinking” in a group review. The meeting note supported the wording. He later apologised privately and helped revise the proposal. The group that heard the dismissal did not hear the correction. Luca said he was frustrated by an assumption already discussed, not questioning the person's intelligence. That explains the trigger without cancelling the effect: an imperfect question had become a risk of public embarrassment. The counterexample was a review in which he invited a junior engineer to challenge his own design and adopted the change. He can create a safe, demanding environment. He does not do so consistently under pressure. When harm happens publicly, a private apology alone leaves the wider lesson unchanged. ### Self-importance, standards and credit The assessment did not label Luca a narcissist. It examined behaviour colleagues could experience as self-important: dismissing another person's reasoning, treating his preferred approach as the only sound option, and reopening a delegated decision. There was meaningful counterevidence. He credited an engineer whose simpler solution replaced his own, and accepted a different implementation in the joint exercise. The concern becomes stronger when he believes a core standard or his authority has been bypassed. The practical issue is whether “quality” is a standard others can apply or a word meaning “Luca approves.” Independent judgement cannot scale if the standard changes whenever the founder dislikes the answer. ### Pressure and long-term compatibility Luca reviews more work personally under pressure and delays disagreement until his reasoning feels complete. By then, others may be committed. He experiences their momentum as disregard; they experience his late objection as control. A leader who wants clear technical limits and freedom inside them could work well with him. A leader expected to own outcomes while needing informal approval would struggle. Luca needs to state essential constraints early, give a timely recommendation and stop reviewing when the agreed decision is sound. ## What happened when the partnership was tested ### They remembered the same promise differently Maya remembered a customer date as agreed. Luca remembered permission to explore it, subject to two dependencies. The note recorded enthusiasm but no authority to commit a date. A colleague described work being rearranged after Maya's customer call. During separate reconstruction, they supplied different rules for when consent existed. In the shared discussion, Maya acknowledged removing room to negotiate. Luca acknowledged leaving his conditions implicit and allowing silence to look like approval. They produced one corrective account for affected leaders. This shows they can repair a specific conflict. It does not erase the cost managers had already carried. Compatibility requires a reliable way to prevent conflicting instructions, not endless skill at reconciling afterwards. ### Could somebody else make a decision neither preferred? The joint exercise combined customer expansion, a reliability problem and limited capacity. A proposed functional leader recommended a smaller pilot while protecting essential reliability work. Maya accepted a less impressive customer promise without blaming product. Luca accepted a different implementation while retaining two safeguards. Both first added another approval through themselves. Asked whether the leader really owned the choice, they removed those universal gates. They can share control when the pattern is made visible. Their first impulse still makes senior leaders wait. The operating plan should not assume the habit has changed because both can describe the right answer. ### What reaches the board when things go wrong? Maya opened a missed-milestone update with the recovery plan. Luca opened with technical causes. Neither started with the missed commitment and its consequence. This need not mean deliberate concealment. Maya may be preserving confidence; Luca may be seeking accuracy. The effect is that investors must work to discover what changed. Both revised the update to state the miss, effect, uncertainty and decision required first. A team should not have to choose between being reassuring and being truthful. Future updates need the same standard without an assessor prompting it. ## Investment-committee brief: the people assumptions | Assumption | Evidence and counterevidence | Practical implication | |---|---|---| | They want the same company | Both want a durable product; Maya favours earlier market expansion, Luca a stronger base first. | Agree the sequence and acceptable downside before treating capital as permission to pursue both. | | Senior hires will create independence | Both relinquished a decision in the exercise; both first added personal approval. | Current habits do not yet support the hiring plan. Name decisions founders will stop making. | | Challenge is safe | Both changed their view; Luca's public dismissal was repaired only privately. | Correct public harm publicly and check whether quieter colleagues still speak. | | Team contribution will be recognised | Maya corrected credit; Luca credited an alternative design. Status pressure also produced contrary examples. | Inspect recognition around visible wins, not only declarations of team-first values. | | Bad news will arrive early | Both improved the update; initial versions delayed the consequence. | Require the miss and impact first, before recovery or explanation. | | More resources solve the friction | Resource limits are real; control patterns remained when the exercise clarified capacity. | Do not confuse a headcount problem with a relationship or authority problem. | This brief concerns people and operating assumptions. It does not establish investment merit, company value or transaction terms. The investment team and its advisers retain those judgements. ## How the founders would work together **A normal week:** Maya creates energy and opens doors; Luca protects the business from careless promises. They can argue and still value the other's contribution. The team benefits when the argument ends with one owner and one decision. **A bad month:** Maya seeks a quick win and calls a manager directly. Luca discovers the commitment and adds reviews. Managers spend time predicting each founder's response instead of making the best decision. Some may soften bad news to avoid triggering either pattern. **After two senior hires:** stronger decision owners could help. The relationship could also worsen if both founders experience a loss of status and quietly take authority back. Evidence supports both possibilities; the current plan does not yet protect the better one. Their personalities are not inherently incompatible. Their present habits conflict with the independent leadership the plan assumes. The change required is visible: accept a sound decision they dislike, leave credit with its owner and correct an override through the people who received it. ## A practical authority agreement | Situation | Required behaviour | What should stop | |---|---|---| | Customer exception | Maya takes the opportunity and its cost to the named owner. | A private promise becoming everyone else's emergency. | | Technical choice meets safeguards | The delegated owner decides even if Luca prefers another solution. | Reviews with no clear stopping point. | | Public disagreement | Address the argument; correct any dismissive response before the same audience. | Embarrassment as the price of speaking up. | | Visible team success | Credit names the people who made it happen. | Founder storytelling that erases others' work. | | Missed milestone | State the miss and consequence before reassurance. | Updates requiring repeated questions to expose the problem. | | Market-entry disagreement | Use the agreed founder/board decision route and state the accepted downside. | Different teams acting on different growth plans. | This is a working agreement, not a substitute for formal governance documents. Its credibility rests on what the founders do when a decision affects their pride, relationships or sense of control. ## Priorities for the first 90 days **Before approving the operating plan:** replace the assumption that senior hires automatically create independence. Define decisions each founder will stop making, agree market sequencing and reflect any delay in the plan. Relevant advisers determine transaction implications. **Days 1–30:** test the agreement through real decisions. Record the owner, any founder override and its consequence. Maya should correct missing team credit. Luca should complete the public repair of the dismissive review and explain how challenge should work. **Days 31–60:** inspect a decision each founder disliked. Did it stand? Did its owner retain access, trust and credit afterwards? Agreeing in a meeting and then excluding the person is not delegation. **Days 61–90:** ask affected leaders about actual experiences. Can they bring an unfinished idea, admit a mistake and decline an unrealistic request without personal cost? Compare accounts with decisions and board updates rather than substituting a general satisfaction score. The strongest counterargument is that positive exercise behaviour proves enough adaptability to keep the plan unchanged. It demonstrates capacity to change, not an established habit. Make the required changes explicit rather than asking future hires to absorb the risk. Private assessment detail is not automatically board material. The investor brief contains decision-relevant implications; fuller personal feedback stays within the agreed engagement audience. **Illustrated scope:** Founder Dynamics is €15,000 for two founders. Each additional founder or C-level leader receiving a full assessment is €5,000. Applicable VAT is additional. ## Deeper reading: twelve MindFrame inquiries These work-focused questions explain the compatibility assessment. They connect values and motives to behaviour without producing a diagnosis or a compatibility percentage. ### 1. Identity Maya opens doors; Luca makes the product dependable. Both need a valued contribution when someone else owns more of their current work. ### 2. Others' perceptions Maya is energising but can change the promise. Luca is rigorous but can make questions feel like a test. Intent and experience do not always match. ### 3. Group role Maya creates momentum; Luca tests logic. Neither contribution decides who owns the choice once both have been heard. ### 4. Misunderstanding Enthusiasm sounded like commitment; questions sounded like refusal. They repaired the specific promise, but need shared rules before the next one. ### 5. Multiplying others Both delegate execution more readily than judgement. The exercise showed they can let another leader choose a route neither prefers. ### 6. Toward and away Maya fears becoming irrelevant and slow; Luca fears losing product coherence and technical relevance. These are hypotheses supported by their accounts and choices, not hidden facts. ### 7. Resources Maya favours commercial growth; Luca protects product capacity. Their different priorities need a sequence, not an assumption that funding removes trade-offs. ### 8. Best and worst At best they improve each other's judgement. At worst, managers must manage their disagreement instead of doing their jobs. ### 9. Friction Maya dislikes objections without alternatives. Luca dislikes consultation after a promise has been announced. Each can trigger the other's least useful response. ### 10. Being wrong Both corrected the commitment account. Maya repaired team credit. Luca's private apology was incomplete because the dismissal had been public. ### 11. Starting and finishing A choice is not delegated if a founder can reopen it without new evidence. A repair is not complete until affected people hear it. ### 12. Future failure A larger team could still revolve around two founders. The key question is whether success makes them willing to share authority, visibility and credit.