Nexxiv Technology · November 4, 2026

When a video call drops or a payment device disconnects, the internet connection often gets the blame. Sometimes that is correct. In other cases, the problem sits between the device and the router: weak coverage, interference, congestion or a poorly configured network.

Identify where the problem occurs

Start by recording the affected device, location, time and application. Check whether other people experience the same issue. If a wired computer remains reliable while nearby wireless devices struggle, that points towards the local wireless connection, although further testing is still needed.

Test during a normal busy period. An empty office can make a network look healthier than it is. Avoid buying a faster internet plan before establishing whether the internet service is the limiting factor.

Coverage is not the same as capacity

A device may display Wi-Fi bars and still have a poor connection. Walls, distance, neighbouring networks and the device’s own radio all influence performance. Communication works in both directions: a powerful access point does not necessarily hear a small device reliably at the edge of coverage.

Capacity matters too. More staff, video meetings, cloud applications and connected equipment can place pressure on a single wireless unit. Adding more access points without planning their placement and channels can create additional interference rather than improve the experience.

Separate the network’s jobs

A typical consumer router combines routing, switching and wireless access in one box. That can be adequate in a small, simple space. A larger workplace may benefit from separate access points placed where coverage is needed, supported by suitable switching and routing equipment.

Business access points can be centrally configured and monitored, depending on the system. Their value comes from the design and management around them, not the label on the box. The equipment still needs updates, secure administration and documented settings.

Build on reliable cabling and power

Wired connections are useful for fixed equipment and access-point uplinks where practical. They reduce the amount of traffic that must cross a wireless link. Cabling work should be planned with an appropriately qualified cabler, including outlet locations, testing and identification.

Power over Ethernet can supply compatible access points through their network cable. Check the required PoE standard, the power available on each port and the switch’s total power budget. Compatibility should be confirmed against the exact equipment specifications. An available network port does not automatically mean enough power is available.

Keep guest access separate

Visitors generally need internet access, not access to business files or printers. A guest wireless name is only part of the arrangement; network separation and firewall rules must enforce the intended boundary. Test the result rather than assuming the label creates isolation.

Other equipment, such as cameras or specialised devices, may also need separate treatment. Segmenting a network should solve a practical security or operational requirement, with clear documentation so future changes remain manageable.

Plan for the workplace you actually have

A compact office, a warehouse and a business with outdoor working areas have different requirements. Consider building materials, device types, movement between spaces and expected growth. Placement testing and a site assessment can prevent unnecessary purchases.

The outcome should be reliable access in the areas that need it, an understandable network layout and a supportable configuration. Keep a record of equipment, connections and administrator access. Business Networks & Wi-Fi covers this wider environment, rather than treating every connectivity issue as a router replacement.

Further reading: Ubiquiti Wi-Fi connectivity guidance; Ubiquiti Wi-Fi troubleshooting; Ubiquiti PoE requirements.

Nexxiv Technology · November 4, 2026

A good IT provider should make responsibilities easier to understand. The business should know how to obtain help, who maintains its systems and which decisions still need the owner’s approval. The words “IT support” alone do not define any of that.

Make support straightforward

Staff need a clear reporting channel and a process that captures enough information to investigate an issue. The provider should explain how urgency is assessed, how progress is communicated and when an issue needs escalation. A business-wide outage and a routine software request should not be treated as identical.

Check the support hours, response arrangements and boundaries in the agreement. Do not infer around-the-clock coverage or a guaranteed resolution time from broad marketing language. Ask how urgent work outside the agreed hours is handled, including whether it is available at all.

Maintain the environment between incidents

Under a managed service, routine activities may include device monitoring, patching, account administration and security checks. The important question is what happens when a check fails. An alert that is collected but never investigated provides little operational value.

Ask which systems are included and how exceptions are recorded. Computers, network equipment, cloud services and specialist applications may have different owners or support arrangements. The scope should make those boundaries visible rather than leaving staff to discover them during a fault.

Keep useful documentation

The provider should maintain enough information to support the agreed environment consistently. Depending on scope, that can include device records, network diagrams, key suppliers, subscriptions, configuration notes and recovery procedures.

Business ownership matters. Domain names, tenants and essential services should remain under the company’s control, with appropriate authorised access. Agree how documentation and access will be handed over if the relationship changes. This is ordinary business continuity, not a sign that a provider is distrusted.

