The Paradox Process

Role
Full-stack developer & technical director
When
June 2024 to July 2026
Stack
  • Next.js
  • React
  • TypeScript
  • Stripe
  • Zoom
  • Neon
  • PostgreSQL
  • ComfyUI

From June 2024 to July 2026, I was the sole web developer at The Paradox Process, an NYC coaching company. I built its website and tools for selling and delivering classes. These systems served paying customers while I worked there.

The work began with a recurring task: setting up each month's Manifesting Lab classes. The same dates, prices, and access details had to be entered in several services. I built a system that could use those details throughout the purchase and class-delivery process.

Setting up a class once

A staff member previously created a Thinkific course, a sales page, a Keap form, and an email automation for each new class. Setup took about an hour.

I first built a sales page the team could update through a password-protected admin portal. Stripe handled payment. After a purchase, the application sent the selected classes and schedule to Keap so its campaigns could send the relevant emails.

The Paradox Process public site before and after the custom websiteCustom website
Thinkific public page
Thinkific public pageCustom website

The custom site is available in an archived preview.

Connecting payment to access

The company used one shared link for all classes and asked customers to attend only the sessions they had purchased. I wanted the purchase itself to determine access.

Keap custom fields proved awkward for managing a separate link for each purchase. I began building a course-operations and contact-management system that became Anpa. Its Zoom integration supplied individual class links and recorded attendance. Its Vimeo integration uploaded completed class recordings for customers to watch later.

Live class listings on the custom website
A reusable listing for upcoming classes.
Course offers on the custom store page
The store brought the course offers together.

Leaving a workable handoff

The custom system reduced recurring setup, but it also needed technical support. I provided documentation and made time for training. When I left in July 2026, the team was not operating it independently and had no ongoing technical owner.

I moved the team back to established services with their own support teams. That gave staff a way to keep running classes without depending on me or immediately hiring a replacement developer. Ongoing support had to be part of the final choice of tools.

Anpa continues separately. Its Wellspring reference site demonstrates the system with a fictional course business.

The AI prototype

A separate AI therapy tool remained a prototype. I raised concerns about cost, its value to customers, and responsibility for its use. Those questions were unresolved, so I did not recommend launching it. The website and course tools described above were the systems that served customers.