Fulcrum pricing for asset inspection teams

Price the people collecting and reviewing asset records, then test offline evidence and export access before choosing a plan.

Kartik Deshpande··6 min read

An inspector photographs a valve, records its location, and leaves a finding for the office to review. A second visit needs to point to the same asset without overwriting the first inspection. Fulcrum pricing should account for the people collecting those records and the people checking them. This evaluation concerns the field operations product at fulcrumapp.com, not other businesses named Fulcrum.

Evaluate Professional for a defined field collection and export workflow. Consider Elite when the reporting design needs the APIs or administration features listed in its plan. Keep your current setup if it preserves asset identity, inspection history, and usable evidence through offline work and review. A small number of editors does not establish a small license bill: price every person who needs account access before choosing.

Price collectors and reviewers for the same year

Kartik Deshpande prepared this evaluation from official sources checked October 29, 2026, without testing an account. Fulcrum’s pricing page lists Professional at US$43 per user license per month and Elite at US$55. Both require an annual subscription and at least five users per organization. Enterprise requires a quote.

For a hypothetical team of eight inspectors and two office reviewers, ten full licenses for twelve months cost $5,160 on Professional or $6,600 on Elite. The $1,440 difference compares the same people and period, before tax and separately scoped services. A discounted reviewer rate was not verified; ask for one rather than assuming restricted editing makes a seat free.

Purchase decisionPublished scopeBudget implication
Collection and exported reportingProfessional: offline capture, linked records, import/export, 100 GB storageTen annual licenses: $5,160 before extras
API-based reporting or added administrationElite: APIs, webhooks, SSO, audit logging, 500 GB storageTen annual licenses: $6,600 before extras
Broader organization agreementEnterprise: tailored agreementTotal unknown until quoted

Send the seller the same ten-person roster, expected inspection frequency, retention period, and media estimate. Request separate amounts for implementation, additional storage, training, and any integration work. Record who maintains forms after rollout. A proposal that excludes ongoing form changes should not be compared with one that includes that work without adjusting the scope.

Measure media demand with a representative inspection. A short record with several photos has a different storage profile from a visit with video, and retention compounds that difference. Use the sample size and expected visit count to estimate a year of collection, then include the archive you intend to keep. Ask how the order treats storage expansion and renewal changes.

Limit editing without assuming a different license

Fulcrum’s role definitions separate creating records, editing records, changing status, exporting, and running reports. Define those actions for your reviewer before choosing a role. Someone who checks a finding may need to change its status without changing the original observation, while the person preparing the archive needs export access.

The system-role documentation says Standard users can collect and edit accessible records, while Record Creator users cannot edit records or run reports. That restricted role is not automatically a reviewer role. Custom roles have plan conditions, so verify the quoted entitlement and the resulting permissions in the trial.

Test the proposed role with a second project that the reviewer should not see. Check search results, linked records, downloaded data, and report generation. If a person needs to see the valve record through a link, Fulcrum’s record-link documentation requires access to both the linking app and the referenced app. Include that access dependency in the role design.

For a separate comparison of inspection frequency and reader access, see SafetyCulture pricing for inspectors and report readers. Its seat model needs its own evaluation; carrying a reader assumption from another product into this purchase can misstate the cost.

Try an asset record and a repeat visit offline

Use a fictional asset register containing valve V-104 at a test location. Create an inspection form with the asset reference, observation, photo, visit time, and reviewer status. Prepare the authorized records and forms on the mobile device while connected, then run the exercise without a network connection. This is a proposed acceptance test, not a claim of hands-on results.

Fulcrum’s offline documentation supports collection without internet access, but syncing records and apps requires a connection. Record the visit offline, reconnect, and check the web record and photo. Have the reviewer inspect the result before treating it as available to downstream reporting.

Repeat the visit with a changed observation and a second photo. The expected result is two distinguishable inspection events linked to one asset, with the chosen review state preserved. Check the location and identifier instead of relying on a similar asset description. If a collector and reviewer both change the same record, test how the configured workflow handles that conflict before allowing the pattern in production.

Collection access and review access have different requirements
Field collector

Asset reference, location, visit, photo

Office reviewer

Received evidence, review state, exceptions

Use the same asset reference in both views, and check that synced evidence reaches the reviewer under the intended permissions.

Check the exported records and photo files together

Fulcrum offers a Data Downloader and an Exporter. Its export overview distinguishes filtered exports with full geometry support from general exports that can include history. Choose the route that preserves your required fields and geometry, then inspect a sample from both visits rather than accepting a count of downloaded rows.

The photo export instructions distinguish media URLs, which require a Fulcrum login, from downloaded files. They also distinguish the Exporter’s photo metadata from the Downloader output. Open the archive outside the application session and check that each inspection still maps to its photos. A working link during the trial does not establish that the archive will work after access ends.

If the finding becomes repair work, preserve that relationship without equating inspection completion with repair acceptance. The construction punch-list software comparison covers assigning and verifying the corrective work. Keep the original observation available when the follow-up status changes.

Where Permute fits in inspection reporting

Permute sells connected business data and custom applications, so this evaluation has a commercial interest. We can scope reporting from available Fulcrum exports and an asset register, match the asset identifiers, and retain references to inspection evidence. The supported data path needs verification; this does not claim a native Fulcrum connector.

The inspection manager defines which visit and review status count for each report. Those rules can be reused to show missing reviews, unmatched assets, or absent photos without treating an incomplete record as an accepted inspection. A reviewer should be able to inspect the source behind an exception and see when the reporting data last received an update.

Inspect your asset and inspection exports

Use a non-sensitive sample to identify the asset keys, repeated visits, and evidence references needed for a recurring report.

Keep inspection acceptance with qualified people

This reporting scope does not certify asset condition, conduct an inspection, or establish regulatory compliance. The responsible people set the criteria and accept the work. Reporting changes also do not authorize changes to the source record; any write process needs a separately scoped and approved contract.

Preserve asset relationships before switching

Inventory forms, record links, choice lists, map layers, permissions, and attachments before moving the workflow. Fulcrum’s instance-migration documentation warns that imported records receive new identifiers and linked records need remapping. It also says roles require reconstruction. Those details are reasons to test relationships, even when the record export itself succeeds.

Keep an old-to-new identifier map and rebuild the intended reviewer access. Reconnect approved reporting integrations, rerun the offline visit, and compare the source records, media, and review state. Retain the old archive until the responsible team accepts the destination and owns any remaining exceptions.

Price the full inspection roster over the same year, including the people who only review records. Use the asset-and-repeat-visit test to check offline capture, review access, and usable exports. Choose the plan whose documented access and integration scope fits that work. If the current process already passes those checks, focus the purchase decision on the remaining gap.

Review the inspection-to-asset reporting handoff

Bring an inspection export and the asset register it needs to match to discuss review rules and evidence access.

Questions about Fulcrum inspection costs

Which Fulcrum product does this pricing cover?

It covers the field operations and inspection product at fulcrumapp.com. Check the vendor domain when comparing proposals because other companies use the same name.

Does restricting a reviewer’s editing reduce the seat price?

A permission change does not establish a discounted license. Ask for the applicable reviewer entitlement and price, then test the account against the review and export actions that person needs.

Can the office use an inspection before the device syncs?

Do not treat a locally saved inspection as received by the office. Reconnect the device and check that the record and supporting media have reached the reporting source before relying on them.

Is a CSV with photo links enough for a retained archive?

Check whether those links require the old login. Retain the necessary photo files and their relationship to each inspection, then open the archive with the access the eventual reviewer will have.