Most solar companies don’t lose time on the big stuff. It’s the small things. Someone can’t find the roof drawing. The permit reply went to an inbox nobody’s checking this week. Two people send the same customer two different quotes.
I’ve seen this happen at companies with six staff and at companies with sixty. The fix usually isn’t a new piece of expensive software. It’s getting everyone onto one shared system, which is where a Google Workspace migration comes in. Below is what I’d do if I were setting it up for a solar crew tomorrow.
Follow a single rooftop job from start to finish. Sales speaks to the homeowner. A designer draws the layout. Someone orders the panels and inverter. An installer turns up with a drill and a phone. That’s four or five people, and each one probably keeps their own files.
Google Workspace for teams puts email, calendar, docs, sheets, video calls and storage under one login. Nothing clever about it. The value is that when someone opens the roof layout, it’s the real one, the current one.
Don’t flip the switch on a Monday morning and hope. That’s the most common mistake, and it gets ugly fast.
The Google Workspace setup itself takes a day or two. Deciding how you want everything organised takes longer, so talk that through first.
When you do the Google Workspace email setup, connect your company domain before anything else. After that, create shared addresses such as sales@, projects@ and support@. Say a customer emails about an inspection date and the only person reading that inbox is on leave. That’s a lost job waiting to happen. A shared address means anyone on the team can answer.
Turn on two-step verification for everyone right away. Five minutes each. Do it now, not after somebody’s account gets hacked.
Good Google Workspace file sharing mostly comes down to discipline. Use Shared Drives rather than personal ones. If a file sits in someone’s personal drive and they quit, you’ve lost it. One folder per project, then subfolders for survey photos, designs, permits, quotes and handover papers.
File names matter more than people think. “RoofLayout_Mehta_v2” tells you something. “final_new_FINAL(2).pdf” tells you nothing, and we’ve all made that file. Customers and subcontractors get view-only access. Edit rights stay with your own staff.
And get installers using the mobile app. A site photo should go straight into the project folder, not sit in a phone gallery for three weeks.
Maybe you don’t need a project tool yet. Google Workspace project management can run on one shared Sheet: status, permit date, equipment ordered, crew assigned, expected finish date. Plain, yes. But everyone can read it without training.
Put crew schedules in Calendar. Open a Chat space for each live job, so you aren’t scrolling through fourteen “Re: Re: Re:” emails to find one answer. For tiny reminders, like asking the homeowner where the meter is, Google Tasks is enough.
There are loads of Google Workspace productivity tools, and most teams use maybe a third of them. For solar, these earn their place:
Take one afternoon to build templates. A standard proposal and a standard inspection form mean every job starts from the same place, and new hires pick things up quicker.
Google Workspace automation sounds like a developer job. It isn’t, at least not the useful bits. Link a Google Form to a Sheet and every new site inspection appears in your tracker without anyone retyping it. Set up email filters so permit updates, supplier invoices and customer enquiries land in separate labels. Add a notification in Sheets so the right person knows when a job’s status changes.
Apps Script can come later, for things like generating quotes or sending reminders. But start with one or two automations you trust. If you build ten and half of them break, your team will stop believing in all of them.
Google Workspace for small business works well for young installers because you pay per user. Begin with five people and add seats when you hire. There’s no server in a cupboard to worry about, and updates happen in the background.
Every few months, check who has access to what. Remove accounts for people who’ve left, look at folder permissions, update your templates. Dull work, I know. But skip it for a year and you’re back to the mess you started with.
A Google Workspace migration isn’t really about moving emails from one place to another. It’s about giving your team one dependable spot to work from, whether they’re in the office or standing on a roof.
Plan before you move. Keep folders simple. Set up email properly. Add automation only where it genuinely saves effort, and give slower adopters a bit of patience. After a month or so, you’ll likely see fewer lost files and fewer “did anyone get my email?” messages.
For 5 to 20 people, usually one to three weeks. Planning and the pilot stage often take longer than moving the data.
Yes. Gmail, Drive, Docs, Sheets, Calendar and Meet all have mobile apps. Crews can upload photos, check schedules and fill in forms on site.
It has strong built-in protection, including two-step verification and admin controls. Habits still count, so use strong passwords and remove access quickly when someone leaves.
Not always. Many small teams manage fine with Sheets, Calendar and Chat. If projects get more complex, add a dedicated tool later.
It depends on storage and features. Most small teams start with a basic or standard plan and upgrade as they grow. Check Google’s website for current pricing.
