The engine behind businesses that run on autopilot
We build the custom software, apps and automation that take the manual work out of a business - then we run our own products on the same stack, so we live with every decision we make rather than handing it over at launch.
The switch in the logo is a real one - click it to turn the site monochrome.
Seven things, done properly
Most of what businesses need falls into a handful of shapes. We would rather be genuinely good at these than list twenty services we do occasionally.
Custom Software
Software built around exactly how your business runs.
Read moreWeb & Mobile Apps
Fast, polished apps your customers and team actually use.
Read moreBusiness Automation
Workflows that run themselves, day and night.
Read moreAI Integration
Practical AI wired into the tools you already use.
Read moreCRMs & Client Portals
Your data, your process, your portal - built to fit.
Read moreWebsites with Built-in Software
Sites with booking, quoting and portals built in.
Read moreOne-Page Websites
One page, built properly, for a sensible price. Live in days.
Read moreWhat a Tuesday looks like
- 01Enquiry arrives in the shared inbox
- 02Someone reads it and works out what it is
- 03Details typed into the spreadsheet
- 04Quote built by hand from the price list
- 05Quote emailed, then chased on Thursday
- 06Accepted job typed into the diary
- 07Typed again into the invoice
- 08Typed a third time into the accounts
Products, not just projects
Any developer can show you something they delivered. Fewer can show you something they still run, where they carry the consequences of their own decisions. Three of these are ours, and one of those is sold to other businesses as well as used in our own.
RampDesk
Garage management software for the motor trade - enquiries, quotes, bookings, job cards and invoices. Tuning work too.
Read the case studyNearOps
Bookings, dispatch, coverage zones, payments and payouts for service businesses, under their own brand.
Read the case studyJF Automotive
A full website rebuild with a built-in vehicle registration lookup.
Read the case studyRemaps UK
Enter a registration, see your real power figures in seconds, before giving any details.
Read the case studyTuning File Portal
Dealer uploads a file, automated matching and multi-gate verification return a tuned file.
Read the case studyThree things we do differently
Our own software runs on this
RampDesk and NearOps are ours - live, paid for by other businesses, supported by us. So we handle the migrations, the edge cases and the unglamorous parts of year two. Not as theory. They're our Monday morning.
You own everything, from commit one
Repository under your account. Infrastructure in your accounts, billed to you. No licence, no buy-out, nothing that makes leaving us difficult. We do not build dependency on ourselves as a retention strategy.
We've built the awkward parts
Checkout and card payments. Finance at the point of sale. Dealer portals and trade pricing. Registration lookups against live vehicle data. These are the parts that go wrong quietly and late, and they are the ones we have already shipped.
Where we know the ground
Two sectors we know from the inside, because we've built and run products in them. We work across others too.
Six stages, and you can stop after any of them
The expensive mistake in software isn't the build. It's discovering in month five that the wrong thing got scoped in week one. Every stage below exists to make that less likely.
Discovery
We map how the work actually happens, workarounds included. You get a written plan you own.
Design
How it works before how it looks, reviewed with the people who will use it daily.
Build
Shipped in slices you can run on, each built on what the last one taught us.
Migrate
Its own phase with its own budget. Rehearsed more than once before anything goes live.
Launch
Gradual where possible, with the old system still readable while people learn the new one.
Run or hand over
Keep us on, or take it in-house. Neither option needs a negotiation.
Written to be useful, not to rank
Things we get asked often enough that they are worth writing down properly.
How much does custom software actually cost?
Nobody in this industry wants to answer this question in public. Here is why the numbers vary so much, what actually drives them, and how to tell a real estimate from a hopeful one.
Read Custom software & cost · 7 min readSeven signs your business has outgrown its spreadsheet
Spreadsheets are brilliant, which is the problem. They are good enough for long enough that businesses only notice the cost once it is substantial.
Read Automation & AI · 8 min readWhat to automate first (and what to leave alone)
Most automation projects start with the most impressive-sounding process. That is almost always the wrong place to begin, and it is why so many of them stall.
Read Custom software & cost · 8 min readOff-the-shelf CRM vs custom: how to decide
Most businesses should use an off-the-shelf CRM. This is written by a company that builds custom ones, so take that as meaning something.
ReadWhat would this actually take?
Flip the ones that are true. The more that are, the bigger the thing worth building - and the more of it we have already built for someone else.
Nothing flipped yet
Turn on whichever statements are true for your business. The verdict updates as you go.
This is a rough guide, not a quote. The only way to know properly is to map the process, which is what discovery is for.
Straight answers
What does The Software Engine do?
We build custom software, web and mobile apps, business automation and AI integrations for companies in the US and UK. We also build and run our own products: RampDesk, garage management software for the motor trade, and NearOps, a white-label platform for mobile field service teams.
Where are you based?
The company is registered in Nevada, USA, and the team is based in the United Kingdom. We serve clients in both countries, which means we cover US and UK working hours between us and we're used to projects that span both - including the practical details like date formats, postcode and ZIP handling, tax fields and currency.
How do projects start?
With a short paid discovery phase. It produces a scoped plan with a cost range, plus an explicit list of what the software will not do - usually the more useful half. That document is yours whether or not you build with us, including taking it to another supplier for comparison.
What happens if we want to leave?
You take it, and there's nothing to unpick - the repository is already yours, the hosting is already billed to you, and the deployment steps are written down. In practice a handover takes anywhere from a day to a week, depending on the size of the project. The reason it's that simple is that we never wired anything to ourselves in the first place.
What is the most complicated thing you have built?
Probably JF Automotive, where one site carries a shop with accounts and checkout, Klarna finance at the point of sale, a dealer portal, trade accounts on their own pricing, and a registration lookup that has run more than 10,000 times - all sharing one set of records rather than three. RampDesk is the bigger system, but that one has the most moving parts touching a customer at once.
How long before we see something working?
Discovery is typically two to three weeks. A first usable release is usually weeks rather than months. We scope it to the core path and leave the rest for later (there's always a rest). Getting something real in front of users early is what tells us whether the plan was right. A longer build against untested assumptions tells you nothing until the end.
Tell us what is slowing you down
A short conversation is usually enough for us to tell you what it would take to fix it, and what it would cost you to leave it alone.