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 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.

Episode 17 warps up the breakdown of version 2.21 and begins 2.212, highlighting impactful updates across billing, SLA visibility, and ticket management. The team dives into major improvements like dynamic ticket filters, default billing templates, and better billing tab access controls. This episode is especially useful for MSPs looking to tighten billing accuracy, improve reporting visibility, and streamline ticket workflows.
Watch Now: By the [run]Book: Episode 17
For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword.
The Billing tab is now visible to agents without requiring full billing permissions, with actions locked based on access.
Tickets on hold can now be included in SLA breached filters.
You can now define a default billing template applied automatically when creating a new customer.
Dynamic filters can now be used on ticket lists for more flexible querying.
This helps keep recurring invoices aligned when item third-party IDs change.
Recurring invoices now get the same due date option already available at customer setup.
This adds more control to portal-based approval workflows.
This extends alternate invoicing behavior down to the site level.
This helps prevent tickets from disappearing into inactive-agent limbo.
More ticket list criteria means more practical operational views.
This update improves the ManageEngine Endpoint Central integration.
Halo now supports generic OpenID Connect SSO.
You can now duplicate item bundles instead of rebuilding them manually.
This adds more naming flexibility to the UI.
This makes SLA breach reporting more honest and more useful.
A major improvement for standard billing configuration.
This adds more flexibility to meter-driven recurring billing.
Dynamic ticket filters add a much stronger filtering experience.
Cloning custom fields speeds up admin work.
This update improves chart label readability.
This update refines the encryption update workflow.
This improves call handling context.
This gives more control over quantity precision.
This improves flexibility when linking work records from sales orders.
This adds better billing visibility without fully exposing billing controls.
Spreadsheet imports can now target existing tickets by ID.
A small UI cleanup on the ticket details pane.
This adds flexibility for co-managed support models.
This improves control over CSP user mapping behavior.
This adds clarification around tax rate usage in Xero-linked setups.
This makes Avalara tenant cleanup easier from the client billing tab.
This is a strong automation improvement.
Custom table row deletion gets more precise.
This cleans up recurring invoice visibility.
This is a documentation/config clarity improvement.
Ticket rule assignment now supports more role-based options.
Approval rule logic gets another useful condition.
Supplier-related configuration gets more flexible.
Project templates now get more dynamic input from sales-order-driven creation.
This expands visibility in quote and sales order line views.
This makes customer/site control more precise.
The API docs continue to improve.
This improves ticket logging layout flexibility in the agent app.
This is an important reliability improvement for payment processing.
This adds more flexibility when services are generated from assets.
This improves parent/child ticket data behavior.
Third-party ID linking is now available across more entities.
Query Builder gets another field for reporting logic.
This expands visibility of account/prospect records in top-level views.
Custom buttons now get access control.
This adds polish to the opportunity creation experience.
This is one of the biggest integration-facing updates in the episode.