Ask HN: What are the biggest challenges preventing startups from hiring remote?

176 points by hichamin ↗ HN
We're starting a new company focused on solving the problem of talent war by helping late-stage startups have successful remote collaborations with tech talent. However, we're still trying to figure out which vertical to focus on. Which of these verticals is most pressing?

1. Sourcing & vetting candidates? 2. Managing international payroll? 3. Bootcamps? 4. Infrastructure & working space?

Let me know your thoughts!

136 comments

[ 2.6 ms ] story [ 205 ms ] thread

  - International payroll: often impacts tax situation
  - Adjusting to remote collaboration. e.g. no more walls of sticky notes; can no longer rely on water cooler conversations or "quick meetings"
  - Timezones
These are more important barriers from my experience. The other areas mentioned already have some type of incumbent solution in place.

Problems 1-4 only become real problems after the management team feels comfortable with:

5) How are we going to integrate them into our workflow and team?

"Hire remote workers" has become an extended and rebranded form of "offshoring". Folks learned some hard lessons from the offshoring days that you can't just hire remote. Your organizational thinking and processes need to be ready.

My take is, if you're solving 1-4, you're selling to companies who already have some remote workers. If you're focused on companies with few to 0 remote folks, you'll need something to help them solve 5.

What exactly is the pain with international payrolls? I don’t quite understand..
Dealing with taxes and with contracts in different jurisdictions. Sure, some people may be ok with working self-employed and handle all of that themselves, but not everyone will do.
Somebody should build startup which would solve payroll issues with remote employees.
Is it profitable / worth the effort?

The US has 300 some million people. India has a billion some.

If you can't find an employee in those two countries, it seems you have other problems? (or add 1 or 2 more if you want to spread it around).

Not that there are not great people in all countries. But opening your resume pool from say 1.5 billion people to 3 billion people is unlikely to have a huge benefit to hiring.

just sending someone money can be a problem. not such much in europe but try getting americans to send a wiretransfer...
So tell me, how do you employ someone who is in Germany if you are based in the US? Germany wants its taxes so you can't just put them as a regular US employee and you don't have any presence in Germany so you can't hire them locally.
Even hiring within the US remote workers can cause issues with the "tax nexus" as a remote worker acts as a physical presence in that state, forcing the company to pay taxes as if they did business in that state.
Country A requires all employees to receive a default-opt-in pension.

Country B requires employers to register with tax authorities and deduct tax directly from the employee's salary.

Country C allows employees to buy childcare vouchers with their pre-tax salary.

Country D has a similar scheme, except for bicycles and it's a loan.

Country E considers private healthcare a taxable benefit-in-kind.

Country F has three different tax bands for employee stock options, depending on when they can be exercised.

Country G makes it mandatory to provide flexible working for new parents...

Of course in a lot of cases you can save on admin by being less tax-efficient, like by not participating in tax-efficient government incentive schemes.

It's only a problem if you actually want to hire them as employees. Otherwise paying workers should be as easy as just wiring money to their bank accounts. It's worker's problem to figure out the laws in their country: do they need to incorporate, how to pay taxes etc.
I'd say #4. I am remote and my company has a hard time providing, tracking, maintaining, and upgrading the gear employees need to do their job. It currently involves a lot of manual data entry, trips to the UPS store by both HQ staff and remote employees. Especially an issue when the person who is ordering gear doesn't understand the gear or the needs of the employee.
The gear is not computers, right?
The biggest challenge with remote is coordination. I've now managed 4 remote teams. The turn-around time between communication cycles with people on the other side of the globe can drastically increase the time it takes to get consensus on issues that locally might take 10 minutes.

I can recall several times where clearly (or so we thought) laid out plans were given over to have them come back a week later with some measure of misunderstanding. The 2 solutions to this have either been micromanaging the remote team, which is painful or time consuming -- or giving the team enough autonomy to work independently, which is risky.

I don't have the studies handy, but the general consensus is that you're gonna have a bad time if your team spans more than nine time zones.

In practice what this means is if you're based in the US, you can either focus on having teams in Europe or Asia, but not both.

I've found a middle ground between micromanaging the team and giving them enough autonomy to work independently. It works best on definable tasks when the remote team's manager is technical enough to do their job on her/his own.

