Fixed-scope project
A new app, a migration or a rebuild with a clear end. We agree screens, scope, price and dates after discovery, and bill by milestone.
Good for a first version, a website with a back office, a move to AWS.
Services
We build the systems a business runs on, host them properly and turn their data into reports people use. Most clients start with one of these and stay for the second.
01
We build the systems a business runs on: billing, HR, bookings, stock and customer portals. Web apps in Laravel, NestJS and React; phone apps in Flutter; desktop apps in Tauri that keep working when the internet drops and sync when it comes back.
02
We set up and run infrastructure on AWS and Cloudflare: build pipelines, containers, databases, backups, DNS and monitoring.
03
Most of the businesses we meet keep their numbers in spreadsheets or in an old system nobody wants to touch. We design the database, move the data across with checks at every step, and build the reports and dashboards that replace the monthly spreadsheet.
04
We add language models to products where they save real time: assistants that answer from a company’s own documents and cite them, tools that draft and check, and pipelines that turn a request into finished work. We use Claude, OpenAI and DeepSeek and keep the provider swappable.
Pick the one that fits the work. Many projects start fixed-scope and move to a support plan after launch.
A new app, a migration or a rebuild with a clear end. We agree screens, scope, price and dates after discovery, and bill by milestone.
Good for a first version, a website with a back office, a move to AWS.
A small team of engineers working on your product every week, on a monthly rate, with a two-week release rhythm.
Good for products that change every month and teams that need extra hands.
Hosting, monitoring, backups, security updates and a set number of hours for fixes each month, with an agreed response time.
Good for software that is live and needs looking after.
The same four stages for a two-month app and a year-long platform. Only the length of each changes.
We talk to the people who will use the software, map how the work happens today and list what must be true on launch day.
You get Written scope, screens for the main flows, a fixed price and a timeline
Screens for every page and state, checked with real users where we can, and a data model the reports will need later.
You get Clickable screens and a database plan you can keep
We ship to a staging link every second week. You test it, we fix what you find, and the next release starts.
You get Working software, tests, and notes on what changed
We move data across, train the people who will use it and stay on call for the first weeks. Then the support plan takes over.
You get A live system on your accounts, documentation and handover
The rules every project follows, whatever its size.
No change reaches the main branch without a second engineer reading it.
Business rules such as billing, payroll and permissions have tests that run on every push.
Build, test and deploy run the same way each time, on GitLab, GitHub Actions or AWS CodeBuild.
Every release runs on a staging copy first, with realistic data.
Keys live in AWS Systems Manager or Cloudflare secrets, with least-privilege access.
Nightly backups, and a restore we have actually tried.
Repositories, cloud accounts and domains are in your name from the start.
How to run it, how to deploy it, and where everything lives.