Handle staff and access changes properly

Joining, moving roles and leaving should follow a repeatable process. Someone must authorise access, confirm what the person needs and ensure the work is completed. Offboarding should account for business records and connected applications as well as the primary email account.

The provider also needs timely instructions from the business. A well-designed checklist makes that dependency clear: who approves the request, what information is required and how completion is confirmed.

Provide advice that supports decisions

Useful advice connects technical work to the way the business operates. It explains why a change is needed, the options available, likely disruption and the consequences of deferring it. Owners should be able to distinguish necessary maintenance from an optional improvement.

Projects need their own scope, responsibilities and acceptance criteria when they fall outside the ongoing agreement. Vendor coordination should also be defined. The IT provider may help investigate an internet or application issue without being responsible for the other supplier’s service.

Take recovery seriously

Backup and continuity responsibilities should be explicit. Identify who checks backup jobs, investigates failures and tests restores. Agree which data and systems are covered, and where gaps remain. Recovery planning should reflect how the business would actually resume work after disruption.

Ask for reporting that highlights exceptions, unresolved issues and decisions needing approval. A long list of successful automated tasks is less useful than a clear explanation of what still needs attention.

Compare proposals against the same scope

Write down the services the business needs before comparing providers. Include devices, staff, locations, essential applications and expected support arrangements. A lower fee is not directly comparable when the underlying responsibility is narrower. Managed IT Support and IT projects can complement each other when their boundaries are clear.

Nexxiv Technology · November 4, 2026

Microsoft 365 and Google Workspace can both support a well-run small business. The better choice depends on existing workflows, the documents staff create and the controls the business needs. Moving platforms simply because another company prefers one can add disruption without solving the actual problem.

Start with the applications people rely on

List the everyday tasks before looking at subscriptions. Include email, calendars, meetings, shared files, spreadsheets and any industry software. Test the documents that matter: a complex workbook, a formatted client report or a template used by an external accountant.

A business already dependent on desktop Office applications and Windows administration may find Microsoft 365 a natural fit. A team that works primarily in a browser and collaborates in Google Docs may prefer Workspace. Neither observation replaces testing the actual workflow.

Email and collaboration

Both ecosystems provide business email, calendars and collaboration tools. The daily experience differs: Outlook and Teams have their own conventions, as do Gmail and Google Meet. Existing staff familiarity affects training and the speed of a transition.

Consider shared business addresses, mailbox delegation, meeting-room needs and how staff collaborate with customers. A familiar inbox is useful, but the surrounding processes matter just as much. Make sure the chosen subscription supports the way the business intends to use these features.

File ownership and document management

Microsoft combines OneDrive, SharePoint and Teams for personal working files and team collaboration. Google offers My Drive and shared drives, with capabilities and administrative controls depending on the edition. In either system, shared business records should have a deliberate home and an access model that survives staff changes.

Check external sharing, version history, offline work and file compatibility. A demonstration with an empty folder can hide problems that appear when years of business files are moved. Trial representative documents and ask staff to complete real tasks before committing to a migration.

Administration and security

Both platforms offer account and security controls, but feature availability varies by plan. Compare the requirements first: MFA, device management, administrator roles, external sharing, logging and information retention. Then check which edition provides the necessary capabilities.

Microsoft may suit environments seeking closer integration with Windows devices and the broader Microsoft ecosystem. Google’s browser-focused experience may suit teams with simpler application requirements. Neither platform becomes well managed automatically after a subscription is purchased. Someone must configure it, maintain accounts and review changes.

Look beyond the licence price

The total cost includes migration, training, support, backup arrangements and any additional applications required. A cheaper subscription can become less attractive if a business must separately buy software that is already central to its work.

Compare equivalent requirements, not merely the lowest advertised tier. Check commitment terms, included applications and applicable taxes directly with the supplier when making a purchasing decision. Avoid paying for overlapping services during a migration longer than necessary, while allowing enough time to validate the new environment.

Use a small pilot to decide

Choose a few representative users and test the difficult workflows. Confirm access from the devices they actually use, including mobile and remote working arrangements. Record gaps and assess whether a configuration change, staff training or a different platform is the better answer.

If the current platform meets the business’s needs, improving its configuration may be more valuable than moving. Where a move is justified, plan data mapping, permissions, cutover timing and post-migration checks. A structured migration should preserve usable business information, not simply transfer a volume of files.

