flaibo
HR Operations

Company Policy Document

Remote work policy for our scaling Series B company, covering all full-time employees globally with contractors handled separately

No card required

What this brief specifies

Where the company actually stands

$10M ARR, 60 employees across 8 countries, moving from hybrid to remote-first.

The tension to balance

Flexibility has to coexist with collaboration; roles like Sales and Customer Success actually benefit from regional concentration.

What's actually being decided

Core hours with a 4-hour CET overlap, a workspace stipend, equipment provision, and time zone guardrails on new hires.

What makes this hard

The friction here is that 'remote-first' and 'time zone hiring guardrails' are being announced in the same document, and those two things pull in opposite directions. A company already spread across eight countries, moving off a hybrid model it apparently found insufficient, now has to explain why going more remote comes bundled with new restrictions on where the next hire can be based, plus an explicit carve-out that Sales and Customer Success benefit from staying regionally concentrated. A generic remote work policy hands you a stipend line item and a core-hours block; it doesn't resolve how a $10M ARR company at 60 people justifies looser location rules for most roles while tightening them for the roles closest to revenue.

CorporateSmeFounderConsultantHealthcareLegal

Frequently asked questions

Carrying forward the company's actual size and prior hybrid history, the regional-concentration exception, and the decisions already made, core hours, stipend, hiring guardrails, means the policy an AI assistant helps draft can explain the Sales and Customer Success carve-out instead of contradicting itself. The next policy document that has to reconcile a company-wide rule with a few necessary exceptions starts from that same reasoning instead of a blank template.

Ready to try this in Flaibo?

Get started free

Your context everywhere