Customer stories

How Ironclad's ops team eliminated dual calendar updates and accelerated annual planning with 2sync

Operations & HR

An executive operations lead at a 700-person legal tech company syncs the EPD team's operating calendar from Google Calendar to Notion, cutting planning effort and keeping 70+ people aligned automatically.

Google CalendarGoogle Calendar
"The manual planning overhead is essentially gone. The way the integration is set up, updates flow automatically between Notion and Google Calendar. It just runs itself."
Ashley Owens

Ashley Owens

LinkedIn

Executive Operations, Engineering Product & Design, Ironclad

Key Results

70+

People relying on synced data

Leadership and EPD team members depend on the synced operating calendar

Minimal

Planning effort

Annual planning practically runs itself with automatic sync

250+

Expansion planned

Release train and GTM org adoption will extend sync across EPD and beyond

About Ironclad

Ironclad is a contract lifecycle management platform that helps legal teams manage NDAs, statements of work, and procurement contracts. The company has raised over $300M and employs approximately 700 people. Ashley Owens leads executive operations for the Engineering, Product, and Design (EPD) team of roughly 245 people, responsible for keeping teams aligned, running the right meetings, and maintaining operational cadences.

LocationSan Francisco, US
Company size~700 employees
StackNotion, Google Calendar, Glean, Claude Code

The challenge: one calendar, two places to update

Ironclad's EPD team runs on operational cadences planned months in advance. The operating calendar lived in Google Calendar, but the team's planning database lived in Notion. Every time something changed, Ashley had to update both places manually, and changes made in one system were invisible to the other.

Calendar changes didn't reach Notion

When meetings moved or new cadences were added in Google Calendar, the Notion planning database stayed stale. Ashley had to manually mirror every change, and anything missed meant the team was working with outdated information.

Annual planning required constant manual effort

Building the six-month to one-year operating plan meant creating entries in both Google Calendar and Notion separately. For a team of 245 people, this was significant overhead that compounded with every schedule adjustment.

No single source of truth for operations

Leadership needed to check both Google Calendar and Notion to get the full picture. Some people lived in the calendar, others relied on the Notion database, and neither view was guaranteed to be current.

Other departments wanted the same workflow but couldn't share one account

Operators outside EPD saw the value and wanted to replicate the setup for their own teams, but a single-user account meant Ashley would have to own and manage every integration herself.

The solution: Google Calendar to Notion, always in sync

Ashley connected the EPD operating calendar in Google Calendar to a Notion database using 2sync. Two-way sync means changes flow in both directions automatically. When someone adds an event to the calendar, it appears in the Notion database as "not started." When Ashley updates a timeline in Notion, the calendar reflects it.

Operating calendar updates flow automatically

Calendar events sync into the Notion planning database without manual intervention. New events show up with the right status, and moved dates update in both places.

Annual planning practically runs itself

Because cadences are set up on the calendar and sync automatically, the six-month to one-year planning view in Notion stays current without dedicated planning sessions.

Team alignment without extra work

Leadership and team members see the same information whether they check Google Calendar or the Notion database. No more wondering which source is current.

Activity log catches changes from other editors

Ashley gave a few people edit access to the calendar. When they add events, she can see what was added in the Notion database log without checking the calendar directly.

Implementation: Operating calendar first

Ashley started with the core use case, connecting the EPD operating calendar to a Notion database. Setup was straightforward, and the integration ran reliably from day one.

Time to value: Same day
1

Connected EPD operating calendar to Notion

Google Calendar

Set up two-way sync between the team's Google Calendar and the operating plan database in Notion. Events, dates, and statuses flow automatically in both directions.

2

Configured status tracking for new events

Google Calendar

Set up the sync so that events added to the calendar by other team members appear in Notion with a "not started" status, making it easy to spot new additions and triage them.

The results: no more dual updates, planning on autopilot

Ashley's operating calendar sync eliminated the manual overhead of maintaining two systems. The EPD team now runs a planning process that stays current automatically, and the setup is compelling enough that other departments are adopting it.

Metric
Before
After
Calendar-to-Notion updates
Manual updates in both places for every change
Automatic two-way sync, zero manual effort
Annual planning
Significant effort building and maintaining the plan in two systems
Cadences set once on the calendar, Notion stays current automatically
Team alignment
Calendar and Notion showed different information depending on last manual update
Single source of truth accessible from either tool
Cross-department adoption
Only EPD had the workflow, other operators did manual work
GTM and other departments setting up their own 2sync integrations
"I don't really do a whole ton of planning anymore. The way that the integration is set up, it just keeps updating on Notion and on the calendar automatically."