Further reading: Microsoft file collaboration planning; Google shared drives; Google Drive for business.

Nexxiv Technology · November 4, 2026

Cyber security starts with everyday administration: who can sign in, which devices are maintained and whether important information can be recovered. A business does not need to begin with an extensive shopping list. It needs a clear view of its environment and someone responsible for keeping the fundamentals working.

1. Protect account access with MFA

Multi-factor authentication adds a check beyond a password. Prioritise business email, administrator access, remote access and important cloud applications. Use phishing-resistant methods where supported and appropriate, and provide staff with clear enrolment and recovery instructions.

Do not stop at telling people to turn it on. Check which accounts are actually covered, investigate exceptions and remove stale access. Staff should know not to approve unexpected sign-in prompts. Recovery methods also need protection because they can become an alternative path into an account.

2. Maintain operating systems and applications

Updates address faults and security weaknesses, but an update policy is only useful when installation succeeds. Keep a device and software inventory, schedule updates around business needs and follow up on machines that remain offline or report errors.

Include browsers and business applications as well as the operating system. Review unsupported software and hardware rather than assuming an old system can be maintained indefinitely. Where an application cannot be updated immediately, record the reason, the temporary controls and a plan for resolution.

3. Manage endpoint protection

Computers need suitable protection that remains enabled, current and visible to whoever manages IT. An installed product is not the same thing as a monitored control. Agree who reviews alerts, how suspicious activity is investigated and when the business is contacted.

Endpoint protection works alongside secure configuration, patching and user awareness. It does not guarantee that a device cannot be compromised. Device encryption and sensible screen-lock settings can also reduce exposure when equipment is misplaced or accessed by someone else.

4. Give people the access they need

Use individual accounts and grant permissions according to the person’s work. Restrict administrative privileges to situations that need them. A staff member who processes invoices should not automatically receive access to every confidential folder or system setting.

Review access when roles change and when people leave. Include contractors, old supplier accounts and applications connected to the business tenant. Keep a secure record of ownership and recovery access so the company is not dependent on a forgotten password or an unavailable former employee.

5. Make recovery a practical capability

Identify the files, cloud services, configurations and records that matter to operations. Define how much recent work the business could afford to lose and how long it could operate without those systems. Those answers should guide the backup arrangement.

Backups need appropriate separation and access protection so a problem with the primary environment does not automatically affect every recovery copy. Check job failures and test restoration. A successful backup notification does not prove that a full business process can be recovered within the time available.

Turn the basics into routine work

Assign an owner to each control and record what is implemented, what remains unresolved and when it will be checked again. Staff need a simple way to report suspicious messages or unusual behaviour without delaying because they are unsure who to contact.

These five areas are a foundation, not a complete assessment or a claim of compliance with a framework. The right controls depend on the business, its applications and the information it handles. Nexxiv’s cyber security approach centres on configuration, maintenance and practical risk reduction.

Further reading: ASD’s ACSC small business cyber security handbook; Microsoft MFA guidance.

Nexxiv Technology · November 4, 2026

Microsoft 365 can be central to a small business without being properly configured. Email may work while administrator access, file ownership and recovery arrangements remain unclear. A good setup starts with the way people work, then connects the right controls to those requirements.

Give every person a clear identity

Use individual business accounts for staff so access can be granted, reviewed and removed deliberately. Avoid passing one person’s sign-in around the office. Keep an account register with an owner, role and current licence assignment. It makes onboarding and offboarding easier and gives the business a clearer picture of what it is paying for.

For addresses such as accounts@ or reception@, a shared mailbox may be appropriate. Staff access it through their own permitted accounts rather than sharing its password. Microsoft says the associated shared-mailbox account should remain blocked from direct sign-in. Storage, advanced features and the accessing users’ licences still need to be checked.

Protect ordinary and administrator access

Enable multi-factor authentication using a suitable approach. Microsoft recommends security defaults or Conditional Access. Conditional Access supports more specific access rules where the relevant licensing is available; it needs careful design and testing so essential users and services are not accidentally locked out.

Administrative work should use appropriately restricted administrator access rather than giving everyone broad privileges. Document emergency access and recovery arrangements securely. The business should retain control of its tenant even when an external provider handles day-to-day administration.

