The Order of Decisions Before Your First Nearshore Hire
Share this article
Key takeaways
- Name the exact bottleneck your firm needs to cover before you write a job description.
- Decide the engagement type, full time, part time, or flexible, before you screen a single candidate.
- Confirm upfront what stays with your firm: software licenses, permits, and any required stamping.
- Set vetting and time zone criteria before you review profiles, not after.
- Plan the first weeks handoff and who owns the relationship before day one.

A step by step decision order for architecture firms planning their first nearshore hire, from naming the bottleneck to the first weeks of onboarding.
Most guides about nearshore staffing talk about where to find candidates. Almost none of them talk about the decisions your firm needs to make before you ever look at a candidate. Here is that order, five decisions, in the sequence that actually protects a first hire.
Decision One: Name the Bottleneck Before You Write the Job Post
Do not start with a job title. Start with the specific task that is slowing your firm down this month. Maybe redlines pile up before permit submissions. Maybe 3D modeling eats hours your senior staff should spend with clients. Maybe construction documentation only moves when someone stays late.
Name that one bottleneck before you draft a job description. A job post written around a vague idea of "more capacity" attracts the wrong candidates and makes every later decision harder to reverse.
Decision Two: Choose the Engagement Type Before You See a Candidate
Once you know the bottleneck, decide how you want to engage the person who fills it: full time, part time, or a flexible arrangement that scales with your pipeline. Anchor work, client relationships, design direction, the roles that carry your license, tends to fit full time. Production work, drafting, modeling, documentation, often fits a flexible or part time engagement instead.
Make this call before you see any candidates. Choosing the type after you meet someone you like usually means bending the engagement to fit a person, instead of fitting the engagement to the work.
Decision Three: Confirm What Stays With Your Firm
Before recruiting starts, write down what never leaves your firm. This decision defines what stays in house: licenses, stamps, and software standards. Software licenses, permits, and any required stamping stay with your studio throughout the engagement. A nearshore professional works inside your existing Revit, ArchiCAD, or BIM files and follows your standards. Signature and stamping responsibility stays with the licensed architect of record at your firm.
Confirming this early removes a source of confusion later: nobody on your team, or on the nearshore side, should be guessing who owns what once real project files are involved. For a closer look at how licenses and software standards stay with the studio on a live workload, see How Small Architecture Studios Add BIM and CAD Capacity.
Decision Four: Set Vetting and Time Zone Criteria Before You Review Profiles
Write down the software stack, the experience level, and the time zone you need before you look at a single profile. WorldTeams places every professional in the client firm's own time zone before a profile is ever shared, which only works if your firm has already defined what "the right fit" means for this specific bottleneck.
Skipping this step pushes the vetting work back onto your team later, one resume at a time, instead of letting a defined set of criteria do that filtering upfront.
Decision Five: Plan the First Weeks Handoff Before Day One
Decide who on your team owns the new hire's onboarding before that person's first day. The first weeks should focus on access to your project files, a walkthrough of your standards, and a kickoff with whoever runs the project day to day, not on figuring out who is responsible for any of that.
Every WorldTeams placement also carries a two week replacement guarantee, so if the fit is not right once real work starts, your firm has a defined way to address it instead of living with a mismatch while the next decision waits.
The Order, In One Place
| Decision | Question to answer | Comes before |
|---|---|---|
| 1. Bottleneck | Which specific task is slowing the firm down right now? | Writing the job post |
| 2. Engagement type | Full time, part time, or flexible? | Screening candidates |
| 3. What stays in house | Who holds licenses, permits, and stamping? | Recruiting |
| 4. Vetting and time zone | What stack, experience, and time zone does the role need? | Reviewing profiles |
| 5. First weeks handoff | Who owns onboarding and the project kickoff? | The hire's first day |
Firms that follow this order tend to make one clean hire instead of three rushed ones. If your firm is still weighing whether a nearshore hire even fits your current bottleneck, How Many Remote Seats Your Firm Should Start With is the step right before this one. Once you have named the bottleneck, Full Time or Flexible? A Decision Guide for Your Next Hire walks through decision two in more depth. And for what actually happens after you sign, Remote Architecture Onboarding: What to Expect After You Sign covers decision five step by step.
If your firm wants a partner to work through this order with you, WorldTeams' architecture outsourcing services cover the roles firms most often bring on this way, and our architecture page has more on how engagements are structured for firms like yours.
- nearshore staffing
- architecture firms
- remote hiring
Frequently asked questions
Answers to the questions readers ask most about Sequencing your firm's first nearshore architecture hire.
What is the first decision to make before hiring a nearshore architecture professional?
Name the specific bottleneck, as covered in Decision One, redlines, 3D modeling, or documentation, that is slowing your firm down right now. Sizing the seat comes after that; see How Many Remote Seats Your Firm Should Start With for that next step.
Should we decide the contract type before or after we see candidates?
Decide it first, the way Decision Two lays out. Full time, part time, and flexible engagements fit different pipelines, and Full Time or Flexible? A Decision Guide for Your Next Hire walks through how to sort a role into either bucket.
What stays with our firm when we add a nearshore hire?
Software licenses, permits, and any required stamping stay with your firm throughout the engagement, as Decision Three sets out. That is consistent with how NCARB describes the licensed architect's ongoing responsibility for stamped work.
Do we need to set vetting criteria ourselves, or does a staffing partner handle that?
Define the software stack, time zone, and experience level first, per Decision Four. A staffing partner can vet candidates before you see a profile once those criteria exist.
What happens in the first weeks after we decide to hire?
The first weeks focus on access to your files, a standards walkthrough, and a kickoff with the project owner, the handoff covered in Decision Five. See Remote Architecture Onboarding: What to Expect After You Sign for the full sequence.
What if we skip the order and just hire fast?
Skipping the order in the decision table usually means redoing a decision later: the wrong contract type, a mismatched time zone, or unclear ownership of licenses, once the gap becomes obvious on a live project.
