Suites

A branded portal your customers log into and pay for.

A Suite bundles your flows and agents into a software product your customers access through Login Mode: governed wherever it goes, metered on every call, with each user's context compounding across sessions.

tools.breweryos.com
Suite · Login Mode
B
Welcome back, Harbor Brewing
SubscribedMKMaya K.
FlowsSaved workAccount
Campaign PlannerLast used 2d ago
Strategy CoPilot3 saved
Review ResponderLast used 5h ago
Ask the Expert12 sessions

Not a folder of forms. A governed software product. Your brand, your domain, your pricing. FormWise stays invisible.

The customer logs in, fills out their personalization fields once, and every flow and agent inside the Suite already knows them. You hold the controls: who gets access, what each asset can do, what every call costs, and what the customer pays (subscriptions, credits, or per-use, priced by you). Context compounds every session, and the same suite that serves your own team today opens to the market later. Selling outside is a pricing decision, not a replatform.

What's actually running underneath.

Knowledgebases: the creator layer

Your methodology, PDFs, frameworks, and voice. Grounds every flow and agent in the suite, for every user.

Methodology PDFsCall transcriptsFrameworks & SOPs

Suite user context: the end-user layer

Each customer's own profile, saved work, and history. Compounds every session; never mixes between users.

Personalization fieldsSaved ArtifactsUsage history
01

The product grid

The home view: your flows and agents as branded cards your customers open every day.

02

Suite-level user context

A scoped knowledge layer per end user: personalization fields, saved Artifacts, accumulated history.

03

Login Mode

Multi-tenant access with authentication and session management, on your own domain. You govern who gets in and what they can reach.

04

Metering & monetization

Metered and costed on every call. Native Stripe: subscriptions, per-product purchases, credits, freemium, or email-gated access.

When to bundle.

Build a Suite when…

  • Multiple flows and agents should share the same user context
  • You want access, usage, and cost on one pane
  • You're selling a subscription, not a one-off
  • You want your own branded, gated product line

Keep flows standalone when…

  • It's a single-use case or one deliverable
  • The relationship is transactional
  • You're running it as a lead magnet
  • You're embedding one flow into an existing funnel

The portal that gets smarter every session.

Brand it, load your flows and agents, set your pricing, and launch. Your customers log into your product, not ours, and the same suite opens to the market when you're ready.

Start free trial

7-day free trial. Onboarding call included.