01
Sales follow-up
The quote is sent. Then what?
Prepare the next follow-up when no reply arrives, and stop the reminder when the conversation moves forward.
Power Automate · A dependable next step
Keep work moving. Lose the chasing.
A quote needs following up. An approval is waiting. A review is due. Turn the steps someone has to remember into workflows with clear rules—and a visible place for exceptions.
Discuss a workflowQuote follow-upThe quote. The reply. The next step.
P
Project enquiry · 1042Website redesign · quote sent
2 days- Enquiry captured
- Quote sent
- No reply after 2 days
- Prepare follow-up
Follow-up ready
Two working days have passed without a reply. The next message is ready for review.
Put it in the context of your work
Picture this in your business.
Different businesses. Familiar problems. Here are a few useful places to start.
02
People operations
The review date shouldn’t be a surprise.
Route due reviews to the right manager, with a clear fallback when a recipient or date is missing.
03
Daily operations
Tell me when the plan changes.
Compare new forecasts with the agreed baseline and flag the changes that actually need attention.
The problem
Some work only happens because somebody remembers.
A review becomes due. A forecast changes. An approval is waiting. Someone opens a spreadsheet, checks the dates and sends the same message again.
That routine is a good place to look for automation—provided the rules are clear and somebody can see when an exception needs attention.
What we can build
Useful automation starts with a dependable process.
- Scheduled reminders. Trigger the next step from dates, status changes or defined business rules.
- Approvals and routing. Send requests to the right person and keep the decision attached to the record.
- Change alerts. Compare information and notify people when an agreed threshold or condition is met.
- Connected admin. Move suitable information between Microsoft tools, databases, forms and supported services.
- Existing flow repairs. Investigate failed conditions, missing values, duplicate actions and unreliable runs.
How it works
Built for the ordinary day—and the awkward one.
We define the trigger, the records involved, the people responsible and what should happen when information is missing. The workflow is then tested with ordinary cases, date boundaries, repeated runs and exceptions.
You receive a clear explanation of the flow and its dependencies. Any licensing or connector requirements are checked before the implementation is agreed.
How this service works
From a sent quote to a follow-up that knows when to stop.
A service business wants every quote to have a clear next step.Follow the example through five stages, with a clear output at each step.
01Understand
Follow one enquiry through the business.
We trace how an enquiry is captured, where the quote is recorded and who owns the conversation. The important gaps are often between tools, where someone has to copy details or remember a reminder.
What you take away
A process map, system inventory and named task owners.
The starting pointStart with the inputs.
01Enquiry inbox
02Quote record
03Customer replies
The question to resolveWho follows up, and when?
02Agree
Define the rule—and the stopping rule.
The first scope prepares a follow-up after two working days without a reply. We agree review and approval steps, account access and service costs. A customer reply must change the scheduled next action.
What you take away
An agreed trigger, approval rule and exception path.
The agreed scopeA focused first result.
- Capture the enquiry and owner
- Prepare follow-up after two working days
- Stop the reminder when a reply arrives
Keep the boundaries clear
Automatic pricing and a full customer portal are outside this first workflow.
Confirm access, dependencies and costs before work starts.
03Build
Connect the steps and review the record.
The team sees the enquiry, quote status, owner and next action together. We review the message and the condition that prepares it before enabling any agreed sending behaviour.
What you take away
A reviewable workflow with visible status and ownership.
A view to reviewMake the work visible.
First working view
01Quote 1042 · Owner Alex
02No reply · 2 working days
03Next action · Review follow-up
Review together → refine the important details
Check it against the purpose
Does this view make the next decision clearer for the person using it?
04Test
Try the cases that change the next step.
We check waiting quotes, received replies, missing email addresses and repeat triggers. A run history should explain what happened and leave failed or held work with someone who can resolve it.
What you take away
Checks for normal runs, duplicates and held tasks.
The checks that matterThe condition changes the decision.
The input or conditionTwo working days have passed
Expected resultPrepare follow-up
The owner reviews the message before sending.
Agree the check. Inspect the result. Keep exceptions visible.
05Hand over
Make the workflow understandable to its owner.
The handover explains the triggers, connections and review queue. We identify who maintains account permissions, monitors failed runs and approves any future rule changes.
What you take away
A run guide, connection inventory and monitoring responsibilities.
Ready for everyday useThe result comes with context.
Workflow rules
Triggers, delays, stopping conditions and approval steps.
Connections & ownership
Accounts, permissions, third-party costs and the person responsible for failed runs.
Exception guide
How to review held records, correct a missing field and retry without duplication.
The next stepKnow how to use it.
Know who owns it.
Know who owns it.
Maintenance and continuing support are agreed around the project.
See the wider approach to scope, collaboration and handover.
How we work togetherA few useful answers
Questions before
the first conversation.
Can you fix a flow we already use?
Yes. We can inspect the intended process, reproduce the issue where access allows and propose a focused repair.
Can reminders be sent to different managers?
Yes. Routing can follow defined data and rules, with an agreed fallback when the usual recipient is missing.
Can a workflow connect to SQL?
It can be scoped around supported connections and appropriate permissions. Access, hosting and licensing need to be checked for the particular database.
How do we avoid sending the same notification twice?
The design should track what has already happened and test repeated runs. The exact method depends on the workflow and its record system.
The next useful conversation
Which repeated task would you like to stop chasing?
Describe the trigger, the steps and the tools involved. We can work out whether the process is ready to automate.
Discuss a workflowStart with what needs to changeA report I keep rebuildingA task I keep repeatingA website we’ve outgrownSomething else entirely