Platform area

Integrations, reporting and onboarding.

This area matters when teams need joined-up reporting, cleaner stakeholder visibility, migration support and the security controls needed for wider rollout.

7-day trial. No card. Cancel anytime.

Need the full map first? See platform overview →

Why teams look at this

Three problems this part of the platform actually solves.

Most teams arrive here once the core workflow is running and they need it to connect outward - to other systems, to stakeholders, to a wider team.

System alignment

Fire Door App - delivery record Live
Xero - invoice & billing Synced
CRM - client & job records Synced
No manual re-entry required Joined up

Benefit 01

Joined-up systems.

Keep finance and CRM records closer to the operational trail instead of letting them drift apart. When accounting and delivery live in separate systems with no connection, someone ends up manually reconciling them - and that reconciliation is where errors compound.

  • Xero and accounting integrations from the delivery record
  • CRM records kept aligned with what's happening on site
  • No manual re-entry between operational and finance systems

Portfolio overview

Inspections completed 124 / 148
Remedials outstanding 31 doors
Jobs closed this month 8
No separate dashboard needed Live view

Benefit 02

Operational visibility.

See what is outstanding, complete and changing across buildings without building a separate dashboard to do it. Reporting and exports pull from the same live record - so managers and auditors get the numbers without someone compiling them first.

  • Portfolio progress visible without manual pack-building
  • Exports and dashboards from the live record
  • Audit-friendly evidence without a separate reporting cycle

Rollout progress

Building 1 - workflow proven Complete
Buildings 2-5 - rolling out In progress
Buildings 6-12 - planned Queued
Access controls configured Ready

Benefit 03

Rollout with less risk.

Start on one real building, prove the workflow, then scale with cleaner controls and onboarding. The platform is designed to be committed to incrementally - the migration tools, permissions and workspace setup make expanding to more buildings a controlled process, not a leap.

  • Import existing records before the team goes live
  • Prove the workflow on one building before scaling
  • Roles, 2FA and permissions set before wider access
What lives in this area

The main capabilities teams review before committing.

Start with the capability closest to your current problem, then go deeper via the guides.

Integrations - live

Xero Connected
QuickBooks Connected
CRM - client records Synced
No manual re-entry Aligned

Capability 01

Accounting & CRM integrations

Keep client, billing and finance records aligned with what delivery teams are doing. Accounting and CRM updates flow from the operational record rather than being re-entered separately.

  • Xero and QuickBooks connected to the job record
  • CRM client data aligned with live delivery
  • Finance records without manual reconciliation

Reporting - all buildings

Inspections this quarter 124
Remedials outstanding 31
Jobs closed 8
Exportable for audit PDF · CSV

Capability 02

Analytics & reporting

Use dashboards, exports and histories to show progress and produce audit-friendly evidence. Reports pulled from the live record rather than compiled by hand - available on demand rather than on a reporting cycle.

  • Portfolio dashboards without manual pack-building
  • PDF and CSV exports for internal and external review
  • Door-level histories for audit and compliance

Onboarding - Building 1

Existing records imported Done
Team onboarded & active Done
Workflow proven In review
Scale to portfolio Next step

Capability 03

Migration & onboarding

Import existing records, prove the workflow on a real building, and scale once the team is comfortable. The platform is designed to be adopted incrementally - not committed to all at once.

  • Import existing PDF inspection records
  • Workspace setup checklist before going live
  • Prove on one building before expanding

Access controls

Separate workspaces Available
Role-based permissions Configured
2FA - all accounts Enabled
Ready for wider rollout Secured

Capability 04

Roles & 2FA

Support broader rollout with separate workspaces, granular permissions and stronger access controls. The security layer that helps teams onboard more users, more buildings and external stakeholders without losing control of who sees what.

  • Separate workspaces for customer records
  • Role-based permissions per user and team
  • 2FA available as part of workspace policy

Each capability has a dedicated guide in the resources library.

Browse all guides
What good looks like

What teams need from this in practice.

Two perspectives - the team managing rollout and reporting on the ground, and the stakeholders deciding whether the platform is worth scaling.

