Took Workiva Scripting — pro-code workflow automation letting customers automate manual work in Workiva using Python — from prototype to paid early-access product, and helped Workiva secure millions in revenue. In parallel, owned four concurrent platform infrastructure initiatives — developer platform (CLI + IPS), event streaming, and notifications — that became the foundation for service development across Workiva engineering and underpinned the company's region-expansion and cloud-migration programs.
Scripting 0-to-1 launch:
- Quickly took Scripting from idea to early access — defined and built the MVP, onboarding guide, and Early Access Program framework, then launched it for partners and signed three of them.
- Grew Scripting from 3 partners to a mix of 21 partners and customer early adopters, helped Workiva secure millions in revenue, and announced the product at Amplify 2022 (Workiva's annual user conference) — led the cross-functional launch tiger team spanning professional services, partnerships, and GTM.
- Built the partner qualification framework, authored the Scripting Support Model, and onboarded customer support as first line of defense — the Scripting GTM process was highly regarded internally and became iteration one for standardizing product launches across Workiva.
- Presented Scripting launch challenges directly to SteerCo (directors and VPs); recommendations triggered a product-operations initiative to improve the launch framework across the company.
Infrastructure and platform foundations:
- Developer platform (CLI + IPS): The CLI is the primary tool Workiva engineers use to build, deploy, and operate services. IPS — embedded in the service configuration file as a core part of the platform — standardizes how teams provision and deploy cloud infrastructure. Together they form the foundation of the developer platform. I drove continuous CLI improvements grounded in developer feedback, including the migration to Go — which removed adoption friction, reduced support burden, and enabled extensibility so teams could extend the tool to support their unique practices. While most teams had already adopted IPS, I evangelized its benefits to the remaining holdouts and drove adoption to completion across the last 50 repos. The main outcome of the developer platform is standardized developer practices, accelerated onboarding, and faster day-to-day development across Workiva engineering.
- Event-streaming platform: Workiva's internal event-streaming platform enables service-to-service async communication and ensures that everything customers do in the platform is transparent and auditable. I shaped its core capabilities, prioritized features to accelerate early adoption — including the Transactional Outbox — and evangelized its strategic use cases across engineering teams. I drove initial adoption and paved the path for it to become the standard event infrastructure across the Workiva platform.
- Notifications service: The notification service ran on the legacy cloud provider. My team had no expertise in that infrastructure. I got team buy-in to take ownership of building a new service on the new cloud provider, scoped for parity. I drove definition, design, and documentation of the first-ever UI for configuring notifications, and expanded supported channels beyond the original email-only service (e.g., Slack). I drove adoption ahead of schedule as part of the company-wide cloud migration — existing teams migrated and new teams adopted the service.