The New Hire's Roadmap to Thriving on a Small Team or Startup

On a team of eight, nobody runs a formal onboarding program for you, so here is how to build one yourself, from first-day paperwork through day 90.

By Marguerite Dunlevy · Oct 05, 2026 · 11 min read

Featured image for "The New Hire's Roadmap to Thriving on a Small Team or Startup"

Joining a small team or a startup means there is often no onboarding coordinator, no training week, and no printed org chart. What there is instead: a manager who is also doing three other jobs, a product nobody has had time to document, and a seat waiting for someone who can work out what needs doing. This roadmap covers the paperwork to finish before day one, the specific things to accomplish in your first week, what to have shipped by day 30, 60 and 90, and the exact words to use in the conversations that are hardest to start.

Some of what follows depends on your employer and your state — payroll forms, benefits enrollment windows and equipment policies all vary. Where that is the case, the guide says so and tells you who to ask.

Before You Start: Pre-Day-One Checklist

Work through these in the week before you start. On a small team, nobody will chase you for most of them, and the ones that affect your pay are your problem if they slip.

Email your hiring contact to confirm the start time, the address or video link, who will meet you, and whether the first day is in person. Startups move offices and change plans often.
Ask which identity and work-authorization documents to bring for Form I-9. Every employee hired after November 6, 1986 completes Form I-9, with Section 1 done when you start work (Wikipedia, citing federal I-9 requirements, undated). Your employer must complete and sign Section 2 within three business days of your first day (U.S. Citizenship and Immigration Services, 2025-01-20).
Complete your Form W-4, the Employee's Withholding Certificate, which your employer uses to withhold the right amount of federal income tax from your pay (Internal Revenue Service, 2022-06-21). All new employees fill one out when starting a job (Paychex, 2025).
Ask whether your state requires a separate withholding form, since state payroll paperwork differs from state to state. Your employer's payroll contact will tell you which ones apply.
Submit direct deposit details and ask when the first payday falls and which period it covers. Pay schedules vary by employer and some new hires wait longer than they expect for the first deposit.
Ask when benefits enrollment opens and when it closes. Enrollment windows are set by the employer and the plan, and missing one can mean waiting months.
Turn on your work laptop or accounts before day one if IT allows it. Set up two-factor authentication on your work email and password manager at home, not while three people wait for you in a kickoff meeting.
Do a commute dry run at the actual hour you will travel, or, if remote, test your camera, microphone and internet on the company's video tool with a friend.
Read everything public about the product: the website, the pricing page, recent blog posts, app store reviews. Write down five questions the public material does not answer.
Ask for a list of who works there and what each person does. Teams under about 30 people often have no org chart, and a plain list from your manager saves you a month of guessing who owns what.
Create one running notes document for acronyms, customer names, internal tool names and decisions you overhear. You will hear 40 unfamiliar words in week one and remember six.
Confirm what people actually wear and whether there is a standing team meeting you are expected to attend on day one.

Day 1 to Week 1

First morning (first three hours)

Hand over your I-9 documents and complete Section 1. Your employer has three business days from your first day to finish Section 2 (U.S. Citizenship and Immigration Services, 2025-01-20), so do not leave your documents at home.
Get into email, chat and the shared drive, and send one message in the team channel introducing yourself in three sentences.
Write down the first five names you hear with a note about what each person does. Say each name back once in conversation that morning.

End of day 1

Payroll paperwork submitted: I-9 Section 1, W-4, direct deposit, and any state form your employer gave you.
You can name your manager's top priority for the quarter in one sentence, because you asked and wrote it down.
A recurring 1:1 with your manager is on the calendar — weekly is standard on small teams. If your manager does not book it, book it yourself.
One question asked out loud in a group setting, so people hear your voice on day one rather than day nine.

End of day 3

Ten teammates' names, roles and the thing each one owns, written in your notes doc.
You have found where the real work lives: the ticket board, the shared folder, the channel where decisions actually get made rather than the one where they get announced.
Access confirmed to every tool you need. On small teams, access is usually granted by whoever has admin rights rather than an IT desk, so ask the person, not a form.
One small task completed, however minor — a typo fixed, a document tidied, a customer email answered under supervision.

End of week 1

A written list of what your manager expects from you in your first month, in their words, confirmed by email so you both have the same version.
Three 20-minute introductory calls held with people outside your immediate function, each ending with the question: "What slows you down that I might be able to help with?"
Your own summary sent to your manager on Friday: what you learned, what you are unclear on, what you plan to do next week. Four bullets is enough.

The difference this makes is concrete. One new hire spends week one reading documentation and waiting to be assigned work, then on Friday has nothing to show and no questions. Another finishes the same reading, notices the customer onboarding checklist is six months out of date, asks "Can I update this?", and has a visible contribution by day five. Same information, different ending.

30/60/90 Day Benchmarks

These are things a manager can check without taking your word for it. Adjust the specifics to your role, but keep the shape: by 30 you have produced something, by 60 you own something, by 90 you improve something.

Day 30

One piece of work shipped end to end and visible to someone outside your team: a feature released, a campaign sent, a report published, a customer issue resolved from first contact to close.
Four weekly 1:1s held with your manager, with notes you keep and refer back to.
A written list of every recurring task you now own, shared with your manager so they can correct anything you have wrongly assumed is yours.

Day 60

