Comparison

Firstweek vs. your company wiki.

Those are exactly the kind of source Firstweek reads from. The gap was never access to documentation - it's that nobody has synthesized it into something a new hire can actually use before Day 1.

A wiki is where information lives. It isn't organized for a specific new hire.

Your wiki has the answer to almost everything, scattered across hundreds of pages written for whoever needed them at the time. A new hire doesn't know which pages matter for their role, or how to tell a current decision from a stale one.

Nobody has time to write the synthesis.

The real bottleneck was never "do we have documentation" - it's that assembling a role-specific narrative from scattered pages is a research project, and nobody's job is to do that research for every new hire, every time.

Firstweek reads your wiki - it doesn't replace it.

Firstweek connects read-only to Confluence and Notion and synthesizes from what's already there, alongside Slack and your CRM. Nothing to migrate, nothing to duplicate. Your wiki stays the source of truth; Firstweek is what turns it into something a new hire actually reads.

The short version

Your wiki answers questions people already know to ask. Firstweek answers the ones a new hire doesn't know to ask yet - built from the same wiki you already have.

See what a real briefing looks like - built from your own tools, with a citation for every claim.