An IT company for software and infrastructure
Every tanglehas a route.
We build websites, apps and business software, and connect the networks, servers, backups and firewalls behind them. One clear plan, documented and handed over to you.
- A person replies
- A written next step
- No obligation
- Web & mobile— Fast, accessible websites, customer portals and mobile apps, designed around what people need to get done.
- Software & integrations— Internal tools, dashboards and integrations that replace fragile spreadsheets and connect the systems you already pay for.
- Servers & cloud— On-premises servers, cloud and hybrid infrastructure set up, maintained and documented so it keeps running.
- Networks— Wired and wireless networks, internet links and site-to-site connections that are planned, documented and dependable.
- Firewalls & security— Firewalls, access controls and sensible security habits that reduce your most likely risks.
- Backup & recovery— Backups designed around how quickly you need to recover — and tested by actually restoring from them.
- Automation— Automated workflows that remove copying, chasing and re-typing between people and systems.
- Design: Understand the problem and plan the route before anything is built.
- Build: Websites, apps and business software, made to be maintained.
- Connect: Networks, servers and integrations that tie it all together.
- Protect: Backups you can restore and security that fits the real risks.
- Improve: Automate repetitive work and keep refining what is there.
01What we do
One partner for the product and the plumbing.
Most organizations need two kinds of technology help. They need digital products — websites, portals, apps and business software. And they need the infrastructure those products depend on — networks, servers, backups and security.
These are usually bought from different people who never speak to each other. Solutionist treats them as one system, because that is how they fail and how they succeed.
Follow the work
See the whole route.
A request, a working day, a restore. Follow the connections behind the things your business needs to do.
Illustrative flow — not a client project
From a tap to a task.
A digital service depends on more than the screen. Here is a simplified view of the work behind it.
Make the first step easy.
A customer uses a website or mobile app to send a request, book a visit or place an order.
Explore this serviceA request entered once, routed to the right person, with the supporting systems documented.
Plan a route for your businessA customer request
A digital service depends on more than the screen. Here is a simplified view of the work behind it.
- Make the first step easy.
A customer uses a website or mobile app to send a request, book a visit or place an order.
- Control the entry points.
Firewall rules and access controls reduce exposure. They are one part of a wider security plan.
- Connect the people and systems.
The network carries the traffic between staff, applications and the infrastructure they use.
- Give the service a home.
Server or cloud infrastructure runs the application, with maintenance, monitoring and clear ownership.
- Enter it once.
An integration transfers the request into your business software, with validation and a visible record.
- Move the work forward.
Rules assign the next task and send a notification. Exceptions go to a person who can make a decision.
- Plan for a way back.
Separate copies and restore tests support recovery. What is covered and the recovery targets are agreed in advance.
A request entered once, routed to the right person, with the supporting systems documented.
A connected office
An office move is a chance to connect the basics properly, before the first working day.
- Start with the floor plan.
Plan cabling, switches and Wi-Fi around the places people work, with separate access for guests.
- Set the boundaries.
Configure the firewall, remote access and staff permissions deliberately, then document the remaining risks.
- Connect the shared tools.
Set up accounts, files and applications on infrastructure sized for the way the team works.
- Include the new site.
Check that important data is included in the backup scope and test restoration to a suitable location.
- Make routine work repeatable.
Use documented onboarding and recurring checks, with alerts that reach a person when something needs attention.
A documented office setup, clear access rules and a recovery plan your team can use.
A tested recovery
A restore rehearsal makes the recovery plan concrete. This example is a planned test, not an incident response service.
- Choose the recovery point.
Identify the right copy and confirm that it contains the agreed data. Recovery depends on the available copies.
- Prepare the destination.
Restore to an appropriate test environment so the original system can keep working while the copy is checked.
- Check access before reconnecting.
Review permissions and the test environment before restoring access. A restore does not remove every security risk.
- Test the route back.
Check that the intended users can reach the restored service through the right network connections.
- Verify the work, not just the files.
Open the data, check the application and its connections, and record the result in the recovery runbook.
A verified test restore and a written record of what worked, what took time and what still needs attention.
02Services
Four groups. Seven services. One system.
Each service stands on its own, and each is designed to connect cleanly to the others. Start with the problem in front of you; we will show you what it touches.
Build
The software your customers and staff actually use.
- B1Websites, web platforms & mobile appsFast, accessible websites, customer portals and mobile apps, designed around what people need to get done.Learn more
- B2Custom business software & integrationsInternal tools, dashboards and integrations that replace fragile spreadsheets and connect the systems you already pay for.Learn more
Connect
The networks and servers everything runs on.
Protect
Backups you can restore and defences that fit.
Improve
Less copying, chasing and re-typing.
03How we work
From tangle to route, in five steps.
Every engagement — a website, a server migration, a backup plan — follows the same route. You always know where we are and what you will receive next.
Listen
We learn how your organization works and what is getting in the way. No jargon, no hard sell.
You receiveA written summary of the problem as we understand it
Map
We trace the systems, data and people involved, and find where the real knot is.
You receiveA map of what exists today and what it depends on
Route
We propose the simplest route that solves it — with scope, cost, timing and trade-offs in plain language.
You receiveA proposal you can compare, question and approve
Build
We deliver in visible increments, test as we go and keep you informed at every checkpoint.
You receiveWorking results at agreed checkpoints
Hand over
Documentation, credentials and training in your name. Then ongoing support if and when you want it.
You receiveEverything you need to run it without us
04What you can hold us to
Promises we can actually keep.
We do not have a portfolio of logos to show you yet. Instead, here is how we will work with you — in writing.
Plain language
Every proposal, report and recommendation is written so a non-specialist can make a decision from it.
You own everything
Accounts, code, credentials and documentation are in your name. No lock-in, no hostage situations.
The simplest route
If an off-the-shelf product or a small change solves it, we will say so — even if it means less work for us.
Careful claims
We tell you what a measure does and what risk remains. We never promise that anything is unbreakable.
Documented work
Anything we set up is documented well enough for another qualified person to take over.
Honest scoping
If something is outside what we do well, we will tell you and help you find the right specialist.
05A new company
New, on purpose.
Solutionist is a young company. That means you work directly with the people doing the work, decisions are made quickly, and every early client relationship matters enormously to us.
It also means we will not dress it up. You will not find invented statistics or borrowed logos here — just a clear description of what we do and how we do it.
06Before we start
A few useful answers.
You can start with one problem. We will help you work out what it needs.
Can we start with just one service?
Yes. A website, a network review or a backup test can be a project on its own. We look at what it depends on and recommend other work only when it is useful.
Can you work with systems we already have?
We start by reviewing what is there, how it is used and who owns it. Keeping or improving an existing system may be the simplest route. We explain any limits before proposing changes.
How are cost and timing agreed?
After understanding the problem, we propose a written scope, priorities, cost and timeline. Equipment, licences and ongoing services are identified separately so you can make an informed decision.
What do we receive at handover?
The agreed work, documentation and access in accounts you control. For custom software, that includes the source code and instructions for running it. Support and maintenance can be scoped separately.
Bring us the tangle.
Tell us what is not working, or what you want to build. We will reply personally with questions and a practical next step.
- Personal reply
- Written next step
- No obligation