ProductReady v0.7.0 Release Notes 🎯
Launch control system, billing reliability, and space-isolated onboarding
Released: 19 Jan 2026
ProductReady v0.7.0 gives you complete control over your product launch with a flexible waitlist and invite-only system. This release also brings rock-solid billing, space-isolated onboarding, and critical bug fixes that make the platform more reliable for production use.
🌟 What's New
- Launch control system - Waitlist and invite-only modes with full admin controls
- Billing that works - Fixed plan display, cache invalidation, and payment flow
- Space-isolated onboarding - Each workspace tracks its own getting started progress
- Agent chat reliability - Fixed 404 errors and improved streaming
- Smart UI polish - Better scrollbar behavior, profile sync, and navigation
✨ Why This Matters
🚀 Launch Your Way: Waitlist & Invite-Only System
The problem we solved: You're building the next great SaaS product, but you're not ready for everyone yet. Maybe you want to collect waitlist signups before launch. Maybe you want to run a controlled beta with selected users. ProductReady had no way to support these crucial pre-launch and early-launch scenarios.
What you can do now:
Choose from three access modes:
- PUBLIC - Normal operation, all users can access everything
- WAITING_LIST - Collect signups, hide login/dashboard UI, show "Get Early Access" button
- INVITE_ONLY - Allow registration but gate dashboard access with invite codes
Complete feature set:
Backend API (tRPC routers):
trpc.waitlist.submit- Public waitlist form submissionstrpc.waitlist.list- Admin management with search, filter, paginationtrpc.waitlist.updateStatus- Manage user status (pending → approved → activated)trpc.waitlist.batchApprove- Bulk operations for efficiencytrpc.systemAdmin.accessMode.getCurrent- Check current modetrpc.systemAdmin.accessMode.update- Switch between modes
Database schema:
waitlist_userstable with full tracking (email, name, company, use case, UTM parameters, status workflow)- Extended
system_redemption_codeswith "invite" reward type - System settings key for
ACCESS_MODE
Email notifications:
- Approval emails with invite codes (using React Email templates)
- Activation confirmation emails
- Rejection emails (optional)
- All emails create in-app notifications for users with accounts
UI components:
- Landing page adapts CTA based on mode ("Get Started" vs "Get Early Access")
- Navigation hides/shows login buttons automatically
- Server-side rendering for better SEO and performance
- Admin interface for managing waitlist users (future UI work)
Why this matters:
Every successful product launch needs controlled access. Whether you're:
- Building hype with a waitlist before launch
- Running a private beta with selected users
- Testing pricing with early adopters
- Creating urgency with limited invites
This system gives you the tools to launch strategically, not just "flip the switch and hope."
Technical highlights:
- Server-side access mode fetching (no client queries, better SEO)
- Conditional notification creation (only if user has account)
- UTM parameter tracking for marketing attribution
- Fraud detection with IP and user agent logging
- Type-safe VO/DTO patterns throughout
💳 Billing You Can Trust
The problem we solved: After users upgraded their subscription plan, the UI showed the old plan. Payment succeeded, database updated correctly, but the billing page displayed stale data. Users were confused and contacted support asking "Did my upgrade work?"
What we fixed:
-
Plan display after upgrade
- Added cache invalidation after successful payment
- Billing page now shows correct plan immediately
- No more manual refresh required
-
Billing page 404 error
- Added
/billingroute to SPA router - Fixed payment success redirects
- Users can now view usage after payment
- Added
-
Cache synchronization
utils.billing.getPlans.invalidate()called after redemption- Spaces list refreshes automatically
- Payment success triggers cache invalidation via URL parameter
Why this matters:
Your billing system is the revenue engine of your SaaS. When users pay for an upgrade and the UI doesn't reflect it, they lose trust. Three critical fixes ensure billing reliability:
- Users see their new plan immediately after payment
- Payment success page loads correctly (no 404)
- Cache stays in sync with database
User experience:
- Click "Upgrade to Pro" → Complete payment → Redirected to
/billing?success=true - Toast notification: "Upgrade successful!"
- Plan badge updates automatically
- Usage limits reflect new plan
Technical improvements:
- Payment webhook updates database
- URL parameter triggers cache invalidation
- React Query refetches current plan
- UI updates without page reload (with 1-second safety delay)
🎯 Space-Isolated Onboarding
The problem we solved: The Getting Started stepper showed progress from all spaces for a user. Complete steps in Space A, switch to Space B, and it looked like you'd already finished onboarding. This was confusing when managing multiple projects.
What's different now:
Before (user-level):
user_profiles.onboarding.gettingStarted(shared across all spaces)- One user, one onboarding state
- Completing steps in any space marked them complete everywhere
After (space-level):
spaces.onboarding.gettingStarted(isolated per space)- Each space has its own progress
- Completing steps only affects current space
Why this is better:
You're managing multiple spaces (projects, clients, environments). Each one needs proper setup. Space-isolated onboarding means:
- Create test space → Complete onboarding
- Create production space → Fresh onboarding checklist
- Create client space → Track their setup progress
- Switch between spaces → See correct progress for each
Technical migration:
- Changed from
protectedProceduretospaceProcedure - Queries read from
spacestable instead ofuser_profiles - Updates write to current space record
- Old user-level data preserved (not deleted)
- Backward compatible API contract
Real scenarios:
- Agency managing client workspaces
- Developer with dev/staging/prod spaces
- Team lead tracking onboarding across projects
- SaaS with per-customer workspace isolation
🤖 Agent Chat Reliability
The problem we solved: Users clicked "Send" in the agent chat interface and got 404 errors. Messages never reached the AI. The frontend was calling /api/agent/chat/[taskId]/stream but the actual routes were at /api/agents/chat/[taskId]/stream (plural).
What we fixed:
- Updated default API endpoint in
useAgentChathook from/api/agentto/api/agents - Updated JSDoc comments to reflect correct paths
- Added explicit endpoint configuration for apps still using old paths (
productdrone) - Fixed streaming responses and display
Why this matters:
Your AI agent system is a core feature. When chat doesn't work, the entire value proposition breaks. This was a critical bug affecting every user trying to interact with agents.
Impact:
- 100% of agent chat requests were failing (404)
- Users couldn't send prompts or get responses
- Feature appeared completely broken
After fix:
- All agent chat requests succeed
- Streaming responses work correctly
- Messages display in real-time
- No console errors
🎨 UI Polish & Reliability
What we improved:
1. Profile name auto-update
- Changed name in Account Settings → Sidebar updates immediately
- Added 1-second delay before page reload to ensure database commit
- Fixed Better Auth 5-minute cookie cache issue
2. Scrollbar behavior
- Agent tasks list only shows scrollbar when 3+ tasks exist
- Clean UI for users with few tasks
- No visual clutter from unnecessary scrollbars
3. Onboarding navigation
- "Invite my team" motivation → Opens referral settings modal
- Better post-wizard navigation based on user's choice
- Improved first-run experience
4. User profile in header
- Fixed header still showing "Sign In" after login
- Avatar and name display correctly
- Dropdown menu for Settings and Sign Out
Why these matter:
Small UI details create the perception of quality. When your name doesn't update after you change it, when scrollbars appear unnecessarily, when navigation doesn't guide you properly - users notice. These polish improvements make ProductReady feel professional and reliable.
🐛 Key Fixes
Billing & Payments
- Fixed billing page displaying old plan after upgrade
- Fixed
/billingroute 404 error after payment success - Added automatic cache invalidation on payment success
- Fixed space plan cache after subscription upgrade via webhook
- Added toast notifications for upgrade success/cancellation
Onboarding & Navigation
- Migrated Getting Started progress from user-level to space-level storage
- Fixed onboarding wizard appearing when creating additional workspaces
- Added post-wizard navigation to referral modal when selecting "Invite my team"
- Fixed profile name not updating in sidebar after change
Agent System
- Fixed agent chat API 404 errors (updated endpoint paths from
/api/agentto/api/agents) - Fixed agent tasks scrollbar appearing unnecessarily with few tasks
- Improved agent streaming response handling
Access Control
- Implemented complete waitlist and invite-only system
- Added server-side access mode rendering for better SEO
- Fixed WAITING_LIST mode navigation (now shows "Get Early Access" button)
- Added conditional notification creation for waitlist events
📚 Documentation Improvements
- Added Third-Party Integrations guide (GTM, GA, GSC, Featurebase, ProductDrone)
- Documented access mode comparison (PUBLIC vs INVITE_ONLY vs WAITING_LIST)
- Explained waitlist email + notification pattern
- Added migration guide for onboarding API changes
🔧 For Developers
New APIs
Waitlist Management:
// Submit waitlist form (public)
trpc.waitlist.submit.useMutation();
// Admin operations (protected)
trpc.waitlist.list.useQuery({ page, limit, search, status });
trpc.waitlist.updateStatus.useMutation({ id, status });
trpc.waitlist.batchApprove.useMutation({ ids });
trpc.waitlist.getStats.useQuery();Access Mode Control:
// Check current mode (public)
trpc.systemAdmin.accessMode.getCurrent.useQuery();
// Update mode (admin only)
trpc.systemAdmin.accessMode.update.useMutation({ mode });Notification Helpers:
// Create waitlist notifications
createWaitlistApprovalNotification(userId, inviteCode, emailSent, emailError);
createInviteCodeActivationNotification(userId, emailSent, emailError);Breaking Changes
Onboarding API renamed (same as v0.6.0, documented again):
// Before (deprecated):
trpc.onboarding.getState.useQuery()
trpc.onboarding.completeStep.useMutation()
// After (current):
trpc.onboarding.getUserOnboarding.useQuery()
trpc.onboarding.updateUserOnboarding.useMutation()Onboarding storage location changed:
- Before:
user_profiles.onboarding.gettingStarted(user-level) - After:
spaces.onboarding.gettingStarted(space-level) - API contract unchanged, but data location different
Database Migrations
New tables and fields:
waitlist_userstable with status workflow- Extended
system_redemption_codeswith "invite" reward type - Added
ACCESS_MODEto system settings - Migration file:
0001_careful_living_mummy.sql
Type Safety Improvements
- Defined
WaitlistUserVOandWaitlistUserDTOtypes - Added
AccessModeVOwith "PUBLIC" | "WAITING_LIST" | "INVITE_ONLY" - Proper Zod schemas for all waitlist endpoints
- Type-safe email template exports
📊 By the Numbers
- 3 access modes (PUBLIC, WAITING_LIST, INVITE_ONLY)
- 8 new tRPC endpoints for waitlist management
- 4 email templates for waitlist flow
- 100% of billing payment flows now work correctly
- 0 agent chat 404 errors (down from 100%)
- 3 major onboarding improvements
- 10+ UI polish improvements
🚀 Getting Started
If you're upgrading:
- Update your dependencies:
pnpm install - Run database migration:
pnpm db:migrate(for waitlist tables) - Configure access mode (default is PUBLIC):
- Go to
/systemadmin/access-mode - Select PUBLIC, WAITING_LIST, or INVITE_ONLY
- Go to
- Set up third-party integrations (optional):
- See Third-Party Integrations guide
- Configure GTM, GA, GSC, Featurebase via environment variables
Breaking Changes Summary:
Onboarding data storage - Getting Started progress moved from user-level to space-level. Existing data preserved but no longer used. No code changes needed if you're using standard onboarding components.
Agent chat endpoints - Default endpoint changed from /api/agent to /api/agents. If you have custom implementations, update your endpoint configuration.
💡 What's Next
Looking ahead to v0.8.0:
- System admin UI for waitlist management
- Public waitlist submission form
- Route protection for invite-only mode
- Enhanced email templates with branding
- Real-time collaboration features
- Advanced analytics and reporting
🙏 Thank You
This release represents a major milestone in ProductReady's evolution from a development boilerplate to a complete product launch platform. Special thanks to:
- Teams testing waitlist and invite-only modes
- Users reporting billing display issues
- Developers providing feedback on onboarding isolation
- Everyone identifying agent chat bugs
Your feedback shapes ProductReady. We're building this together.
Ready to upgrade? Run pnpm install and pnpm db:migrate to get v0.7.0.