Services organised around decisions

Support, infrastructure, systems, security, and advisory work are useful only when they answer a real operational question.

Service groups

The working scope is covered by a set of service groups; the detail inside each is agreed per engagement.

01

IT support & maintenance

Day-to-day support for the systems a business already runs, from single requests to a standing arrangement.

  • Requests handled through an agreed channel
  • Faults triaged by impact, not by arrival time
  • Maintenance carried out on a schedule you know in advance
IT support & maintenance
02

Infrastructure & network

Workstations, networking, and the equipment the business depends on, set up and documented.

  • Setup, configuration, and documentation
  • Routine checks and fault handling
  • Changes logged so the next person understands them
Infrastructure & network
03

Business systems & software

Business applications and the workflows behind them, from what is needed to what gets used.

  • Requirements gathered before anything is built
  • Rollout and handover included
  • Changes handled as separate, scoped requests
Business systems & software
04

Security & continuity

Backup, recovery, and the day-to-day protections that decide how bad a bad day gets.

  • Backup and recovery arranged and tested
  • Endpoint protection and patch management
  • Security review of the current setup
Security & continuity
05

IT advisory & management consulting

Assessment and planning work for the decisions that are not yet clear: priorities, budget, sequencing.

  • Options with trade-offs, not a single quote
  • Priorities and sequence agreed with you
  • Findings written down so they survive the meeting
IT advisory & management consulting
How we engage

An assessment that ends with a plan.

How we work together is chosen according to how defined the question already is.

What a project looks like

From understanding the situation to reviewing the outcome with you.

01

Understand the situation

What runs today, who uses it, and what has to keep working while we change things.

02

Agree the scope in writing

What is included, what is not, and what happens if the requirement moves.

03

Do the work, with checkpoints

Progress reported at agreed points rather than at the end.

04

Hand over and review

Documentation handed over, then a review of what the setup looks like once it is live.

Questions we get before the first meeting

The questions that come up before anyone commits to a scope.

What services do you provide?

Support, infrastructure, business systems, security and continuity, and IT advisory and management consulting.

Do you only work with businesses in your sector?

No. We start with the systems, people, and operational question in front of the business.

What happens when I get in touch?

We start by understanding the pressure or decision that is waiting, then explain the most useful next step.

What should I prepare?

Bring the question, the current pressure, and anything that must keep working. You do not need a technical brief.

How are fees determined?

Fees follow the agreed scope, the people required, and the checkpoints needed to complete the work properly.

Can you take over an existing setup?

Yes. We begin with an assessment of what is already running, what is documented, and what needs attention first.

Who does Atlantik Tekno work with?

We work with businesses that need a clear answer about technology without stopping the operation around it.

Scope

Not sure which of these you need?

Describe the situation rather than the service name. We will say which group it belongs to, and whether it is a job worth doing yet.

Discuss your needs