Instead of just a requirements document, give them a requirements document but also define a set of red/green tests to show whether the requirements were met. It's hard to do this with front end, where feel is often very important, but in my experience, it works well provided that the remote team's manager is qualified to make the types of architectural decisions necessary to pull this off.

You can even start tying compensation into passing red/green tests!

That's not likely to be a good idea re the compensation. There are a lot of studies showing knowledge workers perform more poorly at the task with financial incentives.
This is either an unfortunate reality or a limitation of my experience, but I've only had to resort to writing red/green tests when my remote teammates have been at a level where poor performance would be something of an improvement. It's more useful for me when I see tons of commits, yet no forward progress on a measurable goal.
Payroll is the biggest issue. You have to pay taxes in any state your employee is working. This gets expensive and time intensive as you start filing annual reports and paying taxes in 4 or 5 states.
When I ran a business, having a tax preparer really helped with this.
We hire remote.

None of these are big problems. The biggest problem we have is communicating effectively with people in various time zones, and making them feel apart of the team. Video conferencing is still an area that is lacking in this area. I've yet to find a service that meets all our needs. Right now we are using LifeSize because it's the best we've found, and still fairly annoying.

The problem really isn't on the "hiring" end. It's how to work as effectively with remote people as you would with people in the same office. When you introduce friction with remote, it causes problems. That being said, I think it's a worthwhile problem to solve.

Not sure this helps, but this is our biggest struggle right now.

i do not work for zoom, but lately our company switched to zoom after using webex, skype, skype for business, polycom, cisco. hands down zoom has been the best solution for video conferencing, works really well.
totally agree with you on zoom -- also, zoom's slack plugin makes starting meetings quite easy.
The biggest challenge to making remote workers successful is the existing company culture. If the organization has not been built with a conscious "remote-first" mindset, new remote collaborators will inevitably be excluded from necessary communications and decisions. Making a remote worker a true part of the team requires a massive culture shift if your company does not already (successfully) do distributed work.
This takes extraordinary discipline on the part of the in-office team. Fortunately, everything that's good for a remote-first culture is also just good for communication in general. A culture of documenting everything, living in public, and over-communicating is good for any company; and burning those habits into teammates levels them up for life.
>This takes extraordinary discipline on the part of the in-office team. Fortunately, everything that's good for a remote-first culture is also just good for communication in general.

I think it's even harder for companies that have open open offices or are doing Agile. Those two things usually mean the companies are explicitly stressing in-person collaboration. In-person communication isn't a bad thing by itself, but I think that explicitly valuing in-person communication ends up making remote work harder.

This is the best answer.

It is really hard for established companies, full of many different humans with their habits, to shift from shouting across the room to some sort of distributed, async, communication.

I've worked remote for 6 years. This comment echoes my experience.
Red Hat v. Debian.

Arguably, one of Ubuntu / Canonical's failings.

Huh? Canonical is excellent for remote work, and I know many people who work at Red Hat who say the same about it.
I meant far more the former.

The Debian - Canonical distinction is milder, though the latter has at least some centralisation. Nowhere near as much RH's.

You also need to maintain the culture. A phenomenon I just went through is a company that started remote-first, then someone had the brilliant idea to get an office for this or that geographical cluster of people, and slowly but inexorably remote workers were marginalized.

Some people feel really insecure without an office, deep inside they think it isn't a "serious business" unless you own real estate in a "serious" postcode. I don't know if it's just an European thing but it's definitely an attitude I've encountered.

It also depends on the business somewhat, but actually having an office you can invite outsiders to (investors, prospective clients) can be an indicator of success. Truthful or not, it's the perception that counts.
I understand, but that's such an "old world" style. It's like building a datacentre, in the age of cloud computing, simply because owning big iron is an indicator of success (all the big boys have datacentres, right?).

In IT, tbh, I think we should just own it. There are more productive and creative ways to send out that sort of signal.

I'm jumping in to say that I agree with you. Our industry quite literally invented tools to make physical offices obsolete. Speaking as a tech person, it strikes me as hypocritical at best and self sabotaging at worse to maintain this interest in physical space as a marker of success.