Operationally

What the team needs day to day.

The practical friction teams feel once the core workflow is running and they need to scale it outward.

1

A cleaner route from the first building to wider rollout.

Starting on one building is easy; scaling to twelve is where things break down. The team needs migration tools, workspace setup support and a clear path from a proven workflow on one site to confident adoption across a full portfolio - without rebuilding from scratch each time.

2

Reporting that helps managers and auditors see progress without manual pack-building.

Producing a progress report for a manager or an evidence pack for an auditor should not require someone to spend half a day collating data from multiple places. If the platform holds the live record, the report should come from it - not be built on top of it.

3

Security and access controls that support adoption across larger teams.

As more users, more buildings and more external stakeholders join the platform, access control becomes critical. The team needs role-based permissions, tenant isolation and 2FA set up before they expand - not configured in a hurry after something goes wrong.

Commercially

What stakeholders need to see.

The questions buyers and managers ask before committing to wider rollout across a portfolio.

1

Can the platform fit around existing finance and CRM tooling without breaking the workflow?

The commercial objection is not usually about the platform itself - it is about what it displaces. Stakeholders need confidence that adding Fire Door App does not require ripping out Xero, disrupting the CRM or creating a parallel data trail that someone has to maintain.

2

Will reporting be strong enough for internal oversight and external evidence requests?

The reporting question has two audiences with different standards. Internal managers need a dashboard that shows progress without interpretation. External auditors and regulators need exports that trace back to door-level evidence. The platform needs to satisfy both - not just the easier one.

3

Does onboarding make it realistic to start small and scale safely?

The scaling question is really a risk question. Stakeholders need to know the platform will not create a large commitment before the value is proven. Starting on one real building, with clean migration support and a checklist before going live, is what makes a wider rollout feel like a decision rather than a gamble.

The shared outcome

A platform that fits around the tools you already have - scales from one building to a full portfolio, reports without manual compilation, and proves its value before you commit to it fully.

Relevant resources

Guides for this part of the platform.

Use these when you want the process and rollout detail behind each capability - not just the overview.

Integration guide 5 min read

Accounting and CRM integrations

See how operational delivery links back to finance and CRM systems. Covers connecting Xero, QuickBooks and CRM tools to the live job record without creating a parallel data trail.

  • Connecting Xero and QuickBooks to job records
  • Keeping CRM client data aligned with delivery
  • Avoiding duplicate entry across systems
Reporting guide 4 min read

Reports & exports

Review how dashboards, PDFs and CSVs support reporting and oversight. Covers generating portfolio-level summaries and door-level exports that satisfy both internal managers and external auditors.

  • Portfolio dashboards without manual compilation
  • PDF and CSV exports for audit and oversight
  • Door-level histories for compliance evidence
Migration guide 5 min read

Importing PDF inspection reports

See how existing report packs can be brought into the platform more cleanly. Covers preparing historical records for import so the platform holds a complete picture from day one - not just from when the team went live.

  • Preparing existing PDF reports for import
  • Mapping historical evidence to door records
  • Building a complete record before going live
Setup guide 6 min read

Workspace setup

Use a simple rollout checklist before expanding to more buildings and users. Covers the steps to complete before going live - access controls, permissions, integrations and team onboarding - so expansion is controlled rather than ad hoc.

  • Pre-rollout checklist for teams and buildings
  • Access controls and 2FA before adding users
  • Integrations confirmed before scaling further

More guides available across all platform areas.

Browse all resources
Use cases that start here

The audiences most likely to start with integrations.

This part of the platform is for teams scaling beyond one building. Want the audience view? Start with the use case closest to your team.

Contractors and care homes also use this area as they grow their programmes.

Start today

Prove it on one real building.
Then scale with confidence.

Run one live workflow, connect the reporting and rollout pieces that matter, and see how the platform fits around the tools you already use. No setup cost, no card required.

No card. Cancel anytime.

Xero + CRM Portfolio reporting PDF + CSV exports Migration support Workspace setup Roles + 2FA