Are you thinking about Building a Distributed Team?

I'd be happy to be a sounding board, give feedback, and act as a resource so you can make a better decision around going remote.


Reduce the Remote Risk

The decision to build a distributed team or company is a risky one that can have far-reaching consequences (both positive and negative). It's really tough to understand what issues might pop-up before you try it out though.

After working remotely for 6+ years (for 4 different companies), I've seen the good, the bad, and the ugly. 

I'd like to offer you some of my time to help. While I can't make the decision for you, I might be able to provide some advice and help you avoid potential problems along the way.

Collecting feedback

Why are you doing this?

I'm not trying to sell you consulting services. I'm not trying to convince you go remote either. There are two reasons why I'm doing this:

Reason #1: Some of our best customers at Friday are distributed teams. If you like what I have to say, it's possible you may like the software we are building. But don't worry, I'm not trying to sell you.

Reason #2: We want to deeply understand distributed work and the factors involved. This feedback loop helps us build a better product, write better content, and get better at what we do.

In other words, I can give you advice and through our conversation, you can help me build a better product.


Areas I can't help you :(

I can't offer you change management services or consulting. I have a software business that I'm trying to build, so I can't do more than one call. I'd be happy to converse some over email afterwards.

If you are looking for someone to help, I can recommend you to people in my network who specialize in change management & consulting to make the transition to remote work.

Want to connect?

I'd be happy to help you.