Own the workflow before you add another subscription
Most businesses will continue to use subscription software. The advantage comes from owning the workflow, process decisions, data standards, integrations, and management practices around those systems.
Talk through an operating problemWhen the software stack becomes the problem
Most project-driven businesses already use several platforms. The pain is what happens between the logins.
SaaS sprawl
Estimating tool, project management tool, accounting, file storage, scheduling, communication. Each one is a monthly subscription. Each one has its own login.
Duplicate data entry
The same project information gets keyed into Excel, then again into Procore, then again into the abstract sheet. Estimators are paid to win bids, not to retype numbers.
Disconnected estimating
Takeoff lives in one tool. Pricing lives in Excel. Sub bids live in email threads. Nobody can see the full picture until someone manually rebuilds it.
Excel still runs the business
The spreadsheet that everyone says they want to retire is the one that actually holds the real logic. Killing it isn't the goal. Making it work with the rest of the stack is.
Status by phone call
Managers chase project updates manually because there's no clean handoff between the field, the office, and accounting. Everyone is busy and nothing is connected.
Subscription Cost Without Workflow Fit
Software costs increase over time, but the larger concern is paying for platforms the team uses inconsistently or surrounds with manual workarounds.
What you subscribe to vs. what you should own
Subscription software is normal and usually the right call. The question is what stays yours regardless of which vendor you use.
Reasonable to subscribe to
- Accounting, project management, estimating, and field platforms
- Hosting, security, and platform maintenance
- Feature development and vendor support
- Standard functionality most businesses need
- Upgrades you do not want to build or maintain
- Tools your team already knows how to use
Worth owning yourself
- The workflow and how work actually moves
- Process decisions and who owns each step
- Data definitions and reporting standards
- Intentional integrations between systems
- Business knowledge held outside one person or vendor
- Integration or custom automation only where a real operating gap remains
What workflow ownership looks like in commercial construction
These examples show how clearer ownership and intentional system handoffs can improve a commercial-construction workflow.
Takeoff → bid abstract
Quantities from the drawings flow into the abstract sheet without an estimator manually retyping line items.
Subcontractor proposal intake
Sub bids land in a single place, get normalized to the same line-item format, and surface the apples-to-apples comparison estimators usually do by hand.
Estimate review
Before-submission review moves from "let's pull a senior estimator off another job for two hours" to a structured checklist with review criteria the workflow applies consistently.
Bid follow-up
Status doesn't live in someone's head. Follow-ups, status changes, and win/loss reasons get captured the day they happen, not three weeks later.
Project → admin handoff
Once a bid wins, the data behind it moves into the admin and accounting workflow without the project manager rebuilding it from scratch.
Historical data that compounds
Every job feeds back unit costs, productivity rates, and lessons into a library your next bid actually uses. The data stops being decorative.
Why BMG
Operator-led and Phoenix-based, focused on how the work actually runs.
Examples below are from Brad Berlin's operating career, not BMG client outcomes.
20+ years in operations
Brad Berlin brings 20+ years of operations leadership to workflow, systems, and implementation decisions. He has experienced the spreadsheet-as-operating-system problem from inside growing businesses.
26 new connections in under nine months.
At project44, Brad launched 26 new LTL API connections in under nine months across an ecosystem of more than 350 integrations, coordinating across partner technical teams and internal development.
Phoenix-based
On-site Valley work when it helps. Your office, your team, your tools.
Practical and operator-led
Clear ownership, useful workflows, and technology that supports the operation rather than driving it. Every recommendation must make sense to the people responsible for executing the work.
Where to start
Review the workflow creating the most friction, clarify what is breaking down, and identify a practical next step.