[et_pb_section fb_built=”1″ admin_label=”Section” _builder_version=”4.22.0″ _module_preset=”default” custom_margin=”0px||0px||false|false” custom_padding=”0px||0px||false|false” locked=”off” global_colors_info=”{}”][et_pb_row column_structure=”1_4,3_4″ _builder_version=”4.27.0″ _module_preset=”default” custom_padding=”50px||||false|false” custom_css_main_element=”z-index:0!important;” global_colors_info=”{}”][et_pb_column type=”1_4″ disabled_on=”on|on|off” _builder_version=”4.22.0″ _module_preset=”default” custom_padding=”||||false|false” sticky_position=”top” sticky_offset_top=”100px” sticky_limit_bottom=”section” motion_trigger_start=”top” global_colors_info=”{}”][et_pb_text admin_label=”indice” _builder_version=”4.27.6″ _module_preset=”default” custom_margin=”||0px||false|false” custom_padding=”||14px||false|false” link_option_url=”#1″ global_colors_info=”{}”]<\/p>\n
Sections<\/strong><\/p>\n [\/et_pb_text][\/et_pb_column][et_pb_column type=”3_4″ _builder_version=”4.27.0″ _module_preset=”default” custom_css_main_element=”z-index:0!important;” global_colors_info=”{}”][et_pb_text admin_label=”seccion” module_id=”1″ module_class=”ittopicscontent” _builder_version=”4.27.6″ _module_preset=”default” z_index=”0″ custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||false|false” custom_css_main_element=”font-family:%22Pandora-Light%22;” locked=”off” global_colors_info=”{}”]he most important breakthrough in programming and IT, by far, is Ctrl+C and Ctrl+V. But everything has a dark side. When we talk about growing MSPs<\/a>, they must necessarily grow on the foundations of reusable automations<\/a>, because otherwise, it is impossible. When it works, it is great and we feel like kings. But the temptation to press Ctrl+C and Ctrl+V is powerful, and replicating automations as if client environments were identical opens Pandora\u2019s box, never better said in our case. Basically, an MSP that does not reuse is condemned to redo the same work again and again<\/strong>. The same tedious suffering as Sisyphus pushing his stone uphill, but on top of that, billing hours that eat into an ever-shrinking profit margin. In the introduction, we already sensed a challenge that is worth expanding on. The result is that an automation that saved ten minutes for client A causes B to go down and triggers the angry phone call. Nothing is more irritating than pointing out challenges without providing solutions, so let us start with them. At this point, it is important not to confuse the concept of reuse with that of standardising services without depending on manual scripts<\/A>. Efficiency is wonderful until it deletes every file with a message saying: \u201cOops, I destroyed everything (proud smiling emoji with rosy cheeks)\u201d. Earlier I mentioned that good reuse is a matter of design, especially in a multi-client operation<\/A> like that of an MSP. Many technological promises do not translate well from the PowerPoint that sells them to the reality that lives them. But in this case, if there is good reuse, there will also be signs such as:<\/p>\n At this point in the journey, it is time to bring all of this down to tools. Let us recap the most important points. Reusing automations across clients is not about cloning scripts and crossing your fingers<\/strong>. It is about building common logic that is flexible and controlled enough to operate several environments without multiplying risk or work. The key that opens that double lock is design<\/strong>, parameterising instead of practising the noble art of hardcoding, segmenting rather than generalising, validating instead of assuming (which is always a first step towards disaster) and, above all, always keeping the retreat route open, in case an emergency Ctrl+Z needs to be pressed. If we do it this way, we will become an MSP that truly grows, instead of accumulating clients and, with them, scaling problems rather than operations. Trends are powerful, but automating any which way because it seems to be what everyone is doing today can buy us a one-way ticket to bankruptcy. Our mission is to boldly go where no one has gone before, yes, but not by dismantling the ship along the way.[\/et_pb_text][et_pb_button button_url=”@ET-DC@eyJkeW5hbWljIjp0cnVlLCJjb250ZW50IjoicG9zdF9saW5rX3VybF9wYWdlIiwic2V0dGluZ3MiOnsicG9zdF9pZCI6IjM2MjI3MCJ9fQ==@” button_text=”\u2190 Back to IT Topics” button_alignment=”left” _builder_version=”4.22.0″ _dynamic_attributes=”button_url” _module_preset=”default” custom_button=”on” button_text_size=”1em” button_text_color=”#0C312F” button_bg_color=”#FFFFFF” button_bg_color_gradient_direction=”90deg” button_bg_color_gradient_stops=”#82B92E 0%|#3CB92E 100%” button_bg_color_gradient_start=”#82B92E” button_bg_color_gradient_end=”#3CB92E” button_border_width=”1px” button_border_color=”#eaeaea” button_border_radius=”100px” button_use_icon=”off” z_index=”0″ custom_margin=”60px||0px||false|false” custom_padding=”10px|50px|10px|50px|true|true” custom_padding_tablet=”” custom_padding_phone=”10px|20px|10px|20px|true|true” custom_padding_last_edited=”on|phone” custom_css_main_element=”right:0!important;||font-family:%22Pandora-Bold%22!important;” global_module=”367749″ locked=”off” global_colors_info=”{}” button_bg_color__hover_enabled=”on|desktop” button_bg_color_gradient_start__hover=”#eaeaea” button_bg_color_gradient_end__hover=”#f4f4f4″ button_bg_color__hover=”#eaeaea” button_bg_enable_color__hover=”on” button_bg_use_color_gradient__hover=”on” button_bg_color_gradient_stops__hover=”#eaeaea 0%|#f4f4f4 100%”][\/et_pb_button][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ custom_padding_last_edited=”on|desktop” admin_label=”Final CTA” _builder_version=”4.27.0″ _module_preset=”default” background_color=”#161327″ use_background_color_gradient=”on” background_color_gradient_stops=”rgba(22,19,39,0.5) 17%|rgba(22,19,39,0.5) 100%” background_color_gradient_overlays_image=”on” background_image=”https:\/\/pandorafms.com\/wp-content\/uploads\/2023\/12\/banner-contacta-it-topics.webp” background_size=”custom” background_image_width=”121%” background_image_height=”192%” background_position=”top_left” z_index=”1″ max_width=”1080px” max_width_tablet=”98%” max_width_phone=”98%” max_width_last_edited=”on|tablet” module_alignment=”center” custom_margin=”80px||80px||true|false” custom_padding=”40px|20px|120px|20px|false|true” custom_padding_tablet=”40px|0px|120px|0px|false|true” custom_padding_phone=”40px|0px|120px|0px|false|true” scroll_scaling=”40|55|85|100|100%|120%|100%” motion_trigger_start=”top” background_last_edited=”on|phone” background_size_tablet=”cover” background_size_phone=”cover” background_position_phone=”top_center” border_radii=”off|20px|20px|20px|20px” border_color_all=”#ffffff” box_shadow_style=”preset1″ box_shadow_vertical=”0px” box_shadow_blur=”80px” box_shadow_color=”#506da0″ saved_tabs=”all” global_colors_info=”{}”][et_pb_row use_custom_gutter=”on” gutter_width=”2″ make_equal=”on” _builder_version=”4.22.0″ _module_preset=”default” max_width=”750px” module_alignment=”center” custom_margin=”0px||0px||true|false” custom_padding=”0px|0px|0px|0px|true|true” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.22.0″ _module_preset=”default” global_colors_info=”{}”][et_pb_text content_tablet=”<\/p>\n Habla con el equipo de ventas, pide presupuesto, o resuelve tus dudas sobre nuestras licencias<\/p>\n ” content_phone=”<\/p>\n Habla con el equipo de ventas, resuelve tus dudas sobre nuestras licencias o pide presupuesto<\/p>\n ” content_last_edited=”on|tablet” _builder_version=”4.22.0″ _module_preset=”default” header_2_font_size=”2em” text_orientation=”center” module_alignment=”left” custom_margin=”0px||20px||false|false” custom_padding=”0px||0px||true|false” global_colors_info=”{}”]<\/p>\n Habla con el equipo de ventas, pide presupuesto, [\/et_pb_text][et_pb_code _builder_version=”4.27.4″ _module_preset=”default” width=”200px” module_alignment=”center” custom_margin=”40px||0px||false|false” custom_padding=”0px||0px||true|false” locked=”off” global_colors_info=”{}”]<\/p>\n\n
\nToday we will try to navigate those waters, analysing how to reuse what already works without dragging errors, rigidity or poisoned legacies<\/strong> from one environment to another.
\nAnd a small spoiler before we continue. Reuse does not mean wearing out the Ctrl, C and V keys on the keyboard from copying scripts so much.
\nThe key is to design them from scratch so they can be reused<\/strong>.<\/p>\nWhy it is necessary to reuse automations in an MSP<\/h2>\n
\nWithout reuse, operational cost grows in parallel with the client portfolio<\/strong>, because of that need to build everything from scratch. Onboarding drags on forever and consistency between environments fades away, because each technician sets things up their own way, depending on which side of the bed they got out of that day.
\nReuse is what allows scaling not to mean increasing the technical team<\/a> at the same pace as revenue, so it is the ingredient that allows the MSP to grow instead of making the challenge bigger.<\/p>\nThe classic mistake: copying and pasting logic designed for a single client<\/h2>\n
\nSomeone solves a challenge for Client A, it works, it is great, we celebrate, pat ourselves on the back, and that same block tends to be replicated across clients B, C and D without changing a single comma.
\nBut all too often, that logic comes with embedded assumptions that were only true for A, so when we reuse it exactly as it is… No celebration, no pat on the back, no brilliance, just disaster.
\nThe usual suspects in those non-reusable automations are:<\/p>\n\n
\nAnd since mistakes when automating processes in an MSP<\/a> are multiplied by the number of affected clients, what was a stone in the road becomes a landslide that crushes us.<\/p>\nWhat makes a reusable automation safe<\/h2>\n
\nThe good news is that the key difference between a dangerous automation and a reusable one is its design, so it does not come down purely to budget or access to arcane tools.
\nThus, an automation can be safely reused when it follows the following principles<\/strong>, which are also the ones we would apply to any code we want to keep alive:<\/p>\n\n
\nStandardisation aims to define the expected behaviour and unify it, while reuse deploys it. They are not the same, but they need each other, since one without the other limps<\/strong>.<\/p>\nWhat should not be reused without adaptation<\/h2>\n
\nThat is why there are things that should not travel from one client to another without first going through a serious review<\/strong>.
\nThe criterion for deciding what needs to be properly verified is simple: If the cost of getting it wrong is high and context rules, we slow down<\/strong> and take a good look.
\nThat is why we should never reuse without adapting:<\/p>\n\n
How to design reusable automations in a multi-client environment<\/h2>\n
\nAnd what are the steps to follow in that best-practice-based design?<\/p>\n\n
What changes when an MSP reuses with criteria<\/h2>\n
\n
How Pandora FMS helps reuse automations across MSP clients<\/h2>\n
\nObviously, our bet to make the reuse process easier is Pandora FMS. And it is impossible for me to talk about it without bias; it is the tool I know and the organisation that names every one of its own servers after a Star Trek reference. However, what I can guarantee is honesty worthy of the Federation and that we sell technology, not smoke and mirrors.
\nPandora FMS<\/a> is designed from the trenches of the multi-client environment<\/strong>, where reusing without losing control is daily bread.
\nIts reusable templates and policies<\/strong> encode operational knowledge once and apply it to all clients of the corresponding type. This way, a new device inherits the policy it needs without manual intervention or oversights.
\nThe possibility of segmentation by groups and clients<\/strong> enables the necessary separation when operating as multi-tenant.
\nThe inventory and operational context<\/a> prevent acting blindly, and centralised visibility<\/strong> from the Metaconsole provides a single pane of glass<\/A> to supervise every environment<\/a> without blinking, like a benevolent Palantir that only corrupts your soul just enough.
\nAdded to all this is action traceability<\/strong>.
\nWith Pandora FMS, what was executed, with which version and with what result is recorded, something key for healthy change management<\/a> and audits that do not turn into everyone pointing fingers at everyone else.
\nAnd if security is part of the service (I do not know whether there is any environment left where it is not, especially in the current context), Pandora SIEM<\/a> unifies the event console<\/a> and reduces alert overload<\/a>, aligning with reference frameworks such as those from ENISA<\/a> or CISA<\/a>.
\nThus, multi-client management scales in operations and security without control falling by the wayside.<\/p>\nConclusion<\/h2>\n
o resuelve tus dudas sobre nuestras licencias<\/p>\n