Skip to content

Integration for Contact Form 7 and Monday.com ​

WordPress plugin for turning form submissions into structured workflows ​

I built and licensed a WordPress plugin that turns Contact Form 7 submissions into structured Monday.com workflows. The goal was a predictable, configurable integration that teams could set up without fragile third-party automation.

Overview ​

This was the first product I built and sold independently.

While working as a contractor, I repeatedly saw teams struggle to connect Contact Form 7 submissions to monday.com. Existing solutions relied on tools like Zapier, but required complex, error-prone setup. Many users were unable to complete the integration at all.

I validated the problem by reading forum discussions and observing where users were getting stuck, then built a focused solution designed to make the workflow predictable and easy to configure.

Independent Product Launch

First independently built and licensed product — launched in ~2 months, generating $20,000+ in revenue and remaining in active use years later

What Was Built ​

  • WordPress plugin for mapping form submissions to monday.com boards
  • Vue.js interface for configuring field mappings and workflows
  • Data pipeline for transforming form input into structured GraphQL mutations
  • Licensing and subscription system for distributing and managing access
  • Error reporting infrastructure to support users and improve the system over time

Key Decisions ​

Solving the problem directly ​

Instead of layering on top of existing automation tools, I built a direct integration with a clear mapping interface.

This reduced a multi-step, failure-prone process into a single, understandable configuration.

Designing around a deterministic data pipeline ​

Form submissions were treated as structured transformations:

  • Normalize incoming data
  • Apply explicit field mappings
  • Generate predictable outputs for monday.com

This approach made the system easy to reason about and reliable in production.

Enforcing type safety across the system ​

Although the backend was built in PHP, I introduced strong typing patterns and functional composition to ensure consistency.

The frontend was built in TypeScript, creating clear contracts around how data moved through the system.

Engineering Approach ​

  • Functional programming patterns for predictable transformations
  • Abstractions for different monday.com field types and connectors
  • Type-safe boundaries between frontend (TypeScript) and backend (PHP)
  • System designed for fast iteration based on real user feedback

Role ​

  • Sole engineer across the entire system
  • Identified the opportunity through user behavior and market gaps
  • Designed and built the product end-to-end
  • Implemented licensing, billing, and support workflows

Result ​

A small but durable product:

  • $20,000+ in revenue
  • Used in production over multiple years
  • Established the foundation for later products, including Styled Calendar

Context ​

This project marked a shift in how I approached software.

It was the first time I:

  • Built directly from user signal rather than specification
  • Owned the full lifecycle from idea to monetization
  • Iterated based on real-world usage and feedback

That experience carried forward into later work, particularly in products like Styled Calendar, where the same principles were applied at a much larger scale.