What's the difference between the "current state process map" deliverable in the first 30 days and the updated SOP document at the end of day 90?

The current state process map is a diagnostic artifact — it captures how things actually work right now, including handoff points, friction areas, and data flows, before you've changed anything. The SOP document at day 90 is prescriptive — it codifies the improved workflows you've implemented, with step-by-step instructions, screenshots, and ownership assigned. Think of the first as your baseline and the second as the new operating manual.

Do I need admin access to the CRM before I start, or can I get through the first two weeks with read-only?

You can get through stakeholder interviews and initial reporting reviews with read-only, but you'll hit a wall fast — week 3 tasks like setting up validation rules or fixing duplicate records require admin or at minimum elevated permissions. The cheat sheet flags this explicitly: when you're gaining system access in week one, confirm whether you have admin vs. read-only and escalate immediately if you don't have what you need. Don't let access issues eat into your first 30 days.

Which manual processes from the cheat sheet should I automate first versus keep human-led?

Lead routing, CRM field updates, and account enrichment are the clearest candidates for early automation — they're repetitive, error-prone when done manually, and the ROI is easy to show to leadership. Territory realignment and quota structure reviews should stay human-led, at least initially, because they require judgment calls about rep capacity and market dynamics that automation can't make for you. Use the tool inventory you build in weeks 3–4 to identify where you already have automation capability sitting unused before buying anything new.

What data do I need to have ready before I can build the metrics framework in days 31–60?

You need the outputs from your first 30 days: the current state process map, the systems inventory, and your initial data quality findings. Without those, you're defining KPIs against a system you don't fully understand yet, which means your metric definitions and ownership assignments will likely need to be redone. The cheat sheet is deliberate about sequencing — the metrics framework is built on top of the audit, not alongside it.

How do I know if my initial observations report at the end of day 30 is actually good enough to present to leadership?

It should include at least one specific, quantified problem — like "pipeline forecasting is off by ~15% due to inconsistent opportunity stages" — not just a list of vague concerns. If every finding in your report could apply to any company without changing a single word, it's too generic. Leadership needs to see that you've already connected the dots between data issues and business impact, and that you have a concrete quick win ready to execute.

How often should I revisit the process improvement roadmap after the 90-day period ends?

Quarterly is the right default cadence — it aligns with how most GTM teams review pipeline, quota, and headcount, which means your roadmap stays connected to business priorities rather than drifting into a standalone RevOps wishlist. Within each quarter, do a lightweight check at the six-week mark to catch anything that needs course correction before the quarter closes, which mirrors the "refine processes based on initial results" step the cheat sheet calls out in weeks 11–12. The 6–12 month outlook in your day-90 strategy document gives you the longer arc to work against.