By
Mendy Green
December 12, 2022
•
20 min read
Business

As a business owner, it’s important to have a good understanding of your business goals, and its operations. There are several key questions that every business owner should be able to answer in order to ensure the success and growth of their company.
As a business owner, it’s essential to have a strong and focused culture and a set of core values that guide your company’s actions and decisions.
Business culture refers to the values, beliefs, and behaviors that make up a company’s identity. It’s the “personality” of the organization and the way it operates. A strong culture is one that aligns with the company’s goals and mission, and that supports the growth and success of the business.
These values should reflect your company’s mission and goals and should be integrated into every aspect of your business operations. Once your values are established, it’s important to communicate them to your team in to help make sure they are integrated into the company’s operations and decision-making processes. While all the other points are critical for owning and operating a business, they are also all areas that can be delegated (and usually are for larger businesses). The first point, regarding company culture is something that can only come from the top.
There are several reasons why this can have a major impact on the success and growth of your business.
First, a strong and focused culture can help attract and retain top talent. Employees who share your company’s values and beliefs are more likely to be motivated and engaged in their work and are more likely to stay with the company long-term. This can improve morale and productivity and can help drive the success of your business. This can include offering opportunities for professional development and growth, providing a healthy and supportive work environment, and recognizing and rewarding outstanding performance.
Second, a consistent and focused culture can improve customer satisfaction. Customers want to do business with companies that share their values and beliefs. Simon Sinek uses the one wearing the Red Hat as an example. People gravitate to those they connect with and by having a clearly defined culture you can articulate it allows others to see what you stand for and more easily connect with you, which can help increase loyalty and repeat business, as well as establish a greater level of trust.
Third, a focused culture and set of core values can provide guidance and direction for your employees. By having a clear set of values that everyone understands and adheres to, you can create a cohesive and consistent brand and customer experience. This can help improve collaboration and communication within your team and can make it easier to make strategic business decisions.
Finally, having that strong culture and core values established gives you guiding principles when it comes time to pick which companies you start a vendor/client relationship with, being able to articulate what you stand for allows you to recognize easily those that align with you or those that do not. You can quickly identify business practices and test them against your core value. “Is this company being honest”, “Do they care about customer experience” are questions you can easily answer based on the start of the relationship and your interaction throughout.
While having a unique selling proposition (USP) is often considered an essential part of a successful business, there is some debate over whether it is still relevant in today’s competitive market. With so many businesses offering similar products and services, it can be difficult to differentiate yourself and stand out from the crowd.
Additionally, many prospects may not have the time or inclination to thoroughly research and compare different vendors before making a purchasing decision. They may rely on marketing messages and other external factors to make their decision, rather than taking the time to evaluate the validity of a company’s USP.
In some cases, a company’s USP may be seen as simply a marketing tactic, rather than a genuine differentiator. This can lead prospects to view all USPs as equally valid, or to disregard them altogether.
Overall, while having a unique selling proposition is still important, it may not be as effective as it once was as a marketing strategy in a crowded and competitive market. It’s important for businesses to carefully consider their USP and whether it is a genuine differentiator, or if it is simply a generic marketing message, and in reality, aligning this with your Culture will help give you a true differentiator.

Episode 20 of By the [run]Book dives into HaloPSA v2.214 with a mix of practical improvements and some quirky additions. Connor and Mendy walk through everything from new dollar variables and asset controls to Avalara fixes and portal enhancements—highlighting what actually matters for day-to-day MSP operations. This episode is especially useful for MSPs refining workflows, automation, and reporting accuracy in Halo.
Watch Now: By the [run]Book: Episode 20
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Mendy and Connor noted this was very useful.
Highlighted during the user action demo as a practical workflow improvement.
Called out as a genuinely useful UI improvement.
Allows more flexibility in how incoming emails are matched to tickets.
Enables automation of asset configuration through API usage.
Introduces a new variable to output custom fields in Q&A format.
Improves visibility into asset changes over time.
Returns the email address of the user associated with a purchase order.
Enhances usability and visibility of search results in the portal.
Provides control over configuration synchronization.
Ensures correct popup behavior when multiple rules trigger.
Makes ticket source available for reporting and filtering.
Adds safeguards when configuring email matching tags.
Allows distribution lists to target all email addresses tied to a user.
Improves clarity in Avalara transaction records.
Adds control over visibility of user actions in the portal.
Improves flexibility when using Accounts and Prospects.
Enables dynamic fields based on asset lifecycle status.
Ensures asset tagging consistency during stock processes.
Adds control over Avalara synchronization scope.
Allows a predefined score for surveys.
Improves visibility when prorating billing items.
Automatically generates a ticket alongside sales orders.
Allows column width customization in list views.
Changes ordering of lists in the team view.
Adds asset status as a usable variable in buttons.
Improves flexibility when viewing lists.
Allows visual customization of buttons.
Enables distribution lists based on ticket criteria.
Adds control over forecast data ranges.
Enhances performance of Azure/Entra sync.
Improves visibility of ticket closure information.
Optimizes webhook performance and payload handling.
Refines permissions for asset management.

