Your first 15 minutes in RoofCRM

Sign up, then finish three things: your company profile, your first account, and a loaded storm. RoofCRM shows this as a checklist, and the checklist is not decorative — each step is checked against your real data every time you open the app, so it disappears only when the work is genuinely done. Here is what each step actually requires.

Step 1: Set up your company profile

Go to Settings. The profile step is complete when these are all filled in:

• Company name
• Contact name
• Contact phone
• Either a default price per square or a service metro — one of the two is enough

The price per square is used when building estimates; the service metro tells the app where you work. Fill in whichever fits how you price and where you knock.

Step 2: Add your first account

From Accounts, use /accounts?add=1 (or the add button) to create your first account. One real account is all the checklist asks for — an address, a name, a phone number. It can be a lead you have been meaning to call or a past customer you want in the system. Once at least one account exists, this step checks off.

Step 3: Load a storm

Open Storm and load a storm for your area — pick a hail swath from the map and import addresses from it, or save a storm watch for your market. The checklist counts a storm as loaded when you have either imported leads from a swath or set up a storm watch. This is the step that makes the rest of the product useful: storm history starts attaching to your accounts, and your canvass routes start from where hail actually fell.

Step 4: Install the app on your phone

The last checklist item asks you to install RoofCRM on your phone as a PWA. This one works differently: the server never reports it done, because only your device knows whether the app is truly installed. Once you install it from your phone's browser, the checklist clears the step locally.

What the checklist does not do

It does not nag, email you, or count demo data. Every flag is computed live from your company's actual records on every request — nothing is stored, so there is no state to drift. If you delete everything, the checklist comes back. That is the honest behavior.

Questions

Do I have to do the steps in order?

No. They are independent — you can load a storm before adding an account. The order above is just the fastest path to a useful app.

Why does the profile need a price per square or a metro?

Because those are what the estimate builder and territory features actually use. The checklist accepts either one so you are not blocked before you have settled on pricing.