But, then the marketing/sales part of my experience chimes in and I think of all the various times in my career that having physical space added to my credibility. I think of the sectors (government tech and financial tech instantly come to mind) where decisions makers are heavily moved by AAA office space. And, I think of how many times I've seen spending an obscene amount on rent actually convert into paying customers.

My inner developer is saying "right on" but my inner marketer/sales type is thinking of all these times when physical space has a positive ROI from a sales/marketing point of view.

I don't understand why companies don't build specific teams that are 100% remote, with perhaps an onsite project manager (or something like that). Then the team could develop its own norms and culture, and while it would be isolated from the rest of the company, it collectively gives the remote workers much more of a voice than if they were each on different teams.
We are a pure remote company but Tax/employment-law is for us the biggest issue. Or to be more precise, it's the biggest issue for potential co-workers. We find that people are super interested in us, but when we tell them they have to do their own tax and basically act as freelancers, most say no to us. The majority simply wants a standard legal employment. Which I understand and I would like to have that too.
As a Canadian who has worked remotely for US companies it is pretty standard to be paided this way and makes employment a little simplier.
I keep seeing in remote job posts for US companies that you need a work permit, they don't mention the option to work as a freelancer. In the Netherlands a lot of people work from their own one person company.
I doubt that "do their own tax" is the blocker there, I would expect it's much more about "give up on any kind of legal protection as a worker."
Google PEO and stop handling it yourselves.
After working remotely for over a decade for multiple companies my conclusion is the biggest issue is finding managers who grok remote working.

If the person in charge doesn't know what he's doing the rest doesn't matter.

Regarding your options:

1. Hardly any different than on site. 2. Not an issue at all. 3. Huh? 4. For some.

Do you have any suggestion on how to spot a "bad manager" in that regard?

My recent experience left me a bit scarred.

Payroll 100%. When we started hiring people remote it was the biggest surprise, and most headache.

Trying to figure it out on your own is irresponsible at best, so it boils down to hiring a local CPA or tax attorney in each state/city you hire in to go over the implications of bringing someone on in that city.

If the person is right, it's worth the cost, but it's a large, unexpected time-suck.

This problem is already fairly well solved by professional employer organizations like Justworks, Paychex, Extensis HR, etc.
And if you're hiring someone in another country?
I don’t know what the best answer is. We currently treat international employees as contractors.
Communication.

Communication! Communication! Communication!

If any part of your product requires people to communicate with each other, then the team members lying on vastly different time zones will have low efficiency because information round trip time will be larger than those of the local (or time zone near) ones.

Yes, Specifically being able to communicate in front of a whiteboard is crucial. Exploring ideas, creating a shared understanding, etc, all becomes a lot easier if you can support this with some interactive visualization on a whiteboard. I feel disabled if I have to communicate without a whiteboard.
Personally I'd say 1 and 4 are the most pressing, though 2 raises some other issues. Personally I'd not hire anyone junior for remote work at all (sorry), so 3 is an anti-issue to me.

Hiring is hard to begin with, and hiring remotely has additional pitfalls. A company like Triplebyte that would perform additional vetting to prove a candidate's ability to work remotely would be quite welcome.

Re 4. VC systems are still awful and both companies and employees aren't willing to invest to the right level, and commit to workflow changes, in order to make it seamless to work remotely. In particular, latency and packet loss is what just kills VC and makes it very apparent that we're not actually in the same room together. The way to solve that is gigabit home-office Internet connections, but $10k to run lines and an additional $500/month, as well as the hassle of using a wired connection at home to take advantage of it, and then a dedicated VC system, is a total non-starter for many, on both sides, employer, and employee.

Throw in a timezone difference, and the wrong remote employees can take more time to manage than they're worth. (That's not to say there aren't some really really good, really solid remote employees, just that there are also the wrong hires - same as goes for in-person.)

Re. 2. On top of payroll, there are also plain cultural differences between countries that make it more challenging than when there is no difference - holiday schedules, vacation policies, etc, and until you've lived it, it's hard to know what to look for in advance.

Everybody speaks here about communication. With the rise of enterprise messengers like Slack it's becoming easier.

For example, bots like http://tatsu.io or http://standuply.com help running standup meetings.