Decide where business files belong

OneDrive is associated with an individual user’s working files. SharePoint provides shared libraries for team information, and Teams connects collaboration with the underlying Microsoft 365 services. These products work together, but they do not remove the need for an understandable filing structure.

Define shared locations around business functions, with permissions that reflect actual responsibilities. Explain where staff should save final documents, how they should share externally and who approves access. Avoid building the whole company filing system around one employee’s personal work area.

Include the devices people use

Account protection is only part of the environment. Decide how computers are enrolled, updated and protected, and how business information is handled on personal devices. Available device-management and security capabilities depend on the subscription and device platform. A licence should be chosen against a requirement rather than its name alone.

Record device ownership, encryption and recovery information where applicable. Plan how lost devices and staff changes will be handled before either event occurs. Configuration needs ongoing review as the business changes.

Separate file synchronisation from recovery planning

Synchronisation makes files available across locations; it can also synchronise deletions. Version history, recycle bins and retention features provide recovery options, but their scope and time limits matter. Do not assume every item is retained indefinitely or that every recovery scenario is covered.

List the information the business needs to recover, the acceptable loss of recent work and how quickly it needs access again. Compare those requirements with the configured native features and any backup service. Test a restore, document the result and assign someone to review failures.

Make staff changes repeatable

A short checklist should cover accounts, groups, applications, devices, mailbox handling and file access. Offboarding must also consider session access and the preservation of business records before accounts or licences are removed. Microsoft 365 administration works best as a maintained environment rather than a one-off installation.

Further reading: Microsoft shared mailboxes; Microsoft MFA guidance; Microsoft file collaboration; ASD backup and operational management.

Nexxiv Technology · November 4, 2026

A small business does not need a managed IT agreement simply because it owns computers. The more useful question is whether someone is consistently looking after the systems the business depends on. When that responsibility sits between the owner, an office administrator and whoever last fixed the printer, important work can fall through the gaps.

Look at the work being interrupted

Occasional problems are normal. A pattern of staff losing time to login issues, slow devices, missing files or unreliable connectivity deserves a closer look. Keep a simple record for a fortnight: what failed, who was affected, how long it took and whether the same issue had happened before. That gives a more useful starting point than counting support calls alone.

Include the time spent finding help and explaining the environment again. A ten-minute fault can interrupt an hour of work when nobody knows who has the administrator account or which supplier is responsible.

Check whether the routine work has an owner

Updates, account reviews and device checks are easy to postpone when everything appears to work. The test is whether these jobs happen on a schedule and whether someone follows up on failures. A green update notification on one laptop says little about the rest of the business.

• Is there an up-to-date list of computers, software and subscriptions?
• Can authorised people recover access if the usual administrator is unavailable?
• Are new starters given the right access before their first day?
• Are departing employees’ accounts and access dealt with promptly?
• Has anyone checked that important information can actually be restored?

Unclear answers do not mean every system must be replaced. They indicate that ownership and documentation need attention.

When ad hoc support can be sufficient

A simple environment with few devices, limited changes and a capable person responsible for routine administration may only need occasional specialist assistance. A defined project can also solve a specific problem: replacing a network, organising shared files or moving email platforms.

The important distinction is that ad hoc support is normally engaged for an identified task. Unless the arrangement says otherwise, it should not be assumed to include continuous monitoring, regular maintenance or responsibility for issues that have not been reported. Agree who handles those activities between visits.

When ongoing management makes sense

Managed IT becomes more useful as the cost of disruption increases. More employees, remote work, sensitive information and a growing collection of applications all add administration. The owner may still understand the technology but no longer have time to maintain it properly.

An ongoing arrangement can put support, maintenance, user administration and technology planning under a defined scope. It should make responsibilities clearer and recurring work more consistent. It does not mean every project, licence or after-hours request is automatically included.

Assess the arrangement, not the label

Before comparing proposals, describe what the business needs to keep operating: email, files, line-of-business applications, internet access and essential devices. Ask what is covered, what is excluded, how requests are prioritised and what happens when another supplier is involved.

A useful service should reduce the amount of technical coordination falling back on staff. Reporting should explain unresolved risks and upcoming decisions in language the owner can use. Read about Nexxiv’s Managed IT Support for the areas an ongoing arrangement can address, or ad hoc IT projects for defined pieces of work.