The Startup Partner Archetypes I Learned To Avoid

• Category A, The Corporate Bubble Technologist
• Category B, The Entrepreneur Before Experience
• Category C, The Gung Ho Delegator
• Category D, The Idea Person
• Category E, The AI Vibe Founder
• Category F, The Perpetual Networker
• Category G, The Equity Accountant
• Category H, The Weekend Founder
• Category I, The Title Collector
• My Criteria For Technology Business Partners

These are technical people who have worked at large companies for many years and have become disconnected from how a small business earns money.

Large companies often isolate developers from customers, pricing, sales, project costing and collections. The developer receives a ticket, completes the ticket and moves on to the next ticket. Someone else finds the customer, negotiates the contract, manages the budget and explains why the project exists.

After several years of this, some people begin to believe that software appears because somebody created a Jira ticket for it.

They may be very capable technically, but they have never had to convince anyone to buy something, chase an unpaid invoice, reduce a feature because the budget disappeared or decide whether an extra week of development will produce any commercial benefit.

Yes, they may dream about leaving their employer and starting something of their own. You may look at their experience and think you have found the perfect CTO.

Think again.

A startup cannot afford a technical partner who treats every product decision as an engineering exercise. Customers do not care how elegant the architecture is when the product does not address a painful problem. They will not pay extra because the team used the developer’s favourite framework.

Some corporate developers also bring enterprise habits into a company that has no revenue. They want committees, extensive planning, perfect infrastructure and six months to choose a database. Meanwhile, the founder is trying to persuade one customer to return an email.

Your technical partner needs commercial judgment. They should understand that code is part of the company, and the company still has to sell, collect money and stay alive.

These are people coming out of university who reject the idea of working for anyone else and gaining experience first. They want to jump directly into entrepreneurship and gain their experience by failing repeatedly with somebody else’s time and money.

There are exceptional young founders, of course. Age alone tells you very little. The warning appears when confidence has no connection to experience, curiosity or humility.

They may dismiss employment as a waste of time without considering what a good job can teach them about customers, deadlines, teamwork, budgets, management and professional standards.

They want to become the CEO before they have learned how to complete a project, manage a difficult conversation or show up consistently when the work becomes boring.

Failure can teach valuable lessons. It can also become an expensive substitute for listening.

Maturity and experience go a long way. A partner does not need twenty years in an office. They do need evidence that they can accept responsibility, learn from other people and complete something after the excitement disappears.

These are the all gung ho about business types who claim that a good business person should not need to understand the underlying technology. According to them, a visionary founder dreams up the idea and hires “others” to handle all that technical stuff.

They often say things like, “I am the strategy person,” which sometimes means, “I will attend meetings and explain my vision while everyone else does the work.”

This attitude becomes expensive very quickly.

A nontechnical founder can absolutely build a successful technology company. They can bring customer access, sales ability, industry knowledge, operations, partnerships and product judgment. They do not have to become the lead developer.

They do need to understand what they are building.

They need enough technical literacy to evaluate options, ask sensible questions, understand tradeoffs and know when a developer is explaining a genuine challenge or inventing a convenient excuse.

AI coding has made this even more important. A founder can now generate a prototype without understanding databases, permissions, security, billing or deployment. The application appears to work, and everybody celebrates until the first customer logs into somebody else’s account.

You can delegate implementation. You cannot delegate every ounce of technical judgment and still expect to run a technology company responsibly.

The Idea Person arrives with the most valuable contribution of all, an idea.

They expect somebody else to design it, build it, sell it, support it and perhaps provide the money. In exchange, they are prepared to contribute additional ideas whenever the team becomes distracted by execution.

They often protect the idea as if it were a government secret. They ask developers to sign an NDA before explaining that the product is “Uber, but for something Uber has not reached yet.”

The Idea Person also has a generous approach to equity. They may offer a technical partner 10 percent of the company for building the entire product, because the original idea deserves the remaining 90 percent.

Ideas have value when they are connected to customer knowledge, distribution, execution or evidence that people are prepared to pay.

A good partner contributes more than the starting thought. They bring access, skills, credibility, work and the ability to move the company forward without waiting for somebody else.

This is a newer archetype.

The AI Vibe Founder built an application over the weekend using an AI coding tool and now believes the company is 95 percent finished.

The landing page looks impressive. The dashboard has gradients. The buttons move. A chatbot greets you by name.

Behind the interface, the permissions are wrong, the database structure changes every time the founder adds a feature and nobody knows what happens when two customers use the product at once.

The founder keeps prompting the coding agent to “fix everything” until the original bug disappears and three new ones arrive.

AI coding is incredibly useful. It allows founders to test ideas, create prototypes and learn faster. It also makes it possible to create complicated software without understanding the complications.

The warning appears when the founder confuses generated code with a dependable product.

A useful partner respects what AI can do and remains aware of what still needs testing, review and experienced engineering.

