Why Yohan Joined Team Timeforce

Bonjour! Before 2021 I worked at a consultancy with a fountain that tried to look like Las Vegas and badge scanners that still mangle my name. We rolled out enterprise planning for companies with tens of thousands of staff, yet the billable hours always crept back in crusty spreadsheets. When Andy sent me a Loom demo showing Timeforce keeping teams aligned across three continents, I actually spluttered: “you manage this with six people, vraiment?”

The Spark

What hooked me wasn’t a hefty feature matrix. It was Sam’s pandemic diary and Austin’s half-sarcastic automation logs that read like fanzines. They were already looking after a couple of hundred teams and somehow remembered birthdays as well as bug reports. I wanted in so badly my espresso went stone cold.

We jumped on a Friday call. Andy talked about making time data feel warm rather than forensic. My brain kept humming oui, that’s the future, while my cat attempted to chew the ethernet cable like linguine. Two weeks later I resigned, packed far too many adaptors, and declared my Brussels flat the European hub – grand title for a dining table with a slightly flickery ring light.

Scale, Just Without the Swagger

Since joining we’ve welcomed agencies in Québec, finance shops in Lagos, and a charity in Melbourne that tracks volunteer hours with admirable care. Social proof comes in gentle waves: we nudged past eleven thousand active seats, a Fortune 200 contact wrote to say our simple overtime export “made the audit tolerable”, and our #customer-love Slack channel pings most days with screenshots, emojis, and the odd biscuit recommendation.

What Comes Next

Next up? More localised onboarding checklists, compliance-friendly exports that still feel human, and yes, more of Andy’s questionably curated playlists. If you feel buried under timesheets, know there’s a multilingual crew here quietly rooting for your craft. I still can’t quite believe I jumped, but I’m chuffed that I did – tangled cables and all.