The platform

FieldScroll is a managed field-workflow runtime.

The branded mobile and web layer that captures, runs, and routes operational records your customers create in the field. Not a long-term system of record. Not a generic form builder. A managed runtime that lets you sell expertise instead of managing infrastructure.

Three branded phones fanned slightly: a Summit Inspections login screen, a fire-extinguisher inspection form mid-photo capture, and a Coastal Facility Services dashboard with recent records — each showing a different partner variant of the FieldScroll mobile shell.
1
Dedicated backend environment per partner — your data boundary
2
Surfaces included: branded mobile + web
5
Max custom screens via the Advanced extension tier
0
Shared multi-tenant pools, ever
What lives where

What the runtime covers — and what it doesn’t.

FieldScroll is

A managed field-workflow runtime

  • Branded mobile and web data capture for your customers.
  • Drafts, offline submission, sync, and operational review.
  • Document generation and outbound webhook routing.
  • Dedicated cloud infrastructure per partner, monitored 24/7.
  • An operating cadence: onboarding, monthly meeting, QBR.

FieldScroll isn't

A long-term system of record

  • Your downstream system of truth — that lives in your own application or DB.
  • A customer-facing portal, CRM, or vertical app product.
  • Multi-year archival or BI / multi-year analytics.
  • A generic form builder for self-serve end users.
  • A platform you customize freely beyond the extension contract.
Six included services

Everything you need to run the workflow.

Every FieldScroll environment ships with the same six services on day one. No upsell ladder for table-stakes capability.

  • Mobile data capture

    iPhone, iPad, Android. Branded as your app, distributed under your developer relationship or ours.

  • Drafts, offline, sync

    Form execution that survives bad signal. Records queue locally and sync the moment the device reconnects.

  • Submission and review

    Operational review surface, search, and record detail pages. Branded as your web product.

  • Documents

    Branded PDF / DOCX rendering on submission. Custom templates for your downstream report flow.

  • Webhook routing

    Outbound webhooks with payload transformation. Route records into your customer's SQL, CRM, or ITSM.

  • Monitoring + releases

    Error monitoring, product analytics, uptime checks, and mobile release coordination handled by us.

Two-tier tenancy

The boundary is explicit and load-bearing.

FieldScroll ships shared codebase, migrations, and an extension registry into each partner environment. Each partner operates a branded app and a dedicated backend environment that hosts its own downstream customer organizations.
One shared platform; one branded environment per partner; many customer organizations inside each environment.

FieldScroll platform

Maintained by Thirtysix Solutions. One shared codebase, one shared schema, one migration stream.

Partner environment

One dedicated backend environment per partner. One branded mobile and web app variant. Your business boundary — no shared multi-tenant pool.

Customer organization

An organization inside your dedicated environment. Your downstream client, franchisee, location group, fleet, or managed site.

Extension registry1080 × 810

Illustration: a typed extension registry diagram. Central registry box (Survey Blue primary-900 #13243a) with three arrows fanning to three labeled custom-screen tiles. Each tile shows a mock phone screen with a domain-specific layout (asset photo, signature pad, multi-step form). Flat vector. Survey Blue palette with brass #c89a3a (the DS --marker) as the typed-contract accent on the arrows. Geist labels throughout.

Extension model

Custom mobile screens, bounded by a typed contract.

Up to 2 screens in the Mobile Extension tier and up to 5 screens in the Advanced tier. They register through a typed contract and use the existing shell — auth, navigation, data access, and standard components.

Native capabilities — Bluetooth, payment terminals, background services — stay centralized. If you need one, it gets evaluated as a platform capability, not a one-off partner hack.

Branding1080 × 810

Comparison strip showing the same login screen layout in four partner variants: 'ACME FieldOps', 'Northwind Inspections', 'Meridian Compliance', 'Atlas Fleet Audit'. Each has its OWN logo + accent color but identical typography, spacing, and input shapes — that's the point. UI chrome rendered in Geist. Photographic mobile mockups, slight tilt, soft shadow. No FieldScroll Field Grid mark or 'fieldscroll' wordmark visible on any device.

White-label boundary

Branded inside the runtime; not a from-scratch app.

White-labeling is included by default and scoped to what the runtime owns: app identity, branded surfaces, environment-level configuration, and outbound document or webhook branding.

Customizations that imply a durable customer-facing app, complex business hierarchy, multi-year analytics, or rich domain dashboards sit outside the runtime and are quoted as Growth or Enterprise scope.

Next step

See where FieldScroll fits your offer.

A 30-minute discovery call to map your downstream customer unit, the workflows you already run, and where FieldScroll takes load off your team.

Talk with us