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.
PortalsConnected business applications · portals · data workflows
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.
Illustrative imageWhy we exist
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
Scroll sideways, or use the links to read each in depth.
Secure web areas where customers, partners or suppliers submit information, upload documents, follow progress and download what is theirs, without emailing anyone to ask.
PortalsInternal tools that read from and write to your existing systems, so a team works in one place while the record stays where it belongs.
ApplicationsScheduled and event-driven transfers between systems with validation, exception queues and a readable log of every run.
Data workflowsClean, reconciled datasets with written definitions, ready for whatever reporting tool you already use. We build the foundations, not dashboards for their own sake.
Reporting dataDiagnose
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.
Customers email to ask where things are
A portal that shows the status you already hold internally, in language customers understand, with notifications only at the moments that matter. The inbox gets quieter because the answer is somewhere.
A workbook joins two systems together
We turn the workbook’s logic into a scheduled data workflow with validation rules, an exceptions queue for a person to review and a clear audit of what changed.
Two teams quote different numbers
We agree definitions first, then build one reconciled dataset with documented rules, so a figure means the same thing in every report that uses it.
How we connect
Deliverables
| Connection map | A 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 agreement | Field-level definitions, ownership, validation rules and what happens to records that fail them. |
| Working software | Portals, applications and workflows deployed to environments you control, delivered in usable slices. |
| Run book | How each workflow is scheduled, monitored, retried and paused, written for the person who will look after it. |
| Source and access | All code in your repository, all credentials in your accounts, nothing held hostage by us. |
Scope
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
Aftercare
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 requestsQuestions
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.