What the practice has built

Letting an AI agent pay for a tool call, the same way it would call the tool itself.

An MCP (Model Context Protocol) tool server gated behind the x402 payment protocol: a free tool any agent can call, and a paid one that returns an HTTP 402 challenge the agent has to sign and settle before it gets an answer. The client auto-detects the challenge, pays in USDC on Base Sepolia, and retries — no human approving a transaction in the loop.

• TypeScript
• Model Context Protocol
• x402 / HTTP 402
• Solana & Base (EVM)
• Ed25519 signing

A moving-tote rental business, built and operated solo, that takes real bookings and real payments.

Browse packages, pick delivery and pickup windows, e-sign a rental agreement, pay through Stripe. A Postgres function makes double-booking a tote structurally impossible instead of hoping the application layer catches it. Refunds are tiered by cancellation window, every price change is audit-logged, and accessibility is tested with Playwright and axe-core — not just eyeballed.

• Next.js
• Supabase (Postgres, RLS)
• Stripe
• Playwright / axe-core

Matching families to in-home caregivers shouldn't be a phone tree.

A caregiver-matching and booking platform with a trust-scoring engine running as Supabase Edge Functions — ranking and auto-assigning caregivers on availability, proximity, and reliability signals, with a separate path for urgent requests. Claude sits inside the matching and support logic directly, not bolted on as a chatbot widget.

• Next.js
• Supabase Edge Functions
• Anthropic Claude SDK
• Stripe Connect

Donation reconciliation shouldn't require a volunteer squinting at a bank statement.

Membership, sermons, giving, and volunteer check-in for a Calgary congregation, including a custom Gmail/Interac e-transfer parser that reconciles donations automatically instead of by hand, and geofenced check-in for events. Rate-limited and audit-logged throughout.

• Next.js
• Supabase
• Twilio
• Upstash Redis

Postpartum support in Canada shouldn't stop at the hospital discharge.

A postpartum care marketplace connecting new mothers with vetted care providers, rebuilt twice as the model was refined: a first version shipped with real payment and access-control fixes hardened in production, and a ground-up rewrite now in progress adding practitioner invitations and proper error monitoring. Structured as a proper monorepo with separate parent-facing, admin, and API applications rather than one sprawling app.

• Next.js
• Turborepo
• Supabase
• Clerk
• Stripe

Aging-in-place care coordination shouldn't mean five phone calls between the family and the concierge.

A family portal and a separate concierge operations app share one care record — updates, appointments, documents, and a care plan — split into domain, application, and infrastructure layers so the backend can be swapped without touching business rules. Authorization is enforced in that application layer first, with Postgres row-level security mirroring the same rules as a second line of defense. The known v1 shortcuts are documented in the README instead of hidden: connecting a family member to a client is a pasted Clerk user ID today, an email invite once that becomes a real workflow pain point.

• Next.js
• Turborepo
• Supabase
• Clerk

A rental rate that's structurally guaranteed to never be the expensive option.

A Canada-only airport rental booking flow across 10 airports and 8 vehicle classes. The pricing engine computes its own quote against competitor rates on the fly: never more than 3% above the market average, always at least 5% under the second-cheapest listed rate. The same pricing logic drives both a Next.js web app and a matching Expo mobile app.

• Next.js
• Expo / React Native
• TypeScript
• Tailwind

Estate administration for a grieving family shouldn't run on a spreadsheet and a lawyer's inbox.

A fiduciary and estate-management platform for Nigerian families, at home and in the diaspora, built around a real domain model — estates, deceased persons, beneficiaries, properties, bank accounts, professional partners — rather than a generic CRM repurposed for grief. A nine-step onboarding wizard walks a family through the actual intake a fiduciary firm would run, ending in document upload and e-signature. Payments run through Paystack rather than Stripe, matching the market it's built for.

• Next.js
• Supabase
• Clerk
• Paystack
• Cloudinary

Stripping a photo's metadata after you've already shared it is too late.

A PWA that intercepts the phone's native share sheet directly — share a photo to it, and a service worker catches the file via the Web Share Target API, strips EXIF and GPS data with a canvas re-encode, and hands back a clean copy before it goes anywhere else. A free tier is rate-limited to one scrub a day; a paid subscription removes the limit through a real Stripe Checkout and webhook flow.

• React
• Vite
• Workbox / PWA
• Stripe