Skip to main content

Dev Station Technology

Custom software development

Custom software for companies whose process does not fit a licence

We build bespoke web, mobile and enterprise systems for firms in the UK, US and Australia. Our work runs in factories, on construction sites, in vehicle safety testing and in Norwegian schools.

What a scoping call produces

Build orderFeatures ranked, with what we would cut
Architecture sketchStack, integrations, data model
Cost bandA range, never one false number
Team shapeWho works on it, and for how long
Buy or build callIncluding when we say buy

Yours to keep, whether or not you hire us.

500%Rise in potential clients after the Hydrajaws launch
ZeroRecords lost in the Norwegian school migration
6 to 7 hoursAhead of the UK, so we overlap your morning
Week 5First working software in your hands
Buy or build

Build when the licence forces you to work like everyone else

Where custom software starts to pay
A licence that almost fits

The workaround has become the job

  • Someone re-types data between two systems every week
  • Licence cost grows with every head
  • No product models your workflow
Software built for your process

A system you own

  • Reads equipment, sensors and legacy systems
  • Produces the format a regulator dictates
  • You own the code and the IP

When a product already fits, we name the ones worth looking at and stop there. That costs you one call.

Fit check

Is custom the right answer for you?

Pick us when

  • The workaround has become the job
  • Your process is the thing customers buy
  • You need to read from equipment, sensors or legacy systems
  • A regulator dictates a format no product supports

Look elsewhere when

  • A product already fits your process
  • The integrations you need already exist as connectors
  • You can live with the vendor data model and reports
  • Nobody on your team would need retraining anyway
What we build

Four kinds of build, each tied to something we shipped

Custom software, by the work behind it
Product from scratchTwo apps, free and premium, from one shared codebase for Hydrajaws.
Enterprise systemsA school data platform that replaced one that could not carry its volumes.
Rebuilds and rescuesTwo of our largest engagements began as recoveries of another vendor work.
Data migrationYears of sensitive records moved by a dedicated team, with none lost.

Web and mobile builds sit inside these four. We start every rescue by reading the code.

How the work runs

You see working software from week five

Two-week sprints with a demo at the end of each
Week 1

Scoping

The process, the integrations and the constraints. You get the build order, the cost band and the buy or build call.

Weeks 2 to 4

Architecture and design

Data model, stack and interface, with a clickable prototype before production code.

Week 5 onwards

Build in sprints

A demo every two weeks. You change priorities between sprints, with no change request.

After launch

Support and handover

A warranty period, then a support plan or a full handover of code and documentation.

A focused first version takes 3 to 6 months. A large enterprise system takes 9 to 18 months or more.

Technologies

What the builds run on

Each item comes from something we shipped. Select one to see when we pick it.

Builds

Two builds that no product covered

Hydrajaws safety testing app built by Dev Station
Case study, United Kingdom

The app that reads the tester, so the engineer never copies the dial

The old app was poorly documented and the client did not control the code. We rebuilt it as two apps behind Azure AD B2C and integrated the KTC SDK, so torque and pull readings land in the record as measured.

500%Rise in potential clients after launch
National education analytics platform rebuilt by Dev Station
Case study, Norway

Replacing a school data platform without losing a record

The old system could not handle its volumes or meet current security standards. We rebuilt it module by module and put a separate team on migration alone.

ZeroRecords lost in the migration

Tell us what you are trying to build

Three fields. An engineer reads it, and you get a reply within one working day.

  • We map the problem on a 30-minute call
  • You get a build order, a cost band and a buy or build call
  • No obligation, and no phone number needed to start
FAQs

Questions we get on the first call

Is custom software more expensive than buying a product?

Upfront, almost always yes. Over a few years it often is not, once you count licences across your headcount, workarounds and integrations you pay for separately. We tell you which side your case falls on, including when the answer is to buy.

How long does it take?

A focused first version takes 3 to 6 months. A large enterprise system takes 9 to 18 months or more. The scoping week gives you a real timeline for your build.

Who owns the code and the IP?

Your company, entirely, and the service agreement says so. Every engineer signs an NDA before getting repository access.

Can you work with our legacy systems?

Yes, and it is a common reason clients come to us. We have integrated ERP, MES and IoT systems, including ones with no modern interface, and migrated data out of systems past end of life.

Bring us the process nobody wants to own

The spreadsheet everyone depends on, the system two people know how to use, the report that takes a day to produce. Thirty minutes and you will know whether building is worth it.

Let's Talk