I think remote work will become more and more popular in the future despite its challenges.

Infrastructure & working space is a big challenge depending on where your remote team member is based, but overall that has seen a big improvement with more affordable UPS options and wireless connectivity for backup.

Timezone is a tough one. For us, finding a scrum time that works for everyone (in a small team it's doable), and sticking to it daily helped to get the team to communicate more openly with each other, and stay in sync.

Finding the right set of tools to manage remote teams is one the biggest challenge when a team is distributed across the world. Traditional task management tools didn't lets us easily ideate, organize, and share task lists together, hence we were inspired to build Taskade (Disclaimer: I'm the co-founder of https://taskade.com). The idea of having the freedom to work together on task lists in real-time, see each other's progress, and collaborate without any distractions.

Trust building/erosion and buyin/retention.
How does 2 normally work? Apart from invoicing as a contractor, can the company actually hire someone located in another country?
I think the hardest part is the planning process and communicating rapid change.

Startups and fast growing companies grow quickly and changes happen rapidly. If priorities are constantly changing and communication/the planning process isn't really robust you won't have remote people who are successful.

IMO one of the least-solved problems is communication. Two areas in particular: (1) lack of a shared real whiteboard, and (2) video-call quality.

These are two areas where good solutions may exist at reasonable price-points, but if so that information isn't widely known.

Not sure if it fits with your business model, but it would be extremely helpful for someone to carefully evaluate the effectiveness of various technologies / products / services for those areas, and provide recipes for known-good setups.

I.e., if one of your clients can tell you their current and upcoming team sizes, network connectivities, etc., you can tell them what products and services give them good video / whiteboard quality at various price points.

IME companies with remote workers tend to be "penny wise, pound foolish" regarding these things.

EDIT: To be more specific: For call quality, having good data on what setups result in good call quality in Skype vs. Slack vs. Google Hangouts etc. And for shared whiteboards, having good information on how effective / sufficient teams find various approaches such as (some website + iPads), (some website + a particular Wacom tablet), (everyone on the team having a particular model of interactive whiteboard such as this one [0]), etc.

[0] https://www.cdwg.com/product/SMART-Board-6075-75in-LED-displ...

Anecdotally I can say that Zoom has worked the best for us.

But no software can fix variances in bandwidth or latency. I wish there was a way to test a remote hire's internet connection quality. Lack of access to a good internet connection would be a deal breaker for a remote hire for us.

I believe you about Zoom. Unfortunately that's the only kind of information I'm ever able to get on the topic: anecdotal.

I suspect the reality is that, amongst the best-performing services, which one works best depends on network QoS details, network topology, particular client hardware / OS, etc.

For example: some conferencing software seems to have a real problem with echo cancelation, so either (a) everyone needs mic/speaker hardware that sidesteps the issue, or (b) you accept that everyone will go insane.

Similarly, difference conferencing software has different solutions to people talking over each other accidentally due to latency. One product (Cisco's maybe?) has an icon for metaphorically raising one's hand to request a turn speaking.

You know, I might have an idea for you. A few years ago, I built a diagnostics tool for a product whose primary users were using some absolutely horrible internet connections.

One of the most useful parts of it was timing http requests and tracking response times. We solved some very complicated technical support issues using this tool. Do you think it would be useful to adapt something like this to remote workers? It's weird because I've struggled with internet connections when I've worked with remote workers, but never thought of actually testing it until I read this comment...

We've been trying Zoom lately. Seems pretty good, though we always seem to have issues with everyone logging in to a call. Inevitably we have everyone slacking/texting/skyping out the call ID to just get up and running. After we're up though it all works smoothly
A very important contributor to good call quality is good audio hardware.
Yes relying on the cheap 5-10$ pos mic built into a lap top wont work you need a proper soundcard and better microphones and turn off the auto level/compression on skype.

Doing it more seriously you might even want to use a separate older machine as a skype drone (ie only runs skype) and feed your audio out from your main machines sound card into that.

I had an initial phone call with a firm and it was obvious that they where clustered round a mac laptop - inaudible and very low quality sound.

And also improve the acoustics of the room from which you are calling, put some foam on the walls, etc...
I made a quick colloboration app with video chat and more features including a simple whiteboard. Check it out https://oorja.io
I don't understand the downvotes. I just felt excited sharing an app I built that also has a simple whiteboard. :(
I assume you were downvoted thinking you are "marketing" your app "without context", like SPAM

Don't be discouraged. I checked out your site (and github) Looks nice. I'll use the tool next time I need remote collaboration

Keep up the good work.

>Two areas in particular: (1) lack of a shared real whiteboard, and (2) video-call quality.

Amen to that. I recently was interviewed remotely, and the voice call quality was unacceptably low- I could barely even understand the questions being asked!

As a few others have said as well, the biggest challenge personally has been Payroll and Taxes. A lot of good candidates want to feel part of the company which means they need to be hired as employees. But legally, a US company hiring in a different country can at best hire them as a consultant/freelancer for tax purposes unless they open a local office in that country which is a major PITA.

I have a US company and trying to build a remote team as "employees". Going crazy trying to figure out how to set this up other than the usual option of "pay them as freelancers and let them do their own taxes". Not everyone is cut out for that and not able to attract good talent.

We[1] are a fully distributed team and also ran into this problem when we hired our first team member outside the US. There are lots of players[2][3] in the "Global PEO" market that have corporate entities in multiple countries and will handle payroll and benefits for you, but caveat emptor, these solutions are shockingly expensive. The average cost was 18% of the remote worker's salary (!), which I personally considered insane.

We ultimately went with a company[4] that had a different model where they connect you with a local PEO in each market and present a common UI on top of all the disparate local PEOs so that you get a company that specializes in just that country, but a common UX no matter how many countries you work with.

I liked the model, and more importantly, it was a fixed fee and much less expensive, and they published pricing. Disclosure: We made the decision to go with them, but haven't started working with them yet.

[1] https://gruntwork.io

[2] https://www.globalization-partners.com

[3] http://globalpeoservices.com

[4] https://papayaglobal.com

I'm the founder of a company that is ~250 people, remote first, and still fully remote. We do have an office in SF, but ~10% of our employees are present, almost no full teams are centralized, and all our processes revolve around remote work. Important to note that we're a US-founded company (this comes along later).

I'm going to use this comment as a way to talk about remote hiring generally, rather than respond directly to your comments. I want to help others understand some of the challenges it has been being one of the larger (relatively) fully distributed companies.

I think there is a common misconception that the world is mostly flat and that our company can hire from anywhere. I am commonly criticized when tweeting job postings (almost always remote) when the countries we can hire from is limited to a select few. "Not real remote" "first world remote only" "remote != 8 countries" etc. are common criticisms.

Disclaimer for the remainder: I am not a lawyer and my exact details because of that may be wrong. Please consult your own legal team.

When hiring remote, there are a few things to keep in mind:

1.) You have to adhere to employment laws within the country you're hiring from. Employment laws vary widely between countries and getting them wrong can be very expensive. For example: vacation time will vary, holidays will vary, the ability to let someone go will vary, what you can/cannot expect from an employee varies. In one country, emailing an employee outside of work hours is legally considered harassment; when working with multiple timezones that's a challenge because "in work hours" for one country may be "out of work hours" for another country.

2.) To employ someone full time, many countries require you to have a legally entity within that country. Establishing a legal entity takes a lot of time and a lot of money.