The Perpetual Networker knows everybody.

They have coffee meetings, lunches, startup events, investor introductions, mastermind groups and a calendar that appears more impressive than the company.

They speak often about opportunities, partnerships and people they plan to connect you with. Every conversation ends with, “I know someone you should meet.”

Unfortunately, none of these introductions become customers, employees, investors or useful partnerships.

Networking can be valuable. Relationships can open doors that skill alone cannot. The problem begins when networking replaces execution.

Some people enjoy being adjacent to entrepreneurship more than they enjoy building a company. They like the language, events and social status. They disappear when it is time to write the proposal, call the customer or finish the work.

Ask what their network has produced. A long contact list is not the same as the ability to create an outcome.

The Equity Accountant wants to discuss ownership before anybody has created anything worth owning.

They calculate percentages, titles, voting rights and hypothetical exit values during the first meeting. They may spend three weeks debating whether 18 percent is fair while the company has no product, customer or domain name.

They are highly alert to the possibility that somebody else might receive more than them. They are less alert to the possibility that the company might produce nothing.

Ownership discussions are important. Expectations should be documented early. Vesting, responsibilities and decision rights deserve careful thought.

The warning appears when somebody is more interested in protecting their share than increasing the value of the company.

A good partner wants a fair arrangement and understands that 50 percent of nothing remains nothing.

The Weekend Founder is deeply committed, subject to availability.

They have a full time job, family responsibilities, hobbies, travel plans and several other projects. None of that is a problem by itself. Many companies begin while the founders are employed.

The problem is that the startup receives whatever time remains after everything else has been completed.

They miss meetings because work became busy. They delay tasks because the weekend filled up. They promise to make progress during the holidays and then need the holiday to recover.

Every Monday, they return with enthusiasm and a revised plan.

A part time founder can contribute considerably when the commitment is explicit and dependable. A partner who promises full commitment while delivering occasional attention creates resentment.

Discuss availability honestly. Ten dependable hours each week can be useful. Forty imaginary hours cannot.

The Title Collector wants to be called Cofounder, Chief Strategy Officer, Chief Innovation Officer or Chief Visionary Officer before deciding what work they own.

They care about how the role appears on LinkedIn. They announce the company before the team has agreed on the product. They update their biography immediately and their task list eventually.

Titles can help clarify responsibility once responsibility exists.

In a young company, the question is simple: what do you own, and what happens without you?

A title should describe the work somebody is already doing. It should not serve as compensation for work they hope to avoid.

A startup partner should be able to make progress without waiting for perfect conditions, a large budget or detailed instructions. When the obvious route is unavailable, they look for another route.

Resourceful people do not arrive with every answer. They know how to find answers, test assumptions and ask for help before a small obstacle becomes a six week delay.

A good partner understands the customer, the problem and the environment surrounding the product.

Technical ability cannot compensate for complete ignorance of the domain. The team should know how customers currently address the problem, what they dislike, what they already pay for and why previous attempts may have failed.

Every founder should understand how the company plans to attract attention, create demand and convert interest into revenue.

The technical partner does not need to become the head of sales. They should understand that customer acquisition is part of the product conversation.

A feature that takes three months to build and has no effect on sales, retention or delivery deserves to be questioned.

The company needs people who can attract customers, employees, advisors, partners and supporters.

Outgoing does not mean loud. Quiet people can build excellent relationships. The useful quality is the ability to create trust, communicate enthusiasm and make other capable people want to participate.

Business partnerships often fail because expectations remain unspoken.

A good partner can explain what they are doing, raise concerns early, disagree without creating unnecessary drama and admit when they do not know something.

They do not disappear for two weeks and return with either nothing or a completely different company.

A good online presence helps people understand who the partner is, what they know and how they think.

This does not require a huge audience. A thoughtful LinkedIn profile, useful articles, previous projects, open source contributions or examples of their work can establish credibility.

It also shows whether the person has been consistently interested in the field or discovered entrepreneurship last Thursday.

Look for somebody who has completed difficult projects.

The project does not have to be a successful startup. It may be a product launch, client engagement, community, technical project, research initiative or sales target.

Completion demonstrates that the person can survive the less glamorous middle period after the idea and before the result.

A partner should understand that every feature, hire and subscription consumes money or time.

They should be able to discuss tradeoffs, pricing, customer value and priorities without retreating into their specialty.

Commercial judgment helps the team choose what deserves attention now and what can wait.

Two good people can still make poor partners when they want different companies.

One person may want a profitable company with a small team. The other may want rapid growth and venture funding. One may want to sell within five years. The other may want to operate the company for decades.

Discuss ambition before discussing logos.

The best partner is often the person who consistently does what they said they would do.

They attend the meeting, finish the task, communicate delays and remain present when the work becomes repetitive.

Charisma can create an exciting first meeting. Dependability builds the company.