Secure sign-in
Customers sign in with a one-time link, and owners and property managers add a second check.
SIZ Group builds a customer portal for beekeeping companies, where homeowners and orchard owners sign in to see visit history, inspection reports, shared documents and the live status of each request.
A colony inspection produces a visit note, a few photos of the brood frames and a recommendation about feeding or a second box. That information usually lives on a clipboard, in a text thread or in the crew lead's phone. The customer then calls the office a few days later to ask what was found, and the office has to dig for it. A customer document sharing setup would have answered that question before the call was made.
Documents break down the same way. A signed pollination contract, a treatment record and an invoice each travel by a different route, so an orchard owner ends up with three emails and no single place to look. Each missing record turns into a call, and each call takes the office away from booking the next visit.
A property manager with six buildings will judge a beekeeper on follow-up, not on the first visit. They ask whether one login shows every site, whether the inspection report arrives the same day and whether an invoice can be paid without a phone call. A portal answers all three before the first conversation.
A homeowner who had a swarm removed last spring may only return in the next swarm season. The portal keeps that hive service history ready, so the crew can see the old cutout location and the customer does not have to explain it again.
The operations manager needs to see the portal working with real records, not a mock-up. Load a sample customer with two sites, three visits and a pollination contract, then check that each person sees only what their role allows. Removing a staff login should cut off access at once.
The record trail matters too. Every shared document and status change should show who made it and when, so a disputed visit can be traced without searching inboxes. Confirm that reports can be exported as PDF for the accounts team. Ask for a test export with a real invoice and compare the totals line by line.
Customers sign in with a one-time link, and owners and property managers add a second check.
Each visit shows the date, the crew lead, the findings and the photos taken on site.
Contracts, inspection reports and invoices sit in one place, with a record of each time they were opened.
A request moves from received to scheduled to crew on site to complete, and the customer sees each change.
A property manager sees every building under one login and can switch between sites without a new account.
The first release should cover sign-in, visit history, document sharing and request status. Those four areas remove most of the status calls. Sign-in uses a one-time link sent to the customer's email, which gives a secure client login without a password to forget, with two-factor checks for owner and property manager accounts.
Later phases can add a pollination calendar with bloom dates, colony health charts across seasons and a mobile app shell. Build them after the first customers log in regularly, so the team knows which screens are used.
Test sign-in and the invitation link on the phones your crew actually carries, since a link that opens badly on a small screen gets abandoned.
Most beekeeping businesses keep jobs and invoices in field service software such as Jobber or Housecall Pro, and they often use QuickBooks for accounts. The portal should read visit and invoice records from those systems, so the office does not type each record twice.
Where the company keeps records in a spreadsheet or a shared drive, the portal can link to the file instead of copying it. Confirm the source of truth on the scoping call, since two copies of an inspection report will eventually disagree.
Decide early which system owns invoices, so the portal shows the same balance the accounts team sees. A mismatch in the first days of use will cost more trust than any missing screen.
Beekeeping work peaks in spring, when swarm calls and splits flood the office, and again at the summer honey harvest. Late summer brings feeding and mite checks, and the winter prep visits are quiet but important. The portal should show the next visit clearly at each point in that cycle.
During a swarm surge, service request tracking becomes the most used page, so statuses must update quickly and read clearly on a phone. Quiet winters are the right time to review which documents customers opened and remove any that nobody uses. Winter prep visits are booked through the portal too, so a homeowner can confirm the date in the same place they read last spring's report.
Yes. One login can hold many sites, and each site keeps its own visit history and documents. Access can be limited so a building manager sees only the properties they look after.
Data is stored on secure hosting with access limited by role, and sign-in uses one-time links. Documents are served through the portal rather than public file links. Retention and deletion rules are agreed during the scoping call.
They will if the first visit is easy. The crew lead can send the invitation at the end of the visit, and the link opens on a phone without a password to remember. Customers who never log in still receive the same documents by email.
The office removes that person's login from the admin screen, and access stops immediately. Documents they shared stay on record with their name and date, so the trail remains intact for the operations team.
Book a free scoping call and we will map your customer records, documents and sign-in rules for your business.