Episode 19 walks through HaloPSA v2.212 and v2.214, covering a wide range of quality-of-life improvements, admin controls, and workflow enhancements. Connor and Robbie highlight updates around ticket forms, invoicing, templates, and automation, making this especially useful for MSPs looking to tighten processes and improve day-to-day efficiency.
Watch Now: By the [run]Book: Episode 19
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Allows assets to be linked directly to a client instead of only via a site.
Improves tracking of report usage across dashboards.
Adds control over end-user assignment in templates.
Prevents actions on tickets for stopped clients or sites.
Allows updating custom fields directly via actions.
Prevents approval of expired quotes.
Adds variables for original customer addresses.
Ensures hidden fields do not retain values.
Adds advanced relative date filtering.
Adds preview functionality for templates.
Allows editing of existing meter readings.
Improves grouping of invoice items.
Enables merging duplicate assets.
Displays number of related tickets.
Enhances monitoring integration mapping.
Adds more control to purchase order lifecycle.
Enables workflows triggered by agent emails.
Adds mapping and geolocation features.
Introduces guided project setup.
Allows updating ticket fields post-creation in chat.
Prevents deletion of populated top-level structures.
Improves timesheet usability.
Fixes inconsistent quote PDF behavior.
Aligns quote email behavior with configuration.
Adds access to billing profiles from invoice screen.
Allows use of quote data in actions.
Adds new automation trigger.
Adds rich text support for asset fields.
Prevents closure when tasks remain open.
Adds approvals to activity feed.
Removes agent login option from portal.
Adds ordering control to lookup codes.
Adds planning field to releases.
Enables guided onboarding tools.
Adds note field to consignment lines.
Expands team visibility.
Extends accessibility tools to main app.
Displays previous invoice values.
Exposes billing data to API.
Adds search to selection fields.
Aligns call screen logic with ticket settings.
Links credit lines to original sales orders.
Improves invoice ID handling.
Introduces role-based API identity.

In this episode of By the Runbook, the team continues through the HaloPSA 2.212 release notes and spends time unpacking what several of these changes actually mean in practice. The conversation covers workflow design, mail campaigns, ticket views, reporting, and automation behavior, with especially useful commentary for MSPs trying to decide what to enable, what to ignore, and what to be careful with.
Watch Now: By the [run]Book: Episode 18
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
Check out MSP Blueprint for info on runbooks: MSPBlueprint
This allows the ticket screen to automatically refresh when a background automation completes.
Expands qualification matching to include custom field criteria.
Adds delayed and retry-based webhook processing options.
This change limits the available “From” addresses on a ticket action to mailboxes the assigned team can actually access.
Adds Email Address as another attribute option for follower behavior on the portal.
Allows changes to Mail Campaigns after they have started.
Restricts pipeline stages based on opportunity type.
Adds webhook processing options including delayed and retry handling.
Adds the ability to hide tickets from the change calendar.
Adds Service Users as a selectable option in distribution and user lists.
Allows campaigns to be sent from sales mailboxes.
Adds a warning when an action email will fail.
Adds asset relationship mapping during SQL imports.
Adds an isRunning field to asset discovery.
Expands qualification matching with custom field rules.
Allows ticket view to auto-refresh after automation runs.
Adds ability to update currency values on quotes.
Requires comments for negative KB feedback.
Adds control for showing nested tickets.
Enhances AI reporting capabilities.
Restricts KB edits to owners only.
Adds translation support in the portal.
Adds secondary MAC address support.
Adds character limits to text fields.
Adds more fields for OLA and rule reporting.
Prevents approvals from email replies.
Extends field copying to deeper ticket levels.
Adds primary asset as a runbook condition.
Adds AgentID variable for lookups.
Adds reporting changes to config tracking.
Adds filter profiles to child ticket views.
Adds more configuration options to other open tickets view.