PrometAI lifetime deal

Finite plans and monthly editing credits

The six tiers include one, four, ten, twenty-five, fifty or one hundred business-plan creations. A creation is consumed when a plan starts; deleting the result does not return that allowance. This is the most consequential limit for consultants who expect to prepare plans for a changing client list.

An earlier founder answer called these ongoing projects, which could sound like reusable slots. The later deletion answer and current FAQ are more specific: each new business consumes a creation, while an existing business plan remains editable. Treat the allowance as finite creations, not a monthly refill and not a recycling workspace.

Monthly AI requests are separate: 100 on Tier 1, rising to 5,000 on Tier 6. A generation or rewrite uses a request according to the FAQ. Continued editing is therefore possible after the creation allowance is consumed, but starting another unrelated business is not. Image and translation quantities are listed separately; their reset terms were not conclusively established and should not be borrowed from the monthly text-request rule.

Choose the deliverable before choosing capacity

Tiers 1 and 2 include PDF export and core business-plan financials. Tier 3 adds PowerPoint export, view-only sharing, branding controls, strategy overview, scenario/stress analysis and detailed business valuation. Tier 4 mainly raises capacity within that feature set. API, MCP and versioning are listed from Tier 5, not on the cheaper tiers.

For a founder documenting one straightforward business, Tier 1 may be enough. For ten client plans that require an editable presentation export or scenario analysis, Tier 3 is the relevant floor. A consultant who must connect an outside system needs to check Tier 5 even if the expected client count fits Tier 3.

The direct pricing page now uses Explore, Application-Ready and Investor-Grade names, while the deal terms map lower tiers to Basic and higher tiers to Pro. Use the actual AppSumo feature matrix rather than treating a direct subscription name as proof of every lifetime entitlement. The offer requires AppSumo Plus; include any required membership cost in the purchase decision rather than calling the licence price the entire checkout total.

A coherent model still depends on credible inputs

Start with a documented revenue driver such as customers multiplied by average spend, then separately record direct costs, staffing, payment timing and other commitments. Replace illustrative assumptions with evidence from your own business. A connected model can keep statements consistent, but it cannot establish demand for a product that has not been tested with customers.

Use scenarios to ask a concrete question: what happens if sales start later, margins are lower or invoices are collected more slowly? Check that the changed assumption reaches the cash-flow view and that the written narrative does not still describe the original optimistic case. This is a proposed evaluation workflow; it was not executed in a PrometAI account.

DCF valuation is sensitive to assumptions about future cash flows and the discount rate. A precise output is not independent proof of what a business is worth. Have material financial claims and any fundraising document reviewed by someone qualified for the purpose. Generated NDA and term-sheet templates likewise need contextual review, not a signature simply because they appear in the app.

One detailed buyer review reports stale assumptions in the exported PDF after changing the model, and says AI regeneration sometimes replaced custom inputs. The founder discusses how approved numbers are handled rather than providing an independently verified resolution. This makes export reconciliation an essential evaluation step: compare the final revenue, cost and cash-flow figures with the approved assumptions before sending the document.

Client delivery has boundaries

The FAQ permits consulting and multiple-client use, with each business consuming a separate creation. It also says there are no client subaccounts or multi-party approval workflows within a project. A view-only sharing link is a delivery surface, not a permissioned client workspace where several stakeholders can edit and approve.

Before promising a client deliverable, export one representative PDF and inspect its tables, page breaks, currency and totals. If PowerPoint is required, confirm the Tier 3-or-higher output can be edited in the client’s intended software. Watermark-free exports are explicitly confirmed for the AppSumo tiers; free-plan restrictions must not be transferred to the paid deal.

Keep the original assumptions and client approvals outside the generated narrative. This makes later revisions defensible: you can explain which number changed and why. Avoid committing to an unlimited stream of new client plans when even the largest tier has a finite creation allocation.