Skip to content
Halligan Works

Product

The platform

A website, a donation page and an operations console for a volunteer fire department. One subscription, one deployment, and a department that is a row in a database rather than a branch of the code.

Open the demo department
01

Three surfaces

The public site is what a donor sees. The console is where the work actually happens, and it is the part built for somebody standing in a field on one bar of signal.

01

The public site

Apparatus, roster, events, coverage area, conditions, donations and a volunteer application. What appears on it is decided in the console, page by page.
02

The console

Where officers log calls, review photos, manage the roster and update the site. Large targets, high contrast, and built to work badly-connected.
03

The installed app

The site installs to a phone’s home screen with the department’s own name and icon. No app store review, and no per-department app to get rejected.
02

See a department site

The fastest way to understand this is to open one. The demo runs on the platform itself — the same code every subscribing department gets, not a mockup of it — filled with an invented department’s content.

What to look at

  • 01The public site, as a resident or a donor arrives at it
  • 02The incident log, showing what an officer chose to publish
  • 03The burn ban a resident checks before they light anything
  • 04Add it to a phone home screen — it installs with no app store

Note — this department is not real

The name, the district, the roster and every call in the log are invented. The donation page takes no money, and nothing on the site is an emergency contact. If you need a fire department, call 911.

Open the demo department
03

Included in every subscription

No tier below this. A department that pays gets all of it.

Donations

Tiers a chief can set, and funds settling directly into the department’s own merchant account.

Incident log

Calls recorded by an officer, with what gets published to the public site decided separately from what gets recorded.

Roster

Members, ranks and appointed duties. Publishing a member’s details requires that member’s consent, and an import can never grant it.

Apparatus

Every truck, with photographs. Positions are never published — where the apparatus is is operational information.

Conditions

Burn ban and fire weather, read from the state feed. An unreachable source reads as unreachable, never as "no ban".

Events and applications

A calendar, and a volunteer application that works on a phone without printing anything.
04

Paid modules

Sold separately and off by default. Only Halligan Works can enable one; a chief cannot grant himself a module, and what a department has not bought is invisible rather than merely unlinked.

The Box

Scene photos, reviewed by a named officer before anything is published — and shared across the departments that ran the call together.
Read more →

Size-Up

The gate-code binder, searchable, on a phone, and working with no signal.
Read more →

The Roll

Landowner enrollment and a ledger of who owes what. The platform never touches the money.
Read more →
05

What it is built against

These constraints shaped the product more than any feature list did.

Constraint 01

One bar of rural LTE

The console is used from a truck in a district measured in hundreds of square miles. Page weight is a functional requirement here, not a score to chase.
Constraint 02

An older audience

Larger type, high contrast, targets big enough for gloved hands, and no puzzle to prove you are a person.
Constraint 03

Colour is never the only signal

Every status carries a shape and a label as well as a colour, so it survives colour blindness and direct sunlight.
Constraint 04

No metered third-party services

Per-department bills for maps or tiles quietly eat a subscription this size. Where maps are needed they are built on open data, which is also the only option that works offline.
06

What it costs

An annual subscription, per department, quoted for the department. There is no per-seat charge: the whole of a roster uses it for the same price as one person, because a department that has to ration logins will ration them to the people who already had the information.

What moves the number

  • 01How many people are on the roster, and how many of them work in the console
  • 02How much ground the district covers, and how many properties are in it
  • 03Which modules are switched on — The Box, Size-Up and The Roll are separate
  • 04Whether it is one department or a mutual aid group buying together

A twenty-member department covering one district, and a county buying for every department on the box, are not the same purchase — one published number would be wrong for both. Tell us the district and what you need, and we will put a figure to it.

We never take a percentage

Donations settle directly into the department’s own merchant account. Halligan Works never holds or routes the money, so there is nothing to take a cut of.

No setup fee

Getting a department’s content in is part of the subscription, not a line item, and not a reason to hold up a quote.

Your data leaves with you

Roster, incidents, donations and photographs export to ordinary spreadsheet and image files. A department that leaves takes its records with it.
Ask what it would cost