What we shipped: weeks 1–2 (April 25 – May 9, 2026)

This is the first changelog post for Plyrium. Going forward we publish a digest every Monday covering the previous week. This first one covers the entire build to date.

TL;DR

In two weeks we shipped:

• Multi-tenant SaaS with role-based auth (owner, dispatcher, tech, billing, viewer)
• AI voice receptionist (Vapi-powered) with per-client phone numbers + custom greetings
• Live Stripe billing across 4 tiers ($149–$1,199/month)
• Lead capture, dispatcher view, customer + invoice management
• Google Business Profile autopilot (posts, reviews, Q&A)
• Recurring service contracts with three billing modes (autopay, auto-invoice, manual-collect)
• Mobile-first tech day-view + Capacitor scaffold for native apps
• Industry profiles for HVAC, plumbing, roofing, landscaping, and house cleaning
• Bring-your-own-pay-link (BYOPL) for shops that prefer their own payment processor
• Stripe Connect destination charges + save-card-on-file
• Customer-facing self-service billing portal
• Email template registry with version-controlled templates and a revert UI

What changed in the product

Voice receptionist

Built on Vapi. Each customer gets a dedicated AI receptionist with their own phone number, greeting, business voice profile, and tool calls into the dashboard. Spam blocking, lead capture, and after-hours appointment booking all work out of the box.

The public demo line at (928) 666-4329 is the same engine that runs paying customers' phones.

Lead handling

Inbound calls auto-create lead records with categorized urgency, transcript, and a recording. Email and SMS leads route through the same pipeline. The dispatcher view shows everything in a Kanban board with drag-and-drop status changes.

Recurring contracts

Three billing modes:

• Autopay (Stripe) — customer's saved card charged on the contract cadence
• Auto-invoice — generates a draft invoice you send manually
• Manual collect — for cash/check customers; visit gets scheduled, billing handled offline

Autopay uses Stripe Connect destination charges so your money lands in your connected account, not in a Plyrium escrow.

GBP autopilot

Visibility-tier and Front-Office customers get auto-generated Google Business Profile posts, AI-drafted review replies, and seasonal Q&A pre-seeding. Front Office adds 2 SEO blog posts per month on the customer's own website.

Mobile tech app

PWA installable from any phone. Day-view shows today's appointments, route map, ETA to next stop, and a "Directions to next" handoff to Google Maps. Capacitor scaffold is in the repo so we can ship it to App Store + Google Play once we add the developer accounts.

Industry profiles

HVAC, plumbing, roofing, landscaping, and house cleaning each ship with:

• Pre-loaded service catalog
• Industry-tuned voice receptionist prompt
• Lead form fields specific to that trade
• Marketing copy for the /for/[industry] landing pages

What broke (and got fixed)

• A subtle bug in the location filter caused 7 portal pages to crash. Fixed in commit 0415538.
• The wizard's voice provisioning step failed silently if Vapi had a hiccup, leaving signups with no phone number. Now visible via Sentry + admin dashboard, with a manual "Provision voice" recovery button.
• Stripe webhook handler was resolving the wrong workspace, creating duplicate accounts on signup. Fixed by switching from metadata.owner_email to metadata.app_user_id.
• A 30x velocity-estimation error in our internal planning doc — turned out we'd shipped six days of work, not six months. Apparently we're faster than we thought.

What's next

Next two weeks are about getting in front of customers. Cold-outbound to AZ HVAC and plumbing shops, blog content (this is the first post — 2 more per week), and inquiries to PHCC of Arizona, the Phoenix Chamber, and Service World Expo for trade-show exhibiting.

If you run a home-service business, call our demo line at (928) 666-4329 and hear what an AI receptionist actually sounds like in 2026. Or browse our four pricing tiers and start a free trial.

Subscribe via RSS at /blog/feed.xml for next week's changelog.