STORMinatorSTORM RESPONSE. BUILT FOR THE CREW.Follow the weather. Price the response. Get the next move clear—before the trucks start rolling.
Planning, state-rule reviews and private job files are live. Explore the demo.
You already know how to watch the weather. The hard part comes next: deciding where to investigate, what the response could cost, which equipment is needed, and what your crew has to document.
STORMinator connects those decisions. The live workspace turns weather reports into a response plan. The operations workspace brings required steps, condition-specific records, original photos and state-rule reviews into the same process.
Bring active alerts and recent reported events into one place. Review towns, counties and surrounding areas, then choose a location for a closer look. A storm report starts the investigation; field evidence confirms the job.
Explore storm intelligence ↗
A CLEAR NEXT MOVECalculate road miles, drive time, prep and delay allowances. Build the equipment estimate, separate billing from operating costs, and check whether the response fits your arrival target before you commit resources.
Open Camile’s Storm Runbook ↗
THE JOB. THE STEPS. THE RECORD.Move through intake, mobilization, scene records, work, closeout and submission. Keep the confirmed address, original files, factual captions, actual equipment time and activity history together.
Open the job workspace ↗A tree on a roof needs a different record than a tree blocking a driveway. Choose a condition below. Watch the required steps change, then work through the path.
Try the checklist interaction below. For server-saved work, open the live job workspace ↗. This page’s walkthrough resets when you leave.
Start one record with the right person and the right place.
Complete the required items to open the next step.
Show the documentation that fits the work. Keep shared requirements consistent across the crew.
Customer, address, original files, captions, notes and activity history are connected in the live job workspace.
State wording, contracts, pricing and dispatch decisions need the people authorized to make them.
A promising storm area can be a long road from your yard. The live planning workspace puts travel and job economics beside the event so you can see more than a point on a map.
The current route engine estimates car-road travel. Confirm commercial-truck access, driver hours and local conditions before mobilizing. Your actual yard, costs and availability belong in the plan.
Take the planning tools for a spin ↗
Launch plans for the owner watching the map, the crew building a repeatable process, and the operation coordinating the bigger picture.
Storm intelligence and deployment planning for one operator.
Monthly billing at activation.
Planning tools available to exploreA shared playbook and a job record the whole crew can follow.
Monthly billing at activation.
Crew pilot requests openOwner job records are live. Individual crew accounts and seat provisioning are in development.
More people, more moving parts, one operating picture.
Monthly billing at activation.
Multi-crew rollout requests openTeam permissions and multi-crew tools are in development.
Prices in USD. Annual billing saves the equivalent of two monthly payments. Applicable taxes may be additional. Access, scope and launch timing are confirmed before paid activation. No payment is collected on this page.
Four automatic feeds, response planning, state-rule reviews, private job files, original photos and ZIP packages.
Individual team logins, role permissions, multi-crew assignments and paid subscription provisioning.
See what the live workspace does, how the crew release is taking shape, and what belongs in your team’s review.
Tell us about your operation ↘The workspace combines NWS alerts, NOAA Local Storm Reports, SPC reports and OpenFEMA declaration records with source health, mapped review, road planning and deployment calculations. Operations adds private job files, required stages, uploads, captions, actual equipment intervals and ZIP export. Server monitoring runs on a schedule and creates in-app review alerts. Separate crew logins and ad-platform activation are still pending.
The operations workspace keeps server-saved customer/address records and original files together. Six required stages lead from intake through actual submission records; missing required items block progression. Structure contact, access obstruction and other property conditions have different scene-record prompts. Owner records are private, and each public demo session is isolated. Individual crew accounts are the next release.
Weather alerts and storm reports alone cannot establish damage at a particular home. A report point may describe a broad location or an observation away from the property. A confirmed job address, customer-supplied information, photos and field verification are needed to build a reliable property-level record. STORMinator treats the weather signal as a starting point for review.
The current weather view focuses on Georgia, Alabama, Mississippi, Illinois, Indiana, Ohio and Arkansas. These are monitoring priorities. Being visible on the map does not establish that an operation is licensed, authorized to advertise or cleared to use a contract in that state. Wider coverage can be discussed during access planning.
Yes. In the job workspace, the scene record asks for structure-contact details, access/entry-and-exit observations or failed-tree/property details according to the recorded condition. Shared requirements include the site record, factual captions, approved terms and actual work. The shorter walkthrough on this page lets you try the checklist interaction.
No. The platform is for organizing information and operational decisions. It does not classify a claim, guarantee coverage, determine payment responsibility or replace an insurer’s review. Advertising language, customer terms, any service charges and contracts need to match the rules and approvals that apply to your operation.
The live calculator accepts equipment quantities, work hours, daytime rates, after-hours choices, fixed charges and surcharge decisions. The public demo uses rates you enter. The existing owner workspace keeps its source rate card behind separate access. Estimated work billing is revenue; actual fuel, labor, lodging and operating costs need to be entered separately to assess the response.
They use a road route plus the prep, stop, buffer and delay inputs in your plan. The destination timezone is looked up by location when available. The current road engine estimates car travel and does not account for all commercial-truck restrictions, live closures or traffic. Your team must confirm the truck route, driver hours, permits, address and actual availability.
The current workspace can prepare a campaign brief and record planning approvals, en-route status and arrival in the browser. It does not spend an ad budget, send outreach, contact property owners or physically dispatch trucks. Those actions remain with your authorized team and connected operating systems.
Quick planning-board notes remain in the browser. Operations job files, captions, equipment intervals and activity records are stored privately on the server. Original uploads retain their bytes and metadata, with a SHA-256 checksum. The owner workspace is separated from public demo sessions. Public-demo files are disposable and retained for 24 hours; use test information there. Export a job ZIP for a portable package.
Monthly launch pricing is $199 for Scout, $349 for Crew and $599 for Command. Yearly pricing is $1,990, $3,490 and $5,990 respectively, paid as one annual amount after activation. That saves the equivalent of two monthly payments. Package access, timing and applicable terms will be confirmed before payment. Selecting a plan here submits an access request, not a paid subscription.
The aim is to make storm-response decisions and field documentation easier to follow alongside your existing operation. The live workspace exports JSON plans and job ZIP packages with original files. CRM synchronization, accounting connections, insurer-portal delivery and custom integrations are not currently connected. Tell us what your team uses so the crew rollout can be scoped around the work that matters.
The research framework covers 50 states plus DC and 13 review categories. Initial official-source research focuses on the priority states and Iowa. Categories without completed research remain pending. Source content is checked on a schedule; changes, unavailable sources, new storm signals and entered job targets can create review alerts. A source change is a prompt to review, not proof that a law changed. Written scope, source references and current reviewer records are required before a state review can clear in the workspace. The software does not promise exhaustive legal coverage.
The source registry lists 16 provider groups and clearly separates automatic, manual and unconfigured sources. Four automatic feeds are currently connected. DOT APIs, CAD, scanners, utilities and other networks depend on provider access, geographic coverage and commercial usage rights. Reports retain their actual precision; broad warning areas and rounded report points are not confirmed home addresses. NWS and SPC reports may repeat the same observation.
Bring your required steps, your equipment list and the way your team actually works. Let’s shape a STORMinator setup around your operation.