What it does
Measure a roof from the aerial and build the scope right beside it.
Next: Confirm the quantities in the field before pricing the job.Limits: Remote measurements still require scope confirmation and field verification.Every capability, and where it stops
Features
36 capabilities across 5 groups. Each card says when to use it, what it does, what happens next, and the limits we have not solved yet.
Win and connect the work
When to use it
Customer portal
Customers need progress without gaining access to internal operating records.
What it does
Give each customer one private, job-specific place to review the work shared with them.
Next: Keep the customer record and shared job information current.Limits: A passcode proves control of the email address on file, not the identity of the person holding it.
What it does
Email customers and keep every saved message with the connected job.
Next: Record the decision or customer reply on the job.Limits: A sent status means provider acceptance, not recipient delivery, inbox placement, or reading.When to use it
Customer records
Contacts, properties, conversations, and project history live in different tools.
What it does
Keep every customer's contacts, sites, jobs, messages, and files in one place.
Next: Start or reopen the customer's connected job.Limits: Customer visibility follows organization and role permissions.
When to use it
Job templates
Repeatable job scope becomes inconsistent when every record starts from scratch.
What it does
Start every job from the contractor's own repeatable scope and defaults.
Next: Review the copied scope against the actual property.Limits: A template starts a record; it does not price or approve the job by itself.
What it does
Catch each lead, qualify it, and carry it into a connected customer job without retyping.
Next: Convert qualified work into an estimate or job.Limits: An estimator figure is a planning number, not a quoted price or signed contract.
When to use it
Materials catalog
Scope and price become inconsistent when material items are recreated for every proposal.
What it does
Price jobs from the contractor's own catalog of materials, services, and costs.
Next: Confirm cost and availability before sending the proposal.Limits: Catalog records do not place orders or promise supplier availability.
When to use it
Proposals and e-sign
Scope, pricing, terms, and customer activity are hard to reconcile after sending.
What it does
Send a priced proposal and retain the signing event with the connected job.
Next: Turn accepted scope into permit-ready work.Limits: A completed signature records the signing event and is not legal advice about enforceability.
When to use it
Restoration workspace
Damage evidence, carrier activity, repair scope, and roofing work easily fragment.
What it does
Build and document restoration scope on the same job used for field and permit work.
Next: Connect approved scope back to production.Limits: Claim decisions, policy interpretation, and field verification remain outside the software.
Move the job through the field
When to use it
Deadline calendar
A calendar alone does not explain which job owns a consequential date.
What it does
See appointments, inspections, crew starts, and deadlines with their job context.
Next: Open the affected job before changing the handoff.Limits: A date reflects the saved record and source entered; it does not confirm a jurisdiction's calendar.
When to use it
Equipment
Tools and vehicles become unavailable when assignment and service timing are hidden.
What it does
Know what is owned or rented, where it is, and which job or member has it.
Next: Assign the right field asset to scheduled work.Limits: Condition and service dates are team records; the software does not inspect equipment.
Controlled rolloutWhen to use it
Field app
The office record is out of reach when the work happens on a roof with a phone and a weak signal.
What it does
Carry Today, jobs, permits, photos, and the rest of the dashboard on an iPhone that keeps working offline.
Next: Queue photos and field updates against the job and let them sync when signal returns.Limits: Rolling out through TestFlight. Offline sections say when they are stale, and billing and payroll stay off the phone on purpose.
When to use it
Job pipeline
Office and field teams need one reliable source for scope, ownership, and progress.
What it does
Move every job through selling, preconstruction, production, and closeout with its permit and money attached.
Next: Complete the next recorded handoff on the job.Limits: A stage reflects what the team recorded; it does not verify field progress or release payment.
When to use it
Permit review estimate
Permit review timing becomes risky when the expected track is separated from the permit.
What it does
Store the review track on the permit and surface when the estimate is approaching or exceeded.
Next: Confirm the authority status before acting on the estimate.Limits: The clock is an operating estimate based on saved facts, not a county guarantee or live portal status.When to use it
Permit and inspection hub
Permit status becomes risky when authority details, evidence, inspections, and timing are separated.
What it does
Keep each permit, inspection, document, reviewer detail, and next action with the job.
Next: Schedule field work around verified permit readiness.Limits: FL Permit Pay does not file with a county or guarantee a government outcome.
When to use it
Storm job radius
Storm response needs geographic job context without confusing planning areas for weather facts.
What it does
See which open jobs fall inside a contractor-defined storm work area.
Next: Open each affected job before assigning field work.Limits: The radius is planning context, not radar, a forecast, or emergency guidance.
When to use it
Reported hail and wind
Weather reports are easily overread as proof of damage at a customer property.
What it does
Review public NOAA hail and wind observations near saved job addresses.
Next: Inspect the property before describing damage or claim relevance.Limits: Public NOAA observations do not state that a roof is damaged, that a claim exists, or what happened at a property.
Keep proof retrievable
When to use it
Document repository
Proof is difficult to retrieve when files are stored by device or inbox.
What it does
Find job and compliance files where the related operating record expects them.
Next: Use the evidence for review, inspection, claim, or closeout.Limits: A list entry does not imply a private file is available to every visitor.When to use it
Field photos
Field evidence loses value when nobody can tell which job or visit it belongs to.
What it does
Keep dated field photos attached to the job and activity that produced them.
Next: Use the photo with its job context during review or closeout.Limits: A filed photo is not an inspection finding and carries no implied device location.
When to use it
License verification
Stored credential details can drift from the latest reference data available to the team.
What it does
Compare stored licenses with a dated DBPR snapshot and review any difference.
Next: Correct the stored credential or verify against the official source.Limits: The comparison is not real time or an official DBPR record.
When to use it
Lien deadline worksheet
Candidate Florida lien dates are hard to review when the underlying job facts are scattered.
What it does
Work through candidate Florida lien dates using the job's recorded facts.
Next: Review every source fact with current sources and qualified counsel.Limits: Candidate dates require current-source and qualified-counsel review.
When to use it
Compliance Passport
Credential proof is difficult to share cleanly without exposing internal notes or unrelated files.
What it does
Build a redacted preview of selected credentials for a customer or partner.
Next: Confirm current status with the official authority before relying on it.Limits: Recipients must confirm current license status with Florida DBPR.
When to use it
County mail intake
Municipal email becomes disconnected from the permit record that needs it.
What it does
Route forwarded county mail to the permit record that matches its saved references.
Next: Review the message before changing permit status or next action.Limits: FL Permit Pay does not log into a county portal and never changes permit status from an email.
When to use it
Compliance Vault
Licenses and insurance proof lapse when renewal dates and documents live apart.
What it does
Track credentials, proof, expiration dates, and configurable renewal reminders together.
Next: Upload renewed proof and verify current authority status.Limits: Reminder windows are configurable planning aids, not statutory deadlines.
Follow money and workforce
When to use it
Commission reports
Commission totals are hard to trust without the jobs that produced them.
What it does
See what each representative has earned, job by job and period by period.
Next: Open the underlying commission record before approving it.Limits: Reports describe saved commission records and do not issue payroll.
When to use it
Commission simulator
A new compensation rule can create unexpected payouts across different job values.
What it does
Try commission plans against sample work before committing to a rule.
Next: Review the result, then configure an approved commission rule.Limits: Simulator values stay in browser scratch state and are not saved to company records, payroll, or payouts.
When to use it
Commission ledger
Representatives and owners need one traceable record of what is owed and why.
What it does
Track what each representative is owed, tied to the work that earned it.
Next: Review the connected job and approval state.Limits: A commission record is not proof that wages or funds were paid.
When to use it
Pay applications
Completed work and collection timing drift apart without a shared progress record.
What it does
Bill for recorded progress and follow application amount, retainage, approval, and payment state.
Next: Move approved value toward collection and reporting.Limits: A prepared or sent pay application is not evidence of collected funds.
When to use it
Certified payroll
Crew time needs job, classification, photo, and approval context before certification.
What it does
Turn reviewed crew time into a WH-347 draft that remains tied to the job.
Next: Have the employer review the draft before certification or filing.Limits: Draft calculations require employer review before certification or filing.
When to use it
Sales commissions
Commission rules are hard to audit when they are separated from the sale and approval.
What it does
Set commission rules and trace the resulting record from sale to approval.
Next: Keep commission approval separate from payroll payment.Limits: Commission approval and payroll payment remain distinct events.
Run the company
What it does
Ask what needs your attention today and get a straight answer with its source records.
Next: Open the cited workspace before recording a decision.Limits: Answers depend on available permitted records; proposed actions require explicit confirmation and fresh authorization.
When to use it
Workflow automation
Repeatable follow-up fails when nobody owns it and nobody sees the result.
What it does
Run reviewable follow-up from recorded events without hiding what happened.
Next: Inspect run history and pause rules that need attention.Limits: A rule fires on recorded events only; it cannot chase a supplier or customer who never replies.
When to use it
Integrations
Adoption stalls when teams must abandon or retype the book of business they already have.
What it does
Bring in existing records and connect supported accounting and operating handoffs.
Next: Review imported or exported records before relying on them.Limits: Imports and accounting export are supported; supplier-system ordering is not implied.
When to use it
Job costing reports
Margin problems remain hidden when costs and production progress are reviewed apart.
What it does
Find where job margin moved while there is still time to open the source records.
Next: Open the job, cost, or payment record behind the result.Limits: Every figure is only as complete as the costs entered against the job; this is not a forecast.When to use it
Operating ledger
The operating day becomes scattered across permits, schedules, jobs, and collections.
What it does
See the decisions that need attention across the company in one connected view.
Next: Open the source record that needs a decision next.Limits: The queue reflects available records, supported rules, source health, and configured access.
When to use it
Team messages
Crew coordination scatters across personal phones, where the job it is about cannot be seen.
What it does
Read and reply to your own crew's threads next to the work, with unread state you can trust.
Next: Record the decision on the job record it belongs to.Limits: Internal crew messaging only. It never reaches a customer, and a message is delivered inside FL Permit Pay rather than to a phone or an inbox.See the system working together
See plans and pricing