World of Illusion

The Platform Behind the Ministry

From a cold call to souls reached for Christ

Every Global Outreach Event is carried by a purpose-built technology platform — software that takes a single contact all the way from an unanswered phone number to a filled sanctuary and guests who said yes to an invitation. It runs on AWS, serverless-first, and is built to the need: each capability was added the moment the ministry reached for it.

“Go ye into all the world, and preach the gospel to every creature.” — Mark 16:15

The funnel: 1· Outreach 2· Reminders 3· Covenant 4· Congregation 5· The Guest · Voice · Foundations

Stage 1

Cold Outreach

DialDeck cold-calling app & the lead database

Stage 2

Book the Meeting

Live capture & the reminder engine

Stage 3

Seal the Partnership

The Pastor Portal & covenant

Stage 4

Fill the Room

The congregation app & live guest tally

Stage 5

Reach the Guest

The event, the streams & analytics

The guiding principle is simple: take Mike out of everything that doesn't require Mike, so his time goes to the pastors, the platform, and the Gospel. Each stage below is a piece of working software.

Stage 1 · Cold Outreach

DialDeck

A progressive web app Mike uses to cold-call pastors — the cockpit for the top of the funnel.

DialDeck pulls leads from the central church database — name, congregation, phone, status — so every call has context in front of Mike. The decisive moment of the whole ministry is turning a stranger into a committed host pastor, and DialDeck makes it repeatable: Mike books a meeting verbally, during the call, and the agreed date and time are captured on the spot. It is the single source of truth for booked pastor meetings — synced to the cloud, never scattered across notebooks. After each meeting an outcome spine records what happened and the next step, feeding the reminders.

Progressive Web AppDynamoDB lead storeCloud sync

Why it matters: the goal is to book pastor meetings at scale. DialDeck makes the hardest, highest-leverage moment repeatable and captures it so nothing falls through.

Stage 2 · Never Miss the Meeting

The Reminder Engine

A serverless scheduling layer that reminds Mike of every commitment.

Daily and day-before reminders fire for every booked meeting, delivered across multiple channels so they reach Mike where he is. Missing one of these meetings is expensive and a risk to reputation — so memory is never the bottleneck.

EventBridge schedulesAWS LambdaWeb push

Why it matters: at scale, human memory is the failure mode. The engine removes it.

Stage 3 · Seal the Partnership

The Pastor Portal

A secure portal where a host pastor signs in, signs their covenant, manages their outreach, and watches their congregation's progress in real time.

Each pastor — and each Event Coordinator they appoint — gets their own account and signs in with their email; there is no open self-signup, so access stays controlled. Invitations are sent from the ministry's own verified domain, cryptographically signed and domain-authenticated so they're trusted and actually land. Inside, the pastor reviews the curated covenant, attests their authority, and signs — the signature, signer, time, and record are captured as a legal document, rendered to a PDF, stored privately, and shared back only through short-lived, expiring links. A covenant is never left publicly reachable. Access is role-aware: the Event Coordinator is the one partner besides the pastor who can see and sign the covenant; every other event-team role is a roster entry only — enforced on the server, not merely hidden.

Amazon CognitoAmazon SES · DKIM/DMARCE-signaturePDF + presigned S3Role-based access

Why it matters: the covenant is the moment a verbal “yes” becomes a real partnership. The portal makes that dignified, professional, and trustworthy — something you can put your name behind in front of a bishop.

Stage 4 · Fill the Room

The Congregation App

A per-church app given to a host congregation so its members can invite guests.

Each church receives its own installable, offline-capable app for members to invite guests and track invitations. It rolls up a live guest-invite tally — the very same number the pastor sees in their portal in real time, and the heartbeat metric of the whole effort. Guests receive digital e-tickets. One engine serves every church, scoped per congregation, so a new event is a configuration, not a rebuild.

Per-church PWAOffline (IndexedDB)Live tallyDigital e-tickets

Why it matters: the event only reaches people if the congregation invites them. This turns “bring a friend” into a measurable, supported activity — and makes the momentum visible to pastor and ministry alike.

Stage 5 · Reach the Guest

The Event & the Streams

The World of Illusion performances and the digital front door.

The close of the funnel is a guest hearing the Gospel — in the room, and through the streams that extend the room beyond the building. A first-party, privacy-respecting analytics layer measures visits, time on page, video engagement, and reach, with the ministry owning its own data — no third-party trackers — so it knows what's actually reaching people.

Static hosting (S3 + CloudFront)First-party analyticsPrivacy by design

Why it matters: the streams extend the room, and the analytics tell the ministry what's truly landing.

Across Every Stage

The Voice Layer

Real-time, two-way voice AI — because Mike's work is conversation.

Built on Amazon's speech-to-speech AI with advanced reasoning behind it, the voice layer powers Esther, the inbound assistant for Mike Lawrence Productions, and a voice debrief: after a pastor meeting Mike can simply talk — the system listens, summarizes, and writes a structured outcome back to the lead, closing the outcome spine by voice instead of by typing.

Amazon Nova SonicClaude OpusAWS FargateEsther · Voice debrief

Why it matters: voice is the most natural interface for a man whose work is conversation. This lets Mike speak to the system and have it do the structured work.

The Foundations It Stands On

ComputeServerless-first — AWS Lambda, with Fargate for the always-on voice engine
DataAmazon DynamoDB, pay-per-request — leads, portal, call records, guest tallies
IdentityAmazon Cognito — email sign-in, server-enforced authorization
EmailAmazon SES on a verified domain, DKIM-signed and DMARC-published — deliverable and trusted
DeliveryAmazon S3 + CloudFront; presigned URLs for private documents
Infrastructure as codeAWS CDK — the platform is reproducible, not hand-built
ConfigurationAWS Parameter Store / Secrets Manager — no plaintext credentials, hardware-independent

Design principles

  1. Build to the need, not to the catalog. Every capability exists because the ministry reached for it. The tooling matches the work.
  2. Single source of truth. Meetings in DialDeck, covenants in the portal, guest counts in one tally — no conflicting copies.
  3. Take the human out of what the human isn't good at. Reminders, follow-ups, deliverability, record-keeping — handled, so Mike's attention goes to people.
  4. Trustworthy by default. Documents are private and time-limited, email is domain-authenticated, access is enforced server-side. Safe to put in front of clergy.
  5. AWS-native and reproducible. Infrastructure as code means the capability — not a fragile box — is the asset.

Scale & stewardship

The platform runs lean and is designed to scale from one ministry to many. The same patterns — provisioned accounts, per-church apps, live tallies, covenant workflow — are built to serve large numbers of congregations, not just today's events. Infrastructure is treated as a long-term asset: capability is captured as reproducible code before anything is ever torn down.

The battlefield hasn't changed — the Gospel goes out — only the plan for getting it there at scale.