Should You Name Your Business After Yourself? w/ Jodie Cook
with Jodie Cook
Chris Do and Jodie Cook separate naming a business after its founder from making it dependent on them.
Chris Do
Founder, The Futur™ · March 11, 2026
The Name Was Never the Trap
A business can carry its founder's initials and still become independent. It can also hide behind an invented name and remain entirely dependent on one person. Jodie Cook, who started JC Social Media at 22 and later sold the agency, brings that distinction into focus through a naming decision that took almost no thought.
At a networking event, Cook realized that everyone introducing themselves had something she did not: a company name. The room supplied a pattern. Initials followed by a description of the service seemed to be the accepted format, and her turn was approaching.
JC Social Media was the result. Not an elaborate positioning exercise. Not a considered commitment to building an enterprise around her identity. A quick answer to an immediate social problem.
The questions came later. People noticed the connection between her initials and the business, then treated that connection as a potential liability. If the company carried her name, how would it ever function without her?
That concern forms the starting point for her conversation with Chris Do. Cook sees the same assumption discouraging people from developing a personal brand: visibility seems to promise permanent obligation. Become the face of the business, and the business supposedly becomes impossible to leave.
Do separates two decisions that this argument collapses. Naming a company is one. Designing how it operates is another. The letters on the door do not establish who must approve the work, maintain every relationship, or resolve every disagreement.
A founder's name is not the same as founder dependency.
The distinction matters because a naming debate offers an appealingly small problem to solve. Change a name, commission an identity, and the work appears complete. Changing the business beneath that identity requires a different kind of effort: hiring, teaching, transferring responsibility, and resisting the impulse to take it back.
Cook's own experience makes that difference concrete. She wanted a business that would allow her to travel. Instead, she initially built something that behaved like a job, with dependencies attached to her at every turn. The problem was not that clients could decode the initials.
The problem was that the operation needed her.
Personal visibility belongs in this discussion, but not as a substitute for examining the operation. The title of The Futur's You Don't Need a Personal Brand. You Need an Offer. points toward a neighboring distinction: the public identity of a business is not the whole business.
For Cook and Do, the useful question is not whether the founder appears in the brand. It is whether the founder has become the only person through whom the business can deliver. That shifts the discussion from optics to structure, and from what the company is called to what other people are actually allowed to do.
What a Buyer Can Actually Acquire
Do approaches the naming concern through the perspective of a potential buyer. A recognizable founder can attract attention, but attention does not explain what changes hands in a sale. His account centers on three things: the client accounts, the repeatable operation, and the people capable of doing the work.
These are not interchangeable assets. They support one another. Client relationships without delivery capacity leave promises unfulfilled. A process without customers has nothing to serve. A talented team without a workable operation or ongoing assignments is not the same proposition as an established business.
- A book of business: Current accounts and client relationships that can support continuing revenue.
- Repeatable systems: Processes that allow work to move from an initial input toward a dependable result.
- The team's talent: The people whose skills and judgment make those processes useful.
Do explains a book of business in practical terms: the accounts that remain active and the relationships that can produce further work. It is more than a contact list. Its relevance lies in the commercial relationships behind the names, including previous clients who can be approached again.
His description of systems is similarly concrete. There should be a process through which work can proceed without relying on one irreplaceable individual. If that person leaves, becomes ill, or is otherwise unavailable, the buyer should not discover that the supposed business was really access to a single human being.
Yet his own attempted sale reveals a complication. Founder independence is not the same as freedom from all dependency. Another employee can become just as essential to the value a buyer sees.
Do recalls receiving a seven-figure offer for his company. The prospective buyer wanted one particular employee to join as part of the transaction. That employee refused, and the sale did not happen.
The decisive obstacle was not the founder's name. It was a person's decision.
That story gives the discussion a sharper edge than a general endorsement of delegation. Moving work away from the founder does not automatically make every capability transferable. A company can stop depending on its owner while remaining exposed to the departure of another central contributor.
It also changes how the team should be understood. Employees are not simply a cost that sits beneath the founder's reputation. In Do's experience, one employee represented enough of the acquisition's value that the transaction could not proceed without them.
He does not present this as a comprehensive theory of mergers and acquisitions. Later, when discussing company size and saleability, he explicitly limits his authority to the creative businesses he knows. That restraint matters. His examples are operating experience, not universal acquisition criteria.
The narrower lesson is still substantial. A buyer needs more than the promise that a founder has stepped back. The business must contain relationships, methods, and capabilities that can continue working together after a change in ownership. A neutral name cannot manufacture that continuity, just as a founder's initials do not automatically prevent it.
A Different Name, the Same Starting Problem
Cook named her agency in seconds. Do took a more deliberate route with his design company, Blind. The contrast is useful because both businesses initially faced the same underlying condition: their founders were the people clients expected to reach.
For Do, Blind expressed a design philosophy developed while he was in school. The work should not begin with a predetermined answer. It should begin with the client conversation, before assumptions about the solution have hardened into a direction.
The name also created a deliberate contradiction. A visual design company called Blind invited curiosity. It was a way to start a conversation about how the studio thought, rather than simply identify the person who owned it.
None of that made the company independent at the beginning.
Do was the business because he was the person doing the work. Clients wanted him involved and expected to speak with him. The thoughtful name described an ambition and an approach; it did not replace the need to build an organization.
The separation happened through hiring and development. Do describes training people to do work he had previously handled, then gradually moving responsibility toward them. One intern became an art director, then a creative director, and eventually the principal point of contact.
That progression is important. The handoff was not simply an announcement that clients should stop calling the founder. It followed an expansion of another person's capability and standing inside the company.
Delegation includes transferring credibility, not just assigning tasks.
Do reinforced that transfer publicly. When Blind showed its work, the credits included everyone who had contributed. His own name appeared as one credit among others, rather than as the organizing explanation for everything the company produced.
In his telling, some clients eventually did not know he was involved at all. That was not evidence of a weakened company identity. It was evidence that other people had become credible representatives of the work.
The movement from individual maker toward business builder also gives context to The Futur's Moving from Makers to Entrepreneurs. Here, the change is visible in who receives recognition, who speaks to the client, and whose judgment the organization is prepared to trust.
Cook describes a less orderly beginning. First, she did not know how to hire. Then she did not know how to train. After that, she struggled to leave people alone. Each stage exposed a different obstacle, and solving one did not automatically solve the next.
She estimates that she spent about three years getting those things wrong before booking a trip to Australia forced a more serious approach to systemizing the business. The travel she had wanted from the outset became a practical reason to change how the agency worked.
The contrast between the two founders is not accidental naming versus intelligent naming. It is two routes toward the same operational requirement. Other people needed the ability, the standing, and the room to carry the company. Neither a descriptive set of initials nor a carefully chosen philosophy could do that work for them.
The Founder Cannot Remain the Choke Point
There is a stage at which a founder can remain close to nearly everything. Do describes the familiar small creative company where the owner knows every employee, has hired most or all of them, and still touches much of the work. That closeness can conceal how much the company depends on continuous personal intervention.
His rough reference points are around 20 people and around $5 million in revenue. He calls them a rule of thumb, not a boundary that defines every business. He also acknowledges that a smaller team can generate substantially more revenue.
The point is not the number itself. It is the change in what one person can reasonably hold together.
As a company moves from a small team toward a much larger one, the owner cannot remain the approval point for every creative choice, strategy decision, and piece of writing. Hiring more people does not resolve that problem if they are all waiting for the same person to act.
Do makes the absurdity vivid: the founder can end up paying a large team to watch the founder work. Capacity exists on paper, but authority has not moved. The company has expanded its payroll without expanding its ability to decide.
Some owners respond by shrinking the business again. In Do's account, they return to a size at which personal control remains possible. That is a different choice from building an operation that can function beyond their direct involvement.
At Blind, he describes a more deliberate separation. Four creative directors had room to run their work. They could seek his perspective, but that perspective was not automatically an instruction. An opinion from the founder was something to consider, not an order that displaced their judgment.
“Because you don't want to create a dependent culture,” Do says.
His approach contained clear reasons to involve him, rather than an open invitation to route every uncertainty upward:
- Creative directors could call when they felt creatively stuck or needed another point of view.
- They were required to involve him when a job appeared to be slipping away.
- They were expected to make a serious effort to solve the problem before escalating it.
Those conditions distinguish independence from abandonment. The founder remained available, but access had a purpose. His involvement was not supposed to become the default method for moving ordinary work forward.
This is the operational side of the growth question signaled by How To Grow A Small Creative Agency. In Do's example, growth requires more than additional people. It requires a different relationship between the owner and the decisions those people are hired to make.
He also resisted casual hovering. Checking over shoulders and offering unsolicited corrections would have told the team that independent authority was conditional on his constant satisfaction. Instead, the responsibility for requesting help sat with the creative directors.
That did not mean he never intervened. He recalls joining difficult client conversations after the team had exhausted its options and helping close the project. The distinction was frequency and purpose: an experienced closer brought in for a specific problem, not a founder whose presence was required for normal business to occur.
Founder Confidence Is Not a Job Title
Cook introduces a phrase for something less visible than a process: founder vibes. At a gym where she had competed, she began talking with the person at the desk and discovered that he owned the place. Something about his manner had already suggested that relationship to the business.
She wonders whether employees can learn to convey the same quality. The question reaches beyond confidence as presentation. An owner has a kind of authority that an employee does not automatically possess, even when both understand the work.
Do responds with a memory from early in his career. While waiting at an editorial company's office, he encountered a woman who checked whether anyone knew he was there and offered him breakfast. He interpreted her ease and attention as signs of ownership, though the anecdote does not establish her role.
What stayed with him was the willingness to act without making the interaction someone else's problem.
His more consequential example concerns an alarm at an office. He recalls people remaining at their desks, looking around while the sound continued. After finishing what he was doing, he entered the room and told everyone to leave the building.
The alarm turned out to be false. Afterward, he met with his management team and made the expectation explicit: when safety appears threatened, uncertainty is not a reason to leave everyone sitting in place.
Do reads the incident as a contrast between following an established process and recognizing when action is needed outside one. That is his interpretation of a particular event, not proof that employees lack judgment. The management lesson lies in the expectation he had to articulate afterward.
A rulebook cannot anticipate every situation. But expecting people to act beyond the rulebook creates another responsibility for the founder: they need to know what authority they have, and what will happen when they use it.
Responsibility requires permission to exercise judgment.
Do makes that expectation especially forceful with employees who deal directly with clients. He wants them to represent the company's principles rather than retreat into uncertainty whenever a customer challenges a decision.
His examples reflect his own commercial posture:
- Do not discount simply because a customer applies pressure.
- Do not assume every complaint requires an extended defense.
- Be prepared to refund a customer and end an unsuitable relationship.
These are not presented as a universal customer-service script. They illustrate the gap between a founder who feels authorized to make a decision and a representative who believes every difficult interaction requires permission.
There is a tension here. Earlier, Do rejects a culture that waits to discover what the founder wants. Now, he asks people to act in accordance with his principles. The distinction is between requesting a fresh answer and understanding the basis on which an answer can be made.
Without that distinction, delegation becomes imitation. With it, the founder's standards can guide independent decisions without requiring the founder's presence. Cook's contribution is to identify what can still block the transfer: an employee who expects punishment for acting will not experience that authority the way an owner does.
Make Independence Safe Enough to Practice
Cook presses on the consequence of that imbalance. Founders can project certainty partly because they do not experience their own company as employees do. Someone who can be fired has a reason to hesitate that the owner does not share in the same way.
Her question is whether psychological safety requires a promise that employees will not lose their jobs. Do refuses the blanket guarantee. Misconduct, inappropriate behavior, and a hostile working environment remain grounds for action, regardless of an employee's talent or financial value to the business.
He says he has lost good people because of their behavior, even when doing so hurt the company financially. That detail matters because it establishes a boundary around the confidence he wants employees to develop. Acting with authority does not place anyone beyond accountability.
The protection he offers is narrower. Employees should not fear being fired for making an ambitious attempt and taking a considered risk. In contrast, repeatedly choosing safety and doing only what has always been done can become a performance problem.
Protect initiative without excusing misconduct.
That resolves an important part of the conversation. A founder cannot demand independent judgment while making every imperfect decision feel dangerous. Nor can independence mean that standards of behavior disappear. The two forms of accountability need to remain distinct.
The same distinction changes the meaning of a handoff. Transferring a task is easy to announce. Transferring authority requires the founder to tolerate decisions made without prior approval, including decisions that the founder would have handled differently.
Cook's admission that she struggled to leave people alone captures the practical difficulty. Hiring and training were not the final steps. The next obstacle was her own behavior once someone else had the job.
Her wider discussion with Do continues in The Costs of Being Internet Famous. Here, however, the relevant cost is not visibility itself. It is the operational burden created when a founder's importance becomes a requirement for everything to proceed.
The practices described across their two companies offer a concrete sequence of work, without requiring a new name or a disappearance from public view:
- Train people to perform work previously handled by the founder.
- Move client contact toward capable team members as their responsibilities grow.
- Credit contributors publicly so the company is not understood as one person's output.
- Define when escalation is necessary and when the team should decide.
- Give advice without automatically turning it into a directive.
- Distinguish ambitious attempts from conduct the company cannot accept.
These practices also give Cook's travel story its significance. Booking Australia did not supply a better brand strategy. It created a reason to confront the dependencies that her everyday presence had allowed to continue.
Do's account of Blind points toward the same test from another direction. The company could continue while he taught or pursued other work because other people had become legitimate centers of responsibility. His role remained available without remaining universal.
A founder does not need to become invisible. The founder needs to stop being the only acceptable answer.
Before another naming debate, examine the decisions waiting for the owner, the clients who will speak to nobody else, and the employees who carry responsibility without authority. Those are the places where independence is either being built or quietly refused.
The name can stay. The dependency cannot.
TRANSCRIPT
Enjoyed this? There’s more where it came from.
Get insights on creativity, business, and design from The Futur.
You can unsubscribe anytime. By submitting, you agree to receive communications and to our Privacy Policy.
“It's hard to be a big company and have everything be about you.”
— Chris Do
Key Takeaways
Subscribe
Details
- Topic
- ENTREPRENEURSHIP