A lot of growing businesses do not have a sales problem, a service problem, or an employee effort problem.
They have a waiting problem.
A quote waits for one missing detail. A customer onboarding waits for paperwork. A renewal waits for approval. A job waits for scheduling. A service issue waits for someone to notice it moved from "received" to "needs a decision."
Everybody is busy. The CRM says the record exists. The spreadsheet has a row. The inbox has the thread. But nobody can quickly answer the question that matters:
Where is the work stuck, and how long has it been there?
The Hidden Cost of Unseen Bottlenecks
That is why a small HubSpot update from May is worth paying attention to, even if your business does not use HubSpot.
HubSpot expanded stage calculated properties for custom objects, which means teams can track how long records spend in each stage of a pipeline, not just for standard sales deals or support tickets, but for custom business records too. Their May developer notes also point to more control over which pipelines and stages generate those properties, so teams can avoid filling the system with hundreds of measurements nobody uses.
That sounds technical. The business lesson is not.
The lesson is this: if an important piece of work moves through stages, your team should be able to see the wait.
Not just the final outcome. Not just who owns it. Not just whether it is open or closed. The wait.
Because the wait is where time gets lost.
When Workflows Outgrow Your Tools
For a growing business, the most painful workflows often do not fit cleanly into standard software categories. They are not always "deals." They are not always "tickets." They are not always "projects." They might be:
- estimate requests
- customer onboarding packets
- installation jobs
- warranty claims
- change orders
- vendor approvals
- renewal reviews
- compliance documents
- equipment requests
- internal service handoffs
When those workflows are forced into the wrong tool, the team usually compensates with manual updates, side spreadsheets, Teams messages, and hallway memory. That works until the business grows. Then the same duct tape that used to feel flexible starts hiding the bottleneck.
This is where stage tracking matters.
If you can see that estimates spend two days in review, but six days waiting for customer information, you know where to fix the workflow. If onboarding stalls after the welcome email but before document collection, you know the handoff is weak. If service jobs sit in "ready to schedule" longer than they sit in actual field work, you do not need another dashboard. You need a better scheduling flow.
Start With the Bottleneck
The tool is not the point. The shape of the work is the point.
That is a very FlowDevs way to look at it. Start with the bottleneck, not the software.
Sometimes the right fix is a better-configured CRM. Sometimes it is a Microsoft-first workflow using SharePoint, Teams, Power Automate, and Dataverse. Sometimes it is a simple internal tool that gives the team one clean place to move work forward. Sometimes it is a customer portal or website intake flow so the right information arrives before your staff has to chase it.
And sometimes the right answer is to stop adding apps and define the workflow properly.
Defining a Useful Workflow
A useful workflow has a few plain-English answers:
- What is the thing being moved through the business?
- What stages does it actually pass through?
- Who owns each stage?
- What information is required before it can move forward?
- What happens when it is blocked?
- Where does the customer get updated?
- Which system is the source of truth?
- Who supports the workflow after it ships?
Those questions are not glamorous. They are the work.
Visibility Must Come Before Automation
And they matter more now because every major platform is trying to add automation, agents, and AI-assisted workflow tools. HubSpot is doing it. Microsoft is doing it. Webflow, Zapier, Intuit, Salesforce, and plenty of others are doing it too.
That does not mean every business needs to run toward the newest feature.
It means the businesses that already understand their workflow will get more value from these tools. The businesses that do not will automate confusion faster.
That is the sharp edge here.
If your team cannot see where work waits today, adding an agent tomorrow will not magically fix the process. It may just move the confusion around faster and make it harder to explain.
A better next step is smaller and more useful.
Pick one workflow your team complains about every week. Not the whole business. One workflow.
Maybe it is quote follow-up. Maybe it is customer onboarding. Maybe it is service scheduling. Maybe it is collecting documents before a job can start.
Write down the real stages. Then ask how long work sits in each one. If nobody knows, that is the first fix. You need visibility before automation.
Choosing the Right Solution
From there, the software decision gets cleaner.
If the workflow belongs in HubSpot, configure it properly and report on stage movement. If Microsoft 365 is already the backbone, use the tools you already pay for and build the workflow around the actual handoffs. If the work does not fit cleanly anywhere, a custom internal tool may be cheaper and clearer than forcing another subscription into the stack.
FlowDevs is Microsoft-first, not Microsoft-only. The goal is not to worship one platform. The goal is to give the team time back without devaluing the people doing the work.
That means clear scope. Clear cost. Clear next steps. And a system somebody can support after launch.
The takeaway is simple: do not start by asking which tool can automate the workflow.
Start by asking where the work waits.
That answer will tell you what to build next.
If you need expert help uncovering where work is stuck and building systems that remove the wait, book a discovery call with FlowDevs today.
Author: Justin Trantham
Source context used for accuracy: HubSpot Knowledge Base, "Use stage calculated properties," last updated May 21, 2026; HubSpot Developer Changelog, "May 2026 Rollup," including custom-object stage calculated properties and public beta controls for stage calculated properties.
A lot of growing businesses do not have a sales problem, a service problem, or an employee effort problem.
They have a waiting problem.
A quote waits for one missing detail. A customer onboarding waits for paperwork. A renewal waits for approval. A job waits for scheduling. A service issue waits for someone to notice it moved from "received" to "needs a decision."
Everybody is busy. The CRM says the record exists. The spreadsheet has a row. The inbox has the thread. But nobody can quickly answer the question that matters:
Where is the work stuck, and how long has it been there?
The Hidden Cost of Unseen Bottlenecks
That is why a small HubSpot update from May is worth paying attention to, even if your business does not use HubSpot.
HubSpot expanded stage calculated properties for custom objects, which means teams can track how long records spend in each stage of a pipeline, not just for standard sales deals or support tickets, but for custom business records too. Their May developer notes also point to more control over which pipelines and stages generate those properties, so teams can avoid filling the system with hundreds of measurements nobody uses.
That sounds technical. The business lesson is not.
The lesson is this: if an important piece of work moves through stages, your team should be able to see the wait.
Not just the final outcome. Not just who owns it. Not just whether it is open or closed. The wait.
Because the wait is where time gets lost.
When Workflows Outgrow Your Tools
For a growing business, the most painful workflows often do not fit cleanly into standard software categories. They are not always "deals." They are not always "tickets." They are not always "projects." They might be:
- estimate requests
- customer onboarding packets
- installation jobs
- warranty claims
- change orders
- vendor approvals
- renewal reviews
- compliance documents
- equipment requests
- internal service handoffs
When those workflows are forced into the wrong tool, the team usually compensates with manual updates, side spreadsheets, Teams messages, and hallway memory. That works until the business grows. Then the same duct tape that used to feel flexible starts hiding the bottleneck.
This is where stage tracking matters.
If you can see that estimates spend two days in review, but six days waiting for customer information, you know where to fix the workflow. If onboarding stalls after the welcome email but before document collection, you know the handoff is weak. If service jobs sit in "ready to schedule" longer than they sit in actual field work, you do not need another dashboard. You need a better scheduling flow.
Start With the Bottleneck
The tool is not the point. The shape of the work is the point.
That is a very FlowDevs way to look at it. Start with the bottleneck, not the software.
Sometimes the right fix is a better-configured CRM. Sometimes it is a Microsoft-first workflow using SharePoint, Teams, Power Automate, and Dataverse. Sometimes it is a simple internal tool that gives the team one clean place to move work forward. Sometimes it is a customer portal or website intake flow so the right information arrives before your staff has to chase it.
And sometimes the right answer is to stop adding apps and define the workflow properly.
Defining a Useful Workflow
A useful workflow has a few plain-English answers:
- What is the thing being moved through the business?
- What stages does it actually pass through?
- Who owns each stage?
- What information is required before it can move forward?
- What happens when it is blocked?
- Where does the customer get updated?
- Which system is the source of truth?
- Who supports the workflow after it ships?
Those questions are not glamorous. They are the work.
Visibility Must Come Before Automation
And they matter more now because every major platform is trying to add automation, agents, and AI-assisted workflow tools. HubSpot is doing it. Microsoft is doing it. Webflow, Zapier, Intuit, Salesforce, and plenty of others are doing it too.
That does not mean every business needs to run toward the newest feature.
It means the businesses that already understand their workflow will get more value from these tools. The businesses that do not will automate confusion faster.
That is the sharp edge here.
If your team cannot see where work waits today, adding an agent tomorrow will not magically fix the process. It may just move the confusion around faster and make it harder to explain.
A better next step is smaller and more useful.
Pick one workflow your team complains about every week. Not the whole business. One workflow.
Maybe it is quote follow-up. Maybe it is customer onboarding. Maybe it is service scheduling. Maybe it is collecting documents before a job can start.
Write down the real stages. Then ask how long work sits in each one. If nobody knows, that is the first fix. You need visibility before automation.
Choosing the Right Solution
From there, the software decision gets cleaner.
If the workflow belongs in HubSpot, configure it properly and report on stage movement. If Microsoft 365 is already the backbone, use the tools you already pay for and build the workflow around the actual handoffs. If the work does not fit cleanly anywhere, a custom internal tool may be cheaper and clearer than forcing another subscription into the stack.
FlowDevs is Microsoft-first, not Microsoft-only. The goal is not to worship one platform. The goal is to give the team time back without devaluing the people doing the work.
That means clear scope. Clear cost. Clear next steps. And a system somebody can support after launch.
The takeaway is simple: do not start by asking which tool can automate the workflow.
Start by asking where the work waits.
That answer will tell you what to build next.
If you need expert help uncovering where work is stuck and building systems that remove the wait, book a discovery call with FlowDevs today.
Author: Justin Trantham
Source context used for accuracy: HubSpot Knowledge Base, "Use stage calculated properties," last updated May 21, 2026; HubSpot Developer Changelog, "May 2026 Rollup," including custom-object stage calculated properties and public beta controls for stage calculated properties.