In the past 12 months, we've had at least one member (more now) on our HR/finance teams establishing legal entities _full time_. I've had my signature on at least 8 incorporation documents in the past 6 months. By the way, most incorporation documents require a "wet" signature so if you're remote like we are, be prepared to be FedExing a lot of sensitive legal documents around.

Beyond just paperwork, there are often requirements to establish a legal entity: a real, physical, local address is one. In one country, we had to pay out of a local bank account in local currency (which has its own red tape), and this country also required we maintain a minimum balance to pay 3 months salary in the local account in local currency at all times. For a startup, that much cash "not working" can be problematic depending what stage you're at.

In one country we're establishing an entity in, the process just takes a LONG time. We've been responding to any inquiries and sending paperwork immediately and we're 8 months in and still probably 2 months away from completing the process. Meanwhile, we still can't legally hire there.

A lot of legal paperwork is understandable in the local language of where you're creating the entity. This means that you also have to pay lawyers fluent in that language to vet the paperwork. We employ full time lawyers, but primarily in English, so this requires us to go to expensive outside counsel.

Finally, this is all expensive. There are fees to creating entities but also recall that we have multiple full time employees that spend their entire day establishing legal entities. So we have our own full time salary costs plus filing costs plus legal costs.

3.) Hiring contractors DOES work around some issues, but has its own downsides. First, we can't offer options/stock to contractors and we'd like all our employees to benefit from this. Second, we often can extend the same full time benefits we want all our employees to share such as healthcare, 401K, etc. Put another way: we want all HashiCorp employee...

