A new revenue operations hire opens the CRM on day three and finds a lead-routing rule that sends everything from one domain to a single AE. No comment on the rule. No ticket. No doc. It has been running for two years.

He has exactly two options. Leave it alone, because it might be load-bearing. Or change it, and find out the hard way that it was.

Multiply that by the attribution model, the lifecycle stage definitions, the four overlapping lead scoring rules, the campaign taxonomy that stops making sense after 2024, the sync exclusions between the CRM and the marketing platform, and the six-field custom object nobody can explain. That is a RevOps or Marketing Ops onboarding: inheriting a system of decisions where every decision's what is visible and every decision's why is gone.

The Best Existing Advice Names the Problem and Then Stops

The strongest RevOps onboarding content out there gets this right. It tells you to find a point person who can supply the historical insight and team-specific friction you won't get from a spreadsheet. It tells you the tech stack conversation has to cover not just what tools you use but why you chose them.

That is the correct diagnosis. The prescription is where it runs out: assign a champion, build a 30-60-90, schedule shadowing, run structured interviews with each function.

All of which routes the entire problem back through one busy person's memory. The champion has a day job. The person who actually built the attribution model left eighteen months ago. The marketing ops manager who set the sync rules remembers three of the eleven decisions, and misremembers one of them. Shadowing surfaces what someone happens to do that week, not the reasoning behind a configuration built over four years.

And the failure mode is quieter than in sales. A new AE who doesn't know an account's history loses a deal, visibly. A new ops hire who doesn't know why a routing rule exists changes it, and the damage shows up six weeks later as a pipeline attribution discrepancy nobody can trace.

Marketing ops has it worse. Search for marketing ops onboarding and you will mostly get agency content about onboarding clients — not a single serious treatment of onboarding the person who inherits your marketing infrastructure.

What Gets Lost Specifically

For a RevOps or MktOps hire, the missing layer is decision provenance:

Attribution model rationale. Which model is running, and why that one. Almost always there was an argument — first-touch versus multi-touch, whether to credit SDR-sourced pipeline, how to handle the partner channel — and the argument was settled in a thread, not a doc. Without it, the new hire either preserves a model they can't defend or replaces one that finance's board reporting depends on.

Lead-routing logic. Which rules are strategic (named accounts, verticals with a specialist), which are political (a rep who negotiated a carve-out), and which are vestigial (a territory split from a headcount plan two reorgs ago). All three look identical in the config.

Campaign history. What has been run, what worked, what failed, and the read on why. New ops hires reliably repeat a campaign structure that was already tried and abandoned, because the abandonment lives in a Slack retro, not in the campaign object.

Tool configuration decisions. Why this instance is set up this way — the workarounds, the integrations built to bridge two systems that don't talk, the field nobody can deprecate because a report depends on it, and the reason the obvious better approach was rejected.

Data definitions. What an MQL means here. What counts as an opportunity. Whether "pipeline" in the board deck is created or open. Every company defines these differently, and the definitions were argued into existence in meetings nobody wrote up.

Synthesis Instead of Interrogation

Here is the thing that makes this tractable: almost all of that reasoning was written down. It was written down in the moment, in the channel where the decision was made, in the ticket where the change was requested, in the doc that proposed the model, in the comment on the pull request. What was never done is assembling it.

A synthesized ops onboarding briefing reads the systems that hold the record — CRM, Slack, ticketing, shared drives, the knowledge base, the marketing platform — and produces one document covering:

That last point is not optional in ops work. A new RevOps hire cannot act on an unsourced assertion about why a rule exists — they need to open the March 2024 thread, read who was in it, see that the decision was made by a VP who has since left, and decide accordingly. Provenance is what turns a briefing into something a careful operator will actually use.

The Practical Difference

The manual approach gets a new ops hire to competence in a quarter, assuming the champion stays patient and the institutional memory holds. The synthesized approach gets them there in weeks, and — more importantly — it gets them there with the ability to distinguish decisions from accidents.

That distinction is the entire job. An ops hire who can tell which parts of the system were designed and which merely accumulated can start improving it immediately. One who can't spends months treating every configuration as sacred, or breaks something that mattered.

Only 12 percent of employees say their organization does a great job of onboarding. In ops, the gap isn't effort — most companies do assign a champion and build the 30-60-90. The gap is that the thing the new hire actually needs is a written account of four years of decisions, and no human being can produce that from memory on request.

How It Works

Firstweek connects read-only to the tools a revenue org already runs — CRM, Slack, Jira and Confluence, Google Drive and Microsoft 365 — processes content in memory without storing raw messages, and produces a role-specific briefing with inline citations back to the original source. A manager reviews and edits before it reaches the new hire, so what gets delivered is accurate and sanctioned, not just generated.

The reasoning behind your ops stack already exists inside your company. It has simply never been written down in one place for the person whose job it is to inherit it.

See Firstweek pricing and plans.

Related: How to Onboard a New CSM Without Losing Account History — the same context-loss problem on a different specialized hire.

Sources: Gallup, "Why the Onboarding Experience Is Key for Retention" — 12% of employees strongly agree their organization onboards well.