Start a conversation

Connected business applications · portals · data workflows

Connect the work, not just the systems.

Atomic for IT builds the software that sits between the parts of a complex organisation: portals for the people outside it, applications for the teams inside it, and data workflows that keep the two in step. We are a London-registered software practice working with UK organisations whose processes have outgrown a patchwork of tools.

Start a conversationMap your connections

Upper floors of a corten steel and glass building, with lit open-plan offices behind the glazingIllustrative image

Why we exist

The problem we are hired for

Most organisations do not lack software. They have too many places where the same fact lives, and too many people whose job has quietly become copying it between them.

A sales system, a finance package, a case tool, several shared drives and a handful of critical spreadsheets: each was a reasonable decision at the time. Together they create re-keying, delay and disagreements about which figure is right. Customers feel it as slow answers. Staff feel it as busywork.

We do not start by proposing a single platform to replace everything. We start by understanding where information is created, who needs it next and what has to be true about it when it arrives. Then we build the smallest set of connections, portals and applications that removes the copying, using the systems you already pay for wherever they are sound.

Capabilities

Four ways we connect an organisation

Scroll sideways, or use the links to read each in depth.

Portals

Secure web areas where customers, partners or suppliers submit information, upload documents, follow progress and download what is theirs, without emailing anyone to ask.

Portals

Connected applications

Internal tools that read from and write to your existing systems, so a team works in one place while the record stays where it belongs.

Applications

Data workflows

Scheduled and event-driven transfers between systems with validation, exception queues and a readable log of every run.

Data workflows

Reporting foundations

Clean, reconciled datasets with written definitions, ready for whatever reporting tool you already use. We build the foundations, not dashboards for their own sake.

Reporting data

Diagnose

Which symptom sounds familiar?

The same details are typed into three systems

We map where each field is first created and which system should own it, then build the connection that passes it on, with a log of every transfer so a mismatch is visible within minutes rather than at month end.

Polished stone floor and glazed ground floor of an office building

How we connect

Map. Agree. Connect. Prove. Hand over.

  1. Map where each piece of information starts, travels and ends up, including the spreadsheets and inboxes.
  2. Agree which system owns each fact, and what “correct” means for it, in a short written data agreement.
  3. Connect in thin slices, one flow or one portal journey at a time, using published interfaces.
  4. Prove each slice with real data in a test environment, including what happens when things fail.
  5. Hand over with documentation, monitoring notes and an agreed support arrangement.
Read the approach

Deliverables

What you receive

Deliverables
Connection mapA plain diagram and table of your systems, the flows between them and who owns each piece of information. Useful even if you never build anything with us.
Data agreementField-level definitions, ownership, validation rules and what happens to records that fail them.
Working softwarePortals, applications and workflows deployed to environments you control, delivered in usable slices.
Run bookHow each workflow is scheduled, monitored, retried and paused, written for the person who will look after it.
Source and accessAll code in your repository, all credentials in your accounts, nothing held hostage by us.

Scope

Honest limits

We do

  • Design and build software that connects business systems
  • Work through published APIs, exports and secure file exchanges
  • Advise on structure, ownership and sequencing
  • Support what we build during UK working hours

We do not

  • Install cabling, routers or other network hardware
  • Provide round-the-clock operations or on-call cover
  • Resell software licences or take vendor commissions
  • Promise that every legacy system can be connected cleanly

Some older systems have no usable interface. When that is the case we say so early and offer the realistic options: scheduled exports, a careful manual step with validation, or a case for replacement.

Quality

Standards we work to

  • Every flow is observable. Each run logs what it moved, what it rejected and why, in a place your team can read.
  • Failures are designed, not discovered. We decide in advance what happens when a system is unavailable or a record is invalid.
  • Least access. Integrations use dedicated accounts with only the permissions they need.
  • Accessible portals. External users get keyboard-friendly, clearly labelled interfaces checked against WCAG 2.2 AA criteria.
  • Personal data minimised. We only move fields that a downstream process actually uses.
All standards

Aftercare

Support after launch

Connected systems change around you: a vendor updates an interface, a team adds a field, a partner changes a file format. Our support arrangements are designed for that reality. You get a named contact, acknowledgement of requests within one working day during UK hours, a clear distinction between fixes and changes, and a monthly note on the health of each flow if you want one.

We do not offer emergency out-of-hours cover. Where a workflow is time-critical, we design it to pause safely and alert your team rather than fail silently overnight.

Support and requests

Questions

Common questions

Do we need to replace our existing systems?
Usually not. Most of our work connects what you already have. We will tell you if one system is genuinely blocking progress and why.
How long does a first piece of work take?
A connection map typically takes two to three weeks. A first portal journey or data workflow is often four to eight weeks after that, depending on the systems involved.
Can you work with our internal IT team?
Yes, and we prefer to. They know the estate; we bring focused delivery capacity. We agree who owns what before we start.
Where is everything hosted?
In accounts you control, with a UK or EU hosting region where you need it. We will recommend options and explain the running costs.
What do you need to quote?
A conversation, a list of the systems involved and an example of the process that hurts. The planner on this site produces a useful starting note.

Tell us which two systems should be talking.

Start with one painful flow. We will reply within two working days with questions, a suggested next step or an honest note that we are not the right fit.

Start a conversationUse the planner first