Formwise lifetime deal

Choose the first tier that supports your delivery model

Tier 1 costs $49 and supplies 1,000 one-time credits, 1 knowledge base and 3 toolsets. It can establish whether a guided tool is useful, but has no BYOK. After the balance is spent, hosted usage needs another payment arrangement.

Tier 2 costs $159 and adds BYOK, portal MCP, conversational voice and workspace analytics, with 3 organization seats. It is the practical starting point when you want direct provider billing rather than depending solely on the starter balance.

Tier 3 costs $309 and adds white-labeling, native HighLevel integration, advanced analytics and the AI quality checker. Its 15 seats and 10 knowledge bases suit an agency with defined client assets. Tier 4 removes several resource ceilings. Buy that capacity for known needs, not for the end-user integration connector while its release remains uncertain.

One-time credits are different from subscription allowances

The AppSumo plan table explicitly labels its balances one-time. Do not transfer the recurring Pro or Agency allowances from a normal subscription pricing page to this deal. Building and publishing a tool is different from running it: a model call and added actions can consume credits when a user actually uses the tool.

The model picker shows usage costs, and actions such as web search can add to a run. A long multi-step flow may make several calls. Forecast your costs from completed client tasks, including retries and retrieval, rather than calling one credit one answer.

Tier 2 and higher let you connect supported provider keys. Those providers then bill the relevant AI requests; the lifetime payment does not prepay that bill. Hosted on-demand usage is the other route. Set a spending limit and check which actions remain platform-metered for your exact configuration.

In an October 29 founder reply, on-demand credits are quoted at $0.009 each. At that quoted rate, 1,000 additional credits cost $9 before any applicable charges; this is a cost example, not a guarantee of a fixed number of outputs. The founder notes that some conversations use a fraction of a credit while expensive models can use dozens. Recheck the live rate before enabling paid usage.

Price client access after usage and transaction fees

Formwise supports paid or free portal plans, client allowances and Stripe payments. Current documentation describes a pricing receipt that subtracts Stripe and platform fees and the credits at the on-demand rate. A monthly price is therefore revenue, not profit. Exact fees and live model rates must be checked before offering unlimited access.

Portal customers and organization editors serve different purposes. An employee editing tools uses the organization role arrangement; a customer running a published tool uses the access and allowance you assign. Neither means a separate private Formwise workspace is included for every client.

Client groups and subscription plans also differ: current documentation says runs by users who access an asset through an assigned group without a live plan draw from organization credits. Set a real usage allowance for paying customers, and account for internal access that draws on your own balance.

Check the intake and branching pattern before selling a workflow

An October 26 buyer review describes a forward-only flow and workarounds for repeated steps, mid-flow questions and conditional routing. The buyer also distinguishes the conversational intake inside a flow from a regular-looking portal form. These reported design constraints matter if your service requires a client to return to earlier answers.

Sketch the complete interaction before buying: all initial questions, any missing-information request, classification branches, human review and final delivery. Confirm the current editor supports that sequence. A generic claim that the product builds agents does not establish a loop, a pause for human input or enforcement of every field limit.

Separate released features from the reason to upgrade

The pricing matrix includes a Tier 4 integration connector. An October founder answer calls that end-user connection feature beta and available upon release. Do not sell a client service that relies on it until the required account connection works and the vendor confirms availability.

WorkLLM is a different choice for employees sharing models, organization memory and a monthly allowance. BetterClaw focuses on hosted agent runtime with a separate model connection. Formwise is more relevant when the deliverable is your own client-facing tool, but its portal setup and usage economics deserve attention before the purchase.