01 — Business and domestic software
Software Development
Custom applications for the parts of your business that off-the-shelf software will not fit. Built properly, documented, and handed over in full.
Leicester, United Kingdom
Software, portals and IT that earn their place.
We build custom software, customer portals and the infrastructure underneath them — for businesses that have outgrown the spreadsheet, the shared inbox and the tool that almost fits.
Who we are
A small technical team, taking on the awkward half of your software.
Most businesses do not need a new website. They need the thing behind it to work: the quoting that lives in a spreadsheet, the portal customers keep asking for, the two systems that will not talk to each other.
That is what we do. We scope it properly before quoting, build it in fortnightly slices you can see, and hand it over with documentation so you are never held hostage by the people who wrote it. If the honest answer is that you should buy something off the shelf instead, we will tell you that and charge you nothing for the conversation.
What we do
Four service lines, one team.
Registered with Companies House for software development, information technology services and web portals. In practice they overlap on almost every project — which is rather the point.
02 — Web portals
Web Portals and Platforms
Customer portals, member areas, booking systems and marketplaces. Accounts, permissions, payments and a front end that does not get in the way.
03 — Other information technology services
IT Services and Support
Retained support, hardening, migrations and the quiet maintenance that stops small problems turning into a bad Monday morning.
04 — Hosting, pipelines and resilience
Cloud and Infrastructure
Hosting that fits the workload, deployment pipelines that remove the drama, and backups you have actually tested.
3
Disciplines under one roof
1
Working day to a first reply
100%
Code and accounts in your name
0
Licence fees back to us
Typical projects
The shapes of work we take on.
Different industries, similar problems. If yours is not on this list it is still worth an email — the pattern underneath is usually one of these.
Customer portals
Self-service accounts where customers find documents, track orders and raise requests without emailing your team.
Operations platforms
The internal system that replaces four spreadsheets and a shared inbox, built around how your team actually works.
Booking and scheduling
Availability, capacity and resource rules with reminders, rescheduling and calendar sync that holds up under real use.
Integration layers
The quiet middleware that keeps your accounting, CRM and website in agreement about what happened.
Reporting and dashboards
One screen that answers the question your management meeting starts with, built on data you can trace.
Marketing sites that convert
Fast, accessible, well-structured sites your marketing team can edit without breaking the layout.
Sectors we know our way around
- Professional services
- Property and lettings
- Trades and field services
- E-commerce and retail
- Education and training
- Logistics
- Healthcare administration
- Membership bodies
How it runs
From a first conversation to something in production.
No surprises, no three-month silence, no invoice you did not see coming.
01
Conversation
Week 0
Thirty minutes, no charge, no deck. You describe the problem in your own words and we ask the awkward questions. By the end of it we both know whether this is worth taking further.
You get: Outline of the problem, rough budget range, honest yes or no
02
Discovery
Weeks 1–2
A short paid engagement where we sit with the people who will use the thing. We map the current process, find the edge cases that break naive designs, and write it down.
You get: Written specification, wireframes, milestone plan, fixed price for phase one
03
Build
Weeks 3+
Two-week cycles with something you can click at the end of each one. You see progress continuously, which means course corrections cost days rather than months.
You get: Working software on a staging URL, updated every fortnight
04
Launch
Launch week
Data migrated and reconciled, team trained, rollback rehearsed, go-live in a planned window. We stay close for the first month while real use finds the last few edges.
You get: Live system, trained team, documentation, thirty days of included support
05
Operate
Ongoing
Monitoring, patching, backups and a monthly written report. Or a clean handover to your own team with everything they need. Both are a good outcome for us.
You get: Retained support, or full handover with documentation
Why clients stay
Four things we will not compromise on.
01
Plain English, always
You should never leave a meeting with us unsure what was agreed. We write specifications, quotes and reports in language you can forward to a colleague without translating first. If a technical trade-off matters to your decision, we explain the trade-off rather than the technology.
02
We own the outcome
The job is not finished when the code is written. It is finished when the thing works in your business, with your data, used by your people. That means we care about training, migration and the week after launch as much as the build itself.
03
Built for handover
Every project is built as though someone else will maintain it, because one day someone will. Readable code, sensible structure, written documentation and accounts in your name. Nothing we build depends on us staying.
04
Senior hands, small book
You get the people who scoped the work doing the work. We deliberately keep a small number of clients so that when you call, you are not explaining your business from scratch to someone who joined last week.
Insights
Things worth knowing before you spend money.
The backup you have never restored is not a backup
Backups fail quietly and are only discovered at the worst possible moment. The fix is boring and takes an afternoon.
What a good technical specification actually contains
A specification is not a wish list. It is the document that lets two parties agree on what "finished" means before anyone writes code.
Build, buy or configure: deciding before you spend
Most software decisions are made backwards — the tool is chosen, then the business bends around it. Here is a way to get the order right.
Start here
Tell us what you are trying to build.
A short conversation is usually enough to tell whether we are the right team for the job. No sales script, no obligation.
We reply within one working day. No sales sequence, no pressure.