> First, we can't offer options/stock to contractors

Can you elaborate on what is keeping you from offering options to contractors? Sure, incentive stock options can only be given to employees but what about nonqualified stock options? They can be given to anyone.

Tax and legal issues for example in the UK (one of the more friendly countries to the idea of employee stock ownership) there are rules about how an approved share option schemes work- main one is no multiple share classes.

Whilst you can offer on approved schemes - you might have to offer people in the uk more options to cover this which might make local (US employees) jealous

Glad to see employers are breaking hiring norms
Thanks for the all the details here — really useful!

We're a remote team but much smaller and certainly unable to pay a full time employee to create companies.

Do you have, or know where to find, a list of countries that can work without setting up a legal entity? We've lost a lot of time trying to recruit candidates where we've not been to find a workable solution due to local laws and our limited resources (e.g. in France!)

I don't have such a list, sorry.

Learning about this stuff basically requires a huge time sink per country in reading local laws, as well as a cost of paying a lawyer to verify your assumptions. It is unfortunate. A "tldrlegal" site for entity creation and employment laws would be amazing.

Also re: France... yeah, that is a tough one. We're just about ready to hire there. The whole process was very difficult, on the harder end of the spectrum that we've experienced so far. :)

asking for a friend... what if you hire someone 'Alex', a resident of Washington State and then they move to Germany because their spouse is relocated for employment to Germany, where they both receive benefits but are required to remain US Citizens (and return to the US each year)... in that case are you paying Alex as if they are a Washington State resident or are you legally required to pay them as if they are a German resident?
Disclaimer: Not a lawyer, consult a real lawyer.

I don't know for the specific case you've posed, but we've had similar things happen. If an employee moves into a state/country we can't employ them in, it causes a bit of a panic. We either have to 1.) establish the correct legal/financial entities to employ them or 2.) let them go. In theory, you can convert the employee into a contractor, but this has ramifications on options vesting and benefits and so on and is a huge mess. I'm sure there are a lot more caveats to this that are under consideration (again, I'm now a lawyer) that may affect this, so I wouldn't generalize this too far.

I don't think we've ever let someone go for this though, we have once to memory panicked and rushed to establish the entity (potentially paying fines along the way). I may be mistaken, I just don't recall exactly. In any case, we kindly ask our employees to notify us of any change of location, since it almost certainly changes payroll tax even if you are moving to a location we CAN employ in (i.e. even between US states). Also, the panicking is not fun for anyone (including the employee, whose job status is suddenly uncertain).

As soon as you start working on German soil, German employment laws apply fully. Citizenship, prior residence, etc. are almost completely irrelevant. There is a social security agreement between the US and Germany which might exempt the person from German pension contributions but nothing more.

(If the spouse is working for the US military there are NATO agreements which might make German employment law inapplicable but I know almost nothing about that.)

Make sure and include a "Gerichtsstand" in the employment contract. This is basically the name of the city in Germany where legal processes related to the contract will be conducted. This will save you a good deal of unpleasantness later, should any employment issue come before a court of law in Germany.
Super insightful, thanks for sharing. Wondering if it's easier to be a remote-first company from other countries.
What a fantastic post. Thank you Mitchell.

Would you be able to share the actual countries in question? In which country was it required to open a bank account in the local currency? Which one has taken 10 months to complete opening an entity in?

