TechAppForcePricing
Pricing that fits how your product grows
A paid pilot on your own use case first. Then a subscription per app, not per end user.
The problem
Buyers should not need a spreadsheet to predict their bill
Per-user, per-app and per-prompt pricing, in the words of people paying it.
“Pricing model is complex and hard to predict as apps grow, which increases anxiety.”
Review of an enterprise low-code platformPublic comment“Is it one app PER USER or one app for all users?”
Buyer question on a low-code licensing forumPublic comment“I was finding I was 'running out of credits' way too often and what was meant to be a 'toe dip' became expensive.”
Review of a prompt-first AI app builderPublic comment
How it works
Proof on your problem, then a subscription
See a working app before you sign for a year.
- Demo and scopingWhat we cover, where you code
- Paid pilotFixed scope, your success criteria You decide on the result
- Pilot fee creditedAgainst your first year
- Subscription per appAdd an app when you launch a product
What every plan includes
The whole platform, not a feature menu
Nothing below is a paid upgrade.
- Data model and custom fields
- Screens, grids, kanban, charts
- Lifecycles and approvals
- Workflows, jobs, notifications
- Reports, import and audit
- Environments and releases
- TAF Studio for developers
- Code where you need it
- Help from the people who build it
Questions
Pricing and buying, answered
Why is there no price list on this page?
The right plan depends on how many apps you run and how many customers you serve. Ask for a quote and you get the numbers in writing.
Can we try it before we commit?
Yes, on your own use case: a demo, then a paid pilot with a fixed scope. You finish with a working app in staging, not an abandoned sandbox.
What does the contract look like?
The pilot is a short fixed-scope agreement with written success criteria. The subscription is annual, for your production apps. Continue within the agreed window and the pilot fee is credited to your first year.
What if we outgrow our plan?
Adding customers on an existing app adds no per-user charge. When you launch another product, we add that app to your plan, on terms agreed in your quote.
How is TAFI usage priced?
Inside TAF Studio, TAFI runs on an AI account you connect, so your AI provider bills that usage directly. How TAFI is included in your plan is set out in your quote.
Is this only for simple apps?
The opposite: it is built for business software with many roles, approvals, and customers who each want their own fields and rules. For a simple one-off app a lighter tool may suit better, and we will say so.
Will we be locked in?
Everything your team builds stays visible and editable, and developers add real code wherever a setting is not enough. We will walk through what leaving would involve before you sign.
We are a small team. Is this too much?
Small teams benefit most. Start with one pilot on one real process, with our team alongside yours.
Is it safe to build with AI?
TAFI asks questions, shows what it plans to build, and builds only after you approve each step. What it builds is ordinary configuration your team can review and change.
Where is our data kept, and how is it protected?
Tell us where you need it hosted, including any country or customer requirements, and we confirm what we can support before you sign. Access is set per role, and every record keeps a change history. We answer your security questionnaire in writing. How we handle security
Get a quote for your product
Tell us what you are building and who your customers are. We reply with a pilot proposal and a subscription quote in writing.