15 years embedded.
WordPress to a revenue engine.
BizJetJobs is a two-sided business-aviation marketplace. The owner is non-technical. I was the technical partner for fifteen years, across multiple platform rewrites, a recession, and the post-pandemic charter cycle, until the business grew big enough to bring the work in-house with a full team. What started as maintaining a WordPress site became the platform that ran the entire business.
This engagement is what I point to when someone asks what "long-tenure technical partner" actually looks like. The owner is not technical. She hired me to make decisions she did not have to make alone, vendor choices, architecture, build-vs-buy on every new feature, hiring decisions when the team grew.
The work changed many times across the engagement. The relationship did not. The deliverable was never a deck. It was being in the Slack channel when the next decision came up, for fifteen years.
What 15 years of partnership built
What started as maintaining a WordPress site evolved into a custom platform running the entire business. Subscription and revenue engine on Recurly with multi-currency support. Real-time revenue dashboards. A simplified job-posting flow. Contract pilot search by aircraft and location. Mobile dashboard optimization. Slack alerts and SQL reporting. Self-service admin dashboards. Feature flags and A/B testing. Employer sponsorship program. Automated user notifications.
None of that shipped as a single rewrite. It shipped as 15 years of additive iteration, each feature building on what already worked.
Why it renewed for fifteen years
Because the relationship compounded. The cost of swapping a technical partner who holds fifteen years of context you cannot hand off in a doc is enormous, so it renewed year after year. It ended the best way an engagement can: the business grew past what a solo partner could cover and moved to a full in-house team. The accumulated knowledge was the deliverable.