How Solaris Management Group Scaled with Notion

Client

Solaris Management Group

Industry

Construction

Team size

7 People

Delivery time

4 Days

Headline results

2–3 hours saved

per team member, per day, by replacing tool-hopping with a single source of truth.

1–2 → multiple projects

Now confidently scaling beyond the previous ceiling of 1–2 simultaneous projects.

40 minutes/day → seconds

Manual daily logs replaced with a mobile form sub-contractors actually want to use.

The challenge

Solaris Management Group is a construction management firm that operates as a consultant for homeowners associations, embedded inside the HOA team rather than acting as an outside contractor. With a small team running multiple high-value sites, Hollybrook Golf & Tennis and Ocean Colony among them, Jonny Jeune had ambitious plans to grow the business. But the operational reality was working against him.

The day-to-day was running on a patchwork of disconnected tools:

  • Basic to-do lists for personal task tracking
  • Excel spreadsheets for budgets, permits, vendors, and homeowner issues
  • Contractor’s Foreman for daily logs and formal reporting
  • Email for meeting minutes and homeowner issue intake
  • Paper sign-ins collected by gate security each morning at the job site

 

The symptoms were exactly what you would expect from a fragmented stack:

Daily logs alone were eating roughly 40 minutes a day of Jonny’s time. Homeowner issues lived only in an email-based “issues log,” vulnerable to being buried in someone’s inbox. And every team member was bouncing between platforms and notebooks just to figure out the status of basic work.

The deeper risk was strategic. As Jonny put it:

Our biggest risk with sticking to the old way of doing things is that we would have critical tasks that would simply not get done. Team members would feel frustrated because the many tasks were not organized in one single place.

The ceiling was visible. To scale to 3–4 simultaneous projects, the operating system had to change.

The solution: Solaris Management Hub

Over two working sessions and a focused build phase, Solaris went from fragmented tools to a single operating system: Solaris Management Hub.

The architecture is built around 11 interconnected databases that mirror how the business actually runs:

Project execution

  • Projects: top-level container for every engagement
  • Buildings: 65+ buildings pre-populated for Hollybrook, related to projects
  • Tasks: replacing fragile to-do lists with a real, scalable task database
  • Daily Logs: fed by a mobile form, not manual entry

 

Stakeholders & operations

  • Vendors: imported from existing spreadsheets, related to projects
  • Team Members: accountability layer for current and future hires
  • Opportunity Log: homeowner issue tracking, replacing the email-based issues log
  • Site Form: mobile-first daily reporting for sub-contractors

Solaris Hub Buildings database

Knowledge & finance

  • Budgets: connected to projects, importable from Excel
  • Documentation / Permits: typed by category (electrical, plumbing, structural) with vendor relations
  • Meeting Minutes: central repository, no longer trapped in email threads

 

The experience layer

  • Custom homepage replacing Notion’s default
  • Guest access for vendors and contractors
  • Automations for daily-log notifications and follow-ups
  • Zapier path to keep Contractor’s Foreman in the loop for legal and formal reporting

How it changes daily reality

  • The 40-minute daily log is gone. Sub-contractors fill out a simple mobile form from the field. The system writes the entry. Jonny no longer types it.
  • Paper sign-ins are gone. No more gate security collecting handwritten sheets to be re-entered later.
  • Homeowner issues have a home. The Opportunity Log replaces the email-based issues log; nothing slips through the cracks.
  • Information is one click away. Vendors, permits, buildings, tasks, and budgets are all relationally connected, so a question like “which vendor has the electrical permit for unit 12B?” takes seconds.

Site daily log on phone

How we worked together

The build was deliberately collaborative, not a black-box delivery. Jonny and I reviewed database properties together using Notion comments, choosing what to keep, remove, and add before a single relation was wired up.

  • Session 1: Discovery. Mapping the business, the tools, the pain points, and the growth goals.
  • Session 2: Architecture. Choosing the comprehensive Version 2 system over a minimal MVP, defining database properties collaboratively.
  • Build phase. All 11 databases created, relations wired, spreadsheets imported, 65+ buildings pre-populated, mobile site form configured, custom homepage delivered.

