Insights
Notes on systems, operations and building software that fits the business.
Practical writing from the work: how the mess builds up, when to buy, connect or build, and what makes internal software last.
103 articles
Operations
Visibility and control — reporting, tracking and the running of day-to-day work.
What Should a Service Reminder System Do After the Reminder Is Sent?
A service reminder system is only useful if it handles replies, non-replies, deferrals and scheduling handoff properly after the reminder is sent.
How to Design a Quoting Workflow for Consulting and Professional Services Work
A professional services quote should do more than win work. It should define scope, assumptions, billing and handover details clearly enough for delivery and finance to start without rework.
When Do You Need an Internal Operations App Instead of More Workflow Automation?
Workflow automation helps connect systems, but it stops being enough when your team still relies on emails, PDFs and spreadsheets to control real work.
How to Build a Monday.com System That Connects Work Intake, Delivery and Reporting
A workable Monday.com system is more than a collection of boards. Here’s how to connect intake, delivery and reporting so work moves reliably and data stays useful.
How to Build a Professional Services Dashboard That Shows Delivery Risk, Capacity and Profitability
A useful professional services dashboard should show delivery risk, capacity, WIP and profitability signals together so managers can intervene early rather than explain problems after the fact.
What Should Happen Between Job Completion and Invoice Release?
A finished job should not go straight to invoicing. Define a clear invoice-readiness workflow so evidence, approvals and billing conditions are checked before release.
How to Connect Timesheets, Purchasing and Invoicing So Job Costs Stop Being Wrong
Wrong job costs usually come from disconnected labour, materials and invoice data. Here’s the operating model that makes job-level costing reliable.
What Should a Job Sheet Management System Actually Capture Before, During and After Site Work?
A job sheet should do more than record what happened on site. Here’s what a job sheet management system needs to capture before, during and after work so scheduling, invoicing and reporting can keep moving.
What Should an Internal Operations App Replace That Email, PDFs and Shared Spreadsheets Cannot Handle?
A practical guide to recognising when email, PDF forms and shared spreadsheets have reached their limit, and when an internal operations app is justified.
How to Scope a Reporting Dashboard Project When You Need Answers Fast, Not a BI Science Project
A practical guide to scoping a reporting dashboard project so you get useful operational visibility quickly, without letting the work turn into an endless BI exercise.
What Does a Monday.com Consultant Actually Do for an Operations-Focused Business?
If you are considering a Monday.com consultant, the real question is not who can build boards. It is who can design a workable operating system around your actual workflow, ownership rules, integrations and reporting needs.
How to Decide Whether Your Trade or Service Business Needs an Off-the-Shelf System, an Integration Layer or Custom Software
A practical framework for deciding whether your business needs a packaged platform, better integration between existing tools, or custom software.
How to Fix Reporting When Your Job, Finance and Operations Teams All Count Work Differently
If operations, finance and delivery teams all define work differently, dashboards will keep creating arguments. Here is how to fix reporting by aligning definitions, workflow states and source systems first.
How to Build a Service Request Workflow That Connects Intake, Triage, Approval and Delivery Across Multiple Systems
A practical guide to designing a service request workflow that handles intake from multiple channels, routes work correctly, manages approvals and connects cleanly into delivery systems.
When You Need a Client Portal, Vendor Portal or Internal App Instead of Forcing Everything Through Email and PDFs
Email and PDFs work until approvals, documents and status updates start creating delays, rework and poor visibility. Here is how to recognise when a client portal, vendor portal or internal app may be the better operational answer.
How to Design a Monday.com System for Operations Without Turning It Into Another Spreadsheet
Considering Monday.com for operations? Here’s how to assess whether it suits your workflow, what usually goes wrong in setup, and how to design a system that supports clear ownership, handovers and reporting.
How to Build an Operational Data Quality Dashboard That Catches Workflow Problems Before They Reach Customers or Finance
A practical guide to building an operational data quality dashboard that surfaces missing inputs, stale records, status conflicts and integration failures before they affect customers, invoicing or reporting.
How to Scope a Business Process Design Project Before You Automate, Integrate or Build Anything
A practical guide to scoping a business process design project before automation, integration, dashboards or custom software, including workflow boundaries, ownership, exceptions and implementation scope.
How to Design an Internal Timesheet and Time-Capture System That Works Across Payroll, Job Costing and Reporting
A practical guide to designing a time-capture system that supports payroll, job costing and reporting without creating more admin or unreliable data.
How to Build a Revenue Assurance Automation Business Case Without Guessing the ROI
A practical guide to building a revenue assurance automation business case using leakage categories, delays, exception rates and cash-flow impact instead of inflated ROI assumptions.
What Should a Job Management System Actually Do for a Service Business With Multiple Teams, Queues and Handoffs?
A practical guide to what a job management system should actually do when your service business has multiple teams, handoffs, approvals and operational queues.
How to Build the Business Case for Replacing Spreadsheet-Based Job Status Tracking
If your team tracks job statuses in spreadsheets, the real problem usually is not the spreadsheet itself. It is inconsistent workflow control, weak reporting and too much reliance on people remembering what happens next.
How to Scope an Internal Operations Dashboard Project So It Does Not Become a 3-Month IT Job
If your dashboard project keeps dragging on, the problem is usually not the charts. It is unclear KPI definitions, poor source-system decisions and no agreed ownership. Here is how to scope an internal operations dashboard project properly before build starts.
How to Build a Workflow That Flags Jobs at Risk of Missing an SLA Before the Breach Happens
A practical guide to designing workflows that identify SLA risk early, assign ownership, trigger escalation and improve visibility across service operations.
What Should a Service Reminder Software System Actually Do for a Field Service Business?
Service reminder software should do more than send messages. This article explains what field service businesses should assess before choosing a system, from due dates and asset records to booking workflows, invoicing links and exception handling.
How to Build the Business Case for Revenue Assurance Automation
Revenue leakage rarely comes from one dramatic failure. It usually comes from missed variations, incomplete handovers, invoice blockers and disconnected systems. Here’s how to build a practical business case for revenue assurance automation.
What Should a Business Process Dashboard Actually Show to Help You Run Operations?
A useful business process dashboard should help you act, not just observe. Here is what an operational dashboard should actually show if you need better control over workflow, bottlenecks and exceptions.
How to Assign Jobs to the Nearest Available Technician Without Breaking Skills, SLAs or Job Readiness
Nearest available technician sounds efficient, but proximity alone often creates missed SLAs, poor handovers and unnecessary rework. Here is how to design dispatch rules that balance travel time with skills, readiness, priority and service commitments.
What Should a Business Improvement System Include Before You Buy More Software?
Before buying more software to improve the business, clarify the workflow, ownership, reporting, approvals and integrations you actually need. A better result usually comes from system design, not another standalone app.
How to Track Consultant and Professional Services Time Without Creating Admin, Billing and Profitability Problems
Consulting and professional services time tracking often breaks down long before invoicing. This article explains how to design a time-tracking workflow that supports billing, payroll, utilisation and profitability without adding unnecessary admin.
When Do You Need a Job Management System Instead of More Spreadsheets, Email and Whiteboards?
If your jobs are relying on inboxes, spreadsheets and people remembering what happens next, you may be past the point where a proper job management system is needed. Here is how to tell, and what to map before choosing one.
What Does Process Improvement Consulting Actually Look Like in a Growing Business?
Process improvement consulting is not vague advisory work when done properly. It is a practical process of diagnosing operational friction, redesigning workflows, clarifying ownership and using systems, automation and integrations where they genuinely improve reliability.
How to Stop Scheduling Around Technician Availability Without Checking Job Readiness
If a free technician is the main reason a job gets booked, failed visits and last-minute reshuffling are almost inevitable. Here’s how to separate technician capacity from job readiness and build better scheduling rules.
Why Your Workflow Breaks When Nobody Owns the Customer Handover After Work Is Finished
Many jobs are physically finished before they are operationally, customer or commercially complete. Here’s how to define each stage properly and assign clear ownership for the handover in between.
How to Design an Approval Workflow for Supplier Purchases That Do Not Come From a Quote
A practical guide to designing approval workflows for unplanned supplier purchases, including thresholds, urgent exceptions, job linkage, evidence requirements and reconciliation.
When Should a Job Create a Project, Work Order or Task Instead of Staying as One Record?
If one job record is carrying too many owners, dates, costs or deliverables, the structure is probably wrong. Here is how to decide when work should stay as one record and when it should split into projects, work orders, phases or tasks.
How to Stop Service History Living in PDFs, Photos and Technician Memory
Service history only helps if the next person can actually find and use it. Here’s how to structure asset, site and job history so quoting, scheduling and field staff can access the right information without digging through attachments.
Why Your Job Profitability Reporting Fails When Overheads and Non-Job Time Have No Allocation Logic
If travel, admin, supervision and non-billable time are missing from your reporting, job profitability can look better than it really is. Here is why allocation logic matters and how to build reporting you can trust.
How to Know Whether Your Team Needs a Formal Intake Workflow, Not Just a Shared Inbox
A shared inbox works until incoming requests start affecting delivery, revenue or compliance. Here’s how to tell when you need a formal intake workflow instead.
What Should Happen When a Job Needs to Be Split Into Stages, Milestones or Partial Invoices?
Staged work needs more than notes and manual reminders. This article explains how to structure stages, approvals, progress tracking and invoice triggers without creating duplicate jobs or muddy reporting.
How to Stop One Job Creating Multiple Customer Conversations Across Email, SMS and Phone
When customer communication is spread across email, SMS and phone, jobs lose context fast. Here’s how to structure ownership, logging and channel rules so every conversation stays attached to the job.
Should You Let Customers Approve Quotes by Email, Portal or Signed Document?
Choosing how customers approve quotes is not just about convenience. The approval method affects evidence, scope clarity, deposits, job creation and how reliably work moves into operations.
How to Design a Workflow for After-Hours Calls, Messages and Emergency Requests
A practical guide to designing an after-hours workflow for calls, messages and emergency requests, with urgency rules, intake requirements, escalation paths and clean handover to the daytime team.
Why Your Workflow Breaks When the Real Problem Is Unclear Decision Rights
Many workflow problems are not caused by bad software but by unclear authority. When nobody knows who can approve, change, override or close work, delays and inconsistent decisions follow.
How to Design a Workflow for Customer-Supplied Materials, Parts or Equipment
Customer-supplied materials and equipment can create delays, disputes and billing confusion if the workflow is unclear. This article explains how to build clear checkpoints around readiness, responsibility, suitability and documentation.
Should Your Team Be Paid From Timesheets, Clock Events or Job Statuses?
Choosing the wrong source for payroll creates disputes, bad job costing and unreliable reporting. Here is how to decide between timesheets, clock events and job-status data, and what controls matter before a pay run.
What Should Happen When Site Information Arrives After the Job Has Already Been Scheduled?
When site details change after a job is booked, adding a note is not enough. A reliable process needs impact checks, clear ownership, controlled updates and confirmed communication to field staff and customers.
How to Track Rework Separately From New Work So You Can See the Real Cost
If rework is buried inside normal labour entries, your margins will look better or worse for the wrong reasons. Here is how to classify, capture and report rework separately so you can see its real cost.
How to Stop a “Waiting for Customer” Status Becoming a Black Hole
A “waiting for customer” status only works if it has clear reasons, ownership, follow-up rules and exit paths. Here’s how to stop jobs disappearing into limbo.
Why Your Team Keeps Using Free-Text Notes Where Structured Data Should Exist
If important workflow information lives inside notes, comments and emails, your systems cannot reliably trigger actions, report accurately or show clear ownership. Here’s how to decide what belongs in a field and what belongs in a note.
How to Design a Workflow for Jobs That Need Multiple Trades or Teams
Multi-team jobs do not fail because people are lazy. They fail when stages, dependencies and handovers are unclear. Here is how to design a workflow that makes ownership, sequencing and readiness visible.
Should You Let Customers Book Work Online If Your Internal Workflow Is Not Ready?
Online booking can improve convenience, but only if your internal workflow can support it. Here is how to tell whether self-service scheduling will help or create more operational problems.
How to Stop Recurring Jobs Creating Duplicate Work, Missed Work or Scheduling Collisions
Recurring service work often breaks down when repeat jobs are created without clear rules for timing, ownership, skips, pauses and schedule changes. Here’s how to design recurring workflows that avoid duplicate jobs, missed visits and scheduling conflicts.
What Happens When Your Job Management System and Accounting System Disagree?
When job and accounting systems disagree, the problem is usually not careless staff. It is unclear system ownership, poor status mapping or weak integration design. Here is how to find the cause and stop the mismatch recurring.
What Should Your Dispatch Team See That Your Technicians Do Not Need?
A dispatch team and a technician do not need the same screen. Here is how role-based visibility improves scheduling, clarity and data quality without breaking the source of truth.
How to Reconcile Supplier Invoices Against Purchase Orders, Deliveries and Job Costs Without Manual Detective Work
Supplier invoice matching breaks down when purchase orders, deliveries and job costs are disconnected. Here is how to build a workflow that handles partial receipts, split invoices, tolerances and exceptions without relying on manual detective work.
Why Your Approval Workflow Needs Delegation Rules Before Someone Goes on Leave
Approval workflows often fail when one key approver is on leave, sick or travelling. Here’s how to build delegation rules that keep work moving without losing control or visibility.
How to Stop Technicians Closing Jobs Before the Work Is Actually Complete
When technicians close jobs too early, the problem is usually not the person but the workflow. Here is how to separate visit completion from job completion and apply practical controls that still work in the field.
What Should Happen When a Customer Puts a Job On Hold?
An on-hold job should not disappear into a vague status. Here is how to define customer-initiated holds, pause the right workflows, trigger follow-up, and bring work back into active delivery properly.
How to Design a Workflow for Shared Equipment, Vehicles and Other Limited Resources
Jobs often get booked on the assumption that a vehicle, machine or specialist asset will be available. This article explains how to design a workflow that prevents double-booking, handles downtime and links shared resources to job readiness.
Should Your Estimating Team Work From Templates, Assemblies or Rules?
Templates, assemblies and rules each suit different types of estimating work. The right structure depends on how repeatable your jobs are, how much flexibility your estimators need, and what needs to happen after the quote is approved.
How to Stop Defect Rectification Work From Disappearing After Handover
Post-handover defects often disappear into emails, notes and reopened jobs. Here is how to design a defect rectification workflow that keeps ownership, cost and customer expectations clear.
Why Your Job Photos Need Metadata, Not Just File Uploads
Job photos are only useful if they can be found, trusted and linked to the work they prove. Here’s why metadata matters, what to capture, and how photo records should flow into approvals, defects, variations and completion evidence.
How to Design a Workflow for Customer Callbacks That Preserves Context From the First Contact
A reliable callback process needs more than message-taking. Here is how to design a workflow that captures context, ownership, promised response times and outcomes from the first contact.
How to Stop Recurring Service Work Creating Duplicate Jobs, Missed Visits and Billing Errors
Recurring service breaks down when plan rules, job creation and billing drift apart. Here’s how to design a recurring workflow that prevents duplicate jobs, missed visits and invoice errors.
What Should Happen When One Customer Has Multiple Sites, Contacts and Billing Rules?
Multi-site customers often create dispatch, communication and invoicing errors when everything is stored in one flat customer record. Here is a cleaner operational model for handling accounts, sites, contacts and billing rules.
How to Design a Workflow for Customer-Supplied Materials Without Breaking Job Costing
Customer-supplied materials can create confusion in quoting, delivery, responsibility and invoicing. Here is how to design a workflow that keeps those jobs visible without distorting job costing.
Why Your Job Management System Should Not Be Your Scheduling System by Default
If scheduling still feels messy despite having job management software, the problem may be system ownership rather than staff performance. Here is how to decide whether one platform should handle both jobs and scheduling.
How to Stop Reporting Logic Living Only Inside One Person’s Spreadsheet
When reporting only works because one person maintains a spreadsheet full of hidden formulas and workarounds, the real problem is not the spreadsheet. It is undocumented business logic, unclear data ownership and fragile reporting architecture.
Should Your Customer Communication Be Triggered by System Events or Staff Decisions?
Not every customer update should be automated. The right communication model depends on whether your workflow data is reliable, the next step is operationally certain, and the situation needs human judgement.
How to Know Whether a Workflow Needs a Queue, Not Just a Status
Statuses tell you what something is. Queues tell you who needs to act. Here’s how to tell when passive status labels are causing work to sit still and when a queue-based workflow will create clearer ownership and better visibility.
Why Your Purchase Order Workflow Breaks on Split Deliveries and Partial Receipts
Split deliveries and partial receipts expose a common weakness in purchasing workflows: systems that treat purchase orders as either open or closed, with no useful middle state.
How to Stop Multiple Site Visits From Producing Conflicting Job Notes and Photos
When several people attend the same job over multiple visits, unstructured notes and photo uploads quickly become unreliable. This article explains how to structure field evidence so site history stays clear for operations, quoting, invoicing and disputes.
What Should Happen When a Job Needs to Be Rescheduled More Than Once?
Repeated job reschedules are usually a signal that something in the workflow is broken. Here is how to handle multi-reschedule jobs with cause codes, escalation rules and clear operational ownership.
How to Design an Audit Trail for Quote, Scope and Price Changes
A good audit trail does more than record changes. It helps prevent disputes, keeps delivery aligned with the latest approved scope, and ensures invoicing reflects what was actually agreed.
Why Your Renewal and Rebooking Process Still Depends on Human Memory
If renewals and rebookings keep slipping, the problem is usually not effort. It is that no system clearly owns the trigger, status and follow-up path.
Should Your Quote System Generate a Bill of Materials Automatically?
Automated BOMs can reduce rework between estimating and delivery, but only when quote data is structured for operations, not just sales. Here’s how to tell when it will help and when it will create problems downstream.
How to Stop Call Answering and Office Intake Creating Duplicate Job Records
Duplicate job records usually start at intake, not later in operations. Here’s how to design one intake path, one job creation rule and clear exception handling so inbound requests reach quoting or scheduling without admin cleanup.
How to Stop Internal Service Requests Becoming Invisible Work
Internal requests often arrive through chats, calls and quick conversations, then disappear from view while still consuming real time. Here’s how to capture, prioritise and track that work without creating unnecessary bureaucracy.
How to Stop Invoicing Delays Caused by Missing Customer Purchase Order Matching
Invoices often stall because customer PO numbers, line references or approval conditions were never captured properly. Here’s how to fix the workflow from quote and job setup through to billing.
When a CRM Should Not Be the Source of Truth for Operational Work
A CRM can be the right place for customer and pipeline information without being the right place to run live operational work. Here’s how to decide what should live where.
How to Stop Payroll, Scheduling and Job Costing Using Different Time Data
If payroll, scheduling and job costing all use different versions of time, automation will only speed up the confusion. Here’s how to define each type of time properly and build a workflow that keeps them consistent.
Why Your KPI Dashboard Creates Arguments Instead of Clarity
If your KPI dashboard causes debate instead of faster decisions, the problem is usually not the visual layer. It is usually unclear definitions, ownership, timing and source-of-truth choices upstream.
How to Design a Quote Approval Workflow for High-Risk or Non-Standard Jobs
A fast quote process is useful until unusual jobs create bad commitments. Here’s how to design a quote approval workflow that catches delivery, margin and contract risk before the quote goes out.
What Should Happen When a Technician Finds More Work on Site?
When a technician finds extra work on site, the real issue is not the work itself but the lack of a defined workflow for capture, approval, pricing and follow-through.
How to Stop Field Staff and Office Staff Working From Different Scopes of Work
When the sold scope, scheduled scope and site-understood scope drift apart, disputes and missed work follow. Here’s how to create one controlled scope record that stays consistent from quote through delivery.
Why Jobs Keep Reopening After You Thought They Were Finished
Jobs often reopen because “complete” means different things to different teams. Here’s how to design a completion workflow with clear states, proof requirements and exception paths.
How to Stop Customer-Specific Pricing Rules Breaking Your Quoting Process
Customer-specific pricing often breaks quoting when special rates, discounts and inclusions live in inboxes or spreadsheets. Here’s how to structure pricing rules so quotes stay accurate, approvals stay visible and downstream teams can rely on the data.
What Should Happen After a Customer Accepts a Quote?
An accepted quote should trigger a clear operational workflow, not create more chasing. Here’s how to move approved work into delivery with the right checks, ownership and handovers.
How to Know When a Workflow Problem Needs Better Process, Not More Automation
Not every workflow problem should be solved with automation. Here’s how to tell when the real issue is an unclear process, inconsistent decisions or missing ownership.
Why Your Reporting Breaks When Every Team Defines a ‘Completed Job’ Differently
If sales, operations and finance all mean something different by “completed job”, your reports will never reconcile. Reliable reporting starts with shared operational definitions, not better dashboards.
How to Stop Variation Approvals Going Missing Between Site, Office and Customer
Variation approvals usually go missing because the handover between site, office and customer is weak. A reliable workflow needs clear triggers, required evidence, approval status tracking and a clean link to invoicing.
Should Your Technicians Enter Job Notes in the Field or Should the Office Own Them?
Job notes break down when nobody clearly owns what should be captured, when it should be captured, and how it will be used next. Here’s how to separate field observations, operational updates and final admin records.
When AI Is Actually Useful in an Operations Workflow
AI can help in operations, but only in the right places. Here’s where it adds value, where standard automation is safer, and how to test AI in a way that improves workflows without creating noise or risk.
Should You Build a Customer Portal or Fix Your Internal Workflow First?
A customer portal can reduce update requests, but only if your internal workflow is already reliable. Here’s how to tell whether a portal will add value or simply expose poor status control, missing documents and unclear ownership.
How to Turn Website Enquiries Into Properly Qualified Work Without Manual Re-Entry
A better enquiry process does more than capture contact details. It collects the right information, qualifies work properly, assigns ownership immediately and routes good opportunities into the right workflow without manual re-entry.
Why Your Dashboard Still Fails Even When the Data Is There
If your dashboard exists but still doesn’t help you manage the operation, the problem is usually upstream. Here’s why dashboards fail even when the data appears to be there.
How to Automate Timesheet Capture Without Creating Payroll Problems
Automatic time capture can reduce admin, but raw job events rarely translate cleanly into payroll. Here’s how to design a timesheet workflow that captures time automatically while still handling exceptions, approvals and audit trails properly.
What Should Happen When a Customer Does Not Respond?
Customer silence should not leave quotes, approvals or scheduling decisions sitting in invisible queues. Here is how to design a clear non-response workflow with response windows, follow-ups, pause states and escalation rules.
How to Stop Approval Bottlenecks Slowing Down Operational Work
Approval delays usually come from poor workflow design, not a lack of reminders. Here’s how to redesign approvals with clear rules, thresholds, response windows and fallback paths so work keeps moving without losing control.
How to Design Statuses That Actually Drive Workflow
Many businesses have plenty of statuses but very little clarity. Here’s how to design statuses that drive ownership, next actions, reporting and automation across operational workflows.
Why Your Quote Should Produce More Than a Price
A quote should do more than win the job. Done properly, it should generate the operational data needed for job setup, purchasing, scheduling, invoicing and visibility.
How to Automate Handover Between Estimating, Sales and Operations Without Losing Context
Most handover failures are not caused by missing notifications. They happen when scope, assumptions and customer commitments never make it into operations in a usable format. Here is how to design a handover that preserves context and prevents rework.
Next step
Reading this because something isn’t working?
Describe the problem and we’ll tell you what the system should look like.
Free 20-minute conversation. No obligation.