A branded portal your customers log into and pay for.
A Toolset bundles your SmartForms and CoPilots into a software product your end users access through Login Mode, with their context compounding across every session.
Not a folder of forms. A software product.
A SmartForm is a single guided product. A CoPilot is a single guided agent. A Toolset is what happens when those products live together inside a branded portal your customer logs into.
The portal looks like software because it is software. Your logo at the top. Your colors. Your domain. Inside, the SmartForms and CoPilots you've built sit together in a clean grid. The end user picks the one they need, runs it, gets the Artifact, and comes back tomorrow for the next one.
This is what turns FormWise from an AI builder into an AI-powered SaaS layer. A Toolset is what you sell. A Toolset is what your customer subscribes to. A Toolset is the product line your business runs on.
Welcome back, Maple Ridge Brewing.
Seasonal Campaign Builder
Plan your fall release rollout.
Untappd Response Writer
Reply to a review without sounding defensive.
Taproom Strategy CoPilot
Walk through a slow-month playbook.
Distribution Partner Pitch
Draft outreach to a new distributor.
What's actually running underneath.
A Toolset isn't a folder. It's a coordinated software experience with four moving parts. Here's what's happening behind the portal.
The Product Grid
This is the home view your end user sees when they log in. Every SmartForm and CoPilot you've built and added to the Toolset shows up as a card. You control the order. You control the icons. You control which products are visible and which are gated. The grid is the front door.
Toolset-Level User Context
Every Toolset has a scoped knowledge layer that stores the end user's accumulated context. Personalization fields you defined when you built the Toolset. Saved responses from previous sessions. Uploaded documents the user attached. Once the user fills out their context once, every SmartForm and CoPilot inside the Toolset already knows them. They don't re-explain themselves to every product.
Login Mode
Login Mode is the access layer. End users sign up, log in, and authenticate to your Toolset. Each user has their own scoped context, their own usage tracking, their own saved Artifacts, and their own session state. The Toolset behaves like real multi-tenant software, not a public form anyone can hit.
Monetization Layer
Native Stripe integration handles subscriptions, credits, one-time purchases, and freemium gating. You can also accept inbound webhooks from your existing billing stack (GoHighLevel, Kajabi, ThriveCart, or a custom setup) to provision accounts from there. Either way, payment runs through your accounts and your customer relationship.
Two brains. Two scopes. Don't conflate them.
FormWise has two distinct knowledge layers, and the difference matters. Mixing them up is the most common mistake creators make when they're learning the platform.
The org-level Business Brain is yours. The Toolset-level user context belongs to your end user. They look similar in concept and serve completely different purposes.
Business Brain
Your knowledge. Your methodology. The creator layer.
Upload your PDFs, transcripts, frameworks, slide decks, and coaching notes. Every SmartForm and CoPilot you build references this layer. It grounds your products in your expertise. The end user never sees this. It's the intelligence layer that makes your tools sound like you.
Toolset User Context
Their context. Their saved data. The end-user layer.
When you build a Toolset, you define personalization fields the end user fills out once when they log in. Their company name. Their industry specifics. Their goals. Their relevant documents. Every product inside the Toolset references these fields. The user doesn't re-introduce themselves to every form. The end user manages their own context.
Both layers feed every product. The Business Brain knows what you teach. The Toolset User Context knows who they are.
Login Mode is how your customers access what they've paid for.
Login Mode turns your Toolset into a real software product instead of a public form anyone can use. End users sign up, get authenticated, and access the products you've gated to their account. Their context, their usage history, and their saved Artifacts persist across sessions.
You control how access is structured. Subscription pricing, one-time purchases, credit-based usage, freemium with paid upgrades, or email-gated free access. The pricing engine sits at the Toolset level, so you can charge for the whole portal, charge per product inside it, or mix the two.
Native Stripe integration handles the payment flow directly. If you're already billing customers through GoHighLevel, Kajabi, ThriveCart, or a custom system, you can use inbound webhooks to provision accounts from those systems instead. Either way, your customer relationship stays yours. FormWise stays invisible.
Your customers. Your billing. Your relationship.
- Subscription—recurring monthly or annual access to the full Toolset
- Per-product purchase—gate individual SmartForms or CoPilots behind one-time payments
- Credit-based—meter usage and let users buy credit packs
- Freemium—open access to one or two products, paid upgrade for the rest
- Email-gated—free access in exchange for email capture
BreweryOS, the operating system for independent breweries.
BreweryOS is a Toolset built by a marketing agency that specializes in craft breweries. They packaged years of taproom marketing knowledge, seasonal campaign methodology, and brand voice patterns into a single branded portal their brewery clients log into.
A brewery owner signs up, fills out the Toolset's personalization fields once. Their flagship brews. Their taproom location. Their distribution footprint. Their brand voice. From that point on, every product inside BreweryOS already knows them. The seasonal campaign builder writes campaigns for their actual brews. The Untappd response writer matches their voice. The taproom strategy CoPilot understands their geography.
The agency stopped doing one-off content for fifty different breweries. The breweries stopped paying $2,000/month for ad-hoc agency work. Both moved to a Toolset subscription that delivers more value, faster, with the methodology compounding inside every product. The agency built once. The brewery logs in forever.
When to bundle.
Not every SmartForm or CoPilot needs to live inside a Toolset. Some products work best standalone. Others compound when bundled. Here's how to think about it.
Build a standalone SmartForm or CoPilot when...
- The product is a single use case with a clear deliverable
- The end user doesn't need to come back repeatedly
- You want to embed the product into a website, funnel, or email campaign as a lead magnet
- The relationship with the user is transactional, not subscription-based
Build a Toolset when...
- You have multiple products that share a customer or a niche
- The end user benefits from products that share context
- You want to charge for ongoing access, not single-use
- You want the experience to feel like real software, not scattered forms
- You want compounding value across sessions
You can do both. Standalone products for top-of-funnel lead generation. Toolsets for paid customer relationships.
How a Toolset comes together.
Building a Toolset is the assembly step. You've already built the SmartForms and CoPilots that go inside. The Toolset is the portal that wraps them.
Step 1: Create the Toolset.
Name it, add a description, set the niche it serves.
Step 2: Add products.
Drop in your existing SmartForms and CoPilots, or build new ones that route back to the Toolset. Set the order, the icons, and the per-product visibility.
Step 3: Configure user context.
Define the personalization fields your end user fills out on first login. Make them niche-specific.
Step 4: Brand the portal.
Apply your theme, your logo, your colors, your domain. Toggle off FormWise branding.
Step 5: Configure Login Mode and monetization.
Choose your pricing model. Connect Stripe or set up your webhook integration. Define free, paid, and gated access.
Step 6: Test and launch.
Walk through the full end-user experience yourself. Confirm the login flow, the product grid, the personalization fields, the Artifact handling, and the monetization gates. Then publish.
Onboarding call included on every plan.
Start Free TrialThe portal your customers log into and pay for.
Start your 7-day free trial, build your first Toolset, and have a real software product live before the trial ends.