This is really interesting, thanks. Would love to read your thoughts on chat literacy and the importance of decision inclusion.
Thank you for taking time to explain. Very helpful and very interesting. Cheers!
My company hires engineers wherever they are. We're only incorporated in a few countries, the way we work is to engage a firm whose business it is to be incorporated in many countries so that they can hire people in those countries as full time employees, and contract them to our company. This firm charges a flat fee per person per year, and it's not a lot. I've been told that we'd have to have at least 5 people in a single country before incorporating in that country would cost the same as using this firm. They handle all the local obligations, payroll, entitlements, tax, superannuation, etc. I don't know how it works, but we even are able to get stock options, and I've never heard of any problems with that from any of my coworkers in any other countries. Other things like leave - our local job contracts conform to local law for leave allowances, and then we just work it out with our managers - we have an HR system that seems to be able to easily handle different leave policies for each employee, and if there's any problems, you just tell your manager and it gets sorted, no big deal.
Mind sharing the name of the firm?
Not the OP but we use a firm called Velocity Global for exactly this. Though they take a % of salary, so would be interested to hear who the OP uses too
very interesting post, would mind sharing your top 10 countries to hire remotely
> Note we don't want to avoid taxes, that's not what we're doing.

Tax avoidance is perfectly legal and encouraged to maximize shareholder value. Tax evasion is illegal.

> First, we can't offer options/stock to contractors

Can you elaborate why?

I can't remember if I read it here or somewhere else, but someone once made a really good point: that the incentives are strongly skewed against hiring remotely.

Think about it: the benefits of remote work go mainly to the employee, but the drawbacks (harder to communicate, harder to evaluate productivity) fall disproportionately on the manager. Since the manager is the one making the hiring decision, they don't hire remotes.

So to give a really broad answer, my suggestion would be "change the incentives so managers will hire more remote workers". That could mean internalizing costs of on-site workers, better communication tools, etc.

From the comments so far, I'm hearing that your prospective clients would benefit from knowledgable consulting to help them navigate multiple issues:

- Which payroll companies, if any, will be the best solution for handling international (or even just inter-state within the U.S.) payroll / tax issues?

- What communications technologies and practices work best for various team geographies / network-connection-quality / local-hardware setups?

- What's the optimal frequency, duration, structure, etc. of whole-team face-to-face meetings for teams that are typically distributed?

- What management training is most helpful for managers of all-remote teams, or of teams where only some members are remote?

Another comment about consulting services: Client executives might really benefit from a clear (and accurate) presentation of the different levels of remote-team-collaboration quality that are available at different per-employee price points.

For example: At ($10k initially + $3k/year) per employee, you're likely to avoid problems A, B, and C, but still run into D and E occasionally, depending on team size, using recipe $FOO.

At ($20k initially + $10k/year) per employee, you avoid problems A-D, using recipe $BAR.

For us (http://fairpixels.pro) it’s actually the off-work connectivity. Slack, email, todo lists and all of the other tools make us pretty effecient and productive. But I’d love to see how I can boost social connectivity outside of ‘work’.

PS. We are hiring

Do you have a hiring page on the fairpixels site? I couldn't find one
Young founders with zero or near-zero management experience in person, never mind remote. To a lesser degree - and strictly for small team, early stage startups - part of the journey is living it together. The whole vibe loses something when you're staying late and eating ramen together over Skype.
5. Managing people

Personally, I find the toughest part to be actually managing the people. You really need to trust your team to be self-motivating which can be tough for a manager to do, especially new ones, because you need to give up some control.

But even though you trust them you need to have a way to measure results. That means being more disciplined and mature in your project planning than you might be if everyone is co-located.

For a startup that is key. Startups often skimp on disciplined project management.

I also find it tougher to do things like say, identify when someone is having a rough time (personal or professional) and take steps to correct or accommodate for that. If a co-located employee starts underperforming but I can see they are clearly checked out (like their head is somewhere else) I might suspect there is something going on at home and adjust my management style with that person. If they are remote it is harder to tell those things. Communication becomes extremely important when body language / behavioral clues are lacking.

So to pile on a lot of the other answers here... communication, communication, communication.

Yes, this is why it's critical to adopt an output/outcome mentality. When you can't see if or when we're working the only signal of status is whether shit is getting done. This should be the only thing you care about, and it should be super obvious of you're project managing correctly.