Start with a pre-production workspace, launch with a flat production package, then move into a Partner structure when your solution is growing. Three plans, one annual commit, no per-seat math.
Plans at a glance
Annual · USD
Builder
Best for
Teams learning the platform before going to market.
Launch
Best for
Your first commercial FieldScroll-powered solution, end-to-end.
Partner
Best for
Successful businesses scaling past the Launch footprint.
Partner pricing is agreed per engagement — request a pricing conversation. Builder is a learning tier; it can’t be used commercially or in production.
What's included
Launch is the anchor
| Capability | Builder | Launch | Partner |
|---|---|---|---|
| Use case | Pre-production | First commercial launch | Growth and scale |
| Environment | Shared FieldScroll environment | Dedicated instance | Dedicated, scaled as needed |
| Branding | FieldScroll-branded | White-labeled mobile and web | White-labeled, deeper structure as needed |
| Organizations | 1 | Up to 5 | Defined by Partner Schedule |
| Users | Small build team | Up to 100 active users (operational guardrail, not per-seat pricing) | Defined by Partner Schedule |
| Retention | Set in your order form | Set in your order form | Defined by Partner Schedule |
| Support | Minimal async | Standard support, monthly meeting, QBR | Expanded operating cadence |
| Pricing | Flat | Flat inside Launch footprint | Unit, Capacity, Rate |
When to move up
Signals it's time to talk
After the discovery call
From conversation to launch
Pricing is a step inside a working relationship, not a self-serve checkout. Here is what happens once we agree there is a fit.
Discovery call
60–90 minutes mapping your workflow, your downstream customer unit, and the offer you want to take to market. Working session, not a sales pitch.
Scoping note
We write up what we heard: the right plan tier, the customer footprint, the launch shape, and anything that would be quoted separately. You decide whether to move forward.
Order form
A short document that names the plan, the footprint, the retention term, the support cadence, and any separately quoted scope. Annual commit, one signature line.
Onboarding and launch
Environment provisioning, brand setup, training, app store coordination, and the first production launch. Typically four to eight weeks depending on scope.
Not sure where you fit?
The right plan depends on whether you are building, launching, or scaling. A short conversation can identify the right starting point.
Request a pricing conversation