Your customers do not buy forms. They buy your judgment — the inspection rubric you refined over years, the compliance cadence a regulator accepts, the QA checklist that catches the defect before the customer does. Today that judgment lives in your head, a spreadsheet, and a PDF template. This page is about turning it into a product with your name on it, without building software from scratch.
One worked example: a roof inspection program
A building-envelope consultant runs quarterly roof inspections for property managers. The method is proven: a fixed walk order, a condition scale per component, photo evidence for anything rated below "good", and a report the property manager forwards to the owner. It is delivered today with a clipboard, a phone camera, and an evening of copy-paste.
On FieldScroll, the same program looks like this:
- The form is the method. Sections follow the walk order. Each component gets the condition scale as a choice list. A photo field becomes required when the rating drops below "good" — a visibility rule, not a training reminder. A lookup field pulls the building and roof section from a data source so the inspector never types an address.
- The inspector works offline. On the roof, there is no signal. Drafts, photos, and location are stored on the device and sync when the inspector is back in the truck. A QR code on the roof hatch opens the right form with the building already filled in.
- Review happens on the web. The consultant's office sees the submission in the branded dashboard — searchable, filterable, with every photo in place. If a section was missed, dispatch sends the record back to the inspector's device for a follow-up visit, locked so nobody else edits it in the meantime.
- The report writes itself. A report template renders the branded PDF the property manager expects and emails it. A webhook posts the same event to the consultant's job-tracking system. Each delivery is retried on its own and listed with its status.
- The method improves without losing history. Next quarter the consultant adds a drainage check. The new form version ships to every device; last quarter's records still read exactly as they were captured.
Nothing above is a custom build. It is the form builder, the report editor, a webhook subscription, and a data source — the same tools every FieldScroll instance has.
What you bring, what the platform brings
| You bring | FieldScroll brings |
|---|---|
| The method: what to check, in what order, with what evidence | The form builder with logic, lookups, pages, and repeating tables |
| The customers, or a channel to reach them | The branded mobile app and web dashboard your customers use |
| The report your customers already expect | The report editor, PDF and HTML rendering, and email or webhook delivery |
| The systems your customers already run | The REST API, webhooks, and managed data sources |
| The judgment about what version two should be | Version-aware records so version two never rewrites version one |
The commercial model
FieldScroll is priced as a platform you build a business on, not as seats:
- Launch — $25,000 a year. A dedicated instance, white-labeled mobile and web, one production solution line, up to five customer organizations. Most partners start here.
- Partner — from $50,000 a year, priced per engagement around the customer footprint your offer grows with: a site, a fleet, an operating company, a clinic.
- Builder — $10,000 a year for a shared pre-production workspace to learn the platform. Not for commercial use.
Details and the plan comparison are on the pricing page. How the customer footprint is defined is on who it's for.
What to leave out of version one
The programs that launch well are narrow. A single workflow, a single report, one customer or pilot site, and a clear answer to "what does the customer get that they did not get from the PDF". Custom mobile screens, integrations beyond a webhook, and per-customer variations are all possible later and are all scoped separately — see what is quoted separately.
What FieldScroll does not do here
- It does not create the market for you. You need customers or a channel.
- It is not a system of record. Your customers' long-term history, CRM, and analytics stay where they are; FieldScroll hands them clean records, documents, and events.
- It does not approve records. Review is search, filter, detail, edit where permitted, and dispatch. If your program needs a formal sign-off state, say so in the discovery call so it can be designed rather than assumed.