Hiring your first few people feels like a win. It also feels like risk.
Because hiring is not just “finding talent.” It is making legal promises. On paper. With money, equity, and rules tied to them. One sloppy offer letter can create months of stress later—right when you need speed.
This guide is about hiring the clean way. Not the “big company” way. The founder way: simple, clear, and safe. If you build in AI, robotics, or deep tech, this matters even more. Your team touches core code, models, data, designs, and inventions. If the paperwork is weak, your moat is weak.
And if you want help building a real IP wall around what your team creates, Tran.vc can help from day one. You can apply anytime here: https://www.tran.vc/apply-now-form/
The first truth: your offer letter is a contract, even when it feels casual
Many founders treat an offer letter like a polite note: title, pay, start date, “welcome aboard.” Then they send it fast so the person says yes.
But the offer letter is a legal tool. It sets expectations. It shows intent. And in many fights later—about pay, equity, IP, or who owns what—the offer letter is one of the first things lawyers look at.
So the goal is not to make it long. The goal is to make it clear. Clear beats clever. Clear beats friendly. Clear beats “we’ll figure it out.”
If you remember one thing: you are not writing for the person on a happy Friday afternoon. You are writing for the same person on a bad Tuesday six months later, when something goes wrong and everyone is stressed.
That is the moment your words matter.
Employee vs contractor: don’t guess
Most early teams mix full-time hires with contractors. That is normal. But misclassifying someone is one of the easiest ways to create a mess.
Here is the simple way to think about it:
If you tell the person when to work, how to work, what tools to use, and you treat them like part of the team day-to-day, they start to look like an employee.
If they control their schedule, use their own tools, work for other clients, and you pay for a result (not their time), they look more like a contractor.
Why it matters: if someone should have been an employee, but you paid them like a contractor, you can end up with back taxes, penalties, wage claims, and more. Also, equity plans are usually built for employees. Contractors may need different paperwork.
This is not the place to “wing it.” It is cheaper to set it up right than to fix it later.
And for deep tech teams, there is another issue: IP ownership. If a contractor writes code or designs a system, do you really own it? Not always—unless your contract says so in strong, clean language.
If you are not fully sure about your contractor agreements and invention assignment language, this is exactly the kind of foundation Tran.vc helps founders build. Apply anytime: https://www.tran.vc/apply-now-form/
The offer letter basics that should never be missingThe offer letter basics that should never be missing
A strong offer letter does not need fancy legal talk. It needs the right points written in plain words.
Role and who they report to. Titles drift fast in startups. Put the role, team, and direct manager. If you are not sure about title, describe the work. That is harder to argue with later.
Start date and work location. Remote, hybrid, in-office—say it. If the person is in another state or country, that affects taxes and rules. It is not just a culture choice. It is a legal choice.
Pay. Salary or hourly. How often paid. Any sign-on bonus. If there is a bonus, explain the conditions clearly. If it must be paid back when they leave early, put that rule in writing.
Benefits (if you offer them). If you do not, say so. Silence creates assumptions. Assumptions create anger.
At-will employment (for many US roles). If your company is in the US and you use at-will employment, say it clearly. It means either side can end the job at any time, for a legal reason, with or without notice. This matters because many founders accidentally write lines like “we expect at least 12 months” and now it starts to sound like a promise.
Confidentiality, IP assignment, and return of company property. This part is not “extra.” It is the spine. Your startup is mostly ideas turned into systems. Your offer letter should connect to your invention assignment and confidentiality agreement, or include them as part of the package.
Background check or reference check (if you do it). If the offer depends on it, say it.
Immigration note (if relevant). If the person needs visa support, do not keep it vague. Put what you can support and what you cannot. Clarity avoids heartbreak.
Signed acceptance. The offer is not “real” until signed. If you start onboarding before signature, you create risk.
That is the base.
Now let’s talk about the part that causes the most pain: equity.
Equity: your biggest trust asset, and your biggest legal trap
Equity is emotional. People hear “options” and think “ownership.” They hear “0.5%” and imagine a future worth millions. They also compare numbers across friends, posts online, and random calculators.
So your job is to be honest and simple.
Start by using the right words.
Most early-stage hires get stock options, not shares. Options are a right to buy shares later at a fixed price. You usually have to “vest” them over time, and you usually pay taxes at certain events.
If you write “you will receive 0.5% of the company” but you actually mean “you will receive options equal to 0.5% of the fully diluted cap at the time of grant,” you just created confusion.
And confusion is not neutral. Confusion becomes distrust.
Here is what a clean equity section should do:
- Name the equity type. Options? Restricted stock? RSUs? (Early startups rarely use RSUs for early hires. Options are common. Some founders choose restricted stock for very early execs/founders. Each has different tax effects.)
- State the number of units. For options: “X options.” Not a percent. Percent changes with dilution. People can understand “X options out of Y total,” but you need to be careful about what “total” means.
- State vesting clearly. The standard is 4 years with a 1-year cliff, monthly vesting after. That means if they leave before 12 months, they get nothing. After 12 months, they get 25%, then the rest vests monthly. If you do something different, explain it.
- Explain that board approval is needed. Equity grants usually require board consent and a formal grant date. Without that, you are promising something you might not be able to deliver on the date you think.
- Reference the plan documents. The offer letter should say the grant is subject to the equity plan and option agreement. That is where the real rules live.
- Do not promise future refresh grants. You can say you may review compensation, but avoid lines that sound guaranteed. Promises become liabilities.
The percent problem: why you should avoid it in offer letters
Founders love percent because it feels clear. Candidates love percent because it feels like “ownership.”
But percent is slippery. It changes after fundraising, option pool increases, and conversions.
If you must use percent in conversation, do it as a range and be clear: “This is a rough range today; the final grant is in options and approved by the board.” Then put only the option number in writing.
Also, if you do not have an option pool set up yet, do not “promise” options casually. Get your structure ready first.
Tran.vc works with technical founders on building IP and the right early foundations so fundraising and hiring do not get messy later. If you want that support, apply here: https://www.tran.vc/apply-now-form/
Vesting, cliffs, and acceleration: keep it boring, unless you truly know why it isn’t
Most teams should start with boring vesting.
Boring vesting is not lack of care. It is care.
Because custom vesting patterns create questions, exceptions, and feelings of unfairness. They also create legal work later if you need to amend agreements.
If you are hiring a key leader and you want acceleration (like “single trigger” or “double trigger”), do not copy a template from the internet. Acceleration changes incentives during acquisition talks. It can also complicate buyer diligence.
The simple rule: if you cannot explain the acceleration terms in plain words in one minute, do not add them yet.
The post-termination exercise window: a quiet detail that can hurt good people
One of the most overlooked parts of option grants is the time window after someone leaves to exercise options. Many plans use 90 days. That is common.
But think about what that means in real life.
If an engineer leaves and has vested options, they may have to pay exercise cost and maybe taxes within 90 days—at a time when they might be job hunting. Many cannot afford it. They lose the options.
Some startups extend the window. That can be a nice benefit, but it also has tax and plan issues. You need proper advice before changing it.
Even if you keep the 90-day window, explain it clearly during the offer stage. People feel betrayed when they learn later. People feel respected when you tell them early.
Compliance is not “big company stuff.” It is survival stuff.
Compliance sounds like paperwork. But the reason it exists is simple: the government wants taxes paid, workers protected, and discrimination reduced. If you ignore it, the pain shows up fast, usually at the worst time.
Here are the common early-stage compliance holes that bite founders:
1) Hiring in a new state without registering properly
A founder in California hires someone in Texas. They think it’s fine because “remote.” But hiring in a state can trigger state tax withholding, unemployment insurance, workers’ comp rules, and “doing business” registration.
This is not optional. Many payroll systems help, but you still need to set it up correctly.
2) Not using I-9 correctly (US)
In the US, you must complete Form I-9 for employees to verify work authorization. There are timing rules. There are document rules. If you ignore them, penalties can follow.
It is not glamorous, but it is basic.
3) Overtime missteps
If someone is non-exempt, overtime rules matter. Titles do not decide exempt status. Duties and salary thresholds do.
Misclassifying can lead to back pay claims. Those claims can stack quickly.
4) Missing required notices and policies
Many states require you to give certain notices at hire, show posters, provide sick leave rules, and more. If you are small, it still applies.
5) Paying contractors without thinking about IP and security
A contractor can walk away with access to your repo, your model weights, your data pipelines, and your architecture docs. If your access controls are weak and your contract is weak, your risk is high.
This is why “IP and compliance” are tied together. The people you hire touch your inventions. If your legal setup is sloppy, your moat leaks.
Tran.vc focuses on helping technical teams protect what matters early—so you can hire and build with confidence. Apply anytime: https://www.tran.vc/apply-now-form/
Offer Letters That Hold Up
Why the offer letter matters more than founders think
An offer letter is not a “welcome note.” It is a written promise that shapes how someone understands their job, their pay, and their future at your company. When things go well, nobody reads it again. When things get tense, it becomes the first document everyone points to.
A clean offer letter does not need heavy legal words. It needs clear words that leave no space for guessing. The goal is to protect both sides and avoid a slow, painful mismatch later.
What to include so there are no surprises later
Start with the basics: role, manager, start date, and where the work will happen. These sound simple, but they are the parts that drift the fastest in startups. When you spell them out, you create a shared starting point that you can update later with a new letter if needed.
Then write pay in plain terms. If it is salary, say the yearly amount and the pay schedule. If it is hourly, state the hourly rate and how hours are tracked. If you offer a sign-on bonus, explain when it is paid and what happens if the person leaves early.
At-will language without sounding cold
In many US roles, employment is at-will. That means either side can end the job at any time, for a lawful reason. This line is important because founders sometimes add friendly phrases that sound like a long-term promise, even if they did not mean it.
You can keep the tone respectful while staying clear. The goal is not to threaten anyone. The goal is to prevent the offer letter from becoming an accidental “guarantee” of a certain time period.
The documents that should be tied to the offer
The offer letter should connect to your key agreements, even if those agreements live as separate documents. Most teams use a confidentiality agreement and an invention assignment agreement. Some also include a code of conduct and basic security rules for devices and accounts.
If your offer letter does not point to these, you create a gap. That gap often shows up during fundraising or acquisition talks, when someone asks, “Do you own what your team built?” You want the answer to be simple and confident.
Offer letter language that creates confusion
A common mistake is vague wording like “equity will be granted soon” or “we expect a long-term commitment.” These lines may feel friendly, but they can also cause arguments later. Equity is not a promise until it is approved and formally granted, and commitment is not enforceable in the way many founders think.
Another mistake is using percent in writing. Percent can change with dilution and option pool increases. If you discuss percent in conversation, keep it out of the offer letter and focus on the actual option count in the final document.
Equity Without Regret
Start by using the correct words
Most early startup hires receive stock options, not shares. Options are a right to buy shares later at a fixed price, usually after they vest over time. This is different from owning shares today, and it is important to say the right thing from the start.
People trust you more when you explain equity in simple words. They do not need a finance lesson, but they do need you to be honest about what they are getting and what they are not getting.
The five equity details that must be written clearly
Your equity section should name the equity type and show the number of options. It should also state the vesting schedule, because vesting is where most misunderstandings begin. When the vesting is standard, explain it in plain terms so the person knows what happens at month six, month twelve, and year two.
You also need to say the grant is subject to board approval and the terms of the plan. This is not a trick. It is how equity works in a properly run company. When you say it upfront, you avoid the feeling that you changed the deal later.
Vesting that stays fair as the company grows
Standard vesting is boring for a reason. It treats people fairly, it is easy to explain, and it reduces the need for special cases. If you make vesting custom for many hires, you will spend time later explaining why one person is different from another.
If you want to reward a key hire, it is often better to adjust the total grant size rather than invent a complex vesting pattern. Complexity tends to create more questions than motivation.
The cliff, explained like a human
A one-year cliff means the person earns nothing until they complete twelve months. After they cross that line, a chunk vests, and then the rest vests each month. Founders often assume everyone knows this, but many first-time startup hires do not.
Explain the cliff kindly and clearly. The cliff exists to protect the company from giving equity to someone who leaves quickly. It also protects the team from feeling like equity is handed out with no real time earned.
The exercise window problem most founders ignore
Many option plans give a person about 90 days to exercise vested options after they leave. In real life, that is a short window. People may not have the cash to pay the exercise cost, and they may be worried about their next job.
Even if you keep the standard window, it helps to explain it early. People do not like learning key rules after the fact. They feel respected when you tell them the truth at the start.
What not to promise in equity conversations
Avoid promising refresh grants on a set timeline, unless you truly intend to guarantee it and have the plan to support it. It is fine to say you review pay and equity over time, but do not lock yourself into language you cannot keep.
Also avoid promising a future percent. Your company will change as you raise money and grow the option pool. Promise what you can actually deliver: a grant number, approved properly, with the plan terms attached.
Compliance That Keeps You Out of Trouble
Compliance is not paperwork, it is risk control
Many founders think compliance is for big companies with big HR teams. In truth, early startups have more risk because one mistake hits harder. A wage claim, a tax issue, or a misclassified worker can drain focus and cash when you are trying to ship product.
The good news is that most compliance problems come from a small set of repeat mistakes. If you address them early, you reduce your risk fast.
Hiring across states is not “just remote”
When you hire someone in another state, your company may need to register there and follow that state’s payroll and labor rules. This can affect tax withholding, unemployment insurance, workers’ comp, and required notices.
Many payroll providers help, but they do not replace the need to set up the right state accounts. If you skip the setup, problems tend to show up later when the state sends a notice, or when a worker files for benefits.
Employee vs contractor classification is a common trap
If you control the person’s schedule, process, and tools, they start to look like an employee. If they work independently, serve other clients, and deliver a clear output, they look more like a contractor. Founders often blur this line because they just want work done.
Misclassification can lead to back taxes and penalties, but it can also create problems with equity and IP ownership. If a contractor builds core systems and your contract is weak, your ownership story can become messy fast.
The basic hiring steps many teams miss
In the US, you have to complete the I-9 process for employees, and you have to follow certain timing rules. You also need to set people up properly in payroll, with the correct withholding and reporting.
You may also need to provide certain state notices at hire. These vary by place, which is why founders get caught off guard. It feels small, until it becomes a fine or a dispute.
Exempt vs non-exempt is not about job titles
Overtime rules are tied to job duties and pay thresholds, not titles like “engineer” or “manager.” If you get this wrong, you can face claims for unpaid overtime.
Founders often assume salaried means exempt. That is not always true. If you are unsure, it is safer to check early than to fix it after someone leaves and files a complaint.
Protecting IP While You Hire
Hiring creates IP, but only good paperwork makes it yours
Every new hire touches your product and your ideas. In AI and robotics, that can mean model changes, data work, hardware designs, system flows, and new methods. If your agreements do not clearly assign inventions to the company, you can end up with weak ownership.
This matters during fundraising. Investors often ask if every contributor signed invention assignment documents. If you cannot show clean proof, it can slow or kill a deal.
Confidentiality that matches how your team really works
A good confidentiality agreement is not only about “don’t share secrets.” It should fit your actual workflow. If your team uses shared docs, code repos, and customer data, the agreement should cover those areas in simple words.
It should also explain what happens when the job ends. People should return devices, remove access, and not keep private files. When this is clear, it is easier to enforce without drama.
Invention assignment that covers modern tech work
Invention assignment should cover what people build on company time and with company resources. It should also address what happens if someone works on a side project that overlaps with your core product.
For deep tech teams, this is not a minor detail. A small overlap can lead to major confusion later. Clean boundaries protect both the founder and the employee, because everyone knows what belongs where.