← All articles

Building a Custom Capture App for Your Organisation

What does a white-label Preserver deployment actually look like? We walk through the process from first call to launch day — timelines, what's involved, and what you end up with.

Preserver's white-label program lets organisations deploy a fully branded version of the app — your name, your logo, your colours, your workflow — built on the same proven capture engine that powers the consumer product.

We get enquiries from organisations of all sizes. Aged care networks wanting a uniform documentation tool for support workers. Construction companies wanting a site-specific capture app for subcontractors. Government agencies wanting a compliant evidence-capture tool with their own branding. The use case varies; the process is broadly the same.

What "white-label" actually means

A white-label deployment isn't a reskin of Preserver with a new icon. It's a rebuilt application tailored to your organisation's requirements. The core capture engine — text, voice, photo, video, GPS, timestamp — forms the foundation. Everything else is customisable:

  • Branding — your name, logo, colour scheme, splash screen
  • Workflow — custom capture categories, required fields, activity templates, mandatory photo checklists
  • Reporting — export formats aligned with your compliance or case management systems
  • Distribution — published under your organisation's App Store and Google Play accounts, or distributed via MDM for managed devices
  • Data handling — storage options including on-device only, your own cloud infrastructure, or specific third-party integrations

The process

Engagements typically follow four stages:

Discovery call — a conversation about your use case, the number of users, device landscape (iOS, Android, both), and any compliance or data sovereignty requirements. This is where we figure out whether white-label is the right fit and roughly what's involved.

Scoping and proposal — we document what we'd build: the customisations, any bespoke features, integration points, and the timeline. This goes into a fixed-price proposal. There are no surprises mid-project.

Build and testing — development, typically 4–10 weeks depending on scope. We involve your team in testing rounds before submission to app stores.

Launch and handover — app store submission, staff rollout support, and documentation. Ongoing maintenance and update agreements are available.

We wanted something our field workers would actually use. Having our branding on it, and removing features they didn't need, made a real difference to adoption.

Who it's for

White-label makes sense when you have enough users that the per-head economics work, when your workflow requires specific capture templates that the consumer app doesn't provide, or when branding and data control are non-negotiable requirements.

For smaller teams or individuals, the standard Preserver app usually does what's needed. But if you're thinking about rolling out a documentation tool across a team of 20 or 2000, it's worth having the conversation.

Get in touch via our feedback page or the white-label enquiry form on the white-label page. We respond to every enquiry.

Interested in white-label?

Tell us about your organisation and we'll get back to you.

Learn about white-label →