You run at least one recurring responsibility without being asked — the weekly numbers, the support rota, the release checklist — and nobody has had to remind you.
One problem you identified yourself turned into a proposal: a short written note with the problem, two options and your recommendation, sent to the person who can decide.
You have given useful input in someone else's area at least twice — a review of a colleague's draft, a bug caught before launch — which is how trust gets built on a team of ten.

Day 90

One process documented that previously existed only in someone's head, saved where the team can find it. On small teams this is often the single most valued thing a new hire produces.
A feedback conversation held with your manager about two specific pieces of your work, with at least one change you will make as a result written down.
Agreement in writing on what you own for the next quarter, including what you are deliberately not doing.

If your startup has no formal review at 90 days — many do not — hold the conversation anyway. A 25-minute meeting you request is worth more than a review process that never arrives.

Scripts for Common Onboarding Conversations

Use these close to word for word. They are written to be said out loud, not read.

Asking your manager what to prioritize (week 1)

When you have been given five things and no order
"I've got five things on my list: the onboarding emails, the data clean-up, the two customer calls, and the documentation. If I can only finish two of them this week, which two matter most to you? I'd rather do two properly than four badly."

Introducing yourself to the team (day 1)

Posted in the team chat or said at a standing meeting
"Hi, I'm Dana — I started today on the support side. I came from a smaller agency where I did a bit of everything. For the next couple of weeks I'll be asking a lot of questions, so if I'm interrupting at a bad time, just say so and I'll come back later."

Asking for an introductory chat with someone outside your team (week 1)

Sent as a short message, not a calendar invite with no explanation
"Hi Marcus — I joined on Monday and I'll be working on the billing emails, which I think touch your work. Could I get 20 minutes this week or next to hear how it looks from your side? Happy to work around your calendar."

Asking for feedback at 30 days

Booked as its own conversation, not tacked onto a status update
"I've been here a month and I'd like 20 minutes to check I'm pointed the right way. Two specific things: the pricing page draft and the way I handled the refund request last Tuesday. What would you have done differently in each?"

Admitting you are lost (any time in the first 90 days)

Better said on day three than discovered on day thirty
"I want to flag that I'm stuck on the import script — I've spent about two hours on it and I'm going in circles. Can you point me at someone who's done it before, or tell me if it's fine to park it until next week?"

Asking who decides something (first 60 days)

Useful when a small company has no documented process
"Quick question — if I want to change the wording on the signup form, who needs to say yes before I do it? I'd rather ask now than undo it later."

Frequently asked questions

What if I forget someone's name in the first week?

Say so immediately rather than avoiding the person for a month: "I'm sorry, I've met about twenty people this week — tell me your name again?" Nobody holds this against a new hire in weeks one and two, and they will hold it against you in week six. Keep a list in your notes with the name, role, and one detail about what they own, and read it before meetings for the first two weeks.

Nobody has time to train me. What do I do?

This is normal at companies under about 30 people and it is not a sign you were a bad hire. Shift from waiting for training to asking for 20-minute slots with a specific question attached — "Can you walk me through how a refund gets processed?" gets accepted far more often than "Can you train me?". By end of week one, ask your manager directly which two people you should learn the most from, then book time with each.

Am I asking too many questions?

Batch them. Keep a running list in your notes document and bring five questions to your 1:1 rather than sending five separate messages across a day, and search the shared drive and chat history first so you are not asking about something already written down. Expect your question volume to drop noticeably by week three — if it has not by day 60, say so to your manager rather than hoping it resolves itself.

When should I raise pay or a title change?

Not in your first 90 days unless your job changed substantially from what you were hired for. Spend those 90 days producing things your manager can point to, then raise it at the first formal review or at a date you agree in advance. Pay structures differ a great deal between small companies — some have salary bands, many do not, and some weight equity heavily — so ask early how pay decisions get made here and check current market rates for your role and state on public salary sources before you open the conversation.

I made a visible mistake in week two. How bad is it?

Far less bad than hiding it. Tell the person affected within the hour, state what happened, what you have already done, and what you need: "I sent the email to the wrong list. I've paused the sequence and drafted an apology — can you look at it before I send?" Managers judge new hires on how quickly problems surface, not on whether they occur, and a mistake disclosed on day 12 is a story; one discovered on day 40 is a trust problem.

My team is remote or mostly asynchronous. Does this roadmap still work?

Yes, with two changes. Replace the in-person moments with deliberate ones: a short video introduction in the team channel on day one, and video on for your first few 1:1s so people attach a face to your name. Write more than feels necessary for the first 30 days — a Friday summary of what you did, what you learned and what you are blocked on — because on a remote team, work nobody sees is work nobody knows happened.

Sources

U.S. Citizenship and Immigration Services (USCIS) — Form I-9 Instructions (2025-01-20)
Wikipedia (citing federal I-9 requirements) — Form I-9
Internal Revenue Service (IRS) — What people new to the workforce need to know about income tax withholding (2022-06-21)
Paychex — What Is a W-4 Form & How to Fill It Out In 2025 (2025)

Written by

Marguerite Dunlevy

Marguerite oversees coverage of job hunting and career pivots, with a focus on how people make decisions when the path forward isn't obvious. She's drawn to the messy middle of a career change more than the tidy success story. Her writing tends to ask what a 'good job' even means to the person doing it.