The client’s verdict on the experience:

Working with David continues to be a great experience. I work with several other software platforms, and the difference with David's approach in working with his client is to be available to provide quick solutions. My business is a need-to-get-things-done-now type of business. That means our clients can not wait for several days before getting answers to issues. We deal with un-expectancies on a daily basis. David provides the right, exact solutions to address the critical issues, quickly.

The results

The Solaris Management Hub has been running long enough for the effects to show up in three places: the hours in the day, the ceiling on the business, and the way the team feels about its own work.

⏱️ Hours back, every day

The first thing to disappear was the tool-hopping, the constant switching between spreadsheets, notebooks, reporting software, and email just to establish what was happening on site.

 

I believe each team member saves between 2 to 3 hours when we use the Notion platform to streamline all our company info. No more jumping from several different platforms and notebooks.

Across a small team, that’s the equivalent of unlocking a part-time hire’s worth of capacity, every single day, without adding a single person to payroll.

📱 Reporting that happens where the work happens

Much of that time came from one place: the daily log. Pushing it out to a mobile form meant the people closest to the work could report it themselves, and the previous platform’s friction stopped being Jonny’s problem to absorb.

Our sub-contractors are finding this form pretty easy to use. We were forcing contractors and associates to use another platform that had too many steps and was just frustrating to do each day.

What used to be 40 minutes of manual entry for Jonny is now seconds of self-reporting from a phone in the field and the paper sign-ins at the gate are gone entirely.

📈 A ceiling that moved

Time saved matters, but the strategic result is bigger. The old stack physically limited how much work Solaris could take on, because organizing a third or fourth project simply wasn’t possible by hand.

With Notion, I feel very confident in scaling up. I was only able to do 1–2 projects at a time because there was no way I could organize more work using my old systems. Because I now have Notion, I can manage several projects.

The constraint on growth was never demand or expertise. It was operational capacity and that’s the part the system removed.

🪶 Adoption without a fight

None of it would have mattered if the team had quietly gone back to their notebooks. Designing for the simplest possible experience is what made the rollout stick.

Because Notion is easy to use, there was no resistance whatsoever.

That frictionless adoption is what turns a system into a habit, and a habit into a standard the HOA clients can see.

Asked to summarize the change in his team’s performance, Jonny needed four words:

The improvement to our team's performance can be summed up in 4 words: Efficiency, efficiency, efficiency and Accountability!

Key takeaways

  1. Meet the team where they are. The Solaris team self-described as “very simple people” who wanted things at a kindergarten level. The system was designed for that and adoption was frictionless.
  2. Start with a comprehensive architecture, not a minimal MVP. Choosing Version 2 over a stripped-down build paid off the moment the team needed to connect vendors to permits, or buildings to tasks, without retrofitting.
  3. Pre-populate before you launch. Importing 65+ buildings on day one meant the team saw the system as theirs immediately, not a blank shell to fill out later.
  4. Design for the field. Construction is a mobile-first business. Anything that requires a laptop and a desk is friction.
  5. Keep formal tools for formal jobs. Contractor’s Foreman still handles legal documents and formal reporting; Notion handles the operating layer. Don’t try to replace what’s working, connect to it.

Are you running a construction management or HOA consulting business on a patchwork of tools?

If you’re spending hours every day on tasks a connected system could absorb, let’s talk.

More Case Studies

Let's See If We're a Fit

No pitch deck. No obligation. 30 minutes to understand your business and tell you honestly what I think, including if I’m not the right fit.

Built for the businesses that build everything else.

Join Our Newsletter

No product pitches. No padding. One weekly read for serious operators.

© 2026 NotioStore. All Rights Reserved.

Share this:

Like this:

Like Loading…

Discover more from Notiostore

Subscribe now to keep reading and get access to the full archive.

Continue reading