Web applications
Browser-based tools for your team or your customers. They work on any device, with nothing to install, and can grow with your business.
Apps · Hosting · DevOps · Cloud
Your business is unique. Your software should be too.
IT Meadows builds custom web and mobile applications around the way your business works. You talk directly to the engineer building your solution — without unnecessary layers in between. And for teams running software of their own: hands-on DevOps, cloud and platform consulting.
Sound familiar?
Most businesses don’t need more software. They need software that fits.
- spreadsheet.xlsx
The spreadsheet everyone depends on
It started as a quick list. Now it runs half the business, and only one person really understands it.
- copy → paste
Typing the same data twice
Orders in one tool, invoices in another, and someone retyping between them.
- every friday
Admin that eats the afternoon
Reminders, status updates and reports put together by hand, week after week.
- almost fits
Tools built for someone else
Off-the-shelf software that covers most of what you do — and workarounds for the rest.
- someday
The idea that keeps waiting
A customer portal or a field app you’ve wanted for a while, without knowing who to ask.
You don’t need a technical specification to start. A clear description of what’s slowing you down is enough.
01What IT Meadows does
Software shaped around your processes.
From a focused internal tool to a portal your customers use every day — hosted, kept running, and backed by the pipelines, cloud and platforms behind it.
Mobile apps
For work that happens away from a desk — on site, on the road, in the warehouse. Built when a dedicated app genuinely adds value.
Hosting & care, in Europe
Your application hosted in Europe and looked after once it’s live: deployments, uptime and monitoring taken care of, with high availability where your business depends on it. No separate hosting company to coordinate.
DevOps, cloud & platform consulting
For teams that build and run their own software. Hands-on help with delivery pipelines, containers, infrastructure as code, cloud environments and the internal platforms developers rely on — working alongside your engineers.
What that can look like
Examples of what’s possible — not a list of past client projects.
A dashboard
One live overview of jobs, stock or sales, replacing a handful of scattered spreadsheets.
Outcome: See where things stand at a glance
A portal
One clear place where customers or staff submit requests, follow progress and find what they need.
Outcome: Fewer emails asking “any update?”
A workflow tool
Repetitive admin turned into guided steps, with reminders and status updates that happen on their own.
Outcome: Less routine work, fewer things forgotten
An integration
The tools you already use, connected — so information is entered once and shows up where it’s needed.
Outcome: No more retyping between systems
A mobile companion
Photos, signatures, checklists or hours captured on the spot, straight into the system.
Outcome: Paperwork done before you’re back at the office
02Working directly
Built by the person you talk to.
IT Meadows is one independent engineer, not an agency. The person who listens to your problem is the person who designs and builds the solution.
No account-manager layer
Your questions go straight to the person who knows the code.
Fewer handovers
What you explain is what gets built — no retelling along a chain.
Transparent decisions
You hear the trade-offs directly, in plain language, and decide together.
Personal accountability
The person discussing the work is the person doing it.
03Approach
How a project grows.
A proposed way of working — adapted to each project, and always discussed upfront.
Step 01
Listen
We start with your business, not with technology: what happens today, where it hurts, and what better would look like.
Step 02
Scope the first version
Together we define the smallest version that’s genuinely useful, and agree on scope before any building starts.
Step 03
Build in visible steps
You see working software early and often, and can steer while it takes shape.
Step 04
Test and deploy
Tested, released carefully, and handed over with the access and documentation you need.
Step 05
Tend and improve
Once it’s live, IT Meadows can host it in Europe and keep it running — deployments, monitoring and uptime included. Improvements are discussed as people start using it.
04About
Engineering precision, grounded in calm.
During the week I work as a DevOps, cloud and platform consultant for enterprise teams — keeping complex systems deployable, reliable and secure. Alongside that, I build tailored software for smaller businesses.
At weekends you’ll usually find me in the garden, or out in the meadows near home. That’s where the name comes from: IT, and the meadows. Two things I genuinely love — and a fair description of how I like to work.
Working with one person means you always know who’s responsible. The person you talk to is the person building your software.
The mark says it too: an I drawn as circuitry, a T growing out of meadow grass.
05Engineering quality
Software that keeps working after launch.
A feature isn’t finished when it works on a laptop. A background in enterprise DevOps shapes how IT Meadows builds: deployment, maintenance and security are considered from the first day, not bolted on at the end.
Built to be changed
Readable code, sensible structure and documentation, so the application can grow without starting over.
Reliable releases
Repeatable, automated deployments, so updates are routine rather than risky.
Security-conscious
Careful access control, thoughtful handling of data and dependencies kept up to date.
Sensible technology
Proven, well-supported tools chosen for your situation — not for novelty.
Problems noticed early
Monitoring and logging, so issues are spotted and understood quickly.
Clear handover
Documentation and access arranged as part of delivery, so nothing depends on guesswork.
06Questions
Good questions to ask.
Do I need to know exactly what I want to build?
No. Most conversations start with a problem rather than a specification. Describe what’s slow, frustrating or error-prone, and we’ll work out together what’s worth building.
Can you help identify what should be automated?
Yes. Part of the first conversations is looking at how work actually flows — where software would save real effort, and where it wouldn’t be worth it.
Do you build web apps and mobile apps?
Both. Many needs are best served by a web application that works on any device. A dedicated mobile app makes sense when work happens away from a desk, or needs things like the camera or offline use. The right choice depends on your situation.
How do we discuss scope and budget?
Directly and openly. Once the problem is clear, we agree on a sensible first version and talk through scope and budget for it before any building starts. Every project is scoped individually.
Do you also offer DevOps, cloud or platform consulting?
Yes. Alongside building applications, IT Meadows works as a consultant on DevOps, cloud and platform engineering — from delivery pipelines and infrastructure to the platforms development teams build on. What an assignment looks like is agreed together.
Will I work directly with the developer?
Yes. IT Meadows is one independent engineer. The person you talk to is the person designing and building your application.
Can you maintain or improve the application after launch?
That’s something to discuss for your project. Software usually keeps evolving once people use it, and improvements or ongoing support can be agreed based on what you need.
Where is my application hosted, and who keeps it running?
IT Meadows can host your application in Europe and take care of running it: deployments, uptime, monitoring and, where your business depends on it, high availability. You deal with the same person who built it, not a separate hosting company.
Start a conversation
Let’s talk about your idea.
Tell me what you’d like to improve — a process, a spreadsheet, an idea for an app, or the way your software is built and run. No specification needed, and no obligation.
- I read every message myself.
- A rough description is plenty to start.
- Your details are only used to reply.