Ask Ms. Ivey: A Parent-Education Revenue and Fulfillment System

Project Type: Product strategy, revenue system, and full-stack build (client engagement)

Client: Ask Ms. Ivey, an Ivey Alliance parent-education business

Role: Product strategist, revenue architect, full-stack builder, and fulfillment-system designer

Team: Solo lead, with Betty Ivey as subject-matter expert, brand owner, and final client decision-maker

Decision authority: I owned the analysis, recommendation, architecture, implementation, and verification. Betty owned the educational source material, customer promises, brand, and final client approvals.

Duration: July 2026 to present

Stack: JavaScript, Cloudflare Workers and Durable Objects, Stripe, Resend, Google Calendar API, Google Drive API, MailerLite, HubSpot, and Playwright-based browser verification

I took on this engagement because education experts often have the trust and source material their audience needs, but no integrated path from a parent's question to a purchased and fulfilled next step. Closing that operating gap can create far more value than a surface-level redesign.

Ask Ms. Ivey began with something real: Betty Ivey's research, judgment, and years of experience helping parents make better education decisions. The existing site grouped Betty's work into broad parent-support categories and offered a consultation path. It did not yet give a parent a finished, priced offer ladder with a direct way to buy. The offer structure, quiz, payment, scheduling, email, event access, resources, and personalized plan needed to become one connected system.

I treated the engagement as one customer system. The work was to turn expertise into a buyer journey that could explain the offer, collect payment, deliver what was promised, and preserve Betty's judgment where automation could not safely replace it.

The public page described broad parent-support categories and routed parents to a consultation. It did not present a finished offer ladder with clear prices or direct purchasing.

The buyer journey crossed the website, quiz, Stripe, scheduling, email, calendar, and resources. A broken handoff anywhere in that chain became a broken customer promise.

The existing Webflow site made each launch change dependent on a platform Betty did not own as code.

Personalization raised a harder trust problem. A parent plan could use Betty's vetted material, but it could not invent facts about a child or hide gaps in the source record.

I captured the baseline, then worked with Betty to turn her service ideas and source material into a clear parent offer ladder before building pricing and purchase around it. Each package now has a distinct promise, price, and next action. Stripe checkout carries the same brand and terms instead of feeling like an unrelated payment page.

The scored quiz does more than collect an email. It identifies what a parent understands, explains the research behind each answer, and routes the next step without pretending a ten-question score is a diagnosis. The same interaction works on desktop and mobile.

I rebuilt the site as owned JavaScript and moved the public domain from Webflow to one Cloudflare Worker. Cloudflare Durable Objects carry the stateful fulfillment workflow. The visible experience and its operating logic now ship together.

A qualified Stripe payment triggers one authenticated Betty-branded welcome through Resend, private access to all ten Google Calendar sessions, and private Google Drive access to the resource home. The system reconciles Stripe, Resend, Calendar, and Drive every 15 minutes and sends a privacy-minimized daily health receipt when the chain is clean.

The Parent Plan Builder is staged separately from the live purchase system. It drafts only from Betty's vetted material and the parent's supplied facts, preserves missing-source gaps, and stops when it cannot produce a safe, useful draft. Multiple model providers were tested against the same fixed case.

The automation does not disappear after payment. A privacy-safe alert surfaces failures, a 15-minute reconciliation checks Stripe, Resend, Calendar, and Drive together, and a daily health receipt confirms when the full delivery chain is clean.

A live offer system with visible packages, clear pricing, a scored quiz, branded checkout, and private post-payment scheduling

An owned public site and application surface running on one Cloudflare Worker

Automated fulfillment joining payment, authenticated email, ten private calendar sessions, private resource access, 15-minute provider reconciliation, and a daily health receipt

A staged grounded-plan workflow that keeps unsupported family claims out of the deliverable

One operating system joining positioning, conversion, fulfillment, and future personalization without treating any individual tool as the product

The result is a working parent-education business system. A parent can move from uncertainty to a clear offer and a delivered next step, while Betty keeps control of the educational judgment and the material that represents her expertise.

Building a service where the sale and the delivery still live in separate systems? I can map the whole path and make